Re: JavaRpc code modularity

Hi Fabian,

mid-air collision of eMails :-)

Am 19.03.2009 um 09:50 schrieb Fabian Jakobs:

> I would suggest you get in contact with the author Andreas Junghans
> <andreas.junghans@...> and coordinate your efforts.  I would
> prefer  you work inside of the JavaRpc contrib rather than creating a
> new contrib with a different name. You could tag the current version
> with a version number in SVN so others, who depend on the old API can
> still find it and do the changes in the JavaRpc trunk.

The reason I suggested a new contrib was to avoid confusion. I think  
many developers are using the qooxdoo trunk (and presumably the  
qooxdoo-contrib trunk), so a refactoring/rewrite is safer in a  
separate code path IMHO (which can also be an SVN branch of course).  
As soon as the changes are somewhat stable, they could be merged back  
to trunk.

But anyway, the most important thing is to get a decently maintained  
Java RPC backend, and if creating a branch or a new qooxdoo-contrib  
project is deemed too complicated, then just go ahead and use the trunk.

Regards,

   Andreas


------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel