xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

[xwiki-devs] [VOTE] XE 2.0 RC1 date change

by Vincent Massol

Hi, Some date change proposal since we're late on a few things: * RC1: move it to 24th of Aug (instead of 17th). It must contain: - bug fixes - All - distributed events done - Thomas - WYSIWYG changes for macro category - Marius - new skin: background + full horizontal width header + some CSS colors - Cati - watchlist working for XEM - JV * 2.0 final: 31st of Aug (unless we find critical bugs in RC1 in which case we'll do a RC2 and postpone the final to the 7th of Sep.) Here's my +1 Thanks -Vincent

15 years, 5 months

[xwiki-devs] Sortable/Filterable tables

by Vincent Massol

Hi, I find it really not easy to use a sortable/filterable table in xwiki now + it exposes internals (like name and location of CSS and JS scripts): Syntax 1.0: $xwiki.ssfx.use("js/xwiki/table/table.css") $xwiki.jsfx.use("js/xwiki/table/tablefilterNsort.js", true) <table id="tableid" class="grid sortable filterable doOddEven"> .. </table> Syntax 2.0: {{velocity}} $xwiki.ssfx.use("js/xwiki/table/table.css") $xwiki.jsfx.use("js/xwiki/table/tablefilterNsort.js", true) {{/velocity}} {{html}} <table id="tableid" class="grid sortable filterable doOddEven"> .. </table> {{/html}} What's the best practice? How do we fix this quickly? (the longer fix is to implement either sorting/fitering at the syntax level using parameters or by introducing a new generic table/grid macro). Do we remove the documentation for this? (it's currently on the syntax page and broken since it doesn' t mention using ssfx/jsfx). Thanks -Vincent

15 years, 5 months

[xwiki-devs] Problem with parametrized headers - Need CSS help

by Vincent Massol

Hi, Input: (% style="color:blue" %) = header = The result doesn't show the header in blue. The reason is that we have the following CSS in toucan: h1 span, h2 span, h3 span, h4 span { background-color:inherit; border-bottom:1px solid #CCCCCC; color:#000000; display:block; margin:20px 0; overflow:hidden; padding:0; position:relative; } It doesn't work since the style is set on h1 and the span's style is overidden in toucan's css. Question: Why don't we set the styles above on h1 instead of h1 span for ex? What can we do to fix this? I don't think that changing the XHTML renderer to set the style on the span would be a good thing. WDYT? Thanks -Vincent

15 years, 5 months

[xwiki-devs] add new setProperty method to DocumentAccessBridge proposal

by Anamaria Stoica

Hi, Concerning DocumentAccessBridge [0], would it be possible to add another setProperty method, which would indicate the number(index) of the object you add the property value to? Its signature would be: void setProperty(String documentName, String className, int objectNumber, String propertyName, Object propertyValue) throws Exception; I need it to be able to easily add new objects and modify their property values, from a component. Is there any other way of doing this I overlooked? Right now, the only existing setProperty method operates only on the first object attached to the document: void setProperty(String documentName, String className, String propertyName, Object propertyValue) throws Exception; The corresponding getters are both already present: Object getProperty(String documentName, String className, int objectNumber, String propertyName); Object getProperty(String documentName, String className, String propertyName); WDYT? [0] - https://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-bridge/src/ma… Thanks, Anamaria

15 years, 5 months

[xwiki-devs] [XOO] Images in XWiki pages

by Cristina Scheau

Hi everybody! Sorry for bother you again with my questions, but I have a problem that blocks me. I need to know what images are internal (they are attached to the current page or other XWiki page) in order to download them with my XMLRPC client. Using the rendering module I get every ImageBlock [1] and I check the ImageType[2] of every Image[3] object. My problem is that this type is URL for both external and internal images and that's why I can't cast to the DocumentImage class. I've pasted bellow my code and the output for some inputs. Can somebody tell me what I am wrong? Is there any other solution for getting the associated attachments? My client has these methods for getting the attachment data: - Attachment<http://confluence.atlassian.com/display/DOC/Remote+API+Specification#Remote…> getAttachment(String token, String pageId, String fileName, String versionNumber) - get information about an attachment. - byte[] getAttachmentData(String token, String pageId, String fileName, String versionNumber) - get the contents of an attachment. - byte[] getAttachmentData(Attachment attachment) - get the contents of an attachment. My code: // Parse Parser parser = ecm.lookup(Parser.class, syntax.toIdString()); XDOM xdom = parser.parse(new StringReader(source)); for (ImageBlock block : xdom.getChildrenByType(ImageBlock.class, true)) { Image image = block.getImage(); System.out.println(image.getType() + ""); System.out.println(image.getName() + ""); } Tests: Input: source: [[image:IMG3219.JPG]] image:http://www.balsamiq.com/images/xwiki_logo.png Syntax : XWIKI_2_0 Output: URL IMG3219.JPG URL http://www.balsamiq.com/images/xwiki_logo.png Input: source: <p><img src="IMG3219.JPG" alt="IMG3219.JPG"/><br/><br/><img src=" http://www.balsamiq.com/images/xwiki_logo.png" class="wikimodel-freestanding" alt=" http://www.balsamiq.com/images/xwiki_logo.png"/></p> syntax: XHTML_1_0 Output: URL IMG3219.JPG URL http://www.balsamiq.com/images/xwiki_logo.png Links: [1] http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-rendering/xwik… [2] http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-rendering/xwik… [3] http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-rendering/xwik… Best regards, Cristina

15 years, 5 months

[xwiki-devs] [VOTE] Rendering API change: move Syntax classes to syntax package

by Vincent Massol

Hi, I'd like to move syntax-related classes to org.rendering.syntax package. These are: - Syntax - SyntaxFactory - SyntaxType Right now they are in the org.rendering.parser package but that's not right since Syntax classes are used in Listeners, Parsers, Transformations, etc which are all top level rendering packages. This will break the API and is not backward compatible (for those using the rendering api directly) which is why I'd like to do this ASAP so that it's in XE 2.0 (which doesn't have to be backward compatible). Note that we already have lots of api breakage for the rendering module: <exclude>org/xwiki/rendering/listener/chaining/ AbstractChainingListener</exclude> <exclude>org/xwiki/rendering/renderer/EventsRenderer</ exclude> <exclude>org/xwiki/rendering/renderer/ PlainTextRenderer</exclude> <exclude>org/xwiki/rendering/renderer/TexRenderer</ exclude> <exclude>org/xwiki/rendering/renderer/XHTMLRenderer</ exclude> <exclude>org/xwiki/rendering/renderer/ XWikiSyntaxRenderer</exclude> <exclude>org/xwiki/rendering/renderer/ PrintRendererFactory</exclude> <exclude>org/xwiki/rendering/renderer/PrintRenderer</ exclude> <exclude>org/xwiki/rendering/renderer/chaining/ AbstractChainingPrintRenderer</exclude> <exclude>org/xwiki/rendering/renderer/xhtml/ DefaultXHTMLImageRenderer</exclude> <exclude>org/xwiki/rendering/renderer/xhtml/ DefaultXHTMLLinkRenderer</exclude> <exclude>org/xwiki/rendering/renderer/xhtml/ XHTMLRendererFactory</exclude> <exclude>org/xwiki/rendering/util/RenderersUtils</ exclude> <exclude>org/xwiki/rendering/parser/SyntaxFactory</ exclude> <exclude>org/xwiki/rendering/renderer/xhtml/ XHTMLImageRenderer</exclude> <exclude>org/xwiki/rendering/renderer/xhtml/ XHTMLLinkRenderer</exclude> <exclude>org/xwiki/rendering/parser/SyntaxType</ exclude> <exclude>org/xwiki/rendering/macro/descriptor/ MacroDescriptor</exclude> <exclude>org/xwiki/rendering/renderer/printer/ MonitoringWikiPrinter</exclude> <exclude>org/xwiki/rendering/configuration/ RenderingConfiguration</exclude> <exclude>org/xwiki/rendering/macro/MacroManager</ exclude> <exclude>org/xwiki/rendering/block/MacroBlock</exclude> <exclude>org/xwiki/rendering/macro/AbstractMacro</ exclude> <exclude>org/xwiki/rendering/macro/descriptor/ AbstractMacroDescriptor</exclude> <exclude>org/xwiki/rendering/macro/descriptor/ DefaultMacroDescriptor</exclude> <exclude>org/xwiki/rendering/block/ PlainTextBlockFilter</exclude> <exclude>org/xwiki/rendering/util/ParserUtils</exclude> This will add some more. Here's my +1 Thanks -Vincent

15 years, 5 months

[xwiki-devs] Improve performance with new sun hotspot optimizations for Java 6u14?

by Niels Mayer

The latest Sun JDK 6 <http://java.sun.com/javase/6/webnotes/6u14.html> has optional performance optimization for threading. Since Xwiki running in a web-container is thread-intensive, I'm wondering whether performance improvements like Escape Analysis<http://en.wikipedia.org/wiki/Escape_analysis> will be noticed for Xwiki. How about for its increasing amount of work happening out of Groovy scripts? Much attention has been given by Sun, IBM, BEA and others to optimize lock > management and synchronization in their respective Java 6 virtual machine > offerings. Features like biased locking, lock coarsening, lock elision by > escape analysis and adaptive spin locking are all designed to increase > concurrency by allowing more effective sharing amongst application threads. http://www.infoq.com/articles/java-threading-optimizations-p1 http://www.infoq.com/articles/java-threading-optimizations-p2 http://blog.xebia.com/2007/12/21/did-escape-analysis-escape-from-java-6/ http://blog.xebia.com/2009/02/18/jvm-threading-optimizations-revisited/ http://blog.juma.me.uk/2008/12/17/objects-with-no-allocation-overhead/ <http://blog.xebia.com/2007/12/21/did-escape-analysis-escape-from-java-6/> http://java.dzone.com/articles/escape-analysis-java-6-update <http://java.dzone.com/articles/escape-analysis-java-6-update> Niels http://nielsmayer.com PS: I need to try this experiment again with the non-early access version http://nielsmayer.com/xwiki/bin/view/fedora10/64bitJavaAppletIn64BitFirefox… PPS: in clojure land (will this also apply to Groovy?) http://www.mail-archive.com/clojure@googlegroups.com/msg17221.html > > I'm getting a very significant performance improvement by adding a couple > of JVM parameters (using jdk 1.6.0_14). They are: > -XX:+DoEscapeAnalysis > -XX:+UseBiasedLocking (I think the -server flag is required for those two > flags to do anything). > ... > My runtime with n = 5,000,000 goes from ~7.5 seconds to ~4.5 seconds. ... I actually just confirmed that, on my computer at least, those flags have > basically no effect on the java version and a big difference on the clojure > one. ... -XX:+AggressiveOpts improves another 5-10%.

15 years, 5 months

Re: [xwiki-devs] Blog Wiki 2.0 Upgrade 7th Draft

by Andreas Schaefer

Hi Vincent >The easiest is really if you can upgrade your install on XE 2.0M3 >(latest trunk). FYI 2.0M3 should be released tomorrow (if all goes >fine). > >We'd also love to get feedback on 2.0M3 (or latest trunk). We think >it's pretty stable and nice but someone using it for real would be >great to verify all is fine before the final release. > >You'd also wiki macros btw (amongst other things) ;) I upgrade my life wiki on: http://madplanet.com/xwiki to 2.0m3 and it seems to run smoothly. Upgrading the Blog Feed works now and I can see the 2.0 Wiki blog entries nicely. The rest of the wiki seems to run much faster then previously even though I don't have hard numbers. I'll let you know when something goes wrong. Cheers - Andy

15 years, 5 months

Re: [xwiki-devs] [xwiki-notifications] r22741 - sandbox/gsoc/importexport/xwiki-core-importer

by Thomas Mortagne

Why do you need observation in the importer ? On Fri, Aug 14, 2009 at 13:01, asiri<sandbox-notifications(a)xwiki.org> wrote: > Author: asiri > Date: 2009-08-14 13:01:26 +0200 (Fri, 14 Aug 2009) > New Revision: 22741 > > Modified: > sandbox/gsoc/importexport/xwiki-core-importer/pom.xml > Log: > [misc] Fixing an invalid dependancy. > > Modified: sandbox/gsoc/importexport/xwiki-core-importer/pom.xml > =================================================================== > --- sandbox/gsoc/importexport/xwiki-core-importer/pom.xml 2009-08-14 10:10:12 UTC (rev 22740) > +++ sandbox/gsoc/importexport/xwiki-core-importer/pom.xml 2009-08-14 11:01:26 UTC (rev 22741) > @@ -52,7 +52,7 @@ > </dependency> > <dependency> > <groupId>org.xwiki.platform</groupId> > - <artifactId>xwiki-core-observation</artifactId> > + <artifactId>xwiki-core-observation-local</artifactId> > <version>${pom.version}</version> > </dependency> > <dependency> > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications > -- Thomas Mortagne

15 years, 5 months

[xwiki-devs] Fwd: [Fwd: XWiki: change summary is required for announcements [08aecb6d641]]

by Vincent Massol

Seems like we have to change how we publish releases on freshmeat. -Vincent Begin forwarded message: > From: Ludovic Dubost <ludovic(a)xwiki.com> > Date: August 14, 2009 12:58:44 PM CEDT > To: Vincent Massol <vincent(a)xwiki.com> > Subject: [Fwd: XWiki: change summary is required for announcements > [08aecb6d641]] > > > -- > Ludovic Dubost > Blog: http://blog.ludovic.org/ > XWiki: http://www.xwiki.com > Skype: ldubost GTalk: ldubost > > > From: "freshmeat.net ticketing" <tickets(a)freshmeat.net> > Date: August 14, 2009 11:47:49 AM CEDT > To: undisclosed-recipients:; > Subject: XWiki: change summary is required for announcements > [08aecb6d641] > > > // Add your reply above here > > = > = > = > = > = > = > = > = > = > = > ====================================================================== > > danielpearson created this ticket on 2009-08-14 09:47:49 UTC > > A message telling readers to read the release notes is not > acceptable input into > the "Changes" field of a release announcement. Such a statement > literally goes > without saying. This field must contain a summary of the changes > made in the > release. We cannot approve this release announcement until you reply > with such a > summary. > > = > = > = > = > = > = > = > = > = > = > ====================================================================== > > State: Open > Assigned to: danielpearson > Due: 2009-08-21 > View this ticket online: > http://freshmeat.net/projects/xwiki/tickets/08aecb6d641 > View the associated project: > http://freshmeat.net/projects/xwiki

15 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs