Is the code en essential part for the core? How is it used (or will be used)? I would suggest that we take into account the modularity of the package, and if it is not mandatory for the core, we should put it in the plugin section. Sergiu On 1/9/07, Ludovic Dubost <[email protected]> wrote:
Hi,
I'm in the process of finishing an XWiki Google Web Toolkit API (server-side and client-side). I'd like to commit that one in the core including the Java code that is compiled to Javascript. There is common code for both. Curriki will also rely on this API. It is not necessary that the build system compiles the code to Javascript for the moment, however it is needed to compile the server code.
Currently I suggest commiting the code in:
web/standard/src/main/java/api or web/standard/src/main/java/com.xpn.xwiki.gwt.api
I also have a Google Web Toolkit client for the FeedPlugin. It's a very cool RSS Aggregator interface. It's only client side code. I'm not sure if it should be commit in the core. If it is it would be in
web/standard/src/main/java/rssreader or web/standard/src/main/java/com.xpn.xwiki.gwt.reader
Can we vote for these 2 things:
- commit the API - commit the RSS Reader
Ludovic
-- Ludovic Dubost Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost AIM: nvludo Yahoo: ludovic
-- You receive this message as a subscriber of the [email protected] list. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws