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

[xwiki-devs] How to work with workspace withought log in

by Afzal Sharif

Hi , Now I have studied most of the source code for using "xWiki Workspace" . Now I want to integrate xwiki workspace features with my application. Can any give idea how to plan and start my work at coding level. Now I understand architecture of this application and how it is written. My Requirement : I have one 'UserProfile' page. User is already login in that page. The same user now want to click the 'widget of wiki' at 'UserProfile' and he should directly enter to workspace page , where he can create and work in workspace. Thanks , Md Afzal Sharif =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

17 years, 1 month

1
0
0 0

[xwiki-devs] parameters for context generation/customisation

by Amit Chawla

Can someone tell me which actionclass is fired when the applicaiton starts. I want to know this to understand how the 'xwiki-context' is generated so that I can customise it. ac

17 years, 1 month

2
1
0 0

Re: [xwiki-devs] [xwiki-notifications] r11747 - platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/java/com/xpn/xwiki/tool/doc

by Vincent Massol

Jerome, You shouldn't name your test with Abstract as classes starting with Abstract are excluded from tests by default. Thanks -Vincent On Aug 11, 2008, at 12:38 PM, jvelociter (SVN) wrote: > Author: jvelociter > Date: 2008-08-11 12:38:43 +0200 (Mon, 11 Aug 2008) > New Revision: 11747 > > Added: > platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/ > java/com/xpn/xwiki/tool/doc/AbstractDocumentMojoTest.java > Removed: > platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/ > java/com/xpn/xwiki/tool/doc/UpdateDocumentMojoTest.java > Log: > Renamed UpdateDocumentMojoTest to AbstractDocumentMojoTest to match > the tested class > > > Copied: platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/ > test/java/com/xpn/xwiki/tool/doc/AbstractDocumentMojoTest.java (from > rev 11746, platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/ > test/java/com/xpn/xwiki/tool/doc/UpdateDocumentMojoTest.java) > =================================================================== > --- platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/ > java/com/xpn/xwiki/tool/doc/ > AbstractDocumentMojoTest.java (rev 0) > +++ platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/ > java/com/xpn/xwiki/tool/doc/AbstractDocumentMojoTest.java 2008-08-11 > 10:38:43 UTC (rev 11747) > @@ -0,0 +1,68 @@ > +/* > + * See the NOTICE file distributed with this work for additional > + * information regarding copyright ownership. > + * > + * This is free software; you can redistribute it and/or modify it > + * under the terms of the GNU Lesser General Public License as > + * published by the Free Software Foundation; either version 2.1 of > + * the License, or (at your option) any later version. > + * > + * This software is distributed in the hope that it will be useful, > + * but WITHOUT ANY WARRANTY; without even the implied warranty of > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU > + * Lesser General Public License for more details. > + * > + * You should have received a copy of the GNU Lesser General Public > + * License along with this software; if not, write to the Free > + * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA > + * 02110-1301 USA, or see the FSF site: http://www.fsf.org. > + */ > +package com.xpn.xwiki.tool.doc; > + > +import java.io.File; > +import java.io.FileReader; > +import java.net.URL; > + > +import com.xpn.xwiki.doc.XWikiDocument; > + > +import junit.framework.TestCase; > + > +/** > + * Tests for {@link AbstractDocumentMojo}. > + * > + * @version $Id: $ > + */ > +public class AbstractDocumentMojoTest extends TestCase > +{ > + /** > + * Test that a document loaded in memory from XML by the mojo > then written back to XML does not lose any > + * information/is not affected by the process > + */ > + public void testXMLDocumentLoading() throws Exception > + { > + AttachMojo mojo = new AttachMojo(); > + > + URL resURL = this.getClass().getResource("/ > SampleWikiXMLDocument.input"); > + File resourceFile = new File(resURL.getPath()); > + FileReader fr = new FileReader(resourceFile); > + char[] bytes = new char[(int) resourceFile.length()]; > + fr.read(bytes); > + String inputContent = new String(bytes); > + > + assertTrue(inputContent.contains("<class>")); > + > + XWikiDocument doc = mojo.loadFromXML(resourceFile); > + assertEquals(doc.getName(), "Install"); > + > + File outputFile = File.createTempFile("output", "xml"); > + mojo.writeToXML(doc, outputFile); > + > + fr = new FileReader(outputFile); > + bytes = new char[(int) outputFile.length()]; > + fr.read(bytes); > + String outputContent = new String(bytes); > + > + // Check that we did not lose the class definition during > the loading from XML/writing to XML process. > + assertTrue(outputContent.contains("<class>")); > + } > +} > > Deleted: platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/ > test/java/com/xpn/xwiki/tool/doc/UpdateDocumentMojoTest.java > =================================================================== > --- platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/ > java/com/xpn/xwiki/tool/doc/UpdateDocumentMojoTest.java 2008-08-11 > 08:15:58 UTC (rev 11746) > +++ platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/ > java/com/xpn/xwiki/tool/doc/UpdateDocumentMojoTest.java 2008-08-11 > 10:38:43 UTC (rev 11747) > @@ -1,68 +0,0 @@ > -/* > - * See the NOTICE file distributed with this work for additional > - * information regarding copyright ownership. > - * > - * This is free software; you can redistribute it and/or modify it > - * under the terms of the GNU Lesser General Public License as > - * published by the Free Software Foundation; either version 2.1 of > - * the License, or (at your option) any later version. > - * > - * This software is distributed in the hope that it will be useful, > - * but WITHOUT ANY WARRANTY; without even the implied warranty of > - * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU > - * Lesser General Public License for more details. > - * > - * You should have received a copy of the GNU Lesser General Public > - * License along with this software; if not, write to the Free > - * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA > - * 02110-1301 USA, or see the FSF site: http://www.fsf.org. > - */ > -package com.xpn.xwiki.tool.doc; > - > -import java.io.File; > -import java.io.FileReader; > -import java.net.URL; > - > -import com.xpn.xwiki.doc.XWikiDocument; > - > -import junit.framework.TestCase; > - > -/** > - * Tests for {@link AbstractDocumentMojo}. > - * > - * @version $Id: $ > - */ > -public class UpdateDocumentMojoTest extends TestCase > -{ > - /** > - * Test that a document loaded in memory from XML by the mojo > then written back to XML does not lose any > - * information/is not affected by the process > - */ > - public void testXMLDocumentLoading() throws Exception > - { > - AttachMojo mojo = new AttachMojo(); > - > - URL resURL = this.getClass().getResource("/ > SampleWikiXMLDocument.input"); > - File resourceFile = new File(resURL.getPath()); > - FileReader fr = new FileReader(resourceFile); > - char[] bytes = new char[(int) resourceFile.length()]; > - fr.read(bytes); > - String inputContent = new String(bytes); > - > - assertTrue(inputContent.contains("<class>")); > - > - XWikiDocument doc = mojo.loadFromXML(resourceFile); > - assertEquals(doc.getName(), "Install"); > - > - File outputFile = File.createTempFile("output", "xml"); > - mojo.writeToXML(doc, outputFile); > - > - fr = new FileReader(outputFile); > - bytes = new char[(int) outputFile.length()]; > - fr.read(bytes); > - String outputContent = new String(bytes); > - > - // Check that we did not lose the class definition during > the loading from XML/writing to XML process. > - assertTrue(outputContent.contains("<class>")); > - } > -} > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications

17 years, 1 month

1
0
0 0

[xwiki-devs] Writing an XWiki-GWT Calendar

by Samir Chakour

dear all xwiki developer, I'm writing a new XWiki Calendar, the application is written fully in GWT using the XWiki-GWT service methods, in the events module, I asking myself some questions about the events creation feature, there are several ways to do, so the first one is to create a document by calendar-event, the second one is to create a document that may contain several events, the last method can also be divided into two others, one document by an xwiki-user or one document for all users can someone help me to make the right choice? thanks is advanced _________________________________________________________________ Contrôlez les personnes autorisées à parler à vos enfants sur MSN / Windows Live Messenger ! http://www.windowslive.fr/controleparental/default.asp

17 years, 1 month

2
2
0 0

[xwiki-devs] import .xar file

by raja raja

hai how can i import .xar file through coding (velocity), any one help me, regards Sekar...

17 years, 1 month

2
1
0 0

[xwiki-devs] [proposal] Change XWiki Watch distribution

by Anca Paula Luca

Hi devs, Currently XWiki Watch is built as a XWiki application, with no server code, distributable as a xar archive, using only xwiki-web-gwt's XWikiService to communicate with XWiki. While this approach has major advantages from the application accessibility point of view (it can be easily downloaded and installed), the drawback is the big amount of functionality that needs to be implemented on the client side (even if with GWT), with main impact on the application performance (javascript execution in the browser, data transfer, asynchronous calls). I propose to change the current approach and create XWatch server / service and distribute XWatch as a zip / war because: * it improves code performance: less javascript to execute on client side, less network traffic; lighter for the client overall * removing the .xar constraint and distributing watch as zip / war would allow XWatch dependency on plugins / modules versions independent from XE. * some Watch features already need some kind of administration on the hosting machine (emailing press reviews needs a running mail delivery system on the server). As I mentioned already, the only thing we would lose through this change is the possibility of installing XWatch as a simple xar (I am not currently very aware of the amount of users downloading and installing watch as a .xar and not being able to do it otherwise, so if you can give me some info on that...) Since I feel the gains would be above the losses, I am +1 for the switch, WDYT?

17 years, 1 month

8
7
0 0

Re: [xwiki-devs] [xwiki-notifications] r11689 - in platform: skins/trunk/albatross/src/main/resources/albatross web/trunk/standard/src/main/webapp/templates

by Vincent Massol

Maybe this requires a jira issue for Albatross skin too? I know it's a bit of a pain but since we're releasing them separately... Maybe it's a signal that the skins are not very well separated from the core? Thanks -Vincent On Aug 6, 2008, at 6:50 PM, jvdrean (SVN) wrote: > Author: jvdrean > Date: 2008-08-06 18:50:08 +0200 (Wed, 06 Aug 2008) > New Revision: 11689 > > Modified: > platform/skins/trunk/albatross/src/main/resources/albatross/ > print.css > platform/web/trunk/standard/src/main/webapp/templates/stylesheets.vm > Log: > XWIKI-2335 : Printing without using the print template only prints > the first page > > Applied patch from Evelina Slatineanu with a small modification. > > Modified: platform/skins/trunk/albatross/src/main/resources/ > albatross/print.css > =================================================================== > --- platform/skins/trunk/albatross/src/main/resources/albatross/ > print.css 2008-08-06 15:12:06 UTC (rev 11688) > +++ platform/skins/trunk/albatross/src/main/resources/albatross/ > print.css 2008-08-06 16:50:08 UTC (rev 11689) > @@ -17,4 +17,16 @@ > padding: 10px; > text-align: justify; > float: none !important; > -} > \ No newline at end of file > +} > +#rightPanels, #leftPanels, #actionmenu { > + display: none; > +} > +#globallinks { > + display: none; > +} > +#headerspace { > + margin:0 !important; > +} > +#contentcolumn .main { > + margin:0 !important; > +} > > Modified: platform/web/trunk/standard/src/main/webapp/templates/ > stylesheets.vm > =================================================================== > --- platform/web/trunk/standard/src/main/webapp/templates/ > stylesheets.vm 2008-08-06 15:12:06 UTC (rev 11688) > +++ platform/web/trunk/standard/src/main/webapp/templates/ > stylesheets.vm 2008-08-06 16:50:08 UTC (rev 11689) > @@ -4,10 +4,8 @@ > #set ( $defaultstyle = "style.css" ) > #end > #set( $defaultStyleURL = $xwiki.getSkinFile($defaultstyle, true) ) > -<link href="$defaultStyleURL" rel="stylesheet" type="text/css" /> > -#if ( $printss ) > - <link href="$xwiki.getSkinFile("print.css", true)" > rel="stylesheet" type="text/css"/> > -#end > +<link href="$defaultStyleURL" rel="stylesheet" type="text/css" > media="all" /> > +<link href="$xwiki.getSkinFile("print.css", true)" rel="stylesheet" > type="text/css" media="print" /> > ## The stylesheets configuration option allows to override the > alternate stylesheets > ## style1.css, style2.css and style3.css > #set ( $stylesheets = $xwiki.getWebPreference("stylesheets") )

17 years, 1 month

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r11688 - enterprise/trunk/distribution-test/selenium-tests/src/test/it/com/xpn/xwiki/it/selenium enterprise/trunk/distribution-test/selenium-tests/src/test/it/com/xpn/xwiki/it/selenium/framework platform/core/trunk/xwiki-core/src/main/resources platform/skins/trunk/albatross/src/main/resources/albatross platform/skins/trunk/albatross/src/main/resources/albatross/scripts platform/skins/trunk/toucan/src/main/resources/toucan platform/web/trunk/standard/src/main/webapp/te

by Vincent Massol

Hi, Two comments: * This email was sent twice: once to the enterprise@ mailing list and once to the platform@ mailing list. We need to talk to Raff so that duplicate emails are not sent. * I think we're missing some JIRA issues for Toucan and Albatross skins. Otherwise the release notes for them won't contain the changes below. Thanks -Vincent On Aug 6, 2008, at 5:12 PM, jvdrean (SVN) wrote: > Author: jvdrean > Date: 2008-08-06 17:12:06 +0200 (Wed, 06 Aug 2008) > New Revision: 11688 > > Added: > enterprise/trunk/distribution-test/selenium-tests/src/test/it/com/ > xpn/xwiki/it/selenium/DocExtraTest.java > platform/web/trunk/standard/src/main/webapp/templates/information.vm > platform/web/trunk/standard/src/main/webapp/templates/ > informationinline.vm > Modified: > enterprise/trunk/distribution-test/selenium-tests/src/test/it/com/ > xpn/xwiki/it/selenium/AllTests.java > enterprise/trunk/distribution-test/selenium-tests/src/test/it/com/ > xpn/xwiki/it/selenium/KeyboardShortcutsTest.java > enterprise/trunk/distribution-test/selenium-tests/src/test/it/com/ > xpn/xwiki/it/selenium/framework/AbstractXWikiTestCase.java > enterprise/trunk/distribution-test/selenium-tests/src/test/it/com/ > xpn/xwiki/it/selenium/framework/AlbatrossSkinExecutor.java > enterprise/trunk/distribution-test/selenium-tests/src/test/it/com/ > xpn/xwiki/it/selenium/framework/SkinExecutor.java > platform/core/trunk/xwiki-core/src/main/resources/ > ApplicationResources.properties > platform/core/trunk/xwiki-core/src/main/resources/ > ApplicationResources_fr.properties > platform/skins/trunk/albatross/src/main/resources/albatross/ > classes.css > platform/skins/trunk/albatross/src/main/resources/albatross/ > colorsblack.css > platform/skins/trunk/albatross/src/main/resources/albatross/ > screenlayout.css > platform/skins/trunk/albatross/src/main/resources/albatross/ > scripts/shortcuts.js > platform/skins/trunk/albatross/src/main/resources/albatross/ > style.css > platform/skins/trunk/albatross/src/main/resources/albatross/xwiki.js > platform/skins/trunk/toucan/src/main/resources/toucan/toucan.css > platform/web/trunk/standard/src/main/webapp/templates/ > attachmentsinline.vm > platform/web/trunk/standard/src/main/webapp/templates/ > commentsinline.vm > platform/web/trunk/standard/src/main/webapp/templates/contentview.vm > platform/web/trunk/standard/src/main/webapp/templates/docextra.vm > platform/web/trunk/standard/src/main/webapp/templates/ > historyinline.vm > platform/web/trunk/standard/src/main/webapp/templates/macros.vm > platform/web/trunk/standard/src/main/webapp/templates/menuview.vm > platform/web/trunk/standard/src/main/webapp/templates/tagedit.vm > platform/web/trunk/standard/src/main/webapp/templates/xwikivars.vm > Log: > XWIKI-2606 : Improve pages footer (comments, attachments, etc) > XWIKI-522 : Add a Document Information section below the document > > Implemented. > [snip]

17 years, 1 month

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r11685 - in platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src: . test test/java test/java/com test/java/com/xpn test/java/com/xpn/xwiki test/java/com/xpn/xwiki/tool test/java/com/xpn/xwiki/tool/doc test/resources

by Vincent Massol

Hi Jerome, see below On Aug 6, 2008, at 12:53 PM, jvelociter (SVN) wrote: > Author: jvelociter > Date: 2008-08-06 12:53:03 +0200 (Wed, 06 Aug 2008) > New Revision: 11685 > > Added: > platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/ > platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/java/ > platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/java/ > com/ > platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/java/ > com/xpn/ > platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/java/ > com/xpn/xwiki/ > platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/java/ > com/xpn/xwiki/tool/ > platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/java/ > com/xpn/xwiki/tool/doc/ > platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/java/ > com/xpn/xwiki/tool/doc/UpdateDocumentMojoTest.java > platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/ > resources/ > platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/ > resources/SampleWikiXMLDocument.input > Log: > XTXMLDOC-6 XClasses lost when exporting documents with existing > objects > * Added a test that proves we lose classes when writting back the > doc to XML. > > > Added: platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/ > test/java/com/xpn/xwiki/tool/doc/UpdateDocumentMojoTest.java > =================================================================== > --- platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/ > java/com/xpn/xwiki/tool/doc/ > UpdateDocumentMojoTest.java (rev 0) > +++ platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/ > java/com/xpn/xwiki/tool/doc/UpdateDocumentMojoTest.java 2008-08-06 > 10:53:03 UTC (rev 11685) > @@ -0,0 +1,85 @@ > +/* > + * See the NOTICE file distributed with this work for additional > + * information regarding copyright ownership. > + * > + * This is free software; you can redistribute it and/or modify it > + * under the terms of the GNU Lesser General Public License as > + * published by the Free Software Foundation; either version 2.1 of > + * the License, or (at your option) any later version. > + * > + * This software is distributed in the hope that it will be useful, > + * but WITHOUT ANY WARRANTY; without even the implied warranty of > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU > + * Lesser General Public License for more details. > + * > + * You should have received a copy of the GNU Lesser General Public > + * License along with this software; if not, write to the Free > + * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA > + * 02110-1301 USA, or see the FSF site: http://www.fsf.org. > + */ > +package com.xpn.xwiki.tool.doc; > + > +import java.io.File; > +import java.io.FileReader; > +import java.io.IOException; > +import java.net.URL; > + > +import org.apache.maven.plugin.MojoExecutionException; > + > +import com.xpn.xwiki.doc.XWikiDocument; > + > +import junit.framework.TestCase; > + > +/** > + * Test for {@link AbstractDocumentMojo} > + * > + * @version $Id: $ > + */ > +public class UpdateDocumentMojoTest extends TestCase > +{ > + > + /** > + * Test that a document loaded in memory from XML by the mojo > then written back to XML does not lose any > + * information/is not affected by the process > + */ > + public void testXMLDocumentLoading() > + { > + AttachMojo mojo = new AttachMojo(); > + URL resURL = this.getClass().getResource("/ > SampleWikiXMLDocument.input"); > + try { > + File resourceFile = new File(resURL.getPath()); > + XWikiDocument doc = mojo.loadFromXML(resourceFile); > + FileReader fr = new FileReader(resourceFile); > + char[] bytes = new char[(int) resourceFile.length()]; > + fr.read(bytes); > + String inputContent = new String(bytes); > + > + assertTrue(inputContent.contains("<class>")); > + > + assertEquals(doc.getName(), "Install"); > + > + File outputFile = File.createTempFile("output", "xml"); > + mojo.writeToXML(doc, outputFile); > + > + fr = new FileReader(outputFile); > + bytes = new char[(int) outputFile.length()]; > + fr.read(bytes); > + String outputContent = new String(bytes); > + > + // Test that prove class definitions are lost during > the process of loading/writing back the XML document. > + // It currently fail, see http://jira.xwiki.org/jira/browse/XTXMLDOC-6 > + assertTrue(outputContent.contains("<class>")); > + > + // check there is no diff bewteen input and output > file, as no transformation > + // has been applied. > + assertEquals(inputContent, outputContent); > + > + } catch (MojoExecutionException e) { > + fail(); > + } catch (IOException e) { > + fail("Could not load wiki xml document resource file."); > + } The best practice is to not use a try/catch block and instead have the test signature throws an Exception. That's unless you're specifically testing for an exception but that's not the case here. Thanks -Vincent

17 years, 1 month

1
0
0 0

[xwiki-devs] Error number 3 in 0: Could not initialize main XWiki context

by Arpit Jain

Hi, I just upgraded my system and before that Xwiki was running fine. Now, it is giving me error HTTP ERROR: 500 Error number 3 in 0: Could not initialize main XWiki context Wrapped Exception: Error number 3001 in 3: Cannot load class com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager from param xwiki.store.migration.manager.class Wrapped Exception: net.sf.cglib.proxy.Enhancer RequestURI=/xwiki/bin/view/XWSAdmin/ Complete logs here : http://pastie.org/249438 Please help, it's been more than couple of hours since I am stuck in this. I didn't change any configuration during kernel upgrade. -- Arpit Jain http://www.intinno.com

17 years, 1 month

4
8
0 0

[xwiki-devs] [GSOC] xwiki API content assistance complited

by malaka ekanayake

Hi devs, I have complied the content assistance for xwiki API.Now the proposals are readout from a seperate resource file.There are seperate file for each context type ( i.e seperate files for $xwiki ,$doc .. ) .At the moment the API information is stored in the files in the following format xwiki.copyDocument(java.lang.String docname, java.lang.String sourceWiki,java.lang.String targetWiki, java.lang.String wikilanguage) is transtatet to a single line entry in the xwiki.txt resourse file as bellow copyDocument String docname String sourceWiki String targetWiki String wikilanguage Now i'm looking at velocity variable proposal and error notification.In order to provide content assistance and error marking, there is a requirement to parse and build the an object model of document which contains both XWiki and Velocity. AFAIK, XDOM only supports XWiki. Is there an object model which can r present these two languages. For velocity code, there is a possibility to use the parser shipped with Apache Velocity. But then we need to develop our own object model. Any help would be greatly appreciated. -- Malaka

17 years, 1 month

2
1
0 0

[xwiki-devs] new rendering syntax concerning Groovy

by Pascal Voitot

Hello, Do you foresee a special syntax for groovy scripts as you already have for velocity using {{velocity}} with some more features? My idea is to be able to code cleanly using groovy and to put some "generic" part of scripts in separated documents and to be able to import them in other docs containing other parts of scripts. It would be really nice to be able to type some part of scripts or to define some groovy classes in a page and tell "this is groovy code which is not "WIKI-renderable" as is". Then we could simply import/include this script in another page (just paste the code without any rendering) using something like #include("MySpace.MyGroovyDoc"). xwiki.parseGroovyXXX is useful sometimes but not when you only want to include some part of scripts. Existing #includeXXX macros always render the content and here I only want to paste a script from somewhere else (xwiki.getDocument("").getContent() in fact) Moreover the idea would be also to allow using both "xwiki.parseGroovy" and the #include macro for the same groovy "document". For the time being, one need to use the trick /* groovygroovy #* */ /* *# */ and then you are condemned to use xwiki.parseGroovyXXX because no other function can interprete this tricky syntax. best regards Pascal

17 years, 1 month

3
15
0 0

[xwiki-devs] Fwd: [ANN] Apache FOP 0.95 Released

by Vincent Massol

We should try it. Who's game to upgrade our FOP version and verify our PDF/RTF exports still work? Thanks -Vincent Begin forwarded message: > From: Jeremias Maerki <jeremias(a)apache.org> > Date: August 6, 2008 8:05:47 AM CEDT > To: fop-dev(a)xmlgraphics.apache.org, fop- > users(a)xmlgraphics.apache.org, general(a)xmlgraphics.apache.org, general(a)xml.apache.org > , announce(a)apache.org, XSL-FO(a)yahoogroups.com, www-xsl-fo(a)w3.org > Subject: [ANN] Apache FOP 0.95 Released > > Apache FOP (Formatting Objects Processor) is a print formatter > driven by > XSL Formatting Objects [1] and an output independent formatter. It > is a > Java application that reads a formatting object tree and renders the > resulting pages to a specified output. Output formats currently > supported include PDF, PS, PCL, AFP, Print and TIFF/PNG. Apache FOP is > Open Source software and published under the Apache License v2.0. > > It took longer than expected but we're happy to present the final > Apache > FOP 0.95 stable release. This is basically a bugfix release to > 0.95beta. > The most important changes since the previous stable release (0.94) > are: > - many bug fixes and improvements in tables, better support for keeps > and breaks, new features: conditional borders and background on > columns and header/footer/body; > - better image handling thanks to the new image loading framework > provided by the Apache XML Graphics Commons dependency; > - improvements and bugfixes for font handling and font > auto-detection/-registration; > - performance improvements and memory optimizations for the property > handling in the FO tree. > - elimination of a potential multi-threading problem. > - some feature enhancements for RTF output (partial fo:leader support, > fo:page-number-citation) > > Please note that support for Java 1.3 has been dropped. Only one > type of > binaries is provided now, that will run on 1.4+ JREs. > > Other important release notes are available at > http://xmlgraphics.apache.org/fop/0.95/releaseNotes_0.95.html > > For a more complete list of changes, please visit > http://xmlgraphics.apache.org/fop/0.95/changes_0.95.html > > For download information, see the following page: > http://xmlgraphics.apache.org/fop/download.html > > > [1] http://www.w3.org/TR/xsl11/ > > > On behalf of the Apache XML Graphics team, > Jeremias Maerki

17 years, 1 month

3
2
0 0

[xwiki-devs] souce-code setup with eclipse !

by Amit Chawla

Hi, I am student with RMIT University and I am working on a project on open-source wiki application. I have a basic idea of velocity, struts, eclipse, maven, java, xml, etc. as a part of the courses that I am doing in university. Thats is why I looked at the xwiki workspace application. To build my project, I went thru various helps available at xwiki site like: - http://dev.xwiki.org - http://platform.xwiki.org I want to study the source code so that I can understand it better. So, I want to see the source code in eclipse. I went thru the help on above site but I am not sure how to deploy the code in eclipse. I wanted this to do this to make changes in the code and run it to see how it affects the existing environment. In my earlier projects, I had the distribution of files (.war) which included both source and classes, but xwiki_workspaces.war has only class distribution. So, i am unable to make changes and see its affects. Any help would be appreciated. ac

17 years, 1 month

2
1
0 0

[xwiki-devs] Access page object attribute and unrendered page content through SOAP interface

by Hoani Cross

Hi, Is there any way to access to page object attributes and/or unrendered page content ? Thanks in advance. -- Hoani CROSS Globotraders Tahiti Founder [http://globotraders-tahiti.com]

17 years, 1 month

4
4
0 0

[xwiki-devs] Session Variables

by MikSan

How can I set and get a new session variable in xwiki. Something like: context.getRequest().getHttpServletRequest().getSession().setAttribute("The_name",value); context.getRequest().getHttpServletRequest().getSession().getAttribute("The_name"); Thanks for the help -- View this message in context: http://n2.nabble.com/Session-Variables-tp674006p674006.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

17 years, 1 month

2
1
0 0

[xwiki-devs] XWiki Velocity Documentation

by Ludovic Dubost

Hi, I've published in svn a tool based on velocidoc (http://sourceforge.net/projects/velocidoc/) to allow to generate javadoc style documentation for velocity macros. You'll find links to it and an example of generating for the XWiki Platform Web templates directory on the wiki: http://dev.xwiki.org/xwiki/bin/view/Drafts/Documenting+XWiki+Velocity+Macros From now on we should start documeting velocity macros with the following syntax: #** * Description of the macro * @param paramname desc * @param paramname desc * @author author *# A later improvement will allow parsing XWiki xml files and extract documentation of the pages in the same format. Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

17 years, 1 month

7
9
0 0

[xwiki-devs] [proposal] Refactor pages footer (comments, attachments, etc)

by Jean-Vincent Drean

Hi XWikiers, I've recently worked on a refactoring of the page footer and I'd like to get some feedback about it. Features: * New "information" section displaying parent, backlinks, included pages, etc * New "history" section (as described in the original albatross spec) * Tags edition with suggest (information) * Lazy loading of sections via AJAX * Url hash (#comments) taken into account, for example autoload/scroll after having upladed an attachments. * Unobstrusive JavaScript (links are working with JS turned off) Since a demo is worth a thousand words, you can try it here : http://jv.myxwiki.org/xwiki/bin/view/Main/ WDYT ? Thanks, JV.

17 years, 1 month

6
23
0 0

[xwiki-devs] question about integration/roadmap of the new modular architecture/rendering engine etc...

by Pascal Voitot

Hello, I have been working for some time compiling my own snapshot XWikiEnterprise 1.5 (I was following the trunk in fact) but I have stopped following the trunk in order to test some things... Apparently now the version is 1.6... Before looking directly in the code with my own eyes, I prefer asking a few questions about all the new features (modular architecture, new rendering, new macros etc...): Are they integrated in the last available tags? (the modular architecture has appeared long time ago but it's not the default archi yet) Does it break any compatibility? Do you still use the old implementations as the default one? When do you intend to replace the old archi with the new one? Do you have an idea of the roadmap for this? Is version 2.0 the version when the old implementations will disappear? I need to have such information in order to know if I go on upgrading using the trunk because it brings some bug corrections without breaking any existing things? or do I use a tag version to have a stable and fixed platform? I don't fear using new versions and examining bugs and even correcting them as long as they don't destroy my database? Best regards Pascal

17 years, 1 month

2
1
0 0

[xwiki-devs] [GSOC] [WebDAV] Interoperability

by Ludovic Dubost

Hi Asiri, I've worked a little on WebDAV interoperability and made quite some progress. We now have on Mac: - WebDAV working for browsing and downloading files - WebDAV working for drag and dropping files - WebDAV working with vi in view, edit and save (it says on save that the file was changed while editing although it's not true) - WebDAV working with a patched version of OpenOffice (with a fix for locking) or with official NeoOffice in view edit and save - WebDAV working with TextEdit in view, edit but NOT save Mac OSX generates phony attachments to store temporart files. TextEdit fails because it tries to create a file then MOVE it (it might be because of the same locking issue as OpenOffice). And on Windows XP: With Novell NetDrive (mapping webdav to a driver letter): - WebDAV allowing browsing, dowloading , drag and dropping - WebDAV working with notepad and OpenOffice in view, edit, save With Microsoft Web Folders (2 versions on SP2 tested including the latest patch from Microsoft, SP3 would need to be tested) - WebDAV allowing browsing, dowloading , drag and dropping - WebDAV allowing to double click or open from notepad or OpenOffice but by copying to a temp read only file. You then can SAVE AS to the WebDAV folder. It might be possible that MS Office allows to handle this differently. With Microsoft WebDAV redirector (same one available on Vista) - Nothing works at all. I've tried almost all I could to try to use it to map a network drive on the webdav folder.. The constraints are pretty hard on the web dav server and even though I was not able to have it fully working. I find it a dead end. On Windows Vista: - Nothing works at all It seems possible to install a Web Folders package on Vista and have the behavior of XP. In any case, the Microsoft solution is sub-optimal on Windows. Novell NetDrive (free download findable on the web) or WebDrive (it's commercial counterpart) seem to be much more efficient. Maybe MSOffice works correctly with WebFolders but this needs to be tested. On Mac the behavior is pretty nice with the patched version of OpenOffice (patch is published there: http://tools.openoffice.org/issues/show_bug.cgi?id=81536 let's hope they put it in the standard distrib). Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

17 years, 1 month

5
16
0 0

Re: [xwiki-devs] [xwiki-notifications] r11670 - platform/core/trunk/xwiki-core

by vincent＠massol.net

I think we need a jira issue so that it appears in the release notes since upgrading hibernate is not a small thing. -Vincent On 8/4/08, SVN amelentev <platform-notifications(a)xwiki.org> wrote: > Author: amelentev > Date: 2008-08-04 19:28:00 +0200 (Mon, 04 Aug 2008) > New Revision: 11670 > > Modified: > platform/core/trunk/xwiki-core/pom.xml > Log: > [misc] fix antlr version conflict with struts & hibernate > update hibernate to 3.2.6 > > > Modified: platform/core/trunk/xwiki-core/pom.xml > =================================================================== > --- platform/core/trunk/xwiki-core/pom.xml 2008-08-04 17:24:32 UTC (rev > 11669) > +++ platform/core/trunk/xwiki-core/pom.xml 2008-08-04 17:28:00 UTC (rev > 11670) > @@ -297,6 +297,13 @@ > <groupId>struts</groupId> > <artifactId>struts</artifactId> > <version>1.2.9</version> > + <exclusions> > +  > + <exclusion> > + <groupId>antlr</groupId> > + <artifactId>antlr</artifactId> > + </exclusion> > + </exclusions> > </dependency> > >  > @@ -315,7 +322,7 @@ > <dependency> > <groupId>org.hibernate</groupId> > <artifactId>hibernate</artifactId> > - <version>3.2.5.ga</version> > + <version>3.2.6.ga</version> > </dependency> > >  > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications >

17 years, 1 month

2
1
0 0

Re: [xwiki-devs] Daily report

by Fabio Mancinelli

On 3 août 08, at 21:40, malaka ekanayake wrote: > Hi all, > > For the moment I would leave out the user defined macros and > concentrate on the error reporting and $xwiki API assistance. > > WDYT? > > As you have told, I started looking at the $xwiki API and the ways > to provide the content assistance. > > * But then I realized that it would be better off to provide content > assistance to xwiki and velocity. XWiki content assistance is > already implemented, I basically modified that implementation to > provide content assistance to Velociry directives and variables. > Ok. > * Earlier when the partition type was default_content there were > only xwiki syntax. But Now we can expect both xwiki and velocity > syntax. Now I need a way to provide completion proposals depending > on whether it is xwiki or velocity. Therefore I implemented a > DefaultCompletionProcessor which basicall delegates the computing of > proposals to the appropriate completionProcessor depending on xwki > or velocity. I didn' changed the functionaty of the exsisting > XwikiCompletionProcessor. > I was looking at the XWikiCompletionProcessor and it has indeed to be refactored because I think it's a bit messy. There are some idiosyncrasies, for example structural completion and link completion are done in this processor registered for the default content type, while there are already a lot of partition type to assign processors to (I will ask to Venkatesh for that). > * Providing content assistance for Velociry directives is completed. > The list of defined velocity variables can be extracted from the > velocity parser. I could complete processing of proposals for > variables using hardcoded list of variables. This can be replaced > once I integrate the Velocity parser. > Ok. > * When implementing above feature, i had to refactor the way, the > document is partitioned. This also resulted in some changes in > syntax colouring. > That's fine. > Herewith I have attached the patch files, because I can't commit the > code to sandbox. I've sent a mail regariding this to the mailing > list before. > I've see that you were able to commit. I will review the code asap and I'll get you feedback (I am abroad and the internet connection is not very good). > Now I am forcusing on provinding content assistance to the $xwiki > API and integration of velocity parser. > Ok. Great. Cheers, Fabio

17 years, 1 month

1
0
0 0

[xwiki-devs] Chart

by Bruno Amaro Almeida

Hi Devs I want to make a graph with a given table, but i don`t want to see the table in the xwiki page, so i`m trying to make the graph inside my function: Map data = new HashMap(); data.put("x", "1"); data.put("y", "110"); ChartingPlugin chartplugin = new ChartingPlugin("chartingplugin", ChartingPlugin.class.toString(), context); chartplugin.init(context); // ChartingPluginApi chart = new ChartingPluginApi(chartplugin,context); ChartParams chartParams = new ChartParams(); try { chartParams = new ChartParams(data, DefaultChartParams.getInstance(), true); chartParams.addParam(new MapChartParam("source=type:table", false)); chartParams.addParam(new MapChartParam("type=pie", false)); // chartParams.set("SOURCE", "type:table"); // chartParams.set("TYPE", "pie"); chartParams.check(); } catch (ParamException e) { } * Chart chart = new ChartImpl(chartParams,null,null); try { chart = chartplugin.generateChart(chartParams, context); } catch (GenerateException ge) { }* String title = chartParams.getString( ChartParams.TITLE_PREFIX+ChartParams.TITLE_SUFFIX); Integer height = chartParams.getInteger(ChartParams.HEIGHT); Integer width = chartParams.getInteger(ChartParams.WIDTH); Map imageAttr = chartParams.getMap(ChartParams.IMAGE_ATTRIBUTES); Map linkAttr = chartParams.getMap(ChartParams.LINK_ATTRIBUTES); // output the image links StringBuffer sbuffer = new StringBuffer(); sbuffer.append("<a href=\""+ chart.getPageURL() + "\" "); if (title != null) { sbuffer.append("title=\"" + title + "\""); } if (linkAttr != null) { Iterator it = linkAttr.keySet().iterator(); while (it.hasNext()) { String name = (String)it.next(); String value = (String)imageAttr.get(name); sbuffer.append(name+"=\"" + value + "\" "); } } sbuffer.append(">"); sbuffer.append("<img src=\""); sbuffer.append(chart.getImageURL()); sbuffer.append("\" "); if (title != null) { sbuffer.append("alt=\""+ title + "\" "); } sbuffer.append("height=\"" + height + "\" "); sbuffer.append("width=\"" + width + "\" "); if (imageAttr != null) { Iterator it = imageAttr.keySet().iterator(); while (it.hasNext()) { String name = (String)it.next(); if (name != ChartParams.HEIGHT && name != ChartParams.WIDTH) { String value = (String)imageAttr.get(name); sbuffer.append(name + "=\"" + value + "\" "); } else { } } } sbuffer.append("/>"); sbuffer.append("</a>"); return sbuffer.toString(); I get some problems in : * Chart chart = new ChartImpl(chartParams,null,null); try { chart = chartplugin.generateChart(chartParams, context); } catch (GenerateException ge) { } *I think is some problem with the source, Any ideas? Thanks in advance :)

17 years, 1 month

2
5
0 0

[xwiki-devs] Tables Id

by MikSan

Hi all I have a question when I insert a table each table recives an ID the can be used to define wich table to use to creat a Chart. My question is How can I obtain this id. for Example I want to do the following This is Table ID = ? (0) {table} A | B 1 | 2 {table} This is Table ID = ? (1) {table} E | D 1 | 2 {table} And if I delete table 0: This is Table ID = ? (0) {table} E | D 1 | 2 {table} Hope Someone can help me thanks. -- View this message in context: http://n2.nabble.com/Tables-Id-tp668637p668637.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

17 years, 1 month

2
1
0 0

[xwiki-devs] XWIKI - Space Export

by Prathap Pandian

Hi, How can i export single space in the xwiki. I searched in the Code Zone, but i didn't get any docuemnt. -- Prathap

17 years, 1 month

1
1
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