Hi all,
I'd like to just quickly post some of my ideas for the jEdit syntax
package moving forward.
First, I should introduce myself. I'm the chief architect and lead
developer for the dbXML Group, which is the sponsoring company behind
the dbXML Project. dbXML is an Apache licensed native XML database
written in Java. Beyond architecting and writing the core database,
I've also done quite a bit of GUI development. Some of that includes
the GUI for dbXML Professional (CommercialWare), a product that includes
the jEdit Syntax package.
My overall goal is to guide the development of the syntax package in the
direction of being a very customizable standalone JavaBean. Where jEdit
has a definite look and feel to it, a JavaBean needs to be flexible
enough to accommodate the needs of the developers that use it, and
should be able to easily adopt the look and feel of the application that
it's being embedded into.
At the same time, I want to keep the underlying behavior and
functionality of both jEdit and the syntax package as common as
possible, unless it is absolutely necessary to deviate from this. This
will be possible partly through the generous donation of code from the
jEdit developers.
In order to accomplish the level of customization and flexibility that
developers will need in the jEdit Syntax package, I'll need both
feedback to drive the feature set, and help to develop the
functionality. So if you'd like to contribute either code or feedback,
I'd very much like to hear from you.
Thanks,
Tom
|
