xwiki-devs October 2012

xwiki-devs@xwiki.org

29 participants
67 discussions

[xwiki-devs] [PROPOSAL] Introduce MandatoryDocumentInitializer component

by Thomas Mortagne

Hi devs, In order to fix https://jira.xwiki.org/browse/XWIKI-8180 Extension Manager XAR handler need to access some way a mandatory document as it should be when it's "clean" so that It can then be used as previous version in a 3 ways merge. For that the idea is to introduce a new component based mandatory documents initialization and refactor XWiki#initializeMandatoryClasses to use it. This new MandatoryDocumentInitializer would allow: * provide a new mandatory document initializer from an extension since XWiki#initializeMandatoryClasses would lookup all of them * find a clean mandatory document state for a given document reference in extension manager XAR handler since that's the role hint of those components You can find an example of what a XWikiPreferencesDocumentInitializer would look like in https://github.com/xwiki/xwiki-platform/tree/feature-standardclasses branch. WDYT ? -- Thomas Mortagne

12 years, 2 months

[xwiki-devs] [ANN] XWiki Enterprise and XWiki Enterprise Manager 4.2 released.

by Jerome Velociter

The XWiki development team is proud to announce the availability of XWiki Enterprise 4.2. This is the third release of the 4.x cycle. This release brings extension manager improvements including an experimental install/upgrade wizard, new field types (emails, lists of pages, and computed fields), new macros (JIRA and content macros), macros improvements (chart and documents macros), as well as many other new features and improvements. You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download Make sure to review the release notes: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki42 Thanks -The XWiki dev team

12 years, 2 months

[xwiki-devs] [Proposal] XWiki 4.3 Roadmap

by Vincent Massol

Hi devs, Here's a proposal for the 4.3 roadmap. I'm putting names of committers I've discussed it with, please correct me if I'm wrong and please add any other items you'd like to do for 4.3 for committers not listed or even for committers listed if you want to work on other stuff! :) "Large Features" ============= - Improvements on Search Components SOLR Implementation - Assignee: Edy - Implementing Usability Action Plan: from Wysiwyg macros improvements, improvement dashboard look, Help center, XEM Usability - Assignee: JV - Improvements on AppWithinMinutes (according to the initial specs: user fields, suggests, validation, automated naming of pages, doc title + doc content, app generation quality) - Assignee: Marius with Sergiu for "automated page names" - Extension Manager Maintenance (testing, bug fixing, etc.) - Assignee: Thomas - Extension Manager Authentication - Assignee: Thomas - l10n module and especially automatic Registration of translation objects in wiki pages (similar to wiki macros) - Assignee: Thomas - Ludovic's Mobile Skin Patch - Assignee: Sergiu (if he gets the time) - Validating LibreOffice as standard Office Importer (brings pptx support) - Assignee: Sorin JIRAs: ====== There are 3 important JIRAs that we should commit on: - Be able to rename a space from the UI (also Rename Application) - XWIKI-6722 - Assignee: ? (Sergiu maybe if he gets the time) - Improvements on Dashboard editing - XWIKI-7681- Assignee: JV - User picker (User field does not scale to 1000 users - User picker implementation) - Assignee: Sergiu Other important JIRAs (but no commitment): - tag suggest feature does not work if Main.WebHome is not saved with programming rights - XE-539 - Tracking Active Installs - no JIRA yet - Vincent (I hope I can find the time) - Profile Improvements - XWIKI-6307 - Lucene Search should not return HTML tags - XWIKI-8111 - Search suggest does not use translation keys (Show all results... and No results!) Patch aleardy exists, it has to be applied - XWIKI-7138 - PDF Export when CDATA section (generated by Livetable) - XWIKI-7871 - App Within Minutes pages cannot be annotated (and any page using the HTML macro)- JIRA? Investigations: ============ - 4.x Skin. Assignee: Caty - Scalability Auditing. Assignee: Sorin - Mobile Skin + Mobile App investigation. Assignee: Ludovic Dates ===== - 4.3M1: 22 oct (3w) - 4.3M2: 5 nov (2w) - 4.3RC1: 12 nov (1w) - 4.3final: 19 nov (1w) Then 4.4 around beginning of January and 4.5 around beginning of February ==> 4.x cycle finished for early February. WDYT? Thanks -Vincent

12 years, 2 months

[xwiki-devs] Using Byteman to debug XWiki

by Vincent Massol

I've had a lot of fun using Byteman to debug some HSQLDB code last week. I wrote a quick tutorial to explain how it works: http://dev.xwiki.org/xwiki/bin/preview/Community/Debugging#HUsingByteman Enjoy! -Vincent PS: It's really really powerful and simpler to use than Aspects IMO when your use case is to debug stuff.

12 years, 2 months

[xwiki-devs] XWiki @ FOSDEM 2013 - Wiki devroom

by Vincent Massol

Hi guys, FYI I've just sent the following email for proposing a "wiki" devroom for FOSDEM 2013 (see https://fosdem.org/2013/call_for_devrooms.html): ------ start here ------- Hi guys, Several members of the XWiki community (on behalf of other wiki communities too) would like to kindly ask for a devroom at FOSDEM. Here are the details: * Devroom name: What's next for Wikis? * Description: Wiki systems have been proven as an effective way for organizing information and for encouraging and improving collaboration. Wikipedia is among one of the most obvious examples, but wikis have provided solutions in different contexts such education, e-democracy and also in the enterprise domain. By gathering together the experts in open source wiki systems, the goal of this devroom is to start a discussion between the different wiki communities about the next features and ideas they're all working on, with the intent of cross-pollination and synergies between wikis. The topics can also be broadened to discuss what makes wikis different from other collaboration tools today. * Project URLs: In addition to XWiki (we can have 5-10 persons from the XWiki community), we've contacted the MediaWiki and Foswiki communities and they've both agreed to participate to this devroom already. - http://xwiki.org - http://foswiki.org/ - http://www.mediawiki.org/ - http://dokuwiki.org/ - http://moinmo.in/ - any other open source wiki community interested in participating, the more the merrier! * Preferred day: Saturday * Why should FOSDEM accept this proposal? Because FOSDEM is one of the few conferences in the world where people from various wiki open source communities can meet! And because wikis are still a hot topic but they need to reinvent themselves to not lose steam vs all the other types of collaboration tools out there today and a global discussion with the open souce wiki actors on this topic would help a lot. Thanks a lot -Vincent Massol http://about.me/vmassol XWiki open source committer ------ end here ------- I'll let you know if our devroom is accepted. Thanks -Vincent

12 years, 2 months

[xwiki-devs] [VOTE] Introduce BlockCollection Block wrapper

by Thomas Mortagne

Hi devs, In many APIs we sometime want to manipulate several Block but we don't want to put them in a meaningful Block like XDOM which is supposed to mean a full document. Right now the only way to do it is to have both an API with Block and another with Collection<Block> but it's a bit more annoying for return type where you are forced to return a List<Block> even if you are in a case where you actually have only one Block to return like in macros for example. We talked a long time ago with Vincent about a BlockCollection which would not have any meaning (i.e. no corresponding event in the stream rendering API) and would just be here to be able to pass several blocks as a Block. Since UI extension is going to use it a lot I propose to introduce it now. WDYT ? Any better idea for the name ? Here is my +1. -- Thomas Mortagne

12 years, 2 months

[xwiki-devs] [PROPOSAL] Provide an AbstractScriptService best practice helper

by Thomas Mortagne

Hi devs, I find myself starting to copy past a lot of stuff from one ScriptService to another and I wanted to discuss with you think I find common enough to be put in a AbstractScriptService in xwiki-commons-script to be reused everywhere. As a discussion based I committed a first thing in https://github.com/xwiki/xwiki-commons/commit/a19c6df56fa984dacc9a8eeb50bb9… in a branch. So here are some ideas: * helper to set/get exception that every method is supposed to catch to make error handling in languages like velocity easier (in the commit) * helper to find a proper "safe" wrapper based on the type of an object (there is a example of such helper in https://github.com/xwiki/xwiki-commons/tree/master/xwiki-commons-core/xwiki…) Any other ? WDYT ? -- Thomas Mortagne

12 years, 2 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs October 2012