Re: [Springframework-developer] Road map

[Colin S. <col...@ex...>]

I'll be writing a number of tools to support some people here in code 
manipulation and debuggin, but I'm not sure exactly how much actual UI 
there'll be. A fair number of them may be command-line or with simple 
UIs, so at this point it's not a given that I'll need any sort of 
complicated library. I'll probably be starting in about 3-4 weeks.

As for Eclipse, I've used it for ages, but on the programming side I'm 
actually a complete neophyte, although I'm itching to get into the RCP stuff

Keith Donald wrote:

>Colin,
>
>When do you think you'll be moving to the client-side?  It'd be great to
>work together.  I have a similiar requirement: I need RCP in my current
>project, so I will be nicely aligned for developing the module over the
>coming months.  It would be great if you could be an early adopter and
>developer at the same time...
>
>If you decide to go Eclipse RCP that would be good, too.  The main upside I
>think we can offer is better Swing support (Swing is more mature than SWT,
>and obviously a standard) and a nice integration with the rest of Spring.
>But having an Eclipse expert would be invaluable for improving our platform
>capabilities.  I'd also be interested in seeing if there are ways we can
>integrate with the Eclipse effort as it matures, too.
>
>Keith
>
>----- Original Message ----- 
>From: "Colin Sampaleanu" <col...@ex...>
>To: <spr...@li...>
>Sent: Wednesday, March 31, 2004 5:20 PM
>Subject: Re: [Springframework-developer] Road map
>
>
>  
>
>>Actually it's looking like I may be doing some client-side work (as
>>opposed to the mostly back-end/web stuff I am doing now), so I may get
>>involved. Haven't decided if I want to do the stuff in Swing or Eclipse
>>RCP though...
>>
>>
>>Keith Donald wrote:
>>
>>    
>>
>>>Just like to add to the pot here regarding spring-rcp (especially since
>>>      
>>>
>work
>  
>
>>>is picking back up now):
>>>
>>>- I'd like to target the first 1.0 RCP release candidate along side
>>>      
>>>
>Spring
>  
>
>>>1.1 final this summer.
>>>
>>>We plan to include in the distribution a sample application demonstrating
>>>the features of the platform (likely a port of the PetClinic or Thomas's
>>>Beer app, adding RCP value like 'quick' sorting/filtering and as-you-type
>>>field validation.)  I am hopeful by the first release we'll have several
>>>articles lined up, too (I know several people interested in rich client
>>>      
>>>
>dev
>  
>
>>>have expressed interest in helping out there!)
>>>
>>>Thanks,
>>>Keith
>>>
>>>
>>>-----Original Message-----
>>>From: spr...@li...
>>>[mailto:spr...@li...] On Behalf
>>>      
>>>
>Of
>  
>
>>>jürgen höller [werk3AT]
>>>Sent: Wednesday, March 31, 2004 9:44 AM
>>>To: spr...@li...
>>>Subject: Re: [Springframework-developer] Road map
>>>
>>>
>>>Good point regarding scheduling 1.1.1. I've intended to fill in a
>>>placeholder to make the gap to 1.2 RC1 seem less large ;-) I completely
>>>agree that we shouldn't schedule such point releases in an official
>>>      
>>>
>release
>  
>
>>>plan.
>>>
>>>If we manage to get JSF and/or Portlet support done in time for 1.1, then
>>>I'm all for including it earlier. I'd like to release 1.1 final by the
>>>      
>>>
>end
>  
>
>>>of August, though; I don't want to delay it for further features.
>>>
>>>Juergen
>>>
>>>
>>>-----Original Message-----
>>>From: spr...@li...
>>>[mailto:spr...@li...]On Behalf
>>>      
>>>
>Of
>  
>
>>>Rod Johnson
>>>Sent: Wednesday, March 31, 2004 2:41 PM
>>>To: spr...@li...
>>>Subject: Re: [Springframework-developer] Road map
>>>
>>>
>>>Some comments:
>>>
>>>Spring 1.0.x: doc polishing, bugfixing, minor enhancements
>>>- 1.0.1: early April
>>>- 1.0.2: late May
>>>
>>>Spring 1.1.x: JMS support, JMX support, declarative validation
>>>[RJ: pointcut expression language (AOP), JSR-175 preview? ]
>>>- 1.1 RC1: early July
>>>- 1.1 final: late August
>>>- 1.1.1: late September
>>>[RJ: why are we _scheduling_ a 1.1.1?]
>>>
>>>Spring 1.2.x: OGNL support, JCA support, enhanced RMI support
>>>- 1.2 RC1: early November
>>>- 1.2 final: late December
>>>
>>>Further issues are JSF and Portlet support. There is actually quite a bit
>>>      
>>>
>of
>  
>
>>>interest in these from various users/integrators; they are also important
>>>for us from a marketing perspective. I'm not keen on providing official
>>>support before 1.2, though.
>>>
>>>[RJ: depends on what's involved. I'd be keen to have JSF support sooner
>>>rather than later if it's straightforward. I'm going to be looking at
>>>      
>>>
>that
>  
>
>>>soon. Portlets I think are more of a niche interest. ]
>>>
>>>Regards,
>>>Juergen
>>>      
>>>