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

[xwiki-devs] Running wysiwyg GWT editor as standalone
by David Pinn 11 May '10

11 May '10

Marius wrote: * Inherit the WYSIWYG GWT module in your own GWT module descriptor ** Use the same entry point as the WYSIWYG GWT module, which publishes a JavaScript API you can use to instantiate the editor, or ** Use your own entry point and instantiate the editor in GWT code How would I instantiate the editor in GWT code? I've been trying to achieve this, but I get an editor that will not accept typing. That is, typing characters into the editor has no effect; the characters don't display, and there is no change to the state of the editor in the DOM. I figure it must be something to do with the way I'm creating it.

3 5

[xwiki-devs] Invitation application is running on incubator.myxwiki.org, come check it out.
by Caleb James DeLisle 10 May '10

10 May '10

Hello all, The partially completed invitation application is up and running on the incubator. http://incubator.myxwiki.org/xwiki/bin/view/InvitationMail/ Right now the actual sending of the email is disabled until we can decide who's allowed to send. Anyone who's a member of myxwiki.org ( http://www.myxwiki.org/bin/register/XWiki/Register ) can test out the functionality, acting as a user or as an administrator. Even though the email isn't sent, you can still try accepting, rejecting, or reporting your messages as spam. If you report your message as spam (and click confirm) you will not be able to send any more mail unless you use the "view as an administrator" page. The main page (above) has open commenting so you can voice your opinion there or in response to this message and help expand and clarify the "todo" list. I'm anxious to hear good ideas and criticism. Caleb

2 1

[xwiki-devs] [Contrib] Project Wiki3.0
by Fabio Mancinelli 10 May '10

10 May '10

Dear community, XWiki SAS is participating and leading a research project called Wiki3.0 together with the SCORE Team of the "Institut National de Recherche en Informatique et Automatique (INRIA)" (http://score.loria.fr/) and the well known Linux distribution editor Mandriva (http://www.mandriva.com) The Wiki3.0 project aims at developing a next generation collaboration platform that integrates real-time editing and interactions, social-networking features, and that will take advantage of cloud infrastructures. The final outcome of the Wiki 3.0 project is to deliver a solution that will greatly ehnance the productivity in terms of knowledge exchange and creation. This solution will consist of an enhanced version of the XWiki platform that will include real-time collaboration and social-network-oriented features. I am writing this mail for requesting the Wiki3.0 project to be hosted as a contributed project of the XWiki.org platform. The project will use the xwiki.org SVN repository, XWiki developer's mailing list and the JIRA platform to track and document its evolution. Many of the participants of this project are already committers for the XWiki platform. In addition we will need to give committer rights to the SCORE Team members and, in particular, to Bogdan Flueras which will be the main developer at the SCORE Team. I, Fabio Mancinelli, will be the coordinator of the whole project. The current website of the project is https://wiki30.xwikisas.com/ Thank you, - Fabio

4 3

[xwiki-devs] [ANN] XWiki Office 1.1.1 released
by Florin Ciubotaru 10 May '10

10 May '10

The XWiki development team is pleased to announce the release of XWiki Office 1.1.1. This is a bug fix release of version 1.1. All active XOffice instances will be automatically updated. Bugs fixed in version 1.1.1 - Styles not preserved after multiple edits - Image upload and download on localized versions of Microsoft Office - Image upload on pages containing white characters - Grammar markup filtering when on non-English language default settings - Refreshing published documents Detailed release notes are available at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXOffice111 For more information about XOffice please visit: http://xoffice.xwiki.org Thanks, - The XWiki dev team

2 1

Re: [xwiki-devs] [VOTE] "member" field of XWikiGroups objects is supposed to contains only one member (summary)
by Thomas Mortagne 10 May '10

10 May '10

On Mon, May 10, 2010 at 09:34, Ludovic Dubost <ludovic(a)xwiki.org> wrote: > I was also +1 on this.. > > However it would be nice to provide a script to detect any data that might > have been using the feature, and put it in the release notes > Things is that this feature was pretty much not usable anyway since not all the places manipulating groups was using it, in fact it was only applied by XWikiGroupServiceImpl#listMemberForGroup. > > Ludovic > > Le 09/05/10 12:44, Thomas Mortagne a écrit : > > 3 +1 >> >> Committed in trunk >> >> On Fri, May 7, 2010 at 18:36, Thomas Mortagne<thomas.mortagne(a)xwiki.com >> >wrote: >> >> >> >>> Hi devs, >>> >>> I recently created http://jira.xwiki.org/jira/browse/XWIKI-5149, this >>> issue is due to the fact that XWikiGroupServiceImpl#listMemberForGroup >>> is splitting the value of the "member" field based on white space and >>> comma. >>> >>> That does not make sense IMO and makes impossible to have a user with >>> a white space (and comma which is less common) in its name for a very >>> bad reason. Also the name of the field is "member" and not "members". >>> Last reason is that i think in all other places we don't take this >>> value as a list. >>> >>> Note that this bug is mainly a pain for authenticators where you have >>> to remember the real name of the user and have some collision handling >>> to support use case users "somename" and "some name" coming for an >>> external authentication server in which theses are two different >>> users. >>> >>> WDYT ? >>> >>> Here is my +1. >>> >>> -- >>> Thomas Mortagne >>> >>> >>> >> >> >> >> > > > -- > Ludovic Dubost > Blog: http://blog.ludovic.org/ > XWiki: http://www.xwiki.com > Skype: ldubost GTalk: ldubost > > -- Thomas Mortagne

1 0

Re: [xwiki-devs] [VOTE] "member" field of XWikiGroups objects is supposed to contains only one member (summary)
by Thomas Mortagne 10 May '10

10 May '10

3 +1 Committed in trunk On Fri, May 7, 2010 at 18:36, Thomas Mortagne <thomas.mortagne(a)xwiki.com>wrote: > Hi devs, > > I recently created http://jira.xwiki.org/jira/browse/XWIKI-5149, this > issue is due to the fact that XWikiGroupServiceImpl#listMemberForGroup > is splitting the value of the "member" field based on white space and > comma. > > That does not make sense IMO and makes impossible to have a user with > a white space (and comma which is less common) in its name for a very > bad reason. Also the name of the field is "member" and not "members". > Last reason is that i think in all other places we don't take this > value as a list. > > Note that this bug is mainly a pain for authenticators where you have > to remember the real name of the user and have some collision handling > to support use case users "somename" and "some name" coming for an > external authentication server in which theses are two different > users. > > WDYT ? > > Here is my +1. > > -- > Thomas Mortagne > -- Thomas Mortagne

2 1

[xwiki-devs] [VOTE] "member" field of XWikiGroups objects is supposed to contains only one member
by Thomas Mortagne 09 May '10

09 May '10

Hi devs, I recently created http://jira.xwiki.org/jira/browse/XWIKI-5149, this issue is due to the fact that XWikiGroupServiceImpl#listMemberForGroup is splitting the value of the "member" field based on white space and comma. That does not make sense IMO and makes impossible to have a user with a white space (and comma which is less common) in its name for a very bad reason. Also the name of the field is "member" and not "members". Last reason is that i think in all other places we don't take this value as a list. Note that this bug is mainly a pain for authenticators where you have to remember the real name of the user and have some collision handling to support use case users "somename" and "some name" coming for an external authentication server in which theses are two different users. WDYT ? Here is my +1. -- Thomas Mortagne

4 3

Re: [xwiki-devs] [xwiki-notifications] r28794 - platform/xwiki-applications/trunk/administration/src/main/resources/XWiki
by Sergiu Dumitriu 08 May '10

08 May '10

On 05/07/2010 10:42 PM, cjdelisle (SVN) wrote: > Author: cjdelisle > Date: 2010-05-07 22:42:06 +0200 (Fri, 07 May 2010) > New Revision: 28794 > > Modified: > platform/xwiki-applications/trunk/administration/src/main/resources/XWiki/ConfigurableClass.xml > Log: > XAADMINISTRATION-138: ConfigurableClass producing invalid xhtml > Fixed regression introduced in r28787 preventing saving. > > Modified: platform/xwiki-applications/trunk/administration/src/main/resources/XWiki/ConfigurableClass.xml > =================================================================== > --- platform/xwiki-applications/trunk/administration/src/main/resources/XWiki/ConfigurableClass.xml 2010-05-07 20:21:45 UTC (rev 28793) > +++ platform/xwiki-applications/trunk/administration/src/main/resources/XWiki/ConfigurableClass.xml 2010-05-07 20:42:06 UTC (rev 28794) > @@ -567,8 +567,8 @@ > #end > </label> > ## Have to prepend the app name to prevent id collisions. Are you sure it's always going to be _0_ ? > - $obj.display($propName, "edit").replaceAll("$objClass.getName()_0_$propName", > - "${escapedAppName}_$objClass.getName()_0_$propName") > + $obj.display($propName, "edit").replaceAll(" id='$objClass.getName()_0_$propName", > + " id='${escapedAppName}_$objClass.getName()_0_$propName") > </p> > #end## If property is in propertiesToShow > #end## Foreach property in this class > -- Sergiu Dumitriu http://purl.org/net/sergiu/

3 2

Re: [xwiki-devs] [xwiki-notifications] r28793 - platform/xwiki-applications/trunk/administration/src/main/resources/XWiki
by Sergiu Dumitriu 07 May '10

07 May '10

On 05/07/2010 10:21 PM, cjdelisle (SVN) wrote: > Author: cjdelisle > Date: 2010-05-07 22:21:45 +0200 (Fri, 07 May 2010) > New Revision: 28793 > > Modified: > platform/xwiki-applications/trunk/administration/src/main/resources/XWiki/ConfigurableClass.xml > Log: > XAADMINISTRATION-129: Fix save button for 'Registration> Customize XWiki.RegistrationConfig' > Javascript (which fixes buttons) now tested and working in IE7 > > Modified: platform/xwiki-applications/trunk/administration/src/main/resources/XWiki/ConfigurableClass.xml > =================================================================== > --- platform/xwiki-applications/trunk/administration/src/main/resources/XWiki/ConfigurableClass.xml 2010-05-07 18:00:43 UTC (rev 28792) > +++ platform/xwiki-applications/trunk/administration/src/main/resources/XWiki/ConfigurableClass.xml 2010-05-07 20:21:45 UTC (rev 28793) > @@ -222,15 +222,16 @@ > var errorShown = false; > for (var i = elementsInPage.length - 1; i> -1; i--) { > var e = elementsInPage[i]; > - if (e.tagName == 'DIV'&& e.getAttribute('class').indexOf('errormessage') != -1) > + if (e.tagName != undefined&& e.tagName.toLowerCase() == 'div'&& e.getAttribute('class') != undefined&& e.getAttribute('class').indexOf('errormessage') != -1) $(e).hasClassName('errormessage') is a better alternative, since indexOf can also match <div class="notanerrormessage"> > { > errorShown = true; > } else if (!errorShown > -&& e.tagName == 'H1' > -&& e.getAttribute('class') == 'wikigeneratedheader' > -&& e.getAttribute('id').indexOf('HCustomize') == 0) > +&& e.tagName != undefined > +&& e.tagName.toLowerCase() == 'h1' > +&& e.getAttribute('id') != undefined > +&& e.getAttribute('id').toLowerCase().indexOf('hcustomize') == 0) > { > - e.setAttribute('class', 'hidden'); > + e.parentNode.removeChild(e); $(e).remove() or $(e).hide(); You should have a look at what Prototype can offer, see http://www.prototypejs.org/api/element > errorShown = false; > } > } > @@ -239,8 +240,8 @@ > var forms = document.getElementsByTagName('form'); > var inputs = document.getElementsByTagName('input'); > for (var i = 0; i< inputs.length; i++) { > - if (inputs[i].getAttribute('type') == 'submit') { > - inputs[i].setAttribute('class', 'hidden'); > + if (inputs[i].getAttribute('type') != undefined&& inputs[i].getAttribute('type').toLowerCase() == 'submit') { > + inputs[i].parentNode.removeChild(inputs[i]); $(inputs[i]).remove(); > } > } > > @@ -302,6 +303,9 @@ > <number>0</number> > <className>XWiki.TagClass</className> > <guid>ddb1f0f6-1943-4e80-824a-0718cdbf1892</guid> > +<property> > +<tags/> > +</property> This looks like a leftover tag object which should be removed. > </object> > <content>{{velocity}} > #* -- Sergiu Dumitriu http://purl.org/net/sergiu/

1 0

[xwiki-devs] Should email invitation app be a top level application? How should I add it to the sandbox?
by Caleb James DeLisle 07 May '10

07 May '10

I have a working prototype of the invitation mail sender and I would like to put it in the sandbox. I need to know how that should be done and should this be a separate top level project on jira? Some guidance here would be great. Caleb

7 18