Re: [Springframework-rcp-dev] [Desktop]Evolution or ?

[Jan H. <jh...@sc...>]

I would consider the Spring Desktop as a separate branch. An application
that is already deployed with Spring RCP should (in my opinion) not jump
onto Spring Desktop yet. At our company, a number of products are using
Spring RCP, these will continue to use RCP until Desktop has become
stable and at that moment we will need a clear updating path from one to
the other. I expect such a path will be documented along the way.

On the other hand, if you're starting to look for a gui framework and
want to lend a hand, this is the right opportunity to jump in.

The sparse time I've got right now will be dedicated to the maintenance
release of Spring RCP. I'll try to fix a number of issues and will scan
the jira to see which one's are appropriate to include in the next
release.

Kind Regards,
Jan

On Tue, 2008-07-08 at 23:35 +0100, Benoit Xhenseval wrote:
> Hi
> 
>  
> 
> I can see a lot of activity wrt Spring Desktop. This is great but…
> what is the plan? Should an existing Spring Rich Client application
> follow the development of Desktop (ie checkout regularly) or should
> Desktop be considered as another branch (assuming the previous one was
> tagged?) which is not backward compatible?
> 
>  
> 
> In a few words, what is the migration strategy for existing app?
> 
>  
> 
> I’d like to know before doing an update and then ending up is a %*£”$^
> %!!…
> 
>  
> 
> Many thanks
> 
>  
> 
> Benoit
> 
>  
> 
> PS: Could you consider the few patches we provided to make Spring RC
> more flexible before making a lot of changes?  They are truly minor
> for the code base but big for us! Thanks!
> 
>  
> 
> ------------------------------
> 
> IMPORTANT NOTICE 
> 
> This communication contains information that is considered
> confidential and may also be privileged . It is for the exclusive use
> of the intended recipient(s). If you are not the intended recipient(s)
> please note that any form of distribution, copying or use of this
> communication or the information in it is strictly prohibited and may
> be unlawful. If you have received this communication in error please
> return it to the sender and delete the original.
> 
>  
> 
> 
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________ Springframework-rcp-dev mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-rcp-dev


 **** DISCLAIMER ****
 http://www.schaubroeck.be/maildisclaimer.htm