Re: [Spring Desktop] ideas for the Desktop version

Finally,

I've gotten my newsreader to work (again, thanks to Jetbrains :))

So I'll repeat here what I've put on the forum.

1. Merge some modules

- support + core + forms + binding + jdk5 = core
- retain modules jdk6, sandbox and resources

Perhaps we should also merge resources with the core, but only those resources
directly needed in the core. The rest can be more something like 'skinning'.

I know this is quite controversial, but now we have the situation where no
one knows where something should be put, so it ends up in support. Modules
should also be selfcontained, no point in having a module that needs another
module anyhow for it to work.

My suggestion:

Core = essential Desktop stuff needed to make a simple application (forms,
basic binders and all underlying plumbing)
JDK6 = JDK6 specific stuff
Sandbox = playground for new stuff, should be followed-up on a regular basis
though
Resources = extra resources (do we need to have this in Desktop?)
Components = extra components (Jan, perhaps we can put your components in
here?)

2. Pull up the source level to 1.5

Java5 will give us a lot more leniency when dealing with some problems. For
example, I'd like to introduce generics in the FormModel and ValueModel for
starters. I think they're great candidates and I don't think it'll be a lot
of work. Using enums in certain places may also increase readability.

3. Rename Binder to BindingFactory

Since we're not bound to the RCP codebase, we should finally do this...

4. A lot more out-of-the-box bindings

Bindings are the mainstay of the application. Therefor I find it more than
logical that we include more bindings in the standard Desktop.

5. Pull useful stuff from the sandbox

Now that we have the opportunity to do so, we should evaluate what's present
in the sandbox and promote it when useful.

6. Upgrade to Spring Security (Spring 2.5 in general)

Spring 2.5 gives us the possibility to do a lot more, so I think this makes
sense

7. Try to refactor out the singletons like Application and ApplicationServices

We might be able to replace those with the Spring 2.5 @Component and @Autowired
system...

8. Remove VLDocking

It has a GPL license, so it's not compatible with Desktop (unless someone
wants to release Desktop under the GPL?)

Some stuff that has come up on the forums:

1. Modular plugin support (jwray)

OSGi-like support for plugins. Personally not my favorite, I don't know many
enterprise applications that use a plugin model, but I might be wrong about
this.

2. JIDE integration (jwray)

Great idea to include JIDE OSS into Desktop. It's a great collection of components
and making binders for those components will raise the quality of the code.
For commercial JIDE components, we can foresee a separate module, if needed.

3. Integrate mydoggy as a docking framework (peatar)

Looking into it, I've gotten the code from peatar, if I find the time I'll
do a thorough test.

4. Replace commons-logging with slf4j (peatar)

Anyone that can make a clear pro-con analysis on this. I've only worked with
commons-logging.

5. Logger injection (peatar)

PicoContainer has a LogInjector, do know though if this should be a Desktop
feature... Sounds more like Spring-core... Perhaps this already exists in
2.5, I don't know.


Feel free to comment, flame and add suggestions...

Greetz,

Lieven




-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Springframework-rcp-dev mailing list
Springframework-rcp-dev@...
https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev