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

by Vincent Massol

Hi Wang, Could you tell us what's the status of the office converter and whether there's any pending patches or things for me to apply? I've tried using it tonight using the application and it didn't work too well both in XHTML and in wiki format. The main problem is that the cleaning is not good enough. Thanks -Vincent

17 years

2
2
0 0

[xwiki-devs] Accordion Menu Resize Dynamically

by Jain, Prachi

Hi All, By mistake I posted my query in JIRA tracker. From there I got the method to post the queries. My requirement is to set the Accordion Menu and Content Area according to screen resolution(available Height) I have done for content area. Now i have to do for accordion menu. In left panel, I have navigation menu which displays the available spaces and pages within each space . For Accordion effect on this menu, i have created the object of accordion. as under:- <script type="text/javascript"> var obj = {div:'xwikinav',height:document.body.parentNode.clientHeight - (103 + ($mycount *22)), no:$spacecount}; var acc = createAccordion(obj); </script> I have set the height dynamically instead of hardcoded value. $mycount is no of spaces. With this kind of code I get menu as per available height. But moment i resize by pressing F11 key, my content area is resized but the menu is not resized. I understand that, i need to set the height as per above on window.resize event viz. window.resize = currentlyexpandedaccordion.height=document.body.parentNode.clientHeight - (103 + ($mycount *22)) But i dont know how to get the accordion or div which is in expanded state. I even tried. like while creating the accordion, i returned the object. and then on window.resize event , acc.options.defaultHeight= document.body.parentNode.clientHeight - (103 + ($mycount *22)) Please help...I have tried all approches...I am stuck.. Will appreciate your valuable inputs. [ Show > ] Prachi Jain <http://jira.xwiki.org/jira/secure/ViewProfile.jspa?name=hmajmudar> - 05/Sep/08 15:00 - edited My requirement is to set the Accordion Menu and Content Area according to screen resolution(available Height) I have done for content area. Now i have to do for accordion menu. In left panel, I have navigation menu which displays the available spaces and pages within each space . For Accordion effect on this menu, i have created the object of accordion. as under:- <script type="text/javascript"> var obj = {div:'xwikinav',height:document.body.parentNode.clientHeight - (103 + ($mycount *22)), no:$spacecount}; var acc = createAccordion(obj); </script> I have set the height dynamically instead of hardcoded value. $mycount is no of spaces. With this kind of code I get menu as per available height. But moment i resize by pressing F11 key, my content area is resized but the menu is not resized. I understand that, i need to set the height as per above on window.resize event viz. window.resize = currentlyexpandedaccordion.height=document.body.parentNode.clientHeight - (103 + ($mycount *22)) But i dont know how to get the accordion or div which is in expanded state. I even tried. like while creating the accordion, i returned the object. and then on window.resize event , acc.options.defaultHeight= document.body.parentNode.clientHeight - (103 + ($mycount *22)) Please help...I have tried all approches...I am stuck.. Will appreciate your valuable inputs. Thanks, Prachi

17 years

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r12470 - platform/web/trunk/standard

by Vincent Massol

Hi Artem, On Sep 7, 2008, at 9:46 PM, amelentev (SVN) wrote: > Author: amelentev > Date: 2008-09-07 21:46:19 +0200 (Sun, 07 Sep 2008) > New Revision: 12470 > > Modified: > platform/web/trunk/standard/pom.xml > Log: > XWIKI-1839: Query Plugin needs a jar file why is this not in the query plugin pom instead? For deployment time and not build time only you can use <scope>runtime</scope>. Thanks -Vincent > Modified: platform/web/trunk/standard/pom.xml > =================================================================== > --- platform/web/trunk/standard/pom.xml 2008-09-07 17:16:07 UTC (rev > 12469) > +++ platform/web/trunk/standard/pom.xml 2008-09-07 19:46:19 UTC (rev > 12470) > @@ -55,6 +55,13 @@ > <artifactId>xwiki-core-plexus</artifactId> > <version>${platform.core.version}</version> > </dependency> > +  > + <dependency> > + <groupId>org.slf4j</groupId> > + <artifactId>slf4j-log4j12</artifactId> > + <version>1.3.0</version> > + </dependency> > </dependencies> > <build> > <plugins>

17 years

2
1
0 0

[xwiki-devs] [Lucene-Plugin] Input wanted on some enhancements

by David Ward

I am currently adding some enhancements to the Lucene plugin for Curriki, and have a few questions. I have submitted a patch for XPLUCENE-25 in order to not index password fields, the patch seems to have been accepted by Sergiu (with some adjustments) and committed. The other patch (XPLUCENE-26) is to allow better sorting of results. The issue is that when sorting by a field that has been tokenzied by Lucene the sorting is by any of the tokens (seemingly random), so titles for example are sorted by random words within the title. The patch that I have created so far increases the size of the index by about 50% though (indexing non-tokenized versions of each object field) and I am not sure if that is acceptable to the XWiki community at large. One item that I noted was that the object data is being stored in the index, but there does not seem to be anything in the SearchResult interface that allows for getting the values back. Is there a reason the data is stored? I see two options here, first would be to add a method in SearchResult that lets one get the object data out (but that ends up having security issues for pages that one would not normally be able to see), the other would be to just index the data and not store it (which should reduce the index size). Any thoughts on the best direction here? The last question I have is how do I create a string array (String[]) in a velocity script so that I can have a secondary sort column? Velocity seems to create object arrays but the LucenePluginApi requires a string array for the sortField argument of getSearchResults. Any comments/input/suggestions/answers are welcome. David --

17 years

3
2
0 0

[xwiki-devs] [Solution] xWiki 1.5 on MSSQL 2000 & 2005

by Liwoj

Hi I'm just managed to install xWiki 1.5 against Microsoft SQL Server 2005 It wasn't trivial so i have few things to say: 1) hbm.xml file (Hibernate mapping) file which is as a download on http://n2.nabble.com/file/n841396/xwiki.mssql_1.5.hbm.xml xwiki.mssql_1.5.hbm.xml http://platform.xwiki.org/xwiki/bin/view/AdminGuide/InstallationMSSQL http://platform.xwiki.org/xwiki/bin/view/AdminGuide/InstallationMSSQL is outdated. It works only for xWiki 1.4 and required some modifications (based on http://svn.xwiki.org/svnroot/xwiki/platform/core/tags/xwiki-core-1.5/xwiki-… http://svn.xwiki.org/svnroot/xwiki/platform/core/tags/xwiki-core-1.5/xwiki-… ) to work with 1.5 I'm attaching mapping to my post. 2) First note on MSSQL Installation guide mentioned before is not correct. Text types wasn't depreciated in MSSQL 2005, only marked as obsoleted. So attached mapping works ok on both MSSQL 2000&2005 HTH -- View this message in context: http://n2.nabble.com/-Solution--xWiki-1.5-on-MSSQL-2000---2005-tp841396p841… Sent from the XWiki- Dev mailing list archive at Nabble.com.

17 years

2
5
0 0

[xwiki-devs] [Proposal] Move the XE 1.6M2 release date to next Wednesday

by Vincent Massol

Hi, Sergiu has asked us on IRC if we could postpone the 1.6M2 release a bit so we're now proposing to release it on Wednesday morning (the 10th) which means all commits should be done for Tuesday afternoon at latest, including running verification tests that all work fine. Each of the committers who have committed stuff should take the time Tuesday afternoon to run XE and verify that the features they have committed work fine as expected. ok with everyone? Thanks -Vincent

17 years

5
4
0 0

[xwiki-devs] Compiling XWiki enterprise with changes in Platform after changes in SVN

by Tiago Rinck Caveden

Hello all! After the recent changes on the SVN directories, how can I compile the XWiki Enterprise using the changes I have done on XWiki Platform? When I execute the compile it downloads a pre-compiled build of XWiki Platform. Thank you, -- Tiago Rinck Caveden http://caveden.multiply.com

17 years

3
6
0 0

[xwiki-devs] [Rendering] Syntax for definition lists and indentations

by Vincent Massol

Hi, I'd like to propose the following syntax for definition list and definition terms. This is the syntax the most used by other wikis too. Simple definitions: ; definition title1 : definition1 ; definition title2 : definition2 Nested definitions: ; definition title1 : definition1 ;; definition title2 :: definition2 Indentation: : first level indent :: second level indent ::: third level indent etc WDYT? Thanks -Vincent

17 years

6
9
0 0

[xwiki-devs] [Proposal] Linking to attachments/Insert link to image with new rendering

by Vincent Massol

Hi, This has been slightly discussed in other thread but not clearly so here's the clear proposal I'd like to implement: 1) Linking to an attachment: [[label>attachment:my.doc]] or simply [[attachment:my.doc]] 2) Image link: [[label>reference>image=my.png]] or simply [[reference>image=my.png]] 3) Linking to an attachment with an image displayed: [[label>attachment:my.doc>image=my.png]] Note 1: In 2) and 3) the label is only used in the HTML "alt" and "title" attributes since the link is on an image. Note 2: The value for attachment:xxx is an attachment name (as in my.doc) or the qualified name of an attachment. I'm proposing "wiki:space.page^attachment" for now. Note 3: The value for image can be: a full URL, an image attachment name (as in my.png) or the qualified name of the image as in: "wiki:space.page^imagename" (same as above). WDYT? Thanks -Vincent

17 years

6
9
0 0

[xwiki-devs] Lightbox Proposals (2)

by Evelina Vrabie

Hi, Sorry for the previous messy mail. Devs lists don't support html format (didn't know that until I tried :P). So, I created a Design page here: http://dev.xwiki.org/xwiki/bin/view/Design/LightboxImprovements It would be very very nice to have some feedback on this. Thanks for your patience, Evelina

17 years

5
5
0 0

[xwiki-devs] [ANN] XWiki Enterprise 1.4.2 released

by Thomas Mortagne

The XWiki development team is pleased to announce the release of XWiki Enterprise 1.4.2. Go grab it at http://forge.objectweb.org/project/showfiles.php?group_id=170 This is the last 1.4.x version before removing the branch. Changes from 1.4.1: Bug * XWIKI-1284 - Image disappears from WYSIWYG editor in documents with special characters in name * XWIKI-2317 - Documents created from APIs starts at version 2.1 * XWIKI-2453 - Wrong use of cache in LDAP authenticator * XWIKI-2461 - NPE when in LDAP group synchronization LDAP fail to get group's members * XWIKI-2468 - sql exception during delete virtual wiki in Oracle * XWIKI-2474 - When in a wiki with URL http:///, URL factory generate "secure" wikis URLs as https://:80/ in place of https:/// * XWIKI-2475 - Empty table displays error * XWIKI-2482 - {table} with space after newline in cell fails to render * XWIKI-2485 - Calling the Flush Cache API prevents Users and Groups from being deleted properly * XWIKI-2487 - Hiding the edit comment field doesn't work * XWIKI-2514 - Velocity renderer loop (Stack Overflow) * XWIKI-2543 - LDAP authentication lost during a session if user synchronisation fail * XWIKI-2548 - When updating user LDAP should check if given field key exists in users's class * XWIKI-2579 - Free Superadmin access for girliz * XWIKI-2605 - LDAP authentication fail when user already exist and contains ldap_dn field emptied by hand * XWIKI-2608 - Superadmin doesn't have programming rights on sub-wikis Improvement * XWIKI-2557 - Updated German translation of ApplicationResources, customized to XWiki Versions from 1.2 to 1.4.1 New Feature * XWIKI-2492 - Support universal edit button For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise142 Thanks -The XWiki dev team

17 years

1
0
0 0

[xwiki-devs] [New WYSIWYG] Tests for user inputs?

by Vincent Massol

Hi Marius, I'd like to know if we have tests for the new wysiwyg in term of verifying behavior of user inputs. For example yesterday we found that if you enter: "1 Test **bold**" then switched to WYSIWYG editor, moved the cursor somewhere inside "bold", the bold button was not shown as active and you selected the word and clicked on bold you're getting <b><strong>bold</strong></b> instead. Do we have tests for this? We need to be careful not to duplicate tests in the rendering module though. Thanks -Vincent

17 years

1
0
0 0

[xwiki-devs] Lightbox Proposal (2)

by Evelina Vrabie

Hello all, I was assigned with the refactoring of XWiki lightbox ( http://jira.xwiki.org/jira/browse/XWIKI-1689) As I said in a previous post (http://xwiki.markmail.org/search/?q=lightbox#query:lightbox+page:1+mid:gtqk…), there are 2 options: 1. *Clean up the existing code* PROS CONS The current lightbox is already integrated in users & groups management and...it works so far. The code is messy. There is still a lot of js + css +velocity + html in the same place. The css has some weird hacks for ie and mostly don't work as they should. Honestly, I don't see other big PROS here.... Very limited in terms of features. It doesn't support skins (the css only allows different colors or rounded / square corners). And, IMO it looks ugly. It is difficult to use. To use it for users & groups management I had to modify the code and add some hacks I'm not very happy with. It is not at all extensible (or very hard) and this would take a lot of time. So, I think the lightbox was good so far but it's time for something better. This leads me to the second choice. 2. *Integrate an existing lightbox* There are pleny lightboxes out there, but among the ones that are based on prototype (and scriptaculous, for the effects) the best I've seen are: · Prototype Window: http://prototype-window.xilinus.com/index.html · ModalBox: http://www.wildbit.com/labs/modalbox/ · LightWindow: http://www.stickmanlabs.com/lightwindow/#demos *Prototype Window* *ModalBox* *LightWindow* Small (62 k) Very small (22k) Small (63k) Resizable Resizable Resizable Movable Fixed Fixed Fully skinnable (separate images + css) Customizable through css. Not easy to theme. Supports modal windows. Same. Same Supports all visual Effects of Scriptaculous Supports SlideDown and SlideUp transitions. Customizable transition handlers (?). Supports offline + Ajax content. Same. Same. Has pre-build confirm, altert and info dialogs. Doesn't have. Doesn't have. Supports multi-modal windows. Doesn't. Doesn't. Support to save in cookies the windows status (location -- since is movable, open, close, hidden etc.) Doesn't. Doesn't. Has a tooltip add-on. Doesn't. Doesn't. Doesn't have a photo slideshow included. Doesn't have a photo slideshow integrated. Has a photo slideshow integrated. Also supports multi-galleries. Doesn't support media files. ? Supports all known / used media files. Works on Safari, Camino, Firefox and IE6. Works on IE6, IE7, Firefox 1.0, 1.5, 2.0, Safari, Camino, Opera 8 and 9. Works on Windows Firefox/IE6/IE7/Safari3/Opera & Mac Firefox/Safari/Opera/Netscape. Has a svn, a forum to post bugs / requests for features. Releases are often. Is a Google project, with frequent releases and bug tracking. Has a forum (was down when I checked it). MIT licence MIT licence MIT licence. XWiki possible usage of lightbox: - Users & Groups management - Photo gallery - Blog posts - Ajax forms - Embedded media files or swf animations - .... So, based on my brief summary of these 3 lightboxes, I would like to receive ideas, proposals... since is my second post about the subject and I think is a nice feature to have. Thanks, Evelina

17 years

1
0
0 0

[xwiki-devs] [VOTE] Release XE/Core 1.4.2 and delete 1.4 branch

by Thomas Mortagne

Hi devs, I'm planning to release XE/Core 1.4.2 tomorrow and then remove the 1.4 branch (since 1.5 stable is now out). Ok for everyone ? -- Thomas Mortagne

17 years

6
8
0 0

[xwiki-devs] New Panel for creating pages

by Art Yeung

Hello all, Currently we have a panel for creating pages. There is a drop down for selecting Page, Space or Blog Post. New pages are created under the current space. I would like to create a panel for creating pages only. So there is a similiar drop down (existing spaces listed) for selecting which Space the page should be created under. Then the text box as usual for the Title. Any idea how to do it please? does the page creation takes an argument for the space location? Many Thanks Art -- View this message in context: http://n2.nabble.com/New-Panel-for-creating-pages-tp834125p834125.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

17 years

2
2
0 0

[xwiki-devs] Global Variable?

by Art Yeung

Hi, We can do things like this in pages. #set( $myvar = ["123"] ) If I want to make a global variable that share across the entire wiki (XE), where can i set that pls? Thanks Art -- View this message in context: http://n2.nabble.com/Global-Variable--tp789520p789520.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

17 years

2
5
0 0

[xwiki-devs] XWiki - Add Blog Category Through Code.

by Prathap Pandian

HI, When ever new space is created, how can add a blog category with that space name through code. Can anyone know help me how to proceed with this one...? -- Prathap

17 years

3
6
0 0

[xwiki-devs] how to deal with the deprecated tags in xhtml

by Wang Ning

Hi, Using the HtmlCleaner 2.1, we can just replace the deprecated tags to appropriate alternative. We can remove TagSwapCleaningFilter.java and set CleanerTransformations in DefaultHTMLCleaner.java instead. Now we only swap <i> to <em>, <b> to <strong>. Is it necessary to replace more deprecated tags? I collect some other tags I think can be replaced. s -> del strike -> del u -> ins or <p class="underline"> centre -> <span style="text-align:center"> font -> <span style="color:red;font-family=Arial;font-size=12;"> basefont -> <span style="color:red;font-family=Arial;font-size=12;"> Should we replaces all the tags above to their alternative? WDYT? There are some deprecated tags which don't have explicit alternative, as below: applet dir menu isindex -- Thanks Wang Ning

17 years

3
3
0 0

[xwiki-devs] [Proposal] Components and svn directory organization

by Vincent Massol

Hi devs, Right now we have: platform/ |_ core/ |_ xwiki-core/ |_ (others)/ |_ plugins/ |_ ... The problem I see is twofold: 1) We can have platform components that are not core components (for example I'd like to commit the office component done by Wang Ning). 2) I'd like that we decide to deprecate the plugins/ system going forward and that all new code only write components. For 1) I'd like to propose: platform/ |_ components/ (contains (others)/ from above) |_ core/ (is the core/xwiki-core from above, to be removed once fully split into components) |_ plugins/ (to be removed once fully split into components) |_ ... For 2) I'd like to propose: * Create an interface for Velocity APIs. Something like VelocityBridge (or VelocityAccess or VelocityApi or...). It would be empty. * Each component that want to be accessed from velocity will need to implement a component implementing VelocityBridge. It'll have a role- hint being the name under which it'll be access from Velocity. * Create a VelocityService class (component) which has a single get(String name) method and which uses the ComponentManager to look up components which implement VelocityBridge using the name as the role hint. * Put that VelocityService in the Velocity context under the name "services". In practice this means that users will be able to access all our components through the VelocityBridge implementations with a syntax like: $services.office.convert(...) $services.translation.translate(...) ... Note1: We would need to be careful that it would be forbidden for any java code to use a VelocityBridge. This is to ensure all code logic is put into components and not into the bridges. We should use the maven enforcer plugin to enforce this rule. Note2: This means we'll have 2 APIs to maintain: the velocity one (the bridges) + the "Java"' one (the main components). But I don't see any other way... WDYT? Thanks -Vincent

17 years

7
15
0 0

by Sergiu Dumitriu

vmassol (SVN) wrote: > Author: vmassol > Date: 2008-09-02 12:18:10 +0200 (Tue, 02 Sep 2008) > New Revision: 12357 > > Added: > platform/core/trunk/xwiki-rendering/src/main/java/org/xwiki/rendering/block/AbstractVerbatimBlock.java > platform/core/trunk/xwiki-rendering/src/main/java/org/xwiki/rendering/block/InlineVerbatimBlock.java > platform/core/trunk/xwiki-rendering/src/main/java/org/xwiki/rendering/block/StandaloneVerbatimBlock.java > platform/core/trunk/xwiki-rendering/src/main/java/org/xwiki/rendering/block/VerbatimBlock.java > platform/core/trunk/xwiki-rendering/src/test/resources/verbatim/ > platform/core/trunk/xwiki-rendering/src/test/resources/verbatim/verbatim1.test > platform/core/trunk/xwiki-rendering/src/test/resources/verbatim/verbatim2.test > platform/core/trunk/xwiki-rendering/src/test/resources/verbatim/verbatim3.test > Removed: > platform/core/trunk/xwiki-rendering/src/main/java/org/xwiki/rendering/internal/macro/nowiki/ > platform/core/trunk/xwiki-rendering/src/test/resources/macros/macronowiki.test > Modified: > platform/core/trunk/xwiki-rendering/src/main/java/org/xwiki/rendering/block/EscapeBlock.java > platform/core/trunk/xwiki-rendering/src/main/java/org/xwiki/rendering/internal/parser/doxia/DoxiaGeneratorListener.java > platform/core/trunk/xwiki-rendering/src/main/java/org/xwiki/rendering/internal/parser/wikimodel/WikiModelGeneratorListener.java > platform/core/trunk/xwiki-rendering/src/main/java/org/xwiki/rendering/internal/parser/wikimodel/XDOMGeneratorListener.java > platform/core/trunk/xwiki-rendering/src/main/java/org/xwiki/rendering/listener/Listener.java > platform/core/trunk/xwiki-rendering/src/main/java/org/xwiki/rendering/listener/ListenerDelegate.java > platform/core/trunk/xwiki-rendering/src/main/java/org/xwiki/rendering/renderer/EventsRenderer.java > platform/core/trunk/xwiki-rendering/src/main/java/org/xwiki/rendering/renderer/XWikiSyntaxRenderer.java > platform/core/trunk/xwiki-rendering/src/main/java/org/xwiki/rendering/renderer/xhtml/XHTMLRenderer.java > platform/core/trunk/xwiki-rendering/src/main/resources/META-INF/plexus/components.xml > platform/core/trunk/xwiki-rendering/src/test/java/org/xwiki/rendering/RenderingTests.java > Log: > XWIKI-2634: Various tasks for the new rendering implementation > > * Added support for verbatim. > * Removed nowiki macro which is no longer necessary > I'm starting to dislike the way renderers are done. They have many methods to handle each type of element, the renderer classes are already becoming large, and introducing a new element requires changing many classes. Isn't there a better way to do this? One would be to have just an onEvent method, and then the XYZRenderer would forward the call to a specific class responsible for handling that type of event. The downside is that we'll have many small classes and large configuration files, but the advantage is that unimplemented elements won't throw exceptions, but use a generic event handler. I don't know which way is better, fewer huge classes, or more tiny classes. If the syntax will become *very* stable soon, then I guess the current way is good, too. IMHO. -- Sergiu Dumitriu http://purl.org/net/sergiu/

17 years

2
2
0 0

Re: [xwiki-devs] [xwiki-notifications] r12369 - in platform/core/trunk/xwiki-xml: . src/main/java/org/xwiki/xml/internal/html src/test/java/org/xwiki/xml/internal/html

by Sergiu Dumitriu

vmassol (SVN) wrote: > Author: vmassol > Date: 2008-09-02 22:15:02 +0200 (Tue, 02 Sep 2008) > New Revision: 12369 > > Added: > platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/html/HTMLConstants.java > Removed: > platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/html/TagSwapCleaningFilter.java > Modified: > platform/core/trunk/xwiki-xml/pom.xml > platform/core/trunk/xwiki-xml/src/main/java/org/xwiki/xml/internal/html/DefaultHTMLCleaner.java > platform/core/trunk/xwiki-xml/src/test/java/org/xwiki/xml/internal/html/DefaultHTMLCleanerTest.java > Log: > XWIKI-2634: Various tasks for the new rendering implementation > > * Improved HTML Cleaning by upgrading to HtmlCleaner 2.1 and by adding more tag transformations. > Patch submitted by Wang Nine, reviewed by Vincent Massol with modifications (it was failing the build with checkstyle errors) > + tt = new TagTransformation(HTMLConstants.CENTRE, HTMLConstants.P, false); > + tt.addAttributeTransformation(HTMLConstants.STYLE_ATTRIBUTE, "text-align:center"); > + transformations.addTransformation(tt); > + /** > + * HTML <centre> tag name. > + */ > + String CENTRE = "centre"; This should be "center", not "centre" -- Sergiu Dumitriu http://purl.org/net/sergiu/

17 years

2
1
0 0

[xwiki-devs] [Proposal] WYSIWYG 1.6 roadmap

by Marius Dumitru Florea

Hi devs, Here's the roadmap I propose: * Bugs * fix IE bugs * heading doesn't work (1.6M2) * tool bar separator not shown (1.6M2) * fix cross-browser bugs * pass syntax id to ConversionFilter (xwiki/2.0 currently hardcoded) (1.6M2) * skip tool bar separator for unsupported features (1.6M2) * fix output bugs * return should generate a new paragraph (1.6RC1) * nested lists should be wrapped by a list item (1.6RC1) * HTML special characters are replaced by entities (1.6RC1) * Features waiting for rendering support * justify (left, center, right, full) (?) * indent / outdent (currently supported only for nested lists) (?) * font (family, size) (?) * color (background, foreground) (?) * New features * remove formatting (1.6M2) * insert symbol (1.6M2) * monospace (tt) (1.6RC1) * insert link / unlink (1.6RC1) * insert image (1.6RC1) * insert attachment link (1.6RC1) * UI * infrastructure * configurable menus (1.6M2) * generic dialog box with optimised dragging and glass panel in modal mode (1.6M2) * generic tray (1.6M2) * link menu * dialogs & trays for insert link / image / attachment (1.6RC1) * Server side * services for insert link / image / attachment (1.6RC1) So WDYT? Marius

17 years

3
5
0 0

[xwiki-devs] XWiki - HSQL to display Current Space

by Prathap Pandian

HI, How to view current space using HSQL. For Example: select prop.value from BaseObject as obj, StringProperty as prop where obj.className='Blog.Categories' and obj.name = 'Blog.Categories' and prop.id.id = obj.id and prop.id.name='name'* and prop.value = $doc.web* whether above one is correct..? -- Prathap

17 years

1
1
0 0

[xwiki-devs] HtmlCleaner 2.1

by Vincent Massol

Just to let you know that HtmlCleaner 2.1 is now out. http://htmlcleaner.sourceforge.net/release.php Apparently they have implemented some of our requests in there so that's cool. If someone (daning?) is intersted in refactoring our HMTL Cleaner to use it that would be great. Thanks -Vincent

17 years

2
2
0 0

[xwiki-devs] [Rendering] verbatim syntax for xwiki

by Vincent Massol

Hi, Just to let you know that the following verbatim syntax is now implemented for the XWiki Syntax v2.0: This is {{{***verbatim**}}} {{{ verbatim on several lines }}} Or even: abc{{{def{{{verbatim}}}ghi}}}jkl (in this case the "def{{{verbatim}}}ghi" is not rendered). Thanks -Vincent

17 years

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