Re: [Springframework-rcp-dev] [Spring Desktop] ideas for theDesktop version

[Peter De B. <pet...@gm...>]

On Tue, Jun 24, 2008 at 9:19 AM, Lieven Doclo <lie...@ji...>
wrote:

> Hello Peter,
>
> Thanks for the input. As for the Beans Binding, we could take a look at
> that
> indeed. Haven't work with the framework yet, but it looks nice. As for
> complexity,
> I'm not entirely sure whether it'll be an improvement, but we'll have to
> find that out, won't we?
>
> As as for the commons-logging, I agree. But it was an idea on the forums,
> and slf4j can indeed do a bit more than commons-logging. But most of us (I
> think) work with commons-logging. Correct me if I'm wrong.
>
> What custom elements do you have in mind? I see a number of candidates :).
>
> As for the GPL/ASL issue, I think it's backwards, can a ASL project
> (Desktop)
> contain GPL jars (VLDocking) ? I don't think so, unless your project is
> also
> GPL. I'm no fan of the GPL license, so I still don't think we should
> provide
> it. We could put it in a separate module, but I'm afraid this'll cause
> confusion
> with the end-users: 'if I use Desktop with this module, I need to be GPL,
> otherwise I don't'...


I meant a complete separate project (hosted somewhere else, on
dev.java.netof sourceforge), that is gpl licensed. That way we don't
have to worry about
licensing, and can leave the choice to the end-user.


>
>
> With your reply, I've got some more ideas:
>
> 9. Remove the closures in RCP (sorry Keith)
>
> As Keith said to me on SpringOne: SIMPLIFY, SIMPLIFY!! Keith's closures
> were
> a great idea (bit over the top though), but I don't think anyone is using
> them. They're easily refactored out of the codebase thanks to some Java5
> improvemenrs and for the sake of readability, I think we're better of
> without
> the code. So I think we should drop that part of the code.
>
> 10. Implement custom namespace elements for Spring configuration
>
> This can simplify the configuration greatly. We could also create Spring
> 2.5 component stereotype annotations for easy configuration using
> <context:component-scan/>.
>

this is what I meant with "custom elements"

candidates:

- java.util.Preferences instances in beans

something like this:

<bean id="someBean" class="foobar">
    <property name="prefs">
        <desktop:prefs scope="user|system" path="path/to/preferences/node"/>
    </property>
</bean>

- view descriptors

<desktop:view id="someView" viewClass="com.acme.foo.bar.SomeView">
    <property name="someService" ref="serviceId"/>
</desktop:view>

<desktop:view id="otherView" viewClass="com.acme.foo.bar.OtherView"
mdi:closable="true" mdi:resizable="false">
    <property name="someService" ref="serviceId"/>
</desktop:view>

<desktop:view id="yetAnotherView"
viewClass="com.acme.foo.bar.YetAnotherView" docking:closable="false"
docking:draggable="true">
    <property name="someService" ref="serviceId"/>
</desktop:view>

this would allow for shorter xml that's more readable

I'm sure there are a lot more possibilities!

I think we need much closer integration with spring itself (xml support,
custom bean scopes, ...)



>
> WDYT?
>
> 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
> > Spr...@li...
> > https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev
>
>
>
>
> -------------------------------------------------------------------------
> 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
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev
>