Plume Creator is alive
Hello everyone !
Nearly three years ago, I started writing a little software to help me organize my own stories. With the help and suggestions of fellow novelists like Ken MacConnell (see http://ken-mcconnell.com ), features were added and the look-and-feel improved greatly.
One year ago, the team felt a change was needed, and "Plume 2.0" was born on paper. Here are a few ideas of improvements among others :
- allowing the use of plugins
- adding a "binder" (a sort of wiki) to jot down ideas about places, characters, spaceships...
- writing comments
- insertion of images
The development of this little software takes a lot of time and help is always welcome. If you know Python 3 and you are interested in coding, debugging... Feel free to contact me at
You can follow the advancement of the development in https://github.com/jacquetc/plume-creator/tree/develop
For those more technically inclined, not one line of code was used from the old Plume. The reason is simple : I switched from C++ / Qt to Python 3 / pyQt . Also, I'm separating concerns (data, core, gui), like in a MVC pattern. Moreover, plugins will be heavily used (I already coded two of them).
I give you an idea of what look Plume will have ultimately :
The priority is to import an old Plume project without any loss of data. So, the new Plume must feature a minimum before being usable.
Plume Creator v 0.67 very soon
The development of Plume Creator is always active ! The next release will be v 0.67. It will also be the last of this series. As you must know, some future improvements are sometimes easier to code on a brand new software.
Our team of contributors have agreed to make major changes to Plume.
For one, project files will be easily accessible by the user. No more one-file projects. The users of Dropbox or a Version control system will like this. Also, he will be able to open and edit a text in its favourite software.
We will drop the html format for the text, adopting a simplified txt2tags format. If you know BBCode and Markdown, they are in the same family of "Lighweight markup languages".
Lastly, I'll publish a roadmap. So, if someone want to help in the development, he knows where we go.