|
From: Rogan D. <ro...@da...> - 2008-03-05 10:14:43
|
Jan Hoskens wrote: > Hi, > > As you may know, we had planned to have a Spring Richclient 1.0 release > somewhere at the end of Januari. It's March already and no release has > been pushed out. Don't start to panic just yet, I'll let you in on the > details. > > Somewhere in Januari I contacted the people of SpringSource to discuss > the position of Spring Richclient within the Spring universe. As we're > in different parts of the world, it takes some time to schedule a > meeting online and contact the right people, thus time was creeping past > the previously set release date. Our goal with this meetings was to not > only discuss the present and future of the project but also the > involvement of SpringSource. The outcome is the following. > > Current codebase: > > We have set a new target date for the release: March 17. All bugs should > be fixed while documentation will be provided as needed. We don't want > this to delay the release date anymore and interfere with our future > plans. If documentation is requested at some point, we'll provide this > on the developer blog. This release will have maintenance updates as > requested. > > Future plans: > > We've decided to start a new codebase and re-brand the project to Spring > Desktop. One of the reasons behind this is the possibility to update the > existing core techniques after some research. The current codebase core > is about two years old, quite stable but not state-of-the-art anymore. > Another reason is that this allows us to start with the modularity in > mind and review the existing codebase. In order to get something usable by October, I assume that the plan is to migrate a lot of the existing code from Spring RCP? Any thoughts on how folks should migrate their applications? i.e. how much change to you expect to see between the current (1.0) RCP and the future Desktop? Do you intend to create a whole new package structure (e.g. org.springframework.desktop)? That will obviously mean a fair amount of work for people moving over (unless the actual class names stay the same, then maybe the IDE's can resolve them automatically). Regards, Rogan |