xwiki-devs August 2014

xwiki-devs@xwiki.org

29 participants
65 discussions

[xwiki-devs] [VOTE] Start supporting IE10 and IE11

by Andreea Popescu

Hello all, Following the "Start supporting IE10 and IE11" thread I’d like to propose to vote if we will support IE10 and IE11. The most important reasons for supporting these versions are: - Internet Explorer 8 and Internet Explorer 9 are still widely used by users, but many of them are currently choosing to update to IE10 and IE11. - according to netmarketshare.com (Browsers -> Desktop Share by Version) from a total of 100%, IE10 is used by 6.85% users and IE11 by 16.61% users. It’s true that IE10 is not as popular as the older versions (IE8 - 20.85% and IE9 - 8.89%), but its usage percentage is still significant. Here’s my +1. Andreea

10 years, 3 months

[xwiki-devs] [Proposal] Drop the 6.0.x branch/6.0.2 JIRA version and 6.0.x jenkins build

by vincent＠massol.net

Hi devs, I’d like to drop the 6.0.x branch/6.0.2 JIRA version and 6.0.x jenkins build. Even though we’ve released a 6.0.1 I don’t think we’re prepared to release a 6.0.2 version now that we’ve had 6.1 released and 6.2 getting close. Actually I have a personal wish to make 6.2 a very stable release (with possibly a 6.2.1 and 6.2.2 release coming soon after the 6.2 release). So I don’t think we need a 6.0.2. If nobody disagrees I’ll perform the cleanup at the beginning of next week. Thanks -Vincent

10 years, 3 months

[xwiki-devs] [XWiki Day] BFD #62

by vincent＠massol.net

Hi devs, For tomorrow I propose a BFD (BFD#62): http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays If we check the 1 year status we’re behind by 28 bugs, see: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10000#Created-vs-R… So it would be nice to be able to catch up on bugs for the past year! (even though on 1600 days we’re still good) Thanks -Vincent

10 years, 3 months

[xwiki-devs] [Rant][Brainstorming] On the concept of Applications in XWiki

by Eduard Moraru

Hi devs, While thinking about XWIKI-8757 [1] and the fact that the new skin focuses [2] a lot on applications, a number of questions pop up inevitably because of XWiki's loose/ad-hoc way of handling/defining applications. For the AWM problem, I came to the conclusion that we should probably just adapt AWM to use the current convention we have for apps (1 code space and 1 data space) and maybe set the user that created the app as the only one allowed to edit it (have to think about the last part). It seems that this would be best for data-producing applications, such as the ones created by AWM. I`ll list below the questions because I believe they also serve as a summary of the discussions on the topic so far. 1) What is an application? General/Philosophical - Skin/Macro/Class/Code/etc. or just simply "Application"? 2) What is the name, description, icon, author, etc of an application? Metadata - Application descriptor - Panel application UIX should read from an app descriptor to avoid duplication - Extension vs Application -- Every (xar) extension is an application, but most applications (in the wild or just created ones) are not extensions => EM can not reliably provide information about applications. 3) How do I access an application? Structure/Management - UI applications (i.e. IdeasApp) vs Code/Feature applications (i.e. ActivityStream, Syntax Highlighting) - All apps must have 1 entry point, even if it's just some description or a configuration? -- You should not be able to lose an application after you install it. 4) What are the installed applications Management 5) Where is the code, data or configuration of an application? Structure - ((One App = One Space) vs (One code space and one data space)) vs Reality (messy mix) - One page applications (no data) 6) What application(s) do these pages belong to? Structure - Using classes defined by 2 applications in the same page. 7) Who can(not) edit an application? Rights See XWIKI-8757 [1] - most users are application users and not developers, but they are encouraged to edit everything, even the applications themselves. This leads to a maintainance hell for wiki admins that end up with broken applications. - edit rights on the code. 8) Who can(not) use an application? Rights - view rights on the code. Related topics: - Application Descriptor [3] - this discussion went off-topic - Flamingo Application Bar [2] - application metadata is needed - Best practices for storing Application pages [4] I hope someone finds this useful somehow. Thanks, Eduard ---------- [1] http://jira.xwiki.org/browse/XWIKI-8757 [2] http://markmail.org/thread/2ftksr6bxstazg25 [3] http://markmail.org/thread/wqdidryh5ubgvkxa [4] http://markmail.org/thread/467rqhucp5ild273

10 years, 3 months

[xwiki-devs] Create A Page Only If User Login Has Admin Roles.

by Firmusoft Xwiki

Hi Sir; I have an independent HTML/JavaScript application running in XWiki and it can create XWiki pages by sending AJAX request. I need to create those pages ONLY if the logged in user has admin roles. How can I do this ? (a) Is there any way to send back response with JSON/XML from Xwiki pages ? (i.e. If we can send the response with JSON/XML from XWiki page, then I need to use a Ajax call from my application) (b) Or any API available to access the XWikiContext via Servlet ? (i.e. If it is available, then send request to my Servlet) Please help and if you can provide any samples would be great. Thank you for considering..! -Sincerely- Suresh Babu P

10 years, 3 months

[xwiki-devs] XWiki Scalability/Challenge Question

by Danilo Oliveira

Hello Devs, I am developing an application based on XWiki that is mapping, connecting, relating and graphical disposing movie information in order to make possible to the user explore their trailers. At the beginning with a light data set (<5k movies) the application was running well, but today I started to populate my database (MYSQL) and the application became unusable, the queries is taking more than 5 minutes to complete. Actually, it has more than 15k movies (1 movie = 1 doc) and I need to upload more 100k. I already have checked the cache and performance page but I don't know if they[1][2] solve my problem: I think that is a architecture challenge. My AS IS process is: -User insert a movie, -the application search for the movie and their related films based on its characteristics (a lot of joins and other algorithms) (bottleneck) -the application returns the results as a map; I am wondering if I could use the custom mapping[3] to solve my problem due the fact that the relationship information for each movie, in this first moment, don't need to change often. Each movie has X movies related, sorted by similarity. So, I could create some relationship algorithm that will run scheduled ( 1 time by week) and populate this new table .I am thinking to use dataframe panda of python to talk directlly with mysql and make data analysis, any other suggestion? So I would create a custom map to my relationship movie class, run the algorithm, populate the new table, so my TO BE would be: TO BE -user insert movie info; -simple select on the customtable "MoviesRelated"; -the application returns the results; I would appreciate some opinion. Thank you very much. [1]http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Performances [2]http://extensions.xwiki.org/xwiki/bin/view/Extension/Cache+Module [3]http://platform.xwiki.org/xwiki/bin/view/DevGuide/CustomMapping Danilo -- Danilo Amaral de Oliveira Engenheiro de Computação celular (32) 9111 - 6867

10 years, 3 months

[xwiki-devs] [Brainstorming] Should we support only one skin in our functional tests or not?

by vincent＠massol.net

Hi devs, ATM our selenium2-based test fwk for functional tests only supports one skin (Colibri). Guillaume is currently fixing the functional tests by changing our test framework to work with Flamingo. After his changes are made our framework won’t work anymore with Colibri. The question is: * Is this ok? * Do we want to change the framework to support multiple skins? In this case we would need to introduce Interfaces everywhere, for each Page Object to have various implementations. One example of difference is Hover vs Clicking for the top level menus. Another example is that we don’t have anymore a contentmenu; it’s 3 buttons. Etc. Any opinion? Thanks -Vincent

10 years, 3 months

[xwiki-devs] Release Manager needed for 6.2 RC1

by Eduard Moraru

Hi devs, Starting tomorrow and the full next week I won`t be available (holidays), so we need to find someone to take care of the 6.2 RC1 release on Monday. Also, we`d need someone to manage the next 2 XWiki days (tomorrow and next Thursday). Any (committer) volunteers for any of the 2 tasks? Thanks, Eduard

10 years, 3 months

[xwiki-devs] [ANN] XWiki 6.2 Milestone 2 released

by Eduard Moraru

The XWiki development team is proud to announce the availability of XWiki 6.2 Milestone 2. This release mostly focuses on the Flaming skin and sets it as the new default skin for XWiki. A new themes application for the new skin is introduces, along with the AppBar set by default and other various UI polishes and improvements. On the developers side, a new "blame" API has been introduced and some dependencies were upgraded. Finally, a considerable amount of bug fixes (34) and improvements (32) were made so make sure to try it out. 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/ReleaseNotesXWiki62M2 Thanks -The XWiki dev team

10 years, 3 months

[xwiki-devs] About the broken build

by Guillaume "Louis-Marie" Delhumeau

Hi devs. As you might know, the build is currently broken for ~2 weeks. It is due to the fact that I have set Flamingo by default since August, 6th. I have not changed the functional tests that are still designed for Colibri so they fails because some behaviours has changed (like clicking on a menu instead of hovering it to see a submenu, etc...). I'm sorry about all the inconveniences that the broken build have made for the community (public image, difficulty to point out which commit have introduced a regression, etc...). I am now working at fixing the failing tests. It should take time and any help is welcome. Please tell me if it creates problems for you. The other solution would be to put flamingo by default on a distinct branch and to merge it when all tests pass, but it would slow down the Flamingo skin stabilization by not being viewable by everybody. Thanks, Guillaume

10 years, 3 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs August 2014