Just wanted to get some opinions/preferences from the group: 1 - When I move all of the stuff from "core" into "org.jsynthlib", how should it be organized? I'm planning all of the "*ConfigPanel" stuff moving into org.jsynthlib.config, and probably all of "*Widget" going into org.jsynthlib.widget. Things like Base64 and XMLFileUtils probably going into org.jsynthlib.utils. There's a lot more stuff, however, that needs a home. Any suggestions for further categorization are welcome. I'm thinking that we might also want a dedicated package for the classes which the synthdrivers use for superclasses (ie, PatchEditorFrame, LibraryFrame, BankEditorFrame, etc.). I've come across some synthdrivers which were subclassing some fairly strange frames... possibly because they were the first ones that they came across which seemed like they'd work or something.
2 - Some of the classes have their *type* implied in the name. For example, there's an abstract class called "AbstractLibraryFrame" and there are some interfaces called "IDriver" and "IBankPatch". These aren't really the way the base Java libraries do it and, personally, I find it confusing (I keep asking myself "What the heck is an 'abstract library'?"). My preference would be to rename AbstractLibraryFrame to just LibraryFrame, and IDriver to just Driver, etc. Any objections? - Joe ------------------------------------------------------------------------------ Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ _______________________________________________ Jsynthlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
