[Publex-developers] Latest updates

[Jason S. <jns...@gm...>]

So far, the project has had quite a bit added to it.  I will try to cover
the important points here, but I'm sure I'll forget something.

* PubleXCore Project - This project will handle the inner workings of
PubleX.  It encapsulates the plugin manager, DOM interfaces, an incomplete
build manager for publishing, and several services that manage file and path
manipulation, logging, application-to-user messaging, property management,
string parsing, and resource management.
* Security - This project contains much from the SharpZipLib with several
features added.  The Blowfish encryption algorithm has been added, as well
as a customized version of Blowfish of my own that makes use of key
strengthening and stream compression using BZip2.  A newer version of the
library that Security is based upon also contains unfinished code that will
handle creation and reading of ISO images and Microsoft CAB files.
* PubleXImageLib - This library will manage the images used for toolbars,
menus, icons, and other general image resources for PubleX.
* XmlEditor - This library is LARGELY incomplete.  It is the primary reason
why the PubleXCore library has been created.  Once finished, this library
will handle the parsing and display of XML files.

Of particular note, while implementing PubleXCore, I have found various
useful functions to track program options through the Property classes.
These classes are used heavily within PubleXCore, and can easily be exposed
within PubleX.  The LoggingService is also something that can easily be
exposed from within PubleX.  This service handles dumping errors, warnings,
information, and debugging info to a formatted HTML file that can be viewed
as-is in a browser. It can also be sent to the developers for debugging
purposes.

The resource manager isn't 100% compliant to our project, but works as-is
nonetheless.  PubleX can be modified slightly to make use of this service so
that we can fully support the multi-language interface and make PubleX as
professional and muli-lingual as possible.  The resources can also be in the
form of settings, along with the use of the PropertyService.

The Build class is more-or-less empty at this point.  This class will be
responsible for calling delegates within PubleX itself in order to build
(publish) single XML files or multiple files.  This can come in handy for
both "building" the sub-version package that gets sent back to the server
after editing, as well as publishing an entire project into one of the
supported formats.  Most of the work will be done within PubleX, but the
Build class will allow the PubleXCore library to call these functions so
that there is some type of order maintained during this process.

The PluginTree manages the loading and exposition of plugins for PubleX.
The design is much more in-depth that the one previously used.  It might be
worth while to read the Plugin codes to gain a complete understanding of the
functions performed by this section of the library.

As of this time, the project does not compile.  Several features within
PubleXCore must be completed before this can happen.  PubleXCore is the
pivotal point behind the entire project.  Without a functional core, the
rest is useless.