|
From: Jan H. <jh...@sc...> - 2008-03-05 10:58:54
|
> 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? We would prefer narrowing the scope to provide a solid release instead of migrating bags of code to have all the features in a so-so state. We also want to align the code with the current technologies and have a modular approach from the start. This doesn't mean that we won't to port any code at all but that it should be reviewed as thoroughly as possible and with a clean view. > > 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). You could look upon the Spring Desktop as a new project with a lot of influence from Spring Richclient. We don't want to have all the bagage of the current codebase and have our hands tied. This is the moment to fix things at the core where needed. So there will probably be a lot of changes, but I can't predict the future and put a number on how much of a change it will be. A few remarks if you're using Spring Richclient now: - I too am using the current framework in several products, so I'll be thinking of the migration issue as well. I would like to have a migration guide between the two as our company will have to make this step too. - current codebase is not going to abandoned, maintenance will continue during the development of the new project as needed - packages/modules will probably be renamed I'll collect any concerns/remarks that are made so that these won't get lost. Thanks for sharing yours. Kind Regards, Jan **** DISCLAIMER **** http://www.schaubroeck.be/maildisclaimer.htm |