|
This is version 0.4. We're ahead of what I had originally planned, as far as the base code. With this version, we're spinning off an odd-minor-numbered development release (just like the Linux kernel versioning). (Optionally, you may have the 0.5x development release, in which case you're way ahead of the game.)
In this version, there has been some optimization done on memory usage, but the present system of passing arguments to modules needs a bit of work. We're already designing a better system of abstraction and representation of the various output documents -- it's object oriented. Time to put all of those books to good use. The document objects will be held in a hierarchical tree structure, indexed by their place in the output system and linked to each other. They'll also inherit properties from their parents. Buzzword city!
The next version still needs more modules, but the basic ideas are fairly good and the API (for lack of a better term) is solid. Figuring out how to break the One Big Program up into various little modules (actual Perl Modules, not QDMerge 'modules', that is) will take some work. Also, there are a few spots that need documentation and clarity touchups.
Version 1.0 should have piles of modules and clean code and lots of extensibility options and should be secure if you're careful about which modules you add.
After that... hmm... maybe I'll add another Perl program which opens a module, builds a web-page form out of it, and lets people who don't want to use tokens in a text editor to use the program. Maybe Geocities will license the technology for lots of money. (Yeah, right. That'll probably violate my license.)
That's my plan so far. As you can see, I have some fuzzy ideas for the future and just a few concrete ideas for the present. The biggest need is for you to use the program, figure out what kind of modules you want to see, and then write them or convince someone to write them for you!
|