June 2011 - xwiki-devs@xwiki.org

[xwiki-devs] [Proposal][UX][Usability] Usability Surveys
by Ecaterina Moraru (Valica) 08 Jun '11

08 Jun '11

Hi, I've created a proposal for two usability surveys (the fields are not functional) * General Aspects http://incubator.myxwiki.org/xwiki/bin/view/Improvements/UsabilitySurveyGen… * Page Features http://incubator.myxwiki.org/xwiki/bin/view/Improvements/UsabilitySurveyPage I'd like to know what do you think of the surveys' questions. Like the Page Features survey we could create additional surveys that target specific problems we have or want to learn more about them. Thanks, Caty

1 1

[xwiki-devs] [Proposal][UX] Application Within Minutes - Proposal 2
by Ecaterina Moraru (Valica) 08 Jun '11

08 Jun '11

Hi, According to the feedback received I've made another proposal for the Application Within Minutes http://incubator.myxwiki.org/xwiki/bin/view/Improvements/ApplicationWithinM… Changes: - Wizard style creation - Structure in a form editor style (drag&drop, refresh preview on change) Remarks: - "Create application" could be part of the action menu's "Add" submenu and act as a wizard for the creation process. As a result we will have a space for each application that will list on it's homepage the entries livetable. The structure will be changed by entering again the wizard. Thanks, Caty References: [Proposal][UX] Application Within Minutes - Proposal 1: http://xwiki.markmail.org/thread/tvxnoabhbwfcpwmk

6 10

Re: [xwiki-devs] Status
by 许凌志(Jamesxu) 08 Jun '11

08 Jun '11

OK, Marius, I am working for finnal exam all these days after I finishing XWIK-5560, and till now, I have finnished most of exams except one in 10th June, But it is easy, so I am going on these days. Though I am busy with final exams, I still did some prepares for my projects, I have done the following things: 1. I read the some of the source codes of wysiwyg client, found that if I want to listen to the event when user input in wysiwyg editor, I should extend the onKeyUp function in WysiwygEditor.java<https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi…>which is inherited from RichTextEditorController.java<https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwi…>. 2. I am thinking that I can implement the auto-suggestion features without working on the GWT code because there is some APIs for me to hook in the wysiwyg editors, I can use getRichTextArea() function to get the richtextarea object, then add some listeners to it. Here is the sample code, in the callback function of the listeners, we can use getSelectionRange to get the range object of rich text area, it is the base for add auto-suggestion widget to rich text area, what do you think? document.observe('xwiki:wysiwyg:loaded', function() { var editors = Wysiwyg.getAllInstances(); var IsIE=navigator.appName!="Netscape"; for(var hookId in editors){ var editor = editors[hookId]; var richEditor = editor.getRichTextArea(); var frm = richEditor.contentWindow if(IsIE){ frm.document.onkeyup = function(){ console.debug(editor.getSelectionRange()) } frm.document.onmousedown = function(){ console.debug(editor.getSelectionRange()) } frm.document.onmouseup = function(){ console.debug(editor.getSelectionRange()) } } else { frm.document.addEventListener("keyup", function(e) { console.debug(editor.getSelectionRange()) } ,false); frm.document.addEventListener("mousedown", function(e) { console.debug(editor.getSelectionRange()) } ,false); frm.document.addEventListener("mouseup", function(e) { console.debug(editor.getSelectionRange()) } ,false); } } }) 3. For wiki editor, I think there are two most important things I should notice: a. Get the position of the input cursor, and get the context, if the cursor is in the context of "[[ link or image ]]" or "{{ macros }}", then initialized the auto-suggestion under this context, and show up auto-suggestion widget according to user input. b. Listen to the user input, and trigger the auto-suggestion widget when "[[" or "{{" are typed. I am still doing some tests now, so if you have some tips for me, please tell me. On Fri, Jun 3, 2011 at 1:02 AM, Marius Dumitru Florea < mariusdumitru.florea(a)xwiki.com> wrote: > Hi James, > > How is the GSoC work going on? Hope everything is fine. Ping me if you need > help. > > Thanks, > Marius > -- Best wishes, 许凌志(Jame Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

2 5

[xwiki-devs] [PROPOSAL] Introduce XClass property reference
by Thomas Mortagne 07 Jun '11

07 Jun '11

Hi dev, I would like to introduce class property entity type and related reference and syntax separator. For the separator syntax I propose to use the same thing as object separator since you can't have both in the same reference and it's always a pain to find a new separator. Note that I'm inly talking about class property and not class since class reference is exactly the same thing as document reference I don't think we really need to have a specific one. WDYT ? -- Thomas Mortagne

5 12

[xwiki-devs] XWiki Enterprise 3.1 Milestone 2 Released.
by Caleb James DeLisle 07 Jun '11

07 Jun '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The XWiki development team is proud to announce the release of XWiki Enterprise 3.1 Milestone 2. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download This is the second and final milestone in the 3.1 development cycle, you can review the changes made and bugs fixed since 3.0 by going to: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterpris… Thanks - -The XWiki development team If you would like to download the new release now, you can using these links: - ---- XWiki Enterprise for Servers ---- xwiki-enterprise-web-3.1-milestone-2.war SHA1: 1e903ab1bb230e6823597db2c6034ecd27a4275a http://forge.ow2.org/project/download.php?group_id=170&file_id=16712 xwiki-enterprise-wiki-3.1-milestone-2.xar SHA1: c82aa727bf6a81929d91c1e9182921eac9e0ea7e http://forge.ow2.org/project/download.php?group_id=170&file_id=16713 - ---- XWiki Enterprise Standalone ---- xwiki-enterprise-installer-windows-3.1-milestone-2.exe SHA1: 9f71d54eeff3b136454d15164e94b5484815ebf3 http://forge.ow2.org/project/download.php?group_id=170&file_id=16711 xwiki-enterprise-jetty-hsqldb-3.1-milestone-2.zip SHA1: fa04ee328387ab48bbf5a8f5b2fab22e4684858e http://forge.ow2.org/project/download.php?group_id=170&file_id=16719 xwiki-enterprise-installer-generic-3.1-milestone-2-standard.jar SHA1: b93969196e73e30ffc6a65cd6033b03ebdfc1a85 http://forge.ow2.org/project/download.php?group_id=170&file_id=16710 - ---- XWiki Manager for Servers ---- xwiki-manager-web-3.1-milestone-2.war SHA1: 12f514ddd2913378b07b8b43b5654dbb6ad33ed8 http://forge.ow2.org/project/download.php?group_id=170&file_id=16714 xwiki-manager-wiki-administrator-3.1-milestone-2.xar SHA1: 9183f4f069c388ff9963e2ce877b6d75799fe4fa http://forge.ow2.org/project/download.php?group_id=170&file_id=16716 - ---- XWiki Manager Standalone ---- xwiki-manager-jetty-mysql-3.1-milestone-2.zip SHA1: 63a7d30511931fb10569fb4a82c5c42f367f9467 http://forge.ow2.org/project/download.php?group_id=170&file_id=16718 - ---- XWiki Manager Extension for XWiki Enterprise Installations ---- xwiki-manager-application-xem-3.1-milestone-2.xar SHA1: d5381326b71057182256d6aa9eec777b647739aa http://forge.ow2.org/project/download.php?group_id=170&file_id=16717 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iQIcBAEBAgAGBQJN3LFoAAoJECYAmptlsgnWjikP/2dVAZyyWcFzh9paefuqwAXm NDvW6VA/0nHVOhMhzlvyjjpBKW4tAujQqIT2eL9dn5SG2tCygQ6lLE7r6zwFJY0t LHkOtqtK4lRiFJfu7+h/f3/yYRi3mKwht0d8z0lc74w+ACB6VKSfIdcIwh1u7Klm UXNh43lbIJNABGYapGe/aLwr3q7qFZp+sKaO3aVW5cVVzup3KnQPHV9BqgRYfqDd fWip1zZCixJ/yOOQ8VNpNRvr8mVST9pettKmDb6HlLjqvrV+qrX306zIvhcPFoKk tkHZQJaFsf9Sg8pv+U+tBVgvJIcWbf+PeAJKhIU1MPz8wc54bvDGhqBpH1VwLGUD 8W8vhzPs4rnP/w5nKWz15R4KEPBHuzUMx6oEcwPx7G7L8f+tnlAifWJLzQJP1A1U JTADeQ7GnIZ/Jg6ycWeDIIgZLOl6TrzEaDYMTWF6sXElvYfUilrdhJZ1Upbv2aul R2bWqF7Ia//FQxMGNPhwTwF7fsPExJaFQ/OEeoSumusZIl/NGc4gjrytZA2VY2t0 c3zW2CAd8JryJujFuQtbj51rYvKMnDtp3+419pkfmbs5Vg33hFKrKB30xV7nrsm5 zN9itvj7APKy3tndUph2YXaNYlXkrAe2o1B6R8gXw0M8qV/0gVmL2G0DN5d3Vu6x BG460gFTusnCwQXW8TYG =XTgI -----END PGP SIGNATURE-----

2 1

[xwiki-devs] XWiki Enterprise 3.1 Milestone 2 Released.
by Caleb James DeLisle 07 Jun '11

07 Jun '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The XWiki development team is proud to announce the release of XWiki Enterprise 3.1 Release Candidate 1. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download Unless a new bug is discovered, this will become the 3.1 final version. This release was a stability and bug-fix only release so there are no new features. You can read about bugs fixed and translation updates by going to: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterpris… Thanks - -The XWiki development team If you would like to download the new release now, you can using these links: - ---- XWiki Enterprise for Servers ---- xwiki-enterprise-web-3.1-rc-1.war SHA1: 0afab6a2cf62cff56c2351ce5ee5916e3be3eb60 http://forge.ow2.org/project/download.php?group_id=170&file_id=16747 xwiki-enterprise-wiki-3.1-rc-1.xar SHA1: 7286b367c735b8a667a4cb00c7b8403001027821 http://forge.ow2.org/project/download.php?group_id=170&file_id=16745 - ---- XWiki Enterprise Standalone ---- xwiki-enterprise-installer-windows-3.1-rc-1.exe SHA1: 5f71b52c823fc92474a28caebf89af56b176c6a8 http://forge.ow2.org/project/download.php?group_id=170&file_id=16750 xwiki-enterprise-jetty-hsqldb-3.1-rc-1.zip SHA1: 870553bbac3f720135780ee0b89398e38e87797f http://forge.ow2.org/project/download.php?group_id=170&file_id=16748 xwiki-enterprise-installer-generic-3.1-rc-1-standard.jar SHA1: 123309d14972c2391b1824b33a2ce20b11464005 http://forge.ow2.org/project/download.php?group_id=170&file_id=16749 - ---- XWiki Manager for Servers ---- xwiki-manager-web-3.1-rc-1.war SHA1: 0313a8d54053a61e12f1651216c1b64d9989c184 http://forge.ow2.org/project/download.php?group_id=170&file_id=16754 xwiki-manager-wiki-administrator-3.1-rc-1.xar SHA1: 4551d78e9f7b66f6cae3f10982ac69284c05386f http://forge.ow2.org/project/download.php?group_id=170&file_id=16753 - ---- XWiki Manager Standalone ---- xwiki-manager-jetty-mysql-3.1-rc-1.zip SHA1: ec611704fd298774af956beeda1a3b302b0d4744 http://forge.ow2.org/project/download.php?group_id=170&file_id=16751 - ---- XWiki Manager Extension for XWiki Enterprise Installations ---- xwiki-manager-application-xem-3.1-rc-1.xar SHA1: 71659f787ab9c1e7700aee4a2f9b0316194fab9a http://forge.ow2.org/project/download.php?group_id=170&file_id=16752 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iQIcBAEBAgAGBQJN7dwsAAoJECYAmptlsgnWJBIQAIyTSN6wqWfmS+3H4YIZLXOJ CefTZqHFJI38inSzXgbBG3wwtS/EA3ycRoyzuqVSlsuRJ+06KmlUz75WAk0hVsrU 84Ihpq2GXioL2jvwLKNNNvX97Jk93JzNaI5Ys0gh9hZy0/9XKT1jrrvTjxCxkoES eUFAHUF9uFuOGKcazTEYF/itbc0jSMZvbVqz0NQZY7w6EpZKEeds2Xv0fVzYIq6+ GP+AocHYJ7WADajMzYfcvEUdy0SPgAMpgx+vx0k3XczPTa+eT6MgANOYKbV5COaB v5VBLvjiJaLmwDMw/c8rjLPjJzY+EAVC1Wy/DEWMswwOnw1ubjX3vUK9x99mQwgF z0tnW7fgJS+mcY5LFQlWg2FH2+bg04CwoksuOI1JNMksbCC+jQ4rBDDzwPgLUBEL HaAgjLFsF8Eg/Y8V1PdJKFKi5tmfsodqHnJ7Xv9Qrem9D97JrFgbOLr6ULz7NDus 1KDLNoBvcJC74q1Wo+F6XVf2hY1HQjXw4IqIJlYYi1ZAhNS75LasvvWl7nC+XeAo 4BIHx2vskRuMbYtY4wfElPEl9yXCtwOR7DBpzV9JjzmiKHKVuW0+ZuJGnTn/a+G1 BkWB9ttwjFQ/V9MK61GXdSbGRhobccBRwHw+trIrkBK5dOD4bBoF5or/rX/RA9xb c4l27NeRfuPKHRjKZAG9 =QIBM -----END PGP SIGNATURE-----

1 0

[xwiki-devs] Status of XWiki Android Client
by Chamika Weerasinghe 06 Jun '11

06 Jun '11

Hi, I'm currently working on building an Android library which gives RESTful features within android device. As the first step I managed to import jaxb libraries and now I'm trying to execute them within android so that xwiki-android client will not need complete new REST library. For importing jaxb I used following dependencies in maven configuration xwiki-core-rest xwiki-core-annotations-rest wiki-core-rest-model I planed to push to the repo as soon as I build something useful in purpose of code review. Thank you, Best Regards, Chamika Weerasinghe

3 3

[xwiki-devs] [VOTE] Important: Strategy to fix failing tests and stability
by Vincent Massol 06 Jun '11

06 Jun '11

Hi devs, Here's the situation: * We've been having a hard time releasing on time and the main issue is test stability. We lag by at least a week and we even release with failing tests, causing regressions. * It's not the role of the release manager to fix tests before releasing * It's not normal that some people spend time fixing issues caused by others and that others continue to work on the next thing they are working on. Everyone needs to help. Here's what I propose as a drastic and temporary measure till we get better: 1) It's forbidden to commit anything till all tests are passing (unit AND functional tests), unless what is committed is about fixing tests. On the exceptional case when a committer absolutely needs to commit even though tests are failing he needs to ask the permission explicitly. 2) When tests are failing, everyone should stop what they're doing and help stabilize again. We synchronize on IRC. 3) Flickering tests can be marked as @Ignore and a jira issue created to stabilize the build. 4) Release Manager creates a release branch 1 week before the release to let everyone stabilize the build On a long term we need to work on improving our CI so that functional tests are built faster. One idea is: more agents and functional tests spread on several agents. Here's my +1 to apply this now for master (3.2-SNAPSHOT leading to 3.2M1), which means not committing anything more till we have all functional tests passing. Thanks -Vincent

5 8

[xwiki-devs] [Proposal] REST module re-organization
by Jerome Velociter 03 Jun '11

03 Jun '11

Hi, I would like to propose a small re-organization of the rest module. Currently the module is organized as follow : xwiki-platform-rest/ \_xwiki-platform-rest-model/ \_xwiki-platform-rest-server/ Where xwiki-platform-rest-model contains the JAXB bindings and generates model classes ; and where xwiki-platform-rest-server contains "everything else", being the Restlet plumbing to expose a REST application, and the REST resources and representations that makes the XWiki REST API. I'm proposing a first re-organization going towards the following structure : xwiki-platform-rest/ \_xwiki-platform-rest-model/ \_xwiki-platform-rest-resources/ \_xwiki-platform-rest-server/ Where xwiki-platform-rest-model remains the same, and where everything that is not needed to expose a functional REST system is extracted out of xwiki-platform-rest-server and into xwiki-platform-rest-resources. With this, xwiki-platform-rest-resources would become the actual implementation of the XWiki Restful API, while xwiki-platform-rest-server will be the module needed to expose any REST API from XWiki. The rationale behind this is simply to ease implementation of alternate APIs while keeping benefits from the server module which is agnostic to any API exposed. My +1 for this. If we agree I can push it early in the 3.2 cycle (in a couple of days). WDYT ? ---- Note for the future : In the future we could want to split the REST module even more. Right now some parts of the module are tied to Restlet, but resources aren't (basically everything in org.xwiki.rest.resources), and we could extract them out in a generic module while introducing a restlet module for everything Restlet (server plumbing + representations). It could for example look like this : xwiki-platform-rest/ \_xwiki-platform-rest-model/ \_xwiki-platform-rest-restlet/ \_xwiki-platform-rest-restlet-server/ \_xwiki-platform-rest-restlet-representations/ \_xwiki-platform-rest-resources/ This would ease alternative implementations based on other JAX-RS implementations (CFX, Jersey, etc.) Jerome

1 0

[xwiki-devs] Failing tests in XEM
by Caleb James DeLisle 03 Jun '11

03 Jun '11

Does anyone know why the CreateEmptyWiki selenium test is failing in XEM tests? http://ci.xwiki.org/job/xwiki-manager-tests/1164/org.xwiki.manager$xwiki-ma… It seems that it has been failing for quite some time although the failure looks serious enough to warrant attention. If this is a "normal" failure then I propose we @Ignore it and if nobody wants to get it functioning correctly then remove it entirely since it is not proving anything now and if there isn't a regression here then it is just creating unnecessary noise. Caleb

2 2