- xwiki-devs@xwiki.org - lists.xwiki.org

[xwiki-devs] [VOTE] Postponing 1.6RC1 release (again) and going direct to 1.6 final on Thursday the 2nd

by Vincent Massol

Hi devs, You know we've been facing some problems in the new GWT editor. Marius needs 2 days more to finish fixing the 2 important bugs related to: - paragraph support - bolding/unbolding (same for italic and underline I guess) We also need 1 day to all test the new GWT WYSIWYG and try to find more issues. Note that since we've had to do low level JS, it's currently only working for FF... So the editor won't work on IE or any other browser to 1.6 final. It may work but it won't work perfectly well yet. In addition and to reduce the 1.6 final release date (compared to the original plan of 22nd of September), I propose that we release the final 1.6 on this Thursday (the 2nd). To do this I propose that we ALL spend time testing the current 1.6 trunk code to verify that all works fine. This is a bet we're taking but I think we could easily win 1 or 2 weeks by doing it. In addition and should we need it we can quickly release a 1.6.1 release. Here's my +1 for this plan + for helping test it. Thanks -Vincent

16 years, 11 months

8
8
0 0

[xwiki-devs] [XWIKI] - Switch to Advanced edit mode and Switch to Simple edit mode.

by Prathap Pandian

Hi, Can anyone tell me the functionality of "*Switch to Advanced edit mode and Switch to Simple edit mode*" in the user profile. I don't think both are different. Since both are doing the same functionality. -- Prathap

16 years, 11 months

2
1
0 0

[xwiki-devs] [ANN] XWiki Workspaces 1.1 released

by Jerome Velociter

The XWiki development team is pleased to announce the release of XWiki Workspaces 1.1 final. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download This release spanned about 5 months (beginning of May to end of september), with a 2 months pause this summer. During that period we implemented 47 issues, fixing 24 bugs and adding new features such as: * Global groups management * Email invitation manangement * A Workstream application * A Revamped global administration * A new mode of publication : Open For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesWorkspaces11 Regards -The XWiki dev team

16 years, 11 months

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r11418 - xwiki-products/xwiki-workspaces/trunk/wiki/src/main/resources/XWSCode

by Sergiu Dumitriu

jvelociter (SVN) wrote: > Author: jvelociter > Date: 2008-07-22 17:57:57 +0200 (Tue, 22 Jul 2008) > New Revision: 11418 > > Modified: > xwiki-products/xwiki-workspaces/trunk/wiki/src/main/resources/XWSCode/CreateNewWorkspaceForm > Log: > XWS-127 Client side validation on workspace creation form does not work under IE6 > > > Modified: xwiki-products/xwiki-workspaces/trunk/wiki/src/main/resources/XWSCode/CreateNewWorkspaceForm > =================================================================== > --- xwiki-products/xwiki-workspaces/trunk/wiki/src/main/resources/XWSCode/CreateNewWorkspaceForm 2008-07-22 15:50:14 UTC (rev 11417) > +++ xwiki-products/xwiki-workspaces/trunk/wiki/src/main/resources/XWSCode/CreateNewWorkspaceForm 2008-07-22 15:57:57 UTC (rev 11418) > @@ -12,9 +12,9 @@ > <customClass></customClass> > <contentAuthor>XWiki.Admin</contentAuthor> > <creationDate>1208697558000</creationDate> > -<date>1214058248000</date> > -<contentUpdateDate>1214058248000</contentUpdateDate> > -<version>3.1</version> > +<date>1216745595000</date> > +<contentUpdateDate>1216745595000</contentUpdateDate> > +<version>5.1</version> > <title></title> > <template></template> > <defaultTemplate></defaultTemplate> > @@ -140,7 +140,29 @@ > // inform how much chars can be still typed > $('spacetitlecharsleft').innerHTML = maxTitleChars - dTitle.value.length; > } > - }</code> > + } > + > +/* > + * getElementsByClassName rewrite. > + * Developed by Robert Nyman, http://www.robertnyman.com > + * Code/licensing: http://code.google.com/p/getelementsbyclassname/ > + */ > +function getElementsByClassName(className, tag, elm){ > + var testClass = new RegExp("(^|\\s)" + className + "(\\s|$)"); > + var tag = tag || "*"; > + var elm = elm || document; > + var elements = (tag == "*" && elm.all)? elm.all : elm.getElementsByTagName(tag); > + var returnElements = []; > + var current; > + var length = elements.length; > + for(var i=0; i<length; i++){ > + current = elements[i]; > + if(testClass.test(current.className)){ > + returnElements.push(current); > + } > + } > + return returnElements; > +}</code> getElementsByClassName also exists in prototype. We should use that one instead. > </property> > <property> > <name>Create new workspace validation</name> > @@ -235,8 +257,8 @@ > var sDesc = $('XWiki.SpaceClass_0_description'); > var wAccess = $('XWiki.WorkspaceSpaceClass_0_accesslevel'); > var wColor = $('XWiki.WorkspaceSpaceClass_0_color'); > - var colorPreview = wColor.parentNode.parentNode.getElementsByClassName("form-entry-valid")[0]; > - var vSpan=dTitle.parentNode.parentNode.getElementsByClassName("form-entry-valid")[0]; > + var colorPreview = getElementsByClassName("form-entry-valid","*",wColor.parentNode.parentNode)[0]; > + var vSpan = getElementsByClassName("form-entry-valid","*",dTitle.parentNode.parentNode)[0]; > Event.observe(dTitle,"keyup", titleKeyTyped()); > Event.observe(dTitle,"blur", validateTitle()); > // Green the optional/already filled fields on blur... -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 11 months

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r11414 - xwiki-products/xwiki-workspaces/branches/xwiki-workspaces-1.1/wiki/src/main/resources/XWSCode

by Sergiu Dumitriu

jvelociter (SVN) wrote: > Author: jvelociter > Date: 2008-07-22 17:01:40 +0200 (Tue, 22 Jul 2008) > New Revision: 11414 > > Modified: > xwiki-products/xwiki-workspaces/branches/xwiki-workspaces-1.1/wiki/src/main/resources/XWSCode/RegistrationService > Log: > XWS-133 Impossible to register on IE6 > > > Modified: xwiki-products/xwiki-workspaces/branches/xwiki-workspaces-1.1/wiki/src/main/resources/XWSCode/RegistrationService > =================================================================== > --- xwiki-products/xwiki-workspaces/branches/xwiki-workspaces-1.1/wiki/src/main/resources/XWSCode/RegistrationService 2008-07-22 12:04:53 UTC (rev 11413) > +++ xwiki-products/xwiki-workspaces/branches/xwiki-workspaces-1.1/wiki/src/main/resources/XWSCode/RegistrationService 2008-07-22 15:01:40 UTC (rev 11414) > @@ -12,9 +12,9 @@ > <customClass></customClass> > <contentAuthor>XWiki.Admin</contentAuthor> > <creationDate>1211638814000</creationDate> > -<date>1214922499000</date> > -<contentUpdateDate>1214922499000</contentUpdateDate> > -<version>5.1</version> > +<date>1216742225000</date> > +<contentUpdateDate>1216742225000</contentUpdateDate> > +<version>15.1</version> > <title></title> > <template></template> > <defaultTemplate></defaultTemplate> > @@ -353,12 +353,12 @@ > var valid = $('validation_' + fieldId); > if (fail) { > valid.innerHTML = message; > - input.style.border = "1px solid red;" > + input.setAttribute("style", "border:1px solid red;"); > valid.setAttribute("class", "errormessage"); > } > else { > valid.innerHTML = ""; > - input.style.border = "1px solid green;" > + input.setAttribute("style","border:1px solid green;"); > valid.setAttribute("class", ""); > } > } > It's not nice to use setAttribute like this, since it may override other rules set for that element. -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 11 months

1
0
0 0

[xwiki-devs] packaging XWiki application with maven?

by Paul Libbrecht

Hello XWikiers, I did not find a nice way to package our reviews-application. It should yield a xar and I would have expected the xar could be built with all items. Unfortunately, I have only found a way to package the xml files in the xar and I would like to put groovy and .vm sources there... thus far I am copy and pasting. mvn -g did not help me. thank for hints. paul

16 years, 11 months

3
8
0 0

[xwiki-devs] [vote] Add the XWiki Components Tutorial to the tutorials section on platform.xwiki.org

by Anca Paula Luca

Hi devs, while developing my XWiki watch component, I've written a quick start tutorial on XWiki components, which I would like to add in the dedicated section on platform.xwiki.org. It is currently in draft version at http://dev.xwiki.org/xwiki/bin/view/Drafts/CreatingComponents . Please give it a critical look and signal any errors that might have slipped or send improvement suggestions. Here's my +1 for taking it out of draft version, WDYT? Happy coding, Anca Luca

16 years, 11 months

5
10
0 0

[xwiki-devs] [WEBDAV] Grouping of pages under spaces.

by Asiri Rathnayake

Hi Devs, In the current xwiki-webdav implementation we have introduced a feature where all the pages under a certain space is grouped according to the starting characters of those pages. For an example, consider the following setup : space : Farm pages under Farm : Dog, Cat, Donkey, Carrot, Mouse Then the user will see the following directory structure on webdav, xwiki/webdav/spaces/Farm/ | |-D (Dog & Donkey goes here) | |-C (Cat & Carrot goes here) | |-M (Mouse ends up here) Note : How many starting characters used to make groupings depends on the number of documents inside the space. Now, from xwiki-ui to access various documents via webdav, we have to allow direct access to pages as well. That is, following url pattern should work fine : xwiki/webdav/spaces/<space_name>/<page_name> (makes sense right ?) Now the problem with the current implementation is that in a url like xwiki/webdav/spaces/FOO/BAR we don't know whether BAR is a grouping or if it is a page (direct access). So I propose the following : * All the grouped directories should start with a "_" and end with a "_" (may be only one of them, but i like symmetric) By this way we can easily differentiate direct page requests from indirect access. Ex : Indirect : /xwiki/webdav/spaces/Foo/_D_/D Direct : /xwiki/webdav/spaces/Foo/D Note : Here the page name is 'D'. WDYT ? Thanks. - Asiri

16 years, 11 months

2
1
0 0

[xwiki-devs] PROPFIND on /xwiki/ fails.

by Asiri Rathnayake

Hi Devs, Ludovic, I'm faced with the following problem, Currently xwiki-webdav is deployed under /xwiki/webdav/*. And for this to work, we need PROPFIND method to work correctly on following locations { "/" , "/xwiki/" , "/xwiki/webdav/*". } For "/" i have written a separate xwiki-rootwebapp and it works fine. For "/xwiki/" and "/xwiki/webdav/*" I had defined the following servlet mapping elemnts : <servlet-mapping> <servlet-name>xwiki-webdav</servlet-name> <url-pattern>/</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>xwiki-webdav</servlet-name> <url-pattern>/webdav/*</url-pattern> </servlet-mapping> Everything was working fine but lately i discovered that none of the static content is being served correctly. This is because of the first mapping on "/", this seems to overrride the default servet of the container (which serves static files). Without the first mapping some webdav clients fail because they think the url is not a webdav one. I'm really stuck here and can't think of a solution, if you have any ideas please let me know. Thanks a lot. - Asiri

16 years, 11 months

2
5
0 0

[xwiki-devs] FindBugs on XWiki

by Jonas von Malottki

Hello Xwiki-Devs, for the fun of it I let FindBugs check the Xwiki Core code and it found a bunch of "Issues". Some of them are more severe than others. Maybe it is interesting to check it out. In my own programs I found some really interesting errors/problems I was never aware of. (Including some thread safety related stuff) The good thing with Findbugs is the extensive documentation, that gives you a very good explanation why the found issue is an issue. There are also some "false positives", also explained in the documentation. http://findbugs.sourceforge.net/ Findbugs also has good Eclipse Integration and a Maven plugin. Definitely worth a try. A first peek is painlessly done via Java webstart. It's just a pointer.. Greetings Jonas

16 years, 11 months

4
6
0 0

[xwiki-devs] Office converter cleaning status?

by Vincent Massol

Hi Wang, Long time no hear, you must be busy :) Could you let us know what's the status WRT to cleaning up the office- generated HTML? The roadmap I'd like to have is to have it fully working for 1.7 final (that's for the 1st of December). Do you think that's feasible? My take is that we should have some pretty solid cleaning up by 1.7M1 if we want to have a chance of it being finished for 1.7 final. Here's the currently planned 1.7 dates: - 1.7M1: 20th of October (that's more than 3 weeks after the 1.6 release) - 1.7M2: 10th of November (3 weeks after 1.7M1) - 1.7RC1: 17 Nov (one week after) - 1.7RC2 or final: 24 Nov (one week after) - 1.7 final (if needed): 1st of December WDYT? Do you need any help to achieve this? Thanks -Vincent

16 years, 11 months

2
2
0 0

[xwiki-devs] Maven.xwiki.org is down for maitenance

by Vincent Massol

Hi everyone, Just to let you know maven.xwiki.org is undergoign maintenance right now. So you might want to run your builds in offline mode for the time being. Thanks -Vincent

16 years, 11 months

1
1
0 0

[xwiki-devs] [VOTE] Release XWiki Workspaces 1.0 tomorrow

by Jerome Velociter

Hello devs, I would like to promote XWiki Workspaces 1.1 RC1 as 1.1 final tomorrow. Only changes from RC2 will be reviewed English translation resources. Here is my +1 for it. Jerome.

16 years, 11 months

7
8
0 0

[xwiki-devs] Potential synchronization issues

by Vincent Massol

Hi, I think we might need to review our singleton components (i.e. all of them ;)) for sync. issues. For example take DefaultObservationManager: private Map<String, List<RegisteredListener>> listeners = new HashMap<String, List<RegisteredListener>>(); It has for ex a addListener() method. Imagine several threads all calling addListener(). Since HashMap is not synchronized this can cause problems. Thus shared objects should all be synchronized or they should only be filled once (as in an initialize method for ex). WDYT? Do you agree there's a potential bug in the case above? Thanks -Vincent

16 years, 11 months

5
6
0 0

Re: [xwiki-devs] [xwiki-notifications] r13101 - platform/web/trunk/standard/src/main/webapp/templates

by Vincent Massol

Is this temporary? I'm not sure it's a good idea to generate HTML from business code. The HTML should be generated in the templates IMO. WDYT? Thanks -Vincent On Sep 30, 2008, at 6:31 PM, mflorea (SVN) wrote: > Author: mflorea > Date: 2008-09-30 18:31:41 +0200 (Tue, 30 Sep 2008) > New Revision: 13101 > > Modified: > platform/web/trunk/standard/src/main/webapp/templates/ > editwysiwygnew.vm > Log: > I'm using the WysiwygPlugin to generate the HTML input hidden > element that will hold the initial HTML content of the editor. This > way the HTML special symbols are escaped inside the value attribute. > > Modified: platform/web/trunk/standard/src/main/webapp/templates/ > editwysiwygnew.vm > =================================================================== > --- platform/web/trunk/standard/src/main/webapp/templates/ > editwysiwygnew.vm 2008-09-30 16:24:51 UTC (rev 13100) > +++ platform/web/trunk/standard/src/main/webapp/templates/ > editwysiwygnew.vm 2008-09-30 16:31:41 UTC (rev 13101) > @@ -28,7 +28,7 @@ > ## If JavaScript is disabled the user will still be able to edit the > document using this HTML text area. > $xwiki.getTextArea($tdoc.content) > ## We separated the hook of the editor (the previous HTML text area) > from editor's input source (the following hidden input) > -<input type="hidden" id="htmlContent" value="$ > {xwiki.wysiwyg.toHTML($tdoc.content, $doc.syntaxId)}" > disabled="disabled" /> > +$xwiki.wysiwyg.getInput("htmlContent", $tdoc.content, $doc.syntaxId) > <script type="text/javascript"> > //<![CDATA[ > var Wysiwyg0 = {

16 years, 11 months

2
1
0 0

[xwiki-devs] JS in PDF exports

by Vincent Massol

Someone was asking about JS execution in PDF exports. Found this announcement today: http://www.theserverside.com/news/thread.tss?thread_id=50837 This is just a FYI and a reminder to look into it when we overhaul the PDF export. Thanks -Vincent

16 years, 11 months

1
0
0 0

[xwiki-devs] Replacing XWiki Syntax page with new one

by Vincent Massol

Hi devs, I'd like to replace the current: http://platform.xwiki.org/xwiki/bin/view/Main/XWikiSyntax with this one: http://dev.xwiki.org/xwiki/bin/view/Drafts/XWikiSyntax20 I'll also modify the Editing page to explain how to edit in other syntaxes + modify the Admin guide to explain how to change configured syntaxes. Ok with everyone? Thanks -Vincent

16 years, 11 months

3
3
0 0

Re: [xwiki-devs] Rich HTML editing in the browser

by Vincent Massol

(forwarding this very good article to the xwiki dev list) Indeed a very good article explaining well the issues. From the article I conclude that this feature is: * HTML 5 (and XHTML) * not standardized and thus with huge varying implementations depending on the browser Since I'm a newbie in this domain I'll ask some newbie questions... :) As a consequence of the above I don't understand why any cross-browser WYSIWYG editor would use this feature as of now. Wouldn't it be easier to implement everything in javascript? Since there are javascript frameworks that isolate the user from the browser specificities wouldn't it be easy to do that? Are all the existing WYSIWYG editor using this designMode/ ContentEditable feature? Thanks -Vincent On Sep 27, 2008, at 8:25 PM, Marius Dumitru Florea wrote: > Hi Vincent, > > I found by chance this article http://tinyurl.com/5rlwps . I's not > too long and worth reading in order to better understand the > difficulty of making a good cross-browser WYSIWYG editor. You're > already familiar with some of the issues discussed there. > > Have a nice evening, > Marius

16 years, 11 months

2
1
0 0

[xwiki-devs] xwiki-webdav : xwiki-ui integration

by Asiri Rathnayake

Hello devs, Following couple of weeks i've been working on integrating xwiki-webdav in the xwiki ui and i'm confident now it's time to move out this effort from sandbox to our main xwiki source tree. Before discussing about where to put the xwiki-webdav and associated modules in the main source tree, following is a brief status update on what's going with xwiki-webdav. * xwiki-webdav can be deployed on it's own (with a preconfigured hsqldb) or more likely be integrated into an existing XE installation. Once deployed, various webdav clients (provided by your operating system or thirdparty applications) will be able to brows through an XE repository pretty easily. - It's worth to mention at this point that there are so many webdav clients out there and they vary in bahaviour a lot. This is the MOST-PAINFUL problem we're currently facing. And to get xwiki-webdav into shape, we need to test it a LOT! :) * xwiki-webdav is configured as a maven project ( http://svn.xwiki.org/svnroot/xwiki/sandbox/xwiki-webdav/) and it can be deployed (for testing) pretty easily through maven-jetty-plugin. Also we have added quite a few integration tests to make sure of the basic dav functionality. * For interoperability with XP's built-in webdav client we had to put up a separate root servlet, this project is currently located at http://svn.xwiki.org/svnroot/xwiki/sandbox/xwiki-rootwebapp/. xwiki-rootwebapp handles redirection and proper reply for the PROPFIND request at root level of webserver. * xwiki-webdav is integrated into xwiki ui with two approaches, one by provding an 'Edit' link in the attachments view of a page (for editing attachments via webdav) and the other is thorugh foxwiki's context menu. * To implement the 'Edit' link in the attachments view, we created the xwiki-webdav-plugin ( http://svn.xwiki.org/svnroot/xwiki/sandbox/xwiki-webdav-plugin/) which is responsible for providing webdav urls given document attachments. The actual editing of attachments is carried either via foxwiki (if you are running firefox) or via IE's built-in capabilities of openning webdav urls with native editors. * As mentioned above we had to revamp foxwiki to make it easy for us to integrate xwiki-webdav in the xwiki-ui. But we have the added bonus of all previous foxwiki features too :). Presently foxwiki is configured as a maven project (http://svn.xwiki.org/svnroot/xwiki/sandbox/xwiki-clients/FoXWiki/) and it can be built and tested pretty easily (refer to README). * A fully configured test server is located at http://91.121.237.216/xwiki/bin/view/Main/ (along with instructions) so that you may test out xwiki-webdav:xwiki-ui integration yourself :) * So altogether we have 4 projects [xwiki-rootwebapp],[xwiki-webdav],[xwiki-webdav-plugin],[foxwiki] and follwing is our task break down for days to come : 1. Cleanup the source code and make it upto xwiki standards (2 more days work remaining, need to add javadoc comments). 2. Create a maven build (Done). 3. Discuss proper places to land these projects (on trunk). 4. Send a vote to move these projects into trunk. 5. Create JIRA projects as necessary. (i'm not sure if we would have four separate projects or not) 6. Release a first version. * Now to start with, we need to discuss where to place these projects under the main source tree, following are some initial suggessions but i'm not certain about these :) [xwiki-rootwebapp] : No Idea. [xwiki-webdav] : http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-webdav [xwiki-webdav-plugin] : http://svn.xwiki.org/svnroot/xwiki/platform/xwiki-plugins/trunk/xwiki-webda… be we should change the name ?) [foxwiki] : http://svn.xwiki.org/svnroot/xwiki/foxwiki WDYT ? - Asiri

16 years, 11 months

2
3
0 0

[xwiki-devs] jgroups is not downloaded ?

by rssh＠gradsoft.com.ua

------------------------------------------------------------------------------- Test set: com.xpn.xwiki.XWikiTest ------------------------------------------------------------------------------- Tests run: 14, Failures: 0, Errors: 14, Skipped: 0, Time elapsed: 2.609 sec <<< FAILURE! Hmm - looks like maven does not get jgroups. testCreatorAfterDocumentCopy(com.xpn.xwiki.XWikiTest) Time elapsed: 1.077 sec <<< ERROR! java.lang.NoClassDefFoundError: org/jgroups/blocks/RpcDispatcher$Marshaller at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:637) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:277) at java.net.URLClassLoader.access$000(URLClassLoader.java:73) at java.net.URLClassLoader$1.run(URLClassLoader.java:212) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:205) at java.lang.ClassLoader.loadClass(ClassLoader.java:323) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294) at java.lang.ClassLoader.loadClass(ClassLoader.java:268) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:336) at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2444) at java.lang.Class.getDeclaredMethods(Class.java:1808)

16 years, 11 months

2
2
0 0

Re: [xwiki-devs] [xwiki-notifications] r13076 - in watch/trunk: . component component/src component/src/main component/src/main/java component/src/main/java/org component/src/main/java/org/xwiki component/src/main/java/org/xwiki/watch component/src/main/java/org/xwiki/watch/component component/src/main/java/org/xwiki/watch/component/contextualizer component/src/main/resources component/src/main/resources/META-INF component/src/main/resources/META-INF/plexus

by Vincent Massol

Hi Anca, Very good! I'm real happy you're jumping in the bandwagon on this :) Just one note: In the future the way to expose a component in velocity will be done differently. See http://tinyurl.com/3qu923 in case you haven't followed the discussion. This way of doing it should probably be removed once we have the new way. This is the current right way though :) Thanks -Vincent On Sep 29, 2008, at 2:14 PM, lucaa (SVN) wrote: > Author: lucaa > Date: 2008-09-29 14:14:31 +0200 (Mon, 29 Sep 2008) > New Revision: 13076 > > Added: > watch/trunk/component/ > watch/trunk/component/pom.xml > watch/trunk/component/src/ > watch/trunk/component/src/main/ > watch/trunk/component/src/main/java/ > watch/trunk/component/src/main/java/org/ > watch/trunk/component/src/main/java/org/xwiki/ > watch/trunk/component/src/main/java/org/xwiki/watch/ > watch/trunk/component/src/main/java/org/xwiki/watch/component/ > watch/trunk/component/src/main/java/org/xwiki/watch/component/ > DefaultWatchService.java > watch/trunk/component/src/main/java/org/xwiki/watch/component/ > WatchService.java > watch/trunk/component/src/main/java/org/xwiki/watch/component/ > contextualizer/ > watch/trunk/component/src/main/java/org/xwiki/watch/component/ > contextualizer/WatchServiceContextualizer.java > watch/trunk/component/src/main/resources/ > watch/trunk/component/src/main/resources/META-INF/ > watch/trunk/component/src/main/resources/META-INF/plexus/ > watch/trunk/component/src/main/resources/META-INF/plexus/ > components.xml > Modified: > watch/trunk/pom.xml > Log: > XWATCH-230: Prepare build for the creation the component > * created the "component" module in Watch > * created a WatchService component, visible in velocity context > (through the VelocityContextInitializer), with no functions for the > moment. >

16 years, 11 months

2
1
0 0

[xwiki-devs] [Rendering] Multi syntax support configuration

by Vincent Massol

Hi, I'm committing the following change to make it easier for users to try the new syntax: * There's a property in xwiki.cfg to enable different syntaxes: # [Since 1.6RC1] Defines the list of supported syntaxes # Available syntaxes are: # xwiki/1.0, xwiki/2.0, confluence/1.0, jspwiki/1.0, creole/1.0, # mediawiki/1.0, xhtml/1.0, twiki/1.0 xwiki.rendering.syntaxes = xwiki/1.0, xwiki/2.0 * It defaults to XWiki Syntax 1.0 and 2.0 (because the other syntaxes are not quite ready) * I'm adding a new XWiki API: XWiki.getConfiguredSyntaxes() * Any user will be able to see the list of configured syntaxes in wiki edit mode Please shout quickly if you don't think this is a good idea. Thanks -Vincent

16 years, 11 months

2
2
0 0

[xwiki-devs] [Summary] Bug fixing week result - Week of the 22/09/2008

by Vincent Massol

Hi devs, Here's the result of our bug fixing week (31 bugs fixed). Congrats to the following XWiki committers who have participated: Vincent - 8 Thomas - 5 Anca - 4 Sergiu - 4 Artem - 4 Jerome - 6 Out of these,a very special thanks to the committers who fixed *existing* jira issues (unlike myself since I have only fixed bugs on what I was working on, i.e. rendering). Let's hope even more committers participate next time (we are about 15 committers and 6 have participated). Note that we should continue to do our Wednesday bug fixing day too, starting next week. Issues fixed: [XWIKI-2691] Support nesting styles (bold, italic, etc) in the new rendering [XAWM-88] WikiManager plugin doesn't works in sub wikis. [XWIKI-2694] Top level element should be separated by 2 new lines in the XWiki Syntax renderer [XWIKI-2699] Underline elements are not recognized when saved [XWIKI-2700] XHTMLRenderer does not escape XML entities [XWIKI-2702] api.Document#getObjects(class, key, value) don't works for non string properties [XWIKI-2701] Events renderer does not escape attributes [XWS-163] The new XWS Administration interface breaks the underlying XE administration interface [XWIKI-2690] Doing Save and Continue when editing a section displays full content in editor [XWIKI-2706] The (% style="" %) syntax is applied to all items afterwards [XWIKI-2709] XHTMLRenderer does not output span element around wikicreatelink links [XSALBATROSS-39] There is no proper CSS for <blockquote> in the Albatross skin [XSTOUCAN-51] There is no proper CSS for <blockquote> in the Toucan skin [XWS-55] In a photo galerie the "Uploaded on" sometimes overlap its picture box [XE-310] XWiki.Treeview needs programming rights [XWIKI-2712] Some info is missing in object diff when object delete is present [XWIKI-2530] Problem with label when comparing 2 versions having a comment change [XWS-166] When deleting a photo gallery, activity events are generated for each deleted picture [XWS-168] Activity event displayed on space dashboard when deleting a photo gallery present a link to the deleted gallery [XWIKI-2060] Rights Management interface should support adding groups into groups [XWATCH-223] Article titles should be escaped for wiki syntax when printed in the press review [XWATCH-187] WatchCode.LoadingStatus produces too many empty versions of WatchCode.WatchVersionClass [XWATCH-225] Limit does not work for press review macros [XWIKI-1983] "Version $request.rev2" displayed in the version compare interface [XWIKI-2648] Chart Plugin fails in XE 1.6M1 [XSKINX-7] Cache policy: forbid does not actually prevent caching [XSKINX-5] JS should be forced to UTF-8 [XSKINX-6] Language-dependent extensions should be cached separated [XSALBATROSS-40] Fix upper greek list support [XSTOUCAN-52] Greek Numbered lists do not work anymore [XWATCH-168] Search field needs a click on the 'OK'-button, 'Enter' is not working More details at http://tinyurl.com/3n8jnt Unfortunately we're still off by 14 bugs in the past 3 months. We need to continue the effort. Thanks -Vincent

16 years, 11 months

2
2
0 0

[xwiki-devs] Not Able To See The Comment's

by Prathap Pandian

Hi, I have add the comment from the inline form (/xwiki/bin/inline/XWiki/). Now i can't able to see it any where. Can any one tell me we can i able to see the comment. -- Prathap

16 years, 11 months

1
1
0 0

[xwiki-devs] building XWiki

by [Ricardo Rodriguez] Your EPEC Network ICT Team

Hi all, Please, allow me a simple question or, much better, to confirm if I am well understanding the process. Once I get Maven installed and working, I understand that now it is possible to build the whole XWiki modules. But this will be also possible by installing an IDE as Eclipse. Maven is always required for this process, but by using Subclipse, M2Eclipse and WTP the whole process can be done from within Eclipse. Please, is this correct? Thanks! Best, Ricardo -- Ricardo Rodríguez Your EPEC Network ICT Team

16 years, 11 months

3
6
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs