October 2014 - xwiki-devs@xwiki.org

[xwiki-devs] [Discussion] Where does livetable belong?
by Eduard Moraru 17 Oct '14

17 Oct '14

Hi devs, While looking into the delete space UI issue [1], we first thought about directly using the livetable macro to list the documents to be deleted from the space. Now the problem, as state by Vincent: Can/should we use the livetable inside templates? Is the livetable part of xwiki-platform-web or is a removable extension (xwiki-platform-livetable)? Currently, xwiki-platform-livetable only contains the 2 pages that generate the JSON for the livetable, but the html markup is generated by the #livetable macro (macros.vm) and the livetable.css and livetable.js files are all in xwiki-platform-web. The only case of it being used in templates right now is in rightsUI.vm [2] where the macro is not directly called, but the html markup is created by hand and the javascript and css is included. IMO, we should decide on a single approach for the livetable and use it all the way. What we do currently can be confusing even for us. I currently see two directions: 1) Move the content of xwiki-platform-livetable in a xwiki-platform-web as templates so that the livetable is a core feature and that it also works in the UI when the database is empty. 2) Move the livetable macro (as wiki macro?), js (as JSX) and css (as SSX) from xwiki-platform-web to xwiki-platform-livetable and see the livetable as just another extension/feature that is only present when installed. The rightsUI would need a change as well, since it can no longer rely on the livetable and probbaly we would also need to find a way to allow extenions to contribute filesystem resources. I thought it would be a good idea to open a discussion on this topic since it's currently, AFAIK, a grey area. WDYT? Thanks, Eduard ---------- [1] http://jira.xwiki.org/browse/XWIKI-8320 [2] https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi…

6 9

[xwiki-devs] [ANN] XWiki 6.3 Milestone 1 released
by Thomas Mortagne 17 Oct '14

17 Oct '14

The XWiki development team is proud to announce the availability of XWiki 6.3 Milestone 1. This milestone is mostly about improvements but it also introduce new Velocity tools and macros and also add support for catching and display nicely exceptions in Velocity. 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/ReleaseNotesXWiki63M1 Thanks -The XWiki dev team

1 0

[xwiki-devs] [Proposal] New strategy for finding the next Release Manager
by vincent＠massol.net 17 Oct '14

17 Oct '14

Hi devs, It’s been a pain to find the next Release Manager lately so I discussed with other committers and here’s what we would like to propose: Proposal ======== * We have a list of declared Release Managers. This list would start with the following persons: - enygma - evalica - gdelhumeau - mflorea - tmortagne - vmassol If any other existing committers are willing to help the project and become a Release Manager please reply to this thread! That would help the project for sure :) Actually when new committers are added to the project we should ask them if they’d be willing to do releases. * If at any point a committer not in the Release Manager list would like to do a release, he’s more than welcome to do it! * We take turns, following the initial order. When a newcomer is added he's inserted at the bottom of the list. * If a committer cannot do the release for a reason or another (sick, holiday, workload, etc) he’s still responsible for the release and he/she needs to find a replacement. He also has the option to propose changing the release date but that needs to be accepted by the project. If he/she finds a replacement, it’s up to them to decide together who will do the release the next time that replacement’s time comes. * All releases are included (milestones, RCs, final, bugfix releases). * We switch RM at each release (be it a milestone, RC, final or bugfix release). * We put the RM list, order and upcoming releases on http://dev.xwiki.org/xwiki/bin/view/Community/ReleaseManagerRoster Bootstrapping ============= * We have 3 releases to do with some volunteers already: - 13th of Oct: 5.3M1 - Not defined - 15th of Oct: 6.2.2 - Vincent - 5.4.6 (no date defined AFAIK but ASAP) - Guillaume * Thus I propose to start with the following: - vmassol - 6.2.2 - gdelhumeau - 5.4.6 - tmortagne - 6.3M1 - enygma - following release (not known yet - 6.3M2, 6.2.3 or 5.4.7) - evalica - following release (not known yet) - mflorea - following release (not known yet) - vmassol - following release (not known yet) - ... I propose that we try this and fine-tune as we progress. Let me know if you agree or disagree. Thanks -Vincent PS: This is not a vote since I feel that only the person in the list should have a say on this since they’re the one who are going to do the hard work for the moment so it would be bad form for other committers to vote on this if they don’t participate ;) They can still voice their opinion of course...

5 5

[xwiki-devs] My tiny noticed about the top menu (merging buttons again)...
by Pascal BASTIEN 16 Oct '14

16 Oct '14

Hello, At my opinion, It's a pity to come back at 2 click to access at space/page because buttons are no longer split into two parts.... User must click twice to access at space (it is probably the most used case) for this button. But the the most annoying is: javascript with this merging buttons. An current example: I click on Space button and Go to space but during the loading I made a mistake and I would quickly access to page (or wiki) before the javascript loading: it is impossible because I must waiting some seconds to click Backspace, waiting again and then click on Page - Go to page. On 6.2.1 there are not this problem: I could click on Space/Page button before JS loading. Of course, with top menu CSS we would no have this problem but bootstrap required JS, then for my case, the quick issue is to modify template to come back at top menu splitting. :-) Pascal BASTIEN

2 2

Re: [xwiki-devs] My tiny noticed about the top menu (merging buttons again)...
by vincent＠massol.net 16 Oct '14

16 Oct '14

Hi, On 16 Oct 2014 at 17:18:29, Pascal BASTIEN ([email protected](mailto:[email protected])) wrote: > Hello, > > At my opinion, It's a pity to come back at 2 click to access at space/page because buttons are no longer split into two parts.... > User must click twice to access at space (it is probably the most used case) for this button. Some points related to this topic: * You can also access it through the breadcrumb with one click. That may even be more logical because in the majority of cases you want to navigate to the parent of the current page and not necessarily to the space home page. * For general navigation, I believe what we need is a good Navigation panel and Marius is working on that at this moment. Thanks -Vincent > But the the most annoying is: javascript with this merging buttons. > An current example: I click on Space button and Go to space but during the loading I made a mistake and I would quickly access to page (or wiki) before the javascript loading: it is impossible because I must waiting some seconds to click Backspace, waiting again and then click on Page - Go to page. > > On 6.2.1 there are not this problem: I could click on Space/Page button before JS loading. > > Of course, with top menu CSS we would no have this problem but bootstrap required JS, then for my case, the quick issue is to modify template to come back at top menu splitting. :-) > > > Pascal BASTIEN

1 0

[xwiki-devs] [ANN] XWiki 5.4.6 released
by Guillaume "Louis-Marie" Delhumeau 16 Oct '14

16 Oct '14

The XWiki development team is proud to announce the availability of XWiki 5.4.6. This release is a stabilization version that fix important bugs discovered in the 5.4.5 version. 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/ReleaseNotesXWiki546 Thanks -The XWiki dev team

1 0

[xwiki-devs] [Proposal] XWiki 6.2.3
by vincent＠massol.net 15 Oct '14

15 Oct '14

Hi devs, We’ve just released 6.2.2 and we had 51 issues fixed (in 2 weeks). What this means is that we haven’t stabilized 6.2.x yet… Thus I’m proposing to plan ahead a 6.2.3 release. I propose to release 6.2.3 in 2 weeks time, i.e. for the 29th of October (Note: it’s about the same time as the 6.3M2 release). If there are not enough issues in it, we can always decide to cancel it but, unfortunately, I doubt that... What this also means is that we should continue backporting important bugs on the stable-6.2.x branch. We now have a strategy for finding RMs but I’m also ok to perform this release myself if need be. WDYT? Thanks -Vincent

1 0

[xwiki-devs] [ANN] XWiki 6.2.2 released
by vincent＠massol.net 15 Oct '14

15 Oct '14

The XWiki development team is proud to announce the availability of XWiki 6.2.2. This is a bug fix release with lots of issues fixed to stabilize the recent Flamingo skin. 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/ReleaseNotesXWiki622 Thanks -The XWiki dev team

1 0

[xwiki-devs] [Contrib] SecureJira Macro
by Antoine Roger 15 Oct '14

15 Oct '14

Hello, I would like to introduce the macro; The securejira macro allow user to get jira task with user authentification. You can manage username/password/jira_url directly from the administration area. Repo name should be: macro-securejira My github account is: 42aroger Thank you!

2 1

[xwiki-devs] [Proposal] Remove some meta tags
by Guillaume "Louis-Marie" Delhumeau 15 Oct '14

15 Oct '14

Hello. Flamingo is still not HTML5 valid, so I am working on it. We actually use some <meta> tags that are become invalid in HTML5. = X-UA-Compatible = <meta http-equiv="X-UA-Compatible" content="IE=edge" /> It forces the Compatibility mode for IE browsers to use the latest rendering mode. We can replace it by adding the X-UA-Compatible in the HTTP headers, but I actually propose to surround this tag like this:  The code is valid (because inside a comment so the validator does not parse it) and it is still usable with IE. = imagetoolbar = <meta http-equiv="imagetoolbar" content="no"/> it disables the toolbar that comes up when you mouse over an image in MSIE. Same, I propose to add a conditional comment:  = Content-Script-Type = <meta http-equiv="Content-Script-Type" content="text/javascript" /> It defines the default scripting language that is used for intrinsic events (e.g. onmouseover attributes). This tag has been deprecated, and there is nothing to replace it. I don't think this tag is very useful because most of the browsers assume that an intrinsic event will be handled by javascript. Actually I did not know this meta tag before today and my inline javascript did always work! So I propose to just remove it. = Distribution = <meta name="distribution" content="GLOBAL" /> (from XWiki.XWikiPreferences) It actually defines either the website should be considered as public or local (see See http://www.metatags.info/meta_name_distribution) I propose to remove it. = reply-to = <meta http-equiv="reply-to" content="" /> (from XWiki.XWikiPreferences) To be useful, the content should not be empty, so the administrator should set it. Moreover, it is very not well-known, and it could be a problem since the spam bots can read it. I propose to remove it. If the administrator wants it, she can put it in the preferences, with the proper value filled. = language = <meta name="language" content="en" /> (from XWiki.XWikiPreferences) It is actually redundant with <html lang="en">. I propose to remove it. What do you think? Thanks, -- Guillaume Delhumeau (gdelhumeau(a)xwiki.com) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project

2 4