|
From: Larry S. <lst...@au...> - 2008-07-08 20:00:03
|
Peter De Bruycker wrote: > 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, ... I'm still unclear on how we do this without an explosion of XML or intermediate factories, lots of boilerplate (including additional members on objects), or some other nasty artifact that makes the platform difficult to use. Maybe I missed how this was to be done in the earlier email exchange, or I'm just being dense. Could you please elucidate how we get rid of the service locator and keep the solution simple to implement even with dynamic objects? > > 3. osgi support > > First make sure we have something working, then see what we can do to > improve? Do you mean to get the basic modularity cleaned up first and then look at OSGi, or do you mean get OSGi working right away? > > > 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 Good to see things getting ramped up! Thanks, Larry. |