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
Hi,
I think we need to say explicitely what browsers we're supporting on
wiki.org and then make sure we test with all those browsers when we make any
change.
So what's the list of browsers we want to support?
I think the minimal list is:
* IE6
* FF 1.5
* FF 2.0
Do we want to officially support more? (with the available
committers/contributors we have of course - Otherwise we could support all
the browsers on earth :-)).
Note: this doesn't mean it won't work with other browsers. It means it's not
guaranteed it'll work and shouldn't be considered a bug when it doesn't.
Thanks
-Vincent
___________________________________________________________________________
D�couvrez une nouvelle fa�on d'obtenir des r�ponses � toutes vos questions !
Profitez des connaissances, des opinions et des exp�riences des internautes sur Yahoo! Questions/R�ponses
http://fr.answers.yahoo.com
Hi everyone,
We're happy to announce the 1.0 Beta 2 release. It's mostly a bug fix
release but it also contains some new improvements such as new macros.
* Lots of bugs fixed. Most of them are bugs related to the WYSIWYG editor
and the new 1.0 skin.
* Simplified Edit menu with only a single menu entry. This is to make it
simpler for new users. It's possible to switch between Simple and Advanced
from the user profile page.
* New #info("This is some useful information"), #warning("Careful not to
break something") and #error("You did something terrible") macros.
* New #floatingbox() macro to display a floating box (aligned right by
default).
* __text__ is now the notation for underline
* Lots of other minor improvements
Full list: http://tinyurl.com/yz9ccw
Thanks and enjoy
-The XWiki Team
___________________________________________________________________________
D�couvrez une nouvelle fa�on d'obtenir des r�ponses � toutes vos questions !
Profitez des connaissances, des opinions et des exp�riences des internautes sur Yahoo! Questions/R�ponses
http://fr.answers.yahoo.com
Hi everyone,
I patched the Navigation panel in the new skin to display page titles
instead of the page name if a page title exists. If this is useful
please included it in the standard skin.
Cheers,
--
Luis Arias
http://www.xwiki.com
+33 6 14 20 87 93
skype : kaaloo
Hi,
I'm calling a code freeze on 1.0 Beta 2. This means:
* I've created a XWIKI_1_0_BETA_2 branch. All code for Beta 2 must now go
there
* No new code should be submitted for beta 2 unless:
- this code fixes a regression from b1
- this code fixes a bug introduced in b2
* Any code checked in on the beta 2 branch MUST also be merged immediately
on trunk (The beta 2 branch will be removed once we tag the Beta 2)
* People working on beta 3 must commit on trunk
The next step is for me to build beta 2 from the branch and try it out to
see if there's no glaring error. I'd like help from as many developers or
users as possible. Let me know if you're interested in helping out for
testing the beta2 release.
Thanks
-Vincent
___________________________________________________________________________
Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire.
http://fr.mail.yahoo.com
I try to get into maven to build xwiki but I don't find any doc on xwiki.org.
When I checked out xwiki/trunk as a project in eclipse and I enable the maven2
plugin, it starts downloading a bunch of stuff and it complains about 2 items
(see log below). Is that normal? Did I checked out everything I need?
Is everybody using maven2 or ant or something else?
A few pointers would be nice. Thanks.
(I still wonder why it has to download stuff since everything is available in
the svn repository. Actually it would be a good idea to keep the libraries
aside, in another folder, if they have to be re-used in different places but
then why keeping them in the repository as well?)
**********************************
(...)
1/2/07 4:59:04 PM EST: [WARN] Unable to get resource from repository xwiki
(http://maven.xwiki.org)
1/2/07 4:59:05 PM EST: [WARN] Unable to get resource from repository xwiki
(http://maven.xwiki.org)
1/2/07 4:59:05 PM EST: Failed to run generate source goals /xwiki -
trunk/wikis/default/pom.xml Missing:
----------
1) com.xpn.xwiki:xwiki-build-xar-handlers:jar:1.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn
install:install-file -DgroupId=com.xpn.xwiki -DartifactId=xwiki-build-xar-handlers
\
-Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) com.xpn.xwiki:xwiki-wiki-default:xar:1.0-SNAPSHOT
2) com.xpn.xwiki:xwiki-build-xar-handlers:jar:1.0-SNAPSHOT
----------
1 required artifact is missing.
for artifact:
com.xpn.xwiki:xwiki-wiki-default:xar:1.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
xwiki (http://maven.xwiki.org)
*************************************
Hi,
I think we need to improve the way we update the documentation. Right now I
see several issues are marked as closed even though we haven't documented
them. Typical examples include new macros. They should be documented on
xwiki.org before we close the issue IMO. At the very least if for some good
reason we cannot do it immediately at least a new issue for documenting them
should be created at the same time so that it's not forgotten and so that
it's implemented in the future.
Nobody likes documenting stuff so my belief is that someone who does
something must do it completely, i.e. design, implement, *document* and
support.
WDYT?
Thanks
-Vincent
___________________________________________________________________________
D�couvrez une nouvelle fa�on d'obtenir des r�ponses � toutes vos questions !
Profitez des connaissances, des opinions et des exp�riences des internautes sur Yahoo! Questions/R�ponses
http://fr.answers.yahoo.com