Hi devs,
We have planned the GWT 1.4 upgrade for the next XWatch milestone at the
end of march. For this, we need to make a decision regarding the web-gwt
dependencies (for the moment, the xwiki gwt dialogs rely on the gwt-tk
library that does not yet have a release for gwt 1.4) so we must choose
from:
- using another library to provide this functionality, particularly the
MyGwt library
pros: nice looks and good API + the possibility of using the library
components in including projects.
cons: code changes required by the clean switch (updating all involved
classes to use library API instead of GWT API), the lack of a maven
repository with all available MyGwt versions (only 0.5.0 rc). As well,
while testing, I experienced a couple of rendering issues (caused,
seemingly by the use of the strict or xhtml DTD).
- using the native gwt modal dialogs introduced in 1.4:
pros: not styled (we totally control the styling process and can build an
uniform look); widgets consistency, at least at this level. A big
advantage is that the web-gwt module will not depend on any other library
anymore.
cons: not styled, the usual GWT API (which can be poor in some
situations); GWT also has some problems caused by the standard mode
interpretation in browsers (caused by the doctype declaration) but in
this situation the code seems to be stable.
What do you think?
Is the plan to provide a xwiki-enterprise-web1-1.3-rc1.war file on the
Xwiki Download page? When do you think this would be available? Would
it be better to pull it directly from svn? If I get it from svn how is
the RC1 release marked?
I noticed that you were looking at using GWT Html editor. Doesn't GWT
Html editor just wrap the FCKEditor? What is the advantage of using GWT
Html Editor instead of just using the FCKEditor?
Thanks
Glenn Everitt
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
Hi developers,
Do you have any "best pattern" that can be shared for XWiki integration to
J2EE platform? And where can i found any comprehensive documentation for
this?
Thanks & regards,
- iwan
_________________________________________________________________
Get your free suite of Windows Live services today!
http://www.get.live.com/wl/all
Hi,
Here's my proposal for internationalizing XWiki apps. The idea is to
propose several solutions for XWiki apps writers:
* Use case 1: I have lots of text on my page
- solution: use XWiki's mechanism for translating page by creating
several editions of the page in the different languages
* Use case 2: I want translation resources for my application only
and I'd like to share resources between pages
- solution: use: $msg("mykey",
"MySpace.MyTranslationDocForThisApplication")
- MySpace.MyTranslationDocForThisApplication is a standard
document to which a XWiki.PropertiesClass object is attached
- It'll search first in that doc's PropertiesClass and if not
found in XWiki's registered document bundles and if not there in
XWiki's static resource bundle files
* Use case 3: I want translation resources only for a given page
- solution: use: $msg("mykey", $doc)
- You'll need to have attached a PropertieClass object to the page
where $msg is used
- It'll search first in that object and if not found in XWiki's
registered document bundles and if not there in XWiki's static
resource bundle files
* Use case 4: I want to have a global translation resources for all
my apps in the wiki
- solution: use: $msg("mykey")
- You'll need to have created ad registered resource bundle
documents in the Wiki preferences
- It'll search first in XWiki's registered document bundles and if
not there in XWiki's static resource bundle files
Implementation details:
* Add XWikiMessageTool.get(String, String) API
* Add XWiki.PropertiesClass class in XE in the Administration
Application + a class sheet for presenting the properties nicely
WDYT?
Thanks
-Vincent
Hi,
I have been building xwiki directly from source for past some time and
everything is going fine.
Very recently I tried to build xwiki-platform-web using the maven script
under pom.xml for the first time.
This got failed when building the standard module under web.
Here is the console output of the script:
Please tell me where I am going wrong.
Thanks and advance
Sachin
=============================================================================
[INFO] Scanning for projects...
[INFO]
----------------------------------------------------------------------------
[INFO] Building XWiki Platform - Web - Standard
[INFO] task-segment: [install]
[INFO]
----------------------------------------------------------------------------
[INFO] artifact org.apache.maven.plugins:maven-resources-plugin: checking
for updates from xwiki-plugins-externals
[INFO] artifact org.apache.maven.plugins:maven-resources-plugin: checking
for updates from xwiki-plugins-releases
[INFO] artifact org.apache.maven.plugins:maven-remote-resources-plugin:
checking for updates from xwiki-plugins-externals
[INFO] artifact org.apache.maven.plugins:maven-remote-resources-plugin:
checking for updates from xwiki-plugins-releases
[INFO] artifact org.apache.maven.plugins:maven-surefire-plugin: checking for
updates from xwiki-plugins-externals
[INFO] artifact org.apache.maven.plugins:maven-surefire-plugin: checking for
updates from xwiki-plugins-releases
[INFO] artifact org.apache.maven.plugins:maven-war-plugin: checking for
updates from xwiki-plugins-externals
[INFO] artifact org.apache.maven.plugins:maven-war-plugin: checking for
updates from xwiki-plugins-releases
[INFO] artifact org.apache.maven.plugins:maven-install-plugin: checking for
updates from xwiki-plugins-externals
[INFO] artifact org.apache.maven.plugins:maven-install-plugin: checking for
updates from xwiki-plugins-releases
[INFO] resources:resources
[INFO] Using default encoding to copy filtered resources.
[INFO] snapshot com.xpn.xwiki.platform:xwiki-core-parent:1.3-SNAPSHOT:
checking for updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki:9-SNAPSHOT: checking for
updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki-core-parent:1.3-SNAPSHOT:
checking for updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki:9-SNAPSHOT: checking for
updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki-web-gwt:1.3-SNAPSHOT: checking
for updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki-web:1.3-SNAPSHOT: checking for
updates from gwt-maven
[INFO] snapshot com.xpn.xwiki.platform:xwiki-web:1.3-SNAPSHOT: checking for
updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki:8-SNAPSHOT: checking for
updates from gwt-maven
[INFO] snapshot com.xpn.xwiki.platform:xwiki:8-SNAPSHOT: checking for
updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki:8-SNAPSHOT: checking for
updates from xwiki-snapshots
[WARN] Cannot find parent POM: com.xpn.xwiki.platform:xwiki::8-SNAPSHOT for
child: [inherited]:xwiki-web:pom:1.3-SNAPSHOT. Using stub model instead.
[INFO] snapshot org.xwiki.platform:xwiki-core-plexus:1.3-SNAPSHOT: checking
for updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki-core-parent:1.3-SNAPSHOT:
checking for updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki:9-SNAPSHOT: checking for
updates from xwiki-externals
[INFO] snapshot org.xwiki.platform:xwiki-core-container-api:1.3-SNAPSHOT:
checking for updates from xwiki-externals
[INFO] snapshot
org.xwiki.platform:xwiki-core-containers-parent:1.3-SNAPSHOT: checking for
updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki-core-parent:1.3-SNAPSHOT:
checking for updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki:9-SNAPSHOT: checking for
updates from xwiki-externals
[INFO] snapshot org.xwiki.platform:xwiki-core-url:1.3-SNAPSHOT: checking for
updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki-core-parent:1.3-SNAPSHOT:
checking for updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki:9-SNAPSHOT: checking for
updates from xwiki-externals
[INFO] snapshot
org.xwiki.platform:xwiki-core-container-servlet:1.3-SNAPSHOT: checking for
updates from xwiki-externals
[INFO] snapshot
org.xwiki.platform:xwiki-core-containers-parent:1.3-SNAPSHOT: checking for
updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki-core-parent:1.3-SNAPSHOT:
checking for updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki:9-SNAPSHOT: checking for
updates from xwiki-externals
[INFO] snapshot org.xwiki.platform:xwiki-core-action:1.3-SNAPSHOT: checking
for updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki-core-parent:1.3-SNAPSHOT:
checking for updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki:9-SNAPSHOT: checking for
updates from xwiki-externals
[INFO] snapshot com.xpn.xwiki.platform:xwiki-web-gwt:1.3-SNAPSHOT: checking
for updates from xwiki-externals
[INFO] snapshot org.xwiki.platform:xwiki-core-plexus:1.3-SNAPSHOT: checking
for updates from xwiki-externals
[INFO] snapshot org.xwiki.platform:xwiki-core-container-api:1.3-SNAPSHOT:
checking for updates from xwiki-externals
[INFO] snapshot org.xwiki.platform:xwiki-core-url:1.3-SNAPSHOT: checking for
updates from xwiki-externals
[INFO] snapshot
org.xwiki.platform:xwiki-core-container-servlet:1.3-SNAPSHOT: checking for
updates from xwiki-externals
[INFO] snapshot org.xwiki.platform:xwiki-core-action:1.3-SNAPSHOT: checking
for updates from xwiki-externals
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] remote-resources:process
[WARN] Attempting to build MavenProject instance for Artifact
(org.codehaus.swizzle:swizzle-confluence:1.1-20070908) of type: jar;
constructing POM artifact instead.
[WARN] Attempting to build MavenProject instance for Artifact
(xmlrpc:xmlrpc-client:3.0) of type: jar; constructing POM artifact instead.
[WARN] Attempting to build MavenProject instance for Artifact
(velocity:velocity:1.5) of type: jar; constructing POM artifact instead.
[WARN] Attempting to build MavenProject instance for Artifact
(xmlrpc:xmlrpc-server:3.0) of type: jar; constructing POM artifact instead.
[WARN] Attempting to build MavenProject instance for Artifact
(groovy:groovy-all-1.0-jsr:06) of type: jar; constructing POM artifact
instead.
[INFO]
----------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
----------------------------------------------------------------------------
[INFO] org.apache.maven.model.Repository
[INFO]
----------------------------------------------------------------------------
[INFO] Total time: 56 second
[INFO] Finished at: Tue Jan 15 23:09:13 IST 2008
[INFO] Memory 19M/70M
[INFO]
----------------------------------------------------------------------------
--
View this message in context: http://www.nabble.com/Error-building-from-source---xwiki-platform-web---sta…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi,
I was studying the javascript code used in the xwiki UI for making some
extensions to it.
I have found that we use at least 4 ajax toolkits on the UI:
1. YUI (some parts of it)
2. Rico
3. script.aculo.us
4. Prototype JavaScript Framework
Plus there are some other bits and pieces of ajax code in many js files.
I believe prototype is the basic js framework we use as both rico and
script.aculo.us are built on top of this. Also lot of other js code is built
on top of prototype js framework.
Could anyone please confirm this
If this is true I find atealst 4 different versions of prototype.js on the
UI side.
I have following questions:
1. Can I keep just one (latest version of prototype.js).
2. Also what would be the advisable version of prototype.js (latest is 1.6)
3. If there is some conflicts in the dependent js files and frameworks (rico
and script.aculo.us), I am ready to upgrade them and also any used js code.
So can anyone please tell me if any of the js code now lies redundant ie not
used anymore.
4. Lastly is there any other important ajax framework or library we are
using.
Any information in this regard is highly appreciated.
Thanks
Sachin
-----
http://www.assembla.com/wiki/show/sachin_mittal about me:
--
View this message in context: http://www.nabble.com/Need-some-information-on-the-javascript-code-in-xwiki…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi devs,
Julien Maire is currently working on XWiki Concerto (deals with
integrating P2P technologies into XWiki, see http://concerto.xwiki.com/
), and he has some code regarding synchronization among peers and
content replication.
I'd like to vote him as a sandbox committer, so that he can place his
code in the XWiki repository.
Here's my +1
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi,
I was studying the javascript code used in the xwiki UI for making some
extensions to it.
I have found that we use at least 4 ajax toolkits on the UI:
1. YUI (some parts of it)
2. Rico
3. script.aculo.us
4. Prototype JavaScript Framework
Plus there are some other bits and pieces of ajax code in many js files.
I believe prototype is the basic js framework we use as both rico and
script.aculo.us are built on top of this. Also lot of other js code is built
on top of prototype js framework.
Could anyone please confirm this
If this is true I find atealst 4 different versions of prototype.js on the
UI side.
I have following questions:
1. Can I keep just one (latest version of prototype.js).
2. Also what would be the advisable version of prototype.js (latest is 1.6)
3. If there is some conflicts in the dependent js files and frameworks (rico
and script.aculo.us), I am ready to upgrade them and also any used js code.
So can anyone please tell me if any of the js code now lies redundant ie not
used anymore.
4. Lastly is there any other important ajax framework or library we are
using.
Any information in this regard is highly appreciated.
Thanks
-----
http://www.assembla.com/wiki/show/sachin_mittal about me:
--
View this message in context: http://www.nabble.com/Need-some-information-on-the-javascript-code-in-xwiki…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi,
I was studying the javascript code used in the xwiki UI for making some
extensions to it.
I have found that we use at least 4 ajax toolkits on the UI:
1. YUI (some parts of it)
2. Rico
3. script.aculo.us
4. Prototype JavaScript Framework
Plus there are some other bits and pieces of ajax code in many js files.
I believe prototype is the basic js framework we use as both rico and
script.aculo.us are built on top of this. Also lot of other js code is built
on top of prototype js framework.
Could anyone please confirm this
If this is true I find atealst 4 different versions of prototype.js on the
UI side.
I have following questions:
1. Can I keep just one (latest version of prototype.js).
2. Also what would be the advisable version of prototype.js (latest is 1.6)
3. If there is some conflicts in the dependent js files and frameworks (rico
and script.aculo.us), I am ready to upgrade them and also any used js code.
So can anyone please tell me if any of the js code now lies redundant ie not
used anymore.
4. Lastly is there any other important ajax framework or library we are
using.
Any information in this regard is highly appreciated.
Thanks
Sachin
-----
http://www.assembla.com/wiki/show/sachin_mittal about me:
--
View this message in context: http://www.nabble.com/Need-some-information-on-the-javascript-code-in-xwiki…
Sent from the XWiki- Dev mailing list archive at Nabble.com.