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

[xwiki-devs] [Proposal] New Resource module
by Vincent Massol 17 Jun '13

17 Jun '13

Hi devs, See http://jira.xwiki.org/browse/XWIKI-9237: {quote} The idea is to rename the URL module's XWikiURL, AbstractXWikiURL, XWikiEntityURL, etc into Resource, AbstractResource and EntityResource and move them to a resource module. The reason is that they are not URL and are thus badly named. In addition since the goal is to the resource in the Execution Context and the EC should be independent of any environment it's not right to put a URL in it. A Resource is much better. This also brings us one step closer to http://markmail.org/thread/wfj4dupq76agqonz {quote} Specifically the code is in a branch right now at: https://github.com/xwiki/xwiki-platform/tree/feature-resource-and-wiki-modu… Let me know what you think. Thanks -Vincent

1 2

[xwiki-devs] listening to a rename operation?
by Paul Libbrecht 17 Jun '13

17 Jun '13

Hello XWiki experts, is there a way using the "EventListener" of the ObservationManager to detect the move of a document to another space and page? Thanks in advance. Paul

3 4

[xwiki-devs] [Proposal] Adding support for adding dynamic parameters in Query Filters
by Vincent Massol 17 Jun '13

17 Jun '13

Hi devs, Right now the QueryFilter interface allows to modify the query statement and to filter returned results but doesn't allow to pass dynamic value. I'm currently implementing a filter that'll return only results for the current language and thus I need this dynamicity. Are you ok that I break the QueryFitler API to add a new method: public interface QueryFilter { String filterStatement(String statement, String language); List filterResults(List results); // New method Map<String, String> getParameters(); } WDYT? Thanks -Vincent

2 4

[xwiki-devs] Navigation Menu Bar UIX
by Marius Dumitru Florea 17 Jun '13

17 Jun '13

Hi devs, I'm going to add an UI extension point after the XWiki header that could be used to inject a navigation top menu bar. The extension point id can be: org.xwiki.platform.template.header.bottom or org.xwiki.platform.template.header.after I'll go with the first option if no one has a strong preference for the second. Regarding the package prefix in the UIX id, even though it was missing from JV's proposal http://lists.xwiki.org/pipermail/devs/2013-March/053739.html the existing UIX have it (e.g. org.xwiki.platform.panels.Applications) so I'm using it too to be consistent. I would also like to integrate http://extensions.xwiki.org/xwiki/bin/view/Extension/Navigation+Menu+Wiki+M… http://extensions.xwiki.org/xwiki/bin/view/Extension/NavigationMenuConfig into xwiki-platform-menu/xwiki-platform-menu-ui (with various code modifications and some functional tests) without bundle it with XE. This new module could host in the future the menu creator proposed by Caty http://incubator.myxwiki.org/xwiki/bin/view/Improvements/MenuCreator . The goal of all this is to have http://jira.xwiki.org/browse/XWIKI-9148 closed for 5.1 final. It's ok IMO to do this during RC phase because it can't break existing features. Thanks, Marius

5 7

[xwiki-devs] [ANN] XWiki 5.1 Milestone 2 Released
by Marius Dumitru Florea 14 Jun '13

14 Jun '13

The XWiki development team is proud to announce the availability of XWiki 5.1 Milestone 2. This release brings automatic Solr indexing with locale inheritance and a few bug fixes and improvements. You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download (please allow a few hours for the binaries to propagate to the download servers if the download doesn't work yet) Make sure to review the release notes: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki51M2 Thanks -The XWiki dev team

1 0

[xwiki-devs] [Reminder] BFD#25
by Vincent Massol 14 Jun '13

14 Jun '13

Hi everyone, Today is BFD25. Our goal is still to have more bugs closed than created for the past 1200 days! http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10352 As of now we're 24 bugs behind (from 35 last week). Here's the BFD#25 dashboard to follow the progress during the day: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=11599 Thanks -Vincent

1 1

[xwiki-devs] A new XWiki Model! (sort of)
by Caleb James DeLisle 14 Jun '13

14 Jun '13

Hi guys, I've been working on this little side project which I originally needed to scratch a personal itch that came up during my work on the Resilience research project. I needed an efficient way to generate XWiki export (.xar) files and post them to a running wiki for rapid prototyping. In the past I would do some work from within the wiki and once the bulk of the work was done, I'd export an xar file and unzip it. Fixing up the XML and making small changes would be done by hand editing the XML dumps. To test it, the XML files would be packaged into .xar file using Maven then uploaded into the wiki by using the import function in the Admin interface. There are a few problems with this process: 1. Manually editing XMhelL files. 2. My attention span lasts from `mvn clean install` to `[INFO] Scanning for projects...` 3. The turnaround cycle from making a change in the git repository to seeing it in the wiki is somewhere around 2 minutes (edit, compile, upload in browser, test) My solution is called xwiki-tools, it's a Javascript framework for scripting the creation of XWiki packages with documents, objects and classes. Code Golf example: This is the shortest xwiki-tools script which will run (it makes a .xar file): var XWiki = require('xwiki-tools'); var pack = new XWiki.Package(); pack.setName("XWiki - Contrib - XWiki Tools Tiny Example"); pack.setDescription("package name, description and extensionId are required"); pack.setExtensionId("org.xwiki.contrib:xwiki-tools-tiny-example"); var doc = new XWiki.model.XWikiDoc(["Main","TinyExample"]); doc.setContent("A code-golf example of making an XWiki .xar file with 1 document."); pack.addDocument(doc); pack.genXar('XWikiToolsTinyExample.xar'); You can copy/paste this little .js script into a file and run `node yourFile.js` and it will output XWikiToolsTinyExample.xar. But wait, there's more! xwiki-tools doesn't just allow you to wrap little documents into .xar files, it allows you to add attachments, XObjects and even define your own XClasses. It can also generate more than a xar file, it can post the package directly to a running wiki which allows you to edit a file, run the command, page over to the browser and immediately see your changes! If you want, it can also generate output as an Apache Maven build. Check out the example here: https://github.com/cjdelisle/xwiki-tools-example to learn how to add attachments, XObjects and XClasses to your package and how to post to a wiki or generate a Maven build. Performance: user@ubnta8:~/wrk/resiliance/xwiki-tools-example$ time ./do >/dev/null real 0m0.643s user@ubnta8:~/wrk/resiliance/xwiki-tools-example$ time ./do --mvn >/dev/null real 0m0.416s user@ubnta8:~/wrk/resiliance/xwiki-tools-example$ cd mvnout/ user@ubnta8:~/wrk/resiliance/xwiki-tools-example/mvnout$ time mvn clean install >/dev/null real 0m20.578s XWiki Classes: So you've decided you want to give this a shot and you have a big ugly class which you need to represent. If you've looked at one of the existing classes such as: https://github.com/cjdelisle/xwiki-tools/blob/master/lib/model/classes/Wiki… then you know what it needs to look like but getting your class in that form would be painful. Fortunately there is a tool which reads your .xml file with the XClass and prints a .js file like the one above. Just unzip the xar export from XWiki and run the following: node ./bin/describeclass.js /path/to/YourBigClass.xml Note: some of the class properties are unimplemented so some classes will not work. License: LGPLv2.1, same as XWiki, generated code/data explicitly exempted. Thanks, Caleb

1 0

[xwiki-devs] [UX][Iteration] Menu Creator
by Ecaterina Moraru (Valica) 12 Jun '13

12 Jun '13

Hi devs, One of the roadmap entries is the ability to create extensible, reusable menus (XWIKI-9148 <http://jira.xwiki.org/browse/XWIKI-9148>). This proposal reuses the AppWithinMinutes wizard mechanism and adapts it to Menu creation, having a limited fields palette (pages, links, separators, extension points): http://incubator.myxwiki.org/xwiki/bin/download/Improvements/MenuCreator/St… http://incubator.myxwiki.org/xwiki/bin/download/Improvements/MenuCreator/St… Submenus will be created by using the Drag&Drop or by using indent actions in the Toolbox: http://incubator.myxwiki.org/xwiki/bin/download/Improvements/MenuCreator/St… http://incubator.myxwiki.org/xwiki/bin/download/Improvements/MenuCreator/St… This is an example of the menu that could be created with the MenuCreator: http://incubator.myxwiki.org/xwiki/bin/download/Improvements/MenuCreator/Ex… You can read the whole proposal at: http://incubator.myxwiki.org/xwiki/bin/view/Improvements/MenuCreator We could also use it for our #mainmenu and #contentmenu in order to let the user customize what entries are displayed or add more. Let me know what you think, Caty

3 2

[xwiki-devs] [Proposal][QA] Put Test Report Application on xwiki.org
by Sorin Burjan 11 Jun '13

11 Jun '13

Hello everybody, After several months of fragmented work, I have finally managed to complete the next iteration of Test Report Application [1]. Final parts of the code will be committed next week. Taking into consideration the feedback I received, I implemented several changes into the application to make it more user friendly and robust. In order to put the application in production, Manuel and me converted the Manual Test Report Template [2] into Test Cases to be used by the Test Report Application. These test cases are committed on Github [3]. Now we have 404 Test Cases, grouped in 22 Spaces as follows: 1) Action Menus Tests 2) App Within Minutes Tests 3) Dashboard Macro Tests 4) Page Tabs Tests 5) Rights Tests 6) Tags Tests 7) Wiki Editor Tests 8) WYSIWYG Editor Tests 9) Activity Stream Tests 10) Blog Tests 11) Document Index Tests 12) Panels Tests 13) Search Tests 14) User Profile Tests 15) Wiki Manager Tests 16) Administration Tests 17) Color Themes Tests 18) Jump To Page Tests 19) Register and Authentication Tests 20) Space Macro Tests 21) User Status Tests 22) Workspaces Tests My proposal is that we create a dedicated subwiki for this, qa.xwiki.orgwhere we will deploy the application + test cases. The rationale behind having a dedicated subwiki for this is that we don't want to crowd an already existing subwiki with the test cases and also the spaces which will hold the test execution pages. WDYT ? I am waiting for your opinions/concerns/questions about this. Regards, Sorin B. [1] https://github.com/xwiki-contrib/application-testreporting [2] http://www.xwiki.org/xwiki/bin/view/TestReports/ManualTestReportTemplate [3] https://github.com/xwiki-contrib/application-testreporting-cases

3 7

[xwiki-devs] What default language for our documents in releases XAR ?
by Thomas Mortagne 11 Jun '13

11 Jun '13

Hi devs, Right now the XAR plugin format goal systematically empty the <defaultLanguage> property. This is wrong IMO since it means we have no idea what is the default document language, it was not too visible before but it's really not very nice for things like the localization module and especially SOLR which store deferently the content depending on the language (stop words, etc). I see several possibilities: 1) We don't touch the XAR maven plugin and we state that when default language is not set, it's en (in the importer for example or in XWikiDocument#getDefaultLanguage) 2) We stop filtering default language in the XAR plugin and we set it to en for all document in which it make sense 3) We force default language to "en" in the XAR plugin WDYT ? I don't like too much 1) since some technical document could really be seen has having no default language, some document without any literal content. But it's more a -0 than a -1, I understand other would want this for simplicity. About 3) as I said having a default language empty is a valid use case IMO so -0 for this one to. Still a bit better than 1) since the use case is still possible. +1 for 2) -- Thomas Mortagne

6 19