xwiki-devs June 2007

xwiki-devs@xwiki.org

31 participants
65 discussions

by Vincent Massol

Hi developers, I have updated the following page with our CI setup: http://www.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices All comments are most welcome. Thanks -Vincent

17 years, 5 months

Why is PluginApi#getPlugin public?

by Sergiu Dumitriu

Hello, AFAIK, XWiki APIs should be public wrappers around a hidden full-fledged java object, which can only be accessed directly by PR users. Certainly, this is not the case with plugins, which return the inner Plugin object without any check. I'd propose to change this method, so that it behaves as all the other API classes, and checks for programming rights before returning this object. Is there any reason why this change shouldn't be performed? Sergiu -- http://purl.org/net/sergiu

17 years, 5 months

[M2 build] Running XWiki Enterprise quickly

by Vincent Massol

Hi, As you've seen we have moved to Maven2 now and you might be wondering how to quickly run XWiki Enterprise now. Here are some notes about doing that: http://www.xwiki.org/xwiki/bin/view/Community/ Building#HExecutingtheStandardWebWARquicklyindevelopmentmode Thanks -Vincent

17 years, 5 months

Problem

by evelyne24＠gmail.com

Hello all, I'm having the following problem in xwiki: I have a document, which contains an input with autosuggest feature enabled. I create the document and I try to write something in the input but the query that should be executed is not, resulting in "Nothing found!" message for my suggest. If I SAVE the document and then edit it, and write something in the input, that query IS executed, and the suggest feature works fine. I'm guessing that before being saved a document doesn't have the proper rights and that's why the query cannot be executed. Any ideas what I should do in this case? Thanks a lot for your help. Evelina

17 years, 5 months

by Vincent Massol

On Jun 27, 2007, at 3:06 PM, Vincent Massol wrote: > Author: vmassol > Date: 2007-06-27 15:06:20 +0200 (Wed, 27 Jun 2007) > New Revision: 3739 > > Added: > xwiki-products/curriki/trunk/plugins/ > xwiki-products/curriki/trunk/plugins/mimetype/ > xwiki-products/curriki/trunk/plugins/mimetype/src/ > xwiki-products/curriki/trunk/plugins/mimetype/src/main/ > xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/ > xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/ > xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/ > curriki/ > xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/ > curriki/xwiki/ > xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/ > curriki/xwiki/plugin/ > xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/ > curriki/xwiki/plugin/mimetype/ > Removed: > xwiki-platform/web/trunk/gwt/src/main/resources/ > xwiki-products/curriki/trunk/gelcv1/gelcplugins/src/main/java/ > org/gelc/xwiki/plugins/mime/MimeType.java > xwiki-products/curriki/trunk/gelcv1/gelcplugins/src/main/java/ > org/gelc/xwiki/plugins/mime/MimeTypePluginAPI.java > Modified: > xwiki-platform/web/trunk/gwt/pom.xml > xwiki-platform/web/trunk/pom.xml > xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/ > curriki/xwiki/plugin/mimetype/MimeType.java > xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/ > curriki/xwiki/plugin/mimetype/MimeTypeConstant.java > xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/ > curriki/xwiki/plugin/mimetype/MimeTypePlugin.java > xwiki-products/curriki/trunk/plugins/mimetype/src/main/java/org/ > curriki/xwiki/plugin/mimetype/MimeTypePluginAPI.java > Log: > CURRIKI-759: Create a Maven2 build > > * Fixed the build for xwiki-platform-web/gwt. It nows generates a > JAR and a source JAR that can be depended upon by GWT modules doing > the GWT compilation (Watch & Curriki for example). > * I have added the GWT TK jar to our custom remote repo as I > couldn't find it elsewhere > * Removed some resource files in gwt/ module as I couldn't > understand what they were for... Ouch... The curriki/ commits were a mistake. I wasn't ready to commit it them yet. It doesn't really matter though. Only thing is that nobody has agreed yet to my previous email about the new package name for plugins so this is jumping the gun a bit... :) Let me know and I'll revert if necessary. Thanks -Vincent

17 years, 5 months

Maven2 build for Curriki

by Vincent Massol

Hi Curriki developers, The Curriki build is still using Ant and it was calling the Ant build script from XWiki core. However as I haven't put back an Ant build for XWiki core the Curriki build is currently not working. I'm proposing to update Curriki's build to use Maven2. I'm proposing the following directory structure: xwiki-product-curriki/ |_ gwt/ |_ web/ |_ wiki/ |_ plugins/ |_ asset/ |_ framework/ |_ license/ |_ metadata/ |_ mimetype/ |_ distribution/ where: * gwt/ contains GWT Java sources that have to be compiled with GWT to generate Java classes + JS files * wiki/ contains the curriki wiki * distribution/ contains a runnable version of curriki (equivalent to the XWiki standalone distribution for XWiki Enterprise). If that's ok with you I can start working on this as soon as tomorrow morning. I think I need 1 day at most to get it to build again. David, we can work on this together if you want. I'll probably have question for you as I progress. It would be great if you could be on IRC (irc.freenode.net, channel #xwiki) so that we can talk easily. Thanks -Vincent

17 years, 5 months

[Proposal] New SVN directory structure to accommodate the different applications we have

by Vincent Massol

Hi, Note: This email supercedes all my other proposals on the SVN directory structure. The rationale for this mail is that we're starting to have lots of applications built on top of the xwiki platform: XWiki Enterprise (default wiki), XEM, Watch, Curriki, Chronopolys, etc. We need to accomodate them in our directory structure. Top level structure =============== /svnroot/xwiki/ |_ xwiki-platform/ |_ xwiki-applications/ |_ xwiki-enterprise/ |_ xwiki-enterprise-manager/ |_ xwiki-watch/ |_ curriki/ |_ chronopolys/ |_ xwiki-extensions/ |_ xwiki-eclipse/ |_ xwiki-concerto/ |_ sandbox/ where: * xwiki-platform is the xwiki platform on which all the applications are built. * xwiki-applications are applications that extend the platform with: skins, xwiki pages (XAR), plugins * xwiki-enterprise is the name of our previously known "default wiki" application. * xwiki-extensions are any other extensions of xwiki not fitting in xwiki-applications. For example the XWiki Eclipse integration, etc. I've put concerto there but I'm not sure what it'll look like. Definition of xwiki-platform ===================== /svnroot/xwiki/xwiki-platform/ |_ tools/ |_ core/ (JAR) |_ plugins/ (JARs) |_ skins/ (ZIPs) |_ dodo/ |_ finch/ |_ albatross/ |_ web/ (WARs) |_ gwt/ |_ standard/ |_ xarlets (XARs) |_ selenium/ |_ blog/ |_ calendar/ |_ ... where: * tools/ contains tools used to build the platform and xwiki applications * xarlets/ contains independent xwiki apps (we need a word better than xarlets and different than applications which we should reserve for things like curriki, xwiki enterprise, xem, etc) that can be installed in any running xwiki app * In the future core/ will be replaced with: |_ components/ (JARs) |_ xwiki-model/ |_ xwiki-storage/ |_ ... * In the future web/ will be replaced with UI components (see the UI proposal for more) Definition of xwiki-enterprise/ ======================= /svnroot/xwiki/xwiki-applications/xwiki-enterprise/ |_ wiki/ |_ distribution/ |_ distribution-test/ where: * wiki/ contains the xar pages Generic definition of an xwiki-application/ ================================= /svnroot/xwiki/xwiki-applications/<app name>/ |_ wiki/ |_ web/ (optional) |_ plugins/ (optional) |_ skin/ (optional) |_ distribution/ |_ distribution-test/ For example for xwiki-watch/: /svnroot/xwiki/xwiki-applications/xwiki-watch/ |_ wiki/ |_ web/ (the gwt stuff) |_ distribution/ |_ distribution-test/ I think this pretty much includes everything we currently have in SVN. WDYT? Thanks -Vincent

17 years, 5 months

Proposal for full-editing mode

by evelyne24＠gmail.com

Hello all, First of all, thank you for your replays and please forgive my short absence....I was left without electricity and Internet for a few days because a short storm. Sergiu has given me the task to implement a fullscreen editing mode, similar to WYSIWYG or WIKI and I thought about it and found several solutions, each one with advantages and disadvantages. I will present them now and I would like to receive some feedback from you, to know which of the solutions (or maybe other solution if none of mines is good enough) will be better. Ideeas for a new way of editing in xwiki (like WYSIWYG and WIKI in FULLSCREEN) --------------------------------------------------------------------------------- Ideea no. 1: A button in the editor itself, like in FCK editor --------------------------------------------------------------------------------- Sample here: http://www.fckeditor.net/demo (the one next to Help button) Advantages: 1. it doesn't need any other graphical implementation in xwiki (like a new tab for instance), because xwiki has already 2 rows of tabs 2. with a good, expressive icon it can be easily spotted by the user 3. it's very easy and intuitive to use, even for a non-initiated user (specially with a tooltip); the user can use tabs to move to the button, if he doesn't have a mouse 4. it can appear anywhere the editor toolbar is needed, therefore allowing full editing for all those cases (not only for wysiwyg and wiki...) 5. can be more impressive with a nice transition animation 6. it covers all the area in xwiki (no elements visible like panels, header etc, otherwise it will not be fullscreen editing, it will be just like the existing WYSIWYG editing mode) 7. by reducing the size of the textarea, the user is brough back to normal wysiwyg editor and has access to other elements in xwiki...like panels... just like in the existing editing mode. Disadvantages: 1. it's depedent of the editor toolbar 2. in order to save or cancel or save and continue, the user has to reduce the size by pressing the same button and then press the submit button(save, cancel...) --------------------------------------------------------------------------------- Ideea no. 2: Two small buttons, in the corner of both WYSIWYG and WIKI editor, just like in Gmail (composing), which opens a new fullscreen window with the editor, the textarea and save, cancel...buttons --------------------------------------------------------------------------------- Advantages: 1. the user can have acces to other xwiki elements (panels...) in the parent window 2. independent of the editor itself 3. pretty intuitive to use Disadvantages: 1. when the new window is opened, the parent window must be redirected to the view mode -> reloading the page 2. if the user clicks cancel, to edit again he must press Edit (WYSIWYG or WIKI) and then press the little button on the tab -> 2 reloadings 3. what happens if the user opens twice the same editor? the modifications from one must be seen in all other open editor -> quite difficult to implement 4. harder to implement 5. a button like this can be placed in each tab (wysiswyg and wiki) and it a new tab is added in xwiki which supports full screen editing, the button has to be place in it too. --------------------------------------------------------------------------------- Ideea no. 3: Resizable textarea --------------------------------------------------------------------------------- Advantages: 1. the user can resize the textarea as much as he wants, not necessarily fullscreen 2. pretty easy to use, but only if the user has a mouse to drag the textarea Disadvantages: 1. the resizing of the textarea can damage the xwiki interface (all the page has to be resized) -> pretty nasty distorsions 2. the user will have to scroll down a lot to see the footer if the textarea is resized a lot. --------------------------------------------------------------------------------- Ideea no. 4: Like the no. 1 except that when pressed, the button will open a floating pane with a nice animation, that will cover about 60% -70% of the page which will contain only a resizable textarea, the editor and the save, cance,..buttons, while the rest of the page will be covered by a translucent blocking background (similar to those which appear when you have to fill in the username and password in order to access something). When the user finishes editing and presses one of the buttons, the panel closes and the text is put back in the tab from which the editor button was pressed (i.e wysiwyg or wiki or other tab that has the editor) --------------------------------------------------------------------------------- Advantages: 1. advantages of no. 1 and the fact that will be more spectaculous (with a nice effect) Disadvantages: 1. same as no. 1 (dependent of editor etc..) So, these are my ideas for now... I would like to know which seems more appealing to you and also, if you have other opinions, ideeas... Thanks, Evelina Slatineanu

17 years, 5 months

Re: Headless X11 with Xvfb (for running selenium tests without the browser popping up)

by Vincent Massol

Hi catalin, I've checked and yes the selenium plugin we're using is too old. That xvfb support has been added recently. Actually the selenium plugin has been completely rewritten recently (it was in java it's now in groovy... first time I see a maven plugin in groovy). BTW it now supports running HTML selenium tests. I've set up our CI with Raffaello on http://teamcity.xwiki.org and I've discussed the need for an X display. Raffaello is setting up a vncserver which will act as an X server. He prefers this over xvfb as he's more experienced with it and knows it works for sure. I guess we could do the same locally if we wanted. I think the steps are: 1- set up the DISPLAY env variable 2- start vncserver 3- start the selenium RC server 4- launch the browser 5- execute the tests I guess we could integrate steps 1 and 2 in the m2 build in a profile. Of course I think the best solution is http://www.realityqa.com/ realityview.jsp (which I'm working on getting - I've asked Patrick if it's ready to be used) but this vncserver solution would be a nice backup solution in case the realityqa server is down or in offline mode. WDYT? Thanks -Vincent PS: I'm copying the xwiki dev list so that others know what we're working on. On Jun 23, 2007, at 12:30 PM, Catalin Hritcu wrote: > Hi Vincent, > > I was not able to run the tests in headless mode, because I'm getting > a strange error. When you have some time maybe you can have a look. > > So what I did was modify Step 3 in the > xwiki-product-enterprise/distribution-test/pom.xml as documented here: > http://mojo.codehaus.org/selenium-maven-plugin/examples/headless- > with-xvfb.html > Now that part looks like this: > >  > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>selenium-maven-plugin</artifactId> > <version>1.0-beta-2-SNAPSHOT</version> > <executions> > <execution> > <id>xvfb</id> > <phase>pre-integration-test</phase> > <goals> > <goal>xvfb</goal> > </goals> > </execution> > <execution> > <id>start-selenium</id> > <phase>pre-integration-test</phase> > <goals> > <goal>start-server</goal> > </goals> > <configuration> > <background>true</background> > </configuration> > </execution> > </executions> > <configuration> > <background>true</background> > <multiWindow>true</multiWindow> > </configuration> > </plugin> > > > The error I get is as follows: > catalin-4:~/JavaApps/xwiki-trunks-devs/xwiki-product-enterprise/ > distribution-test > hritcu$ mvn install > [INFO] Scanning for projects... > [INFO] > ---------------------------------------------------------------------- > ------ > [INFO] Building XWiki Products - Enterprise - Functional Tests > [INFO] task-segment: [install] > [INFO] > ---------------------------------------------------------------------- > ------ > [INFO] > ---------------------------------------------------------------------- > -- > [ERROR] BUILD ERROR > [INFO] > ---------------------------------------------------------------------- > -- > [INFO] Failed to construct build plan for: > com.xpn.xwiki.products:xwiki-enterprise-test:pom:1.1-SNAPSHOT ( > task-segment: [install] ). Reason: Mojo: xvfb does not exist in > plugin: org.codehaus.mojo:selenium-maven-plugin:1.0-beta-2-SNAPSHOT. > [INFO] > ---------------------------------------------------------------------- > -- > [INFO] For more information, run Maven with the -e switch > [INFO] > ---------------------------------------------------------------------- > -- > [INFO] Total time: 1 second > [INFO] Finished at: Sat Jun 23 12:22:06 CEST 2007 > [INFO] Final Memory: 6M/11M > [INFO] > ---------------------------------------------------------------------- > -- > [INFO] > ---------------------------------------------------------------------- > -- > [INFO] BUILD SUCCESSFUL > [INFO] > ---------------------------------------------------------------------- > -- > [INFO] Total time: 1 second > [INFO] Finished at: Sat Jun 23 12:22:06 CEST 2007 > [INFO] Final Memory: 6M/11M > [INFO] > ---------------------------------------------------------------------- > -- > catalin-4:~/JavaApps/xwiki-trunks-devs/xwiki-product-enterprise/ > distribution-test > hritcu$ > > > However the documentation says this mojo exists > http://mojo.codehaus.org/selenium-maven-plugin/xvfb-mojo.html > So this is really strange for me. > > I tried deleting the selenium-maven-plugin from the local repository > and the usual stuff but without any result. It gets downloaded again > from the XWiki(!) repository: > > [INFO] snapshot > org.codehaus.mojo:selenium-maven-plugin:1.0-beta-2-SNAPSHOT: checking > for updates from xwiki.plugin.snapshot > [INFO] snapshot > org.codehaus.mojo:selenium-maven-plugin:1.0-beta-2-SNAPSHOT: checking > for updates from xwiki.plugins > [INFO] snapshot > org.codehaus.mojo:selenium-maven-plugin:1.0-beta-2-SNAPSHOT: checking > for updates from xwiki > [INFO] snapshot > org.codehaus.mojo:selenium-maven-plugin:1.0-beta-2-SNAPSHOT: checking > for updates from openqa.org > Downloading: http://maven.xwiki.org/org/codehaus/mojo/selenium- > maven-plugin/1.0-beta-2-SNAPSHOT/selenium-maven-plugin-1.0-beta-2- > SNAPSHOT.pom > 8K downloaded > Downloading: http://maven.xwiki.org/org/codehaus/mojo/selenium- > maven-plugin/1.0-beta-2-SNAPSHOT/selenium-maven-plugin-1.0-beta-2- > SNAPSHOT.jar > 12K downloaded > > Is it possible that the snapshot in the xwiki repository is too old? > Otherwise how do I force it to download from the "official" > repository? > > Regards, > Catalin

17 years, 5 months

XWiki Eclipse IDE Integration - Milestone 1

by tharindu jayasuriya

Hi All, We have completed milestone-1 of the eclipse xwiki plug-in binary and source (eclipse project) are available via, http://jira.xwiki.org/jira/browse/XWIKI-1360 Implemented features, 1. Login to XWiki 2. Selectively import spaces 3. Navigate through document hierarchy Thanks. - Tharindu

17 years, 5 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs June 2007