xwiki-devs May 2009

xwiki-devs@xwiki.org

37 participants
104 discussions

[xwiki-devs] [PROPOSAL] Use plain text renderer with ?xpage=plain

by Thomas Mortagne

Hi devs, In 2.0 architecture we have no way currently to print a strongly formatted text (like JSON) or simply a plain text without XHTML which we are doing generally using xpage=plain in XWiki 1.0 I propose to use the plain text renderer when xpage=plain and document is 2.0. The difference between the two is that in xwiki 1.0, wiki syntax generates xhtml when plain text renderer don't. But it's just because XWiki 1.0 does not ave the concept of different renders and the main goal of xpage=plain is JSON and things like that so this difference is not important IMO. Note that this is about supporting XWiki 1.0 "api", we need a generic way to indicate the renderer to use in the URL but that's another subject. For now we have to make xpage=plain works for both 1.0 and 2.0 content. WDYT ? -- Thomas Mortagne

15 years, 7 months

[xwiki-devs] Tree view structure in TOC

by CASTRO roney

Hello Everyone, I was looking forward to have a tree view structure very similar to the one presented in the table of contents in curriki (displayed in the bottom right of this website: http://www.curriki.org/xwiki/bin/view/Coll_curriki/RefineyourSearchforLearn… ) I sent an email to the webmaster of curriki (his answer is forwarded), and as instructed by him, I am sending an email to the developers list in order to ask for a guideline or even some code samples in order to implement this structure in my xwiki if possible. I am currently working with version XE 1.8.1 Thanks in advance for the help! Regards Roney Castro ________________________________________ From: Joshua Marks [mailto:jmarks@curriki.org] Sent: segunda-feira, 27 de abril de 2009 12:01 To: CASTRO roney Cc: webmaster(a)curriki.org Subject: RE: Table of contents in tree view Dear Rooney, We actually have two different tree displays we use, one for the subject/topic select list and one for the TOC. They us different JS libraries (One is Yahoo and one is EXTJS). In both cases we added this to the core xwiki for our application. The Curriki application and code can be found at http://curriki.xwiki.org<http://curriki.xwiki.org/>. If you send a message to the developers list (xwiki-devs), they can point you to some sample code I believe. All the best, Joshua Marks CTO Curriki: The Global Education and Learning Community jmarks(a)curriki.org www.curriki.org US 831-685-3511 ________________________________________ From: Melinda Lies [mailto:mlies@curriki.org] Sent: Monday, April 27, 2009 7:51 AM To: Joshua Marks Cc: webmaster(a)curriki.org Subject: Re: Table of contents in tree view See email below. melinda On Mon, Apr 27, 2009 at 10:49 AM, CASTRO roney <roney.CASTRO(a)gemalto.com> wrote: Hello, I manage an internal xwiki for my group, and I was looking for a way to create a tree structure view, similar to the one you have in your xwiki (displayed in the figure attached). Did you program this tree structure, or is it a default feature that I didn't find in my xwiki? I must say it looks really great! I was wondering if you could please share its code with me, in case you programmed it, or tell me which xwiki feature you used? Thanks in advance! Roney Castro -- -- Curriki 1615 L Street NW, Suite 650 Washington, DC 20036 www.curriki.org mlies(a)curriki.org Office - 202-626-8529 Fax - 202 626 8774

15 years, 7 months

[xwiki-devs] hitting return inside the comment text input field after writing a little commit comment justr returns to the view and throws away my content

by Henning Sprang

I just ran into this little, but very annoying problem, becaue I actually lost 15 minutes of editing: I entered some text in the page edit textfiled, but I also wanted to add a little save/commit comment. So I wrote some words into the the text input field, ad naturally, I hit return. The page view is shown, but all I entered into the text field is gone. Not exactly what I want when entering a save/commit comment, isn't it? Henning -- Henning Sprang http://www.sprang.de | http://lazyb0y.blogspot.com/

15 years, 7 months

Re: [xwiki-devs] [xwiki-notifications] r19341 - in platform/core/trunk/xwiki-rendering: . xwiki-rendering-tests/src/test/java/org/xwiki/rendering xwiki-rendering-tests/src/test/resources/section

by Vincent Massol

On May 4, 2009, at 5:34 PM, tmortagne (SVN) wrote: > Author: tmortagne > Date: 2009-05-04 17:34:15 +0200 (Mon, 04 May 2009) > New Revision: 19341 > > Added: > platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/test/ > resources/section/section10.test > Modified: > platform/core/trunk/xwiki-rendering/pom.xml > platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/test/ > java/org/xwiki/rendering/RenderingTests.java > Log: > XWIKI-3668: Problem when there is a {{velocity}} marker in a title : > double line under the title > > Modified: platform/core/trunk/xwiki-rendering/pom.xml > =================================================================== > --- platform/core/trunk/xwiki-rendering/pom.xml 2009-05-04 14:56:49 > UTC (rev 19340) > +++ platform/core/trunk/xwiki-rendering/pom.xml 2009-05-04 15:34:15 > UTC (rev 19341) > @@ -41,7 +41,7 @@ > <dependency> > <groupId>org.wikimodel</groupId> > <artifactId>org.wikimodel.wem</artifactId> > - <version>2.0.7-20090430</version> > + <version>2.0.7-20090504</version> > </dependency> > </dependencies> > </dependencyManagement> > > Modified: platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/ > src/test/java/org/xwiki/rendering/RenderingTests.java > =================================================================== > --- platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/ > test/java/org/xwiki/rendering/RenderingTests.java 2009-05-04 > 14:56:49 UTC (rev 19340) > +++ platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/ > test/java/org/xwiki/rendering/RenderingTests.java 2009-05-04 > 15:34:15 UTC (rev 19341) > @@ -179,6 +179,7 @@ > suite.addTestsFromResource("section/section7", false); > suite.addTestsFromResource("section/section8", false); > suite.addTestsFromResource("section/section9", false); > + suite.addTestsFromResource("section/section10", false); > > // Escaping > suite.addTestsFromResource("escape/escape1", false); > > Added: platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/ > test/resources/section/section10.test > =================================================================== > --- platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/ > test/resources/section/section10.test (rev 0) > +++ platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/ > test/resources/section/section10.test 2009-05-04 15:34:15 UTC (rev > 19341) > @@ -0,0 +1,33 @@ > + > .#-------------------------------------------------------------------------------- > +.input|xwiki/2.0 > +.# Verify that a header content can start on a new line Are you sure this is the correct comment? Thanks -Vincent > > + > .#-------------------------------------------------------------------------------- > += Title level 1 {{simplemacro}}{{/simplemacro}}= > +.#----------------------------------------------------- > +.expect|event/1.0 > +.#----------------------------------------------------- > +beginDocument > +beginSection > +beginHeader [1, HTitlelevel1] > +onWord [Title] > +onSpace > +onWord [level] > +onSpace > +onWord [1] > +onSpace > +onMacroInline [simplemacro] [] [] > +endHeader [1, HTitlelevel1] > +endSection > +endDocument > +.#----------------------------------------------------- > +.expect|xhtml/1.0 > +.#----------------------------------------------------- > +<h1 id="HTitlelevel1"><span>Title level 1 </span></h1> > +.#----------------------------------------------------- > +.expect|xwiki/2.0 > +.#----------------------------------------------------- > += Title level 1 {{simplemacro/}} = > +.#----------------------------------------------------- > +.input|xhtml/1.0 > +.#----------------------------------------------------- > +<h1 id="HTitlelevel1"><span>Title level 1 </span></h1> > \ No newline at end of file

15 years, 7 months

[xwiki-devs] Custom Editor Panel

by RalphS

Sorry if this has been asked before or is documented, I have found it neither in the mailing list archives nor in the docs. I have created a custom panel that I would like to be visible when a user edits a page using the WIKI or WYSYWIG editor. I have successfully created the panel and set its type to "edit". Now how do I add it to the panel column? In the panel wizard, only panels of type "view" are available. This appears logical to me, because editor panels are not as straightforward to set up as view panels are, since editor panels must somehow be assciated with one or multiples types of editors. E.g. the "Document Information" panel is only visible when the WIKI or WYSIWYG editor is active, which is exactly the behavior I whish for my panel. Could someone please give me a pointer to where this is documented or explain what I have to do? Thanks in advance and best regards, Ralph -- View this message in context: http://n2.nabble.com/Custom-Editor-Panel-tp2761144p2761144.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

15 years, 7 months

[xwiki-devs] [VOTE] Upgrade officeimporter to use JODConverter 3.0-beta-2 release and add support for auto-starting oo server

by Asiri Rathnayake

Hi Devs, Jodconverter 3.0-beta-2 version has been released: http://groups.google.com/group/jodconverter/browse_thread/thread/8b73b26b70… One of the most important fix for us is the first point mentioned there: "OOo is now started with -nofirststartwizard by default. This avoids the frequent problem of OOo refusing to work on a new machine because it's expecting somebody to accept its license dialogue even in -headless mode" Without this fix currently we have to copy an already initialized ooprofile directory to the destination server and point to it from xwiki.properties file. This is a pain. Also there are several other enhancements: http://code.google.com/p/jodconverter/issues/list?can=1&q=label%3ATarget-3.… Unfortunately some of the public APIs of jodconverter has been changed from beta-1 release to beta-2 release. But still, upgrading our officeimporter module to use this new jodconverter release will not require that much of code changes. Note: jodconverter is not available in any public maven repository AFAIK. So we need to release it to our externals repository as we did with the beta-1 version. The other feature is a frequently requested one (auto-strart) and admins are having a hard time without this feature :) Here is my +1 for both features. Thanks. - Asiri

15 years, 7 months

[xwiki-devs] [VOTE] What do we do with links inside links ?

by Thomas Mortagne

Hi devs, We have (at least) two issues about links inside links: http://jira.xwiki.org/jira/browse/XWIKI-3149 and http://jira.xwiki.org/jira/browse/XWIKI-3440 Basically the issue is that XHTML does not support links inside links. To fix this I see two possibilities: 1) valid in XDOM: this means XHTML renderer has to take care of this and skip link inside links 2) not valid in XDOM: this means each parser has to make sure not put link inside links in the XDOM +1 for 1) and -0 for 2) since it's a XHTML issue only and we could have some use cases supporting this like XWiki syntax support it. Thanks, -- Thomas Mortagne

15 years, 7 months

[xwiki-devs] recent problem with {{velocity}+{{html}}

by Pascal Voitot

Hello, I have compiled code directly from the trunk and I have a simple wiki page such as: {{velocity}} {{html}} #warning("(% style='font-size:120%' %) [[mylink>>myspace.mypage]]") {{/html}} {{/velocity}} and I get the following text: (% style='font-size:120%' %) [[mylink>>myspace.mypage]] The content in the velocity macro is not rendered. Ok apparently now, default {{html}} is {{html wiki="false"}} So I write: {{velocity}} {{html wiki="true"}} #warning("(% style='font-size:120%' %) [[mylink>>myspace.mypage]]") {{/html}} {{/velocity}} And I get following exception: ... org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getRenderedContent' in class com.xpn.xwiki.api.Document threw exception java.lang.StackOverflowError @ /templates/preview.vm[6,7] ... Caused by: java.lang.StackOverflowError at org.xwiki.rendering.renderer.printer.MonitoringWikiPrinter.print(MonitoringWikiPrinter.java:41) at org.xwiki.rendering.renderer.printer.XMLWikiPrinter.print(XMLWikiPrinter.java:79) at org.xwiki.rendering.renderer.printer.WrappingWikiPrinter.print(WrappingWikiPrinter.java:39) at org.xwiki.rendering.renderer.printer.MonitoringWikiPrinter.print(MonitoringWikiPrinter.java:41) at org.xwiki.rendering.renderer.printer.XMLWikiPrinter.print(XMLWikiPrinter.java:79) at org.xwiki.rendering.renderer.printer.WrappingWikiPrinter.print(WrappingWikiPrinter.java:39) at org.xwiki.rendering.renderer.printer.MonitoringWikiPrinter.print(MonitoringWikiPrinter.java:41) at org.xwiki.rendering.renderer.printer.XMLWikiPrinter.print(XMLWikiPrinter.java:79) ... Kind of infinite loop... I have tried other combinations with html before velocity, inside warning macro etc... but never works as it should... Do you have an idea??? regards Pascal

15 years, 7 months

[xwiki-devs] Fwd: [ANN] Versions Maven Plugin 1.0-alpha-3 released

by Vincent Massol

FYI -Vincent Begin forwarded message: > From: Stephen Connolly <stephen.alan.connolly(a)gmail.com> > Date: April 23, 2009 9:05:16 PM CEDT > To: "dev(a)mojo.codehaus.org" <dev(a)mojo.codehaus.org>, "user(a)mojo.codehaus.org > " <user(a)mojo.codehaus.org>, Maven Users List <users(a)maven.apache.org> > Subject: [ANN] Versions Maven Plugin 1.0-alpha-3 released > Reply-To: "Maven Users List" <users(a)maven.apache.org> > > The Mojo team is pleased to announce the release of the Versions Maven > Plugin, version 1.0-alpha-3. > > The Versions Plugin has the following goals. > > * versions:display-dependency-updates scans a project's > dependencies and > produces a report of those dependencies which have newer versions > available. > * versions:display-plugin-updates scans a project's plugins and > produces > a report of those plugins which have newer versions available. > * versions:update-parent updates the parent section of a project > so that > it references the newest available version. For example, if you use a > corporate root POM, this goal can be helpful if you need to ensure > you are > using the latest version of the corporate root POM. > * versions:update-properties updates properties defined in a > project so > that they correspond to the latest available version of specific > dependencies. This can be useful if a suite of dependencies must all > be > locked to one version. > * versions:update-child-modules updates the parent section of the > child > modules of a project so the version matches the version of the current > project. For example, if you have an aggregator pom that is also the > parent > for the projects that it aggregates and the children and parent > versions get > out of sync, this mojo can help fix the versions of the child > modules. (Note > you may need to invoke Maven with the -N option in order to run this > goal if > your project is broken so badly that it cannot build because of the > version > mis-match). > * versions:lock-snapshots searches the pom for all -SNAPSHOT > versions > and replaces them with the current timestamp version of that - > SNAPSHOT, e.g. > -20090327.172306-4 > * versions:unlock-snapshots searches the pom for all timestamp > locked > snapshot versions and replaces them with -SNAPSHOT. > * versions:resolve-ranges finds dependencies using version ranges > and > resolves the range to the specific version being used. > * versions:use-releases searches the pom for all -SNAPSHOT versions > which have been released and replaces them with the corresponding > release > version. > * versions:use-next-releases searches the pom for all non-SNAPSHOT > versions which have been a newer release and replaces them with the > next > release version. > * versions:use-latest-releases searches the pom for all non- > SNAPSHOT > versions which have been a newer release and replaces them with the > latest > release version. > * versions:use-next-versions searches the pom for all versions > which > have been a newer version and replaces them with the next version. > * versions:use-latest-versions searches the pom for all versions > which > have been a newer version and replaces them with the latest version. > * versions:commit removes the pom.xml.versionsBackup files. Forms > one > half of the built-in "Poor Man's SCM". > * versions:revert restores the pom.xml files from the > pom.xml.versionsBackup files. Forms one half of the built-in "Poor > Man's > SCM". > > The artifacts have been deployed to the mojo repository and will be > mirrored > to central within the next 24 hours. > > The Mojo Team. > > Release Notes - Maven 2.x Versions Plugin - Version 1.0-alpha-3 > ================================================ > > ** Bug > * [MVERSIONS-3] - display-plugin-updates does not identify the > plugin > version as not being provided when derived from the super-pom > * [MVERSIONS-10] - Property Placedholders output in > versions:display-plugin-updates > * [MVERSIONS-13] - display-plugin-updates warns that version is not > defined if same versio as in parent pom is defined > > ** Improvement > * [MVERSIONS-25] - Users should be made aware that this plugin > relies on > accurate maven-metadata.xml files. > > ** New Feature > * [MVERSIONS-15] - Add comparisonMethod=mercury > * [MVERSIONS-18] - Expose updated versions as a report > * [MVERSIONS-21] - Add mojo to lock snapshots to timestamp version > * [MVERSIONS-24] - Enable resolution of dependency version ranges > * [MVERSIONS-28] - use-releases mojo > * [MVERSIONS-32] - Add versions:commit and versions:revert using a > "Poor-man's SCM" so that changes to the pom can be accepted and > rolled back > * [MVERSIONS-33] - add use-next-releases goal > * [MVERSIONS-34] - add a use-latest-releases goal > * [MVERSIONS-35] - add use-next-versions goal > * [MVERSIONS-36] - add use-latest-versions goal > * [MVERSIONS-37] - add a use-releases goal that replaces -SNAPSHOT > dependencies with their corresponding release version (if available) > > ** Task > * [MVERSIONS-12] - Documentation is incorrect on > http://mojo.codehaus.org/versions-maven-plugin/examples/update-parent.html > > > ** Wish > * [MVERSIONS-26] - Can't resolve pom properties for specifying > plugin > version in pluginmanagement

15 years, 7 months

[xwiki-devs] Survey Application

by Chathura Prabuddha

Hai Ludovic. I liked to continue the survey application project even if I not selected to GSOC. If you give me a chance I can show my commitment to the Xwiki. If I'm on the project. I would like to know about the following points. 1. Ideas that need to change in my application. 2. How the milestone plan should be adjusted based on the above ideas complexity. 3. Changes that need to be done with the mockups that I had created. Its better if I can have a mentor who can guide me to this target. Also I would like to thank all the community members of the Xwiki. I gathered lots of experience to my life during past month.This is my first FOSS community involvement. If something went wrong from me please forgive me. I don't want to loose this connections that I had build with those great people. So Good luck Xwiki... Thank you... -- ~ Chathura Prabuddha Ganegoda~ Undergraduate, Department of Computer Science & Engineering, University of Moratuwa, Sri Lanka. http://gacpganegoda.blogspot.com/

15 years, 7 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs May 2009