|
From: Peter De B. <pet...@gm...> - 2008-07-08 12:40:25
|
2nd attempt: Can we reach a consensus here? I think we need to go as fast as possible, to keep the momentum going... 1. code organization: - core - application: window, dialogs, page, view, action, ... - binding: validation, binding, forms - resources 2. singleton/service locator: Get rid of it by clever use of custom xml, component scanning + autowiring, convention over configuration, simpler object structures, ... 3. osgi support First make sure we have something working, then see what we can do to improve? Again: I think we need to go fast, so we have something working as soon as possible. I already started on work on the application infrastructure code (window, page, pagecomponent, view, editor) that will allow for much simpler (and less) xml, multiple view instances at the same time (formerly known as editors) and easier integration possibilities with 3rd party component providers (i.e. Jide, SwingDocking, ...), and I expect to be able to check them in this week. If you have questions/remarks/suggestions on these parts of the framework, don't hesitate to give me a nudge! regards, Peter |