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

[xwiki-devs] [VOTE] Adding the Locale into the document reference of XWikiDocuments
by Denis Gervalle 16 Dec '11

16 Dec '11

Hi Devs, I am looking at now using the new Locale added in DocumentReference into the implementation of XWikiDocument. I have already deprecated language related stuff in XWikiDocument, and I have introduce a XWikiDocument#getLocale and an XWikiDocument#isTranslation helper since the deprecation of defaultLanguage will increase the need of it. I have also added XWikiDocument#getTranslatedDocument() with Locale in place of language. All the changes are almost backward compatible, which is nice (there is some subtleties with default, "" and null that is now more equivalent, but should not have consequences). The is however one change that is not backward compatible, which is the change of the document reference. Therefore, XWikiDocument#getDocumentReference does not return the same reference than it does before, because this reference now contains the Locale. This cause breakage in several places. I see some option to fix this: A. Fix all places broken. This may be too long for me, and not trivial. B. Introduce a new XWikiDocument#getDocumentReferenceWithLocale() and have XWikiDocument#getDocumentRefence() returns without Locale. Very easy, but not nice. C. Introduce a new XWikiDocument#getDocumentReferenceWithoutLocale() and change all existing calls to XWikiDocument#getDocumentRefence() in platform to use this one. Nicer, but this is not fully backward compatible. Since I am on it right now, I would appreciate your opinion quickly. WDYT ? I am undecided between B and C -- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO

3 6

[xwiki-devs] [Proposal] Improving the "Product Documentation" and "Getting Started" pages
by Silvia Rusu 15 Dec '11

15 Dec '11

Hi, Caty and Vincent are doing a very nice job improving xwiki.org's look and navigation. I think improving a bit the content is also a good idea, so I have a few proposals in this direction. * Improving the Documentation landing page, available from the website menu (http://www.xwiki.org/xwiki/bin/view/Main/ProductDocumentation) Here is a proposal with some small additions: http://dev.xwiki.org/xwiki/bin/view/Drafts/DocumentationImprovedHomepage * Improving the Getting Started guide's WebHome (http://enterprise.xwiki.org/xwiki/bin/view/GettingStarted/WebHome) Draft proposal at: http://dev.xwiki.org/xwiki/bin/view/Drafts/GettingStartedPage * We could also use the "Getting Started" page proposed above on XWiki Enterprise (the product). This would be a page inside the wiki (e.g. like the Sandbox or Syntax pages) which would be linked from the wiki Homepage. It could be helpful to wiki users who don't know where to look for information. Waiting for your feedback and votes. Thanks, Silvia

2 1

[xwiki-devs] [VOTE] Change the default to non-backup instead of backup import when creating a new wiki template from xar in the wiki-manager module
by Eduard Moraru 15 Dec '11

15 Dec '11

Hi devs, Right now, when you create a wiki template from a xar, the import that is done in the background is a backup import, meaning that the last author of the pages that get imported in the new wiki keep the author specified by the xar. This often creates problems like: - Missing Programming Rights - Unregistered macros - Malfunctioning scripts These problems can appear because the user specified in the xar (even if it is XWiki.Admin) is almost always a local user and subwiki local users do not have PR. If it's not a PR issue, then the user specified in the xar can be non-existent and this makes admin checks fail, thus failing wiki macro registration for the entire subwiki. We are currently experiencing this problem in Workspaces, since, at the install step, we create a workspace template by using a workspace-template.xar (default XE but can also be user provided). Since we make sure to delete any local users (including XWiki.Admin), the Wiki macros will not be registered in the template and, obviously, neither in any created workspace. I`m hoping to include this in 3.3 final so that Workspaces can avoid the macro registration problems (and possibly others). So I`m asking for your vote to change the current default to non-backup. This means that all the pages in the new subwiki template will have the current admin user that created the template as last author. Here's my +1. Thanks, Eduard

5 6

[xwiki-devs] Use complex expressions in i18n choice
by coldserenity 12 Dec '11

12 Dec '11

Hello, Doing a translation I found this message to translate {0,choice,0#No|1#One|1<{0}} included {0,choice,0#documents.|1#document:|1} So I wonder is it possible to use arithmetic expression like {0}%10 in those choice statements because in my language, the noun's ending depends on the last digit in a number . Directing me to the page describing full syntax for the language above would be enough. Regards, Roman -- View this message in context: http://xwiki.475771.n2.nabble.com/Use-complex-expressions-in-i18n-choice-tp… Sent from the XWiki- Dev mailing list archive at Nabble.com.

4 7

[xwiki-devs] Why h1 in panel headers ?
by Jerome Velociter 10 Dec '11

10 Dec '11

Hello, I've realized recently that panel titles are exposed in h1. For example : <h1 class="xwikipaneltitle">Quick Links</h1> I don't think that's the best we can offer semantically. Panels are not very import sections of the page. Maybe h2 would be more appropriate ? WDYT ? Jérôme Velociter Winesquare http://www.winesquare.net/

1 0

[xwiki-devs] Changes in the XEM distribution to workspace cause unexpected issue to existing XEM users and even new ones
by Denis Gervalle 10 Dec '11

10 Dec '11

Hi devs, I have just installed the XEM distribution has an upgrade of an existing farm. I have discovered that the new distribution cause an new DB to be created without any confirmation on first access to Main.WebHome to contains the workspace template required by the new workspace feature. IMO, this does not follow the vote we have had before about this change, since existing user of XEM are immediately impacted by the new feature. I would have been -1 if I would have been aware of this. Creating the new database this way has for me some inconveniences: - For new user, after having a possibly hard time setting up the server, there first successful access on the wiki could end in an error, since the creation of the new database could goes wrong. - For existing user, a new database is created without there agreement on there farm. If they delete it, it will probably came back again and again... They really need to understand that the simple access to the home page cause the creation of a new database. IMO, these are not good first experiences with the new release. I propose that the creation of the new database requires at least a user confirmation, and that if the user do not confirm, it should not be tried anymore. This will have two advantage, the user is well aware that a other new database is under creation in case of error, and existing farm user will have an easy way out. WDYT ? -- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO

4 7

[xwiki-devs] XEM Workspaces Install
by Ludovic Dubost 08 Dec '11

08 Dec '11

Hi, I just tried the XEM snapshot and got an error when trying to configure it. I get this after login as Admin: Workspace Manager translations have been successfully installed. Workspace search suggestions have been successfully installed. Error installing workspace template. null Workspace template features can not be installed without the workspace base template being installed first. I also agree with Denis that any install should be done with a confirmation. Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

3 8

[xwiki-devs] |VOTE] Merge improved CM in master
by Thomas Mortagne 08 Dec '11

08 Dec '11

Hi devs, Now that master just moved to 3.4-SNAPSHOT I would like to merge my refactoring of the component manager. You can find the branch on https://github.com/xwiki/xwiki-commons/tree/feature-improvecm. The rational is that it's then going to be indirectly tested during the whole 3.4 timeframe. Never too careful with the most critical code. I already detailed this on another mail but the major difference with current implementation is that it's locking a lot less and since CM is pretty heavily used (and is going to be used more and more) it should make a noticeable difference. It also fix several bugs I found while doing this refactoring and covering it with tests. Here are the related jira issues: * http://jira.xwiki.org/browse/XCOMMONS-63 * http://jira.xwiki.org/browse/XCOMMONS-65 * http://jira.xwiki.org/browse/XCOMMONS-64 * http://jira.xwiki.org/browse/XCOMMONS-66 Here is my +1 Thanks, -- Thomas Mortagne

5 7

[xwiki-devs] Push on translations
by Ludovic Dubost 08 Dec '11

08 Dec '11

Hi XWiki devs and users, I think we need to make a push on translations. We have about 150 translations that are not yet available in French German Latvian Russian Swedish Otherwise we have the following language that would need a small push to get complete: Spanish (es) 459 translations Czech (cs) 258 translations Traditional Chinese (zh_TW) 641 Catalan 863 It would be great to get some contributors for Italian Portugese Dutch Any help is welcome to get this down. If you want to help you can go to http://l10n.xwiki.org If we get the translations numbers under 250 we'll make sure we get the translations in the distribution. Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

1 0

[xwiki-devs] [Idea] Switch to HTML5 doctype ?
by Jerome Velociter 06 Dec '11

06 Dec '11

Hello, Since we are dropping support for IE6 and IE7, wouldn't it be a good time to switch to the HTML5 doctype [1] ? It would also force IE8 to render in non-compatibility mode (meaning using the IE8 rendering engine), as a good side effect. [2] Maybe we can do this in XE 3.4 ? WDYT ? Jerome [1] http://en.wikipedia.org/wiki/HTML5#Markup [2] http://ejohn.org/blog/html5-doctype/ -- Jérôme Velociter Winesquare http://www.winesquare.net/

3 4