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

[xwiki-devs] Adding pages and panels externally

by Alexandre Souza

Thanks, Guillaume But I think that PUT method doesn't work for Panels, only for Pages. I trying another way, using a velocity script in a panel already created, but I have a doubt. Do you known how I can get all existing pages in specific Space to show in panel, as following? #panelheader('Test') #set($page = $xwiki.search("***all pages in Space.Main, for example***")) #foreach($docname in $page) #set($rdoc = $xwiki.getDocument($docname).getTranslatedDocument()) <span class="panelitem"><a href="$rdoc.getURL('view')">$xwiki.getXMLEncoded($rdoc.displayTitle)</a></span> #end #panelfooter() Alexandre 2009/9/3 <devs-request(a)xwiki.org> > Send devs mailing list submissions to > devs(a)xwiki.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.xwiki.org/mailman/listinfo/devs > or, via email, send a message with subject or body 'help' to > devs-request(a)xwiki.org > > You can reach the person managing the list at > devs-owner(a)xwiki.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of devs digest..." > > > Today's Topics: > > 1. Re: [xwiki-users] [Vote] Default Color Theme (Eduard Moraru) > 2. Re: [xwiki-users] [Vote] Default Color Theme (Ecaterina Valica) > 3. Translations for XWiki Enterprise 2.0 (Guillaume Lerouge) > 4. Adding pages and panels externally (Alexandre Souza) > 5. Re: Adding pages and panels externally (Guillaume Lerouge) > 6. Re: [VOTE] Add the IRC Bot application to SVN > (Marius Dumitru Florea) > 7. Re: [Proposal] New Release Dates for the 2.0 Release > (Vincent Massol) > 8. Re: [Proposal] New Release Dates for the 2.0 Release > (Jean-Vincent Drean) > 9. Re: [Proposal] New Release Dates for the 2.0 Release > (Asiri Rathnayake) > 10. Re: [Proposal] New Release Dates for the 2.0 Release > (Guillaume Lerouge) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 02 Sep 2009 17:18:15 +0300 > From: Eduard Moraru <eduard.moraru(a)xwiki.com> > Subject: Re: [xwiki-devs] [xwiki-users] [Vote] Default Color Theme > To: XWiki Developers <devs(a)xwiki.org> > Message-ID: <4A9E7EA7.9070102(a)xwiki.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > +1 for (2) > > On 09/02/2009 05:37 PM, Ecaterina Valica wrote: > > Hi, > > > > So the final decision is between (2), (4), (B).* > > > > (2)* > > > http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/Proposal2/Propo… > > > > *(4)* > > > http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/Proposal4/Propo… > > > > *(B) * > > > http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/BColorTheme/Sch… > > * * > > > > > > I preserved the existing votes: > > > > (4) +1 Caty, +1 Vincent, +1 Ricardo R, +1 Florin, +1 Silvia, +0.5 Trevor, > +1 > > Marius > > (B) +1 Oana, +1 Thomas M, +1 Sergiu, +0.5 Vincent G, +1 Philipp, +1 > Martijn, > > +0.5 Trevor > > (2) +1 Lucien, +0.66 Marta, +0.5 Jean C, +1 Ga?tan, +0.66 Raluca, +0.5 > > Vincent G, +1 Emilie, > > > > > > For the ones that changed their mind and want to change their vote just > > reply again and reset your vote. > > > > Thanks, > > Caty > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > ------------------------------ > > Message: 2 > Date: Wed, 2 Sep 2009 19:12:10 +0200 > From: Ecaterina Valica <valicac(a)gmail.com> > Subject: Re: [xwiki-devs] [xwiki-users] [Vote] Default Color Theme > To: XWiki Users <users(a)xwiki.org>, XWiki Mailinglist <devs(a)xwiki.org> > Message-ID: > <a7bce70e0909021012w5eeac28br62dd50de508958d2(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > (4) > > http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/Proposal4/Propo… > > (B) > > http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/BColorTheme/Sch… > > (2) > http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/Proposal2/Propo… > > Votes: > > (4) +1 Caty, +1 Vincent, +1 Ricardo R, +1 Florin, +1 Silvia, +0.5 Trevor, > +1 > Marius, +1 Christophe P > (B) +1 Oana, +1 Thomas M, +1 Sergiu, +0.5 Vincent G, +1 Philipp, +1 > Martijn, > +0.5 Trevor > (2) +1 Lucien, +0.66 Marta, +0.5 Jean C, +1 Ga?tan, +0.66 Raluca, +0.5 > Vincent G, +1 Emilie, +1 Guillaume, +1 Eduard > > > ------------------------------ > > Message: 3 > Date: Wed, 2 Sep 2009 19:16:46 +0200 > From: Guillaume Lerouge <guillaume(a)xwiki.com> > Subject: [xwiki-devs] Translations for XWiki Enterprise 2.0 > To: XWiki Developers <devs(a)xwiki.org>, XWiki Users <users(a)xwiki.org> > Message-ID: > <1c35d2320909021016n5f8fd583weff86414703bb7b3(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hi XWikiers, > I know some of you regularly update translations for languages on > http://l10n.xwiki.org/ . I've just refreshed the list of translations, > which > created a slew of new empty strings :-) > > It would be great if we could fill as much of them as possible before > releasing XWiki Enterprise 2.0. I'll handle the French ones. > > You can find empty translations for your language on > http://l10n.xwiki.org/xwiki/bin/view/XE/XWikiCoreResources > > Thanks in advance for your help, > > Guillaume > > -- > Guillaume Lerouge > Product Manager - XWiki > Skype: wikibc > Twitter: glerouge > http://guillaumelerouge.com/ > > > ------------------------------ > > Message: 4 > Date: Wed, 2 Sep 2009 15:29:45 -0300 > From: Alexandre Souza <siqsou(a)gmail.com> > Subject: [xwiki-devs] Adding pages and panels externally > To: devs(a)xwiki.org > Message-ID: > <230a3f4f0909021129o6971cc48p5befd2883c81bc34(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi, > > I am development a bash script for adding a lot pages and panels > automatically in my xwiki. > I got to add pages with 'curl' command, as following: > > *curl -u Admin:admin -X PUT -d @newpage.html -H "Content-Type: text/plain" > http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/Main/pages/NewPage > * > This works, but I'm having difficulty to add links in a side panel for the > pages created. > Is it possible make this with 'curl' too? If not, is there another way? > > > Thanks, > Alexandre Souza > > > ------------------------------ > > Message: 5 > Date: Wed, 2 Sep 2009 22:22:39 +0200 > From: Guillaume Lerouge <guillaume(a)xwiki.com> > Subject: Re: [xwiki-devs] Adding pages and panels externally > To: XWiki Developers <devs(a)xwiki.org> > Message-ID: > <1c35d2320909021322x1945069ch7aa1791378dd9477(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hi Alexandre, > > On Wed, Sep 2, 2009 at 8:29 PM, Alexandre Souza <siqsou(a)gmail.com> wrote: > > > Hi, > > > > I am development a bash script for adding a lot pages and panels > > automatically in my xwiki. > > I got to add pages with 'curl' command, as following: > > > > *curl -u Admin:admin -X PUT -d @newpage.html -H "Content-Type: > text/plain" > > http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/Main/pages/NewPage > > * > > This works, but I'm having difficulty to add links in a side panel for > the > > pages created. > > Is it possible make this with 'curl' too? If not, is there another way? > > > > > You simply need to access the panel XObject within the document holding > your > panel and edit its content property to add the links to your pages. I think > there's an API for this since it's supported by XEclipse. You'll have to > dig > a bit more into it to see how it works though. > > Guillaume > > > > > Thanks, > > Alexandre Souza > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > > -- > Guillaume Lerouge > Product Manager - XWiki > Skype: wikibc > Twitter: glerouge > http://guillaumelerouge.com/ > > > ------------------------------ > > Message: 6 > Date: Thu, 03 Sep 2009 07:40:35 +0300 > From: Marius Dumitru Florea <mariusdumitru.florea(a)xwiki.com> > Subject: Re: [xwiki-devs] [VOTE] Add the IRC Bot application to SVN > To: XWiki Developers <devs(a)xwiki.org> > Message-ID: <4A9F48C3.9080300(a)xwiki.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > +0 > > Thanks, > Marius > > Vincent Massol wrote: > > Hi, > > > > I've rewritten the IRC Bot application to make it more generic and > > using XWiki 2.0 syntax and the new Observation mechanism. I'm looking > > for a place where to save the sources. > > > > I'd like to propose to put it in platform/applications/ircbot > > > > Rationale: > > * Since we use it it'll be actively maintained > > * It could be useful for others too > > > > It would have its own JIRA project and its own release cycles of course. > > > > Here's my +1 > > > > Thanks > > -Vincent > > > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > > ------------------------------ > > Message: 7 > Date: Thu, 3 Sep 2009 11:25:13 +0200 > From: Vincent Massol <vincent(a)massol.net> > Subject: Re: [xwiki-devs] [Proposal] New Release Dates for the 2.0 > Release > To: XWiki Developers <devs(a)xwiki.org> > Message-ID: > <c0c158f80909030225x33e7f335y431d6b8b4067aa2a(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Guys, > > Seen that we're now the 3rd of Sep and we're not ready to release the > new colibri skin (lots of remaining issues), I'd like to propose to > postpone the release by 1 week with the new timetable: > > * XE 2.0RC1: 10th of Sep > * XE 2.0 final (if no RC2): 15th of Sep > * XE 2.0RC2 (if blockers found in RC1): 17th of Sep > * XE 2.0 final (if RC2): 22nd of Sep > > Here's my +1 > > Thanks > -Vincent > > On Thu, Aug 27, 2009 at 11:02 AM, Vincent Massol<vincent(a)massol.net> > wrote: > > Hi, > > > > Since we've just released 2.0M4 we need to reschedule the date for the > 2.0 > > release. > > > > I'm proposing: > > > > * 2.0RC1: 2nd of Sep > > * If no blocking bug found in RC1: > > ** 2.0 final: 4th of Sept (it's just a re-release of RC1 in this case) > > * If blocking bugs found in RC1: > > ** 2.0RC2: 9th of Sep > > ** 2.0 final: 11th of Sep (it's just a re-release of RC2 in this case) > > > > WDYT? > > > > Thanks > > -Vincent > > > > > > > ------------------------------ > > Message: 8 > Date: Thu, 3 Sep 2009 11:28:55 +0200 > From: Jean-Vincent Drean <jean-vincent(a)drean.org> > Subject: Re: [xwiki-devs] [Proposal] New Release Dates for the 2.0 > Release > To: XWiki Developers <devs(a)xwiki.org> > Message-ID: > <c58832290909030228s69fc0cc0o2893e9027083e6eb(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > +1, > > JV. > > > On Thu, Sep 3, 2009 at 11:25 AM, Vincent Massol <vincent(a)massol.net> > wrote: > > > > Guys, > > > > Seen that we're now the 3rd of Sep and we're not ready to release the > > new colibri skin (lots of remaining issues), I'd like to propose to > > postpone the release by 1 week with the new timetable: > > > > * XE 2.0RC1: 10th of Sep > > * XE 2.0 final (if no RC2): 15th of Sep > > * XE 2.0RC2 (if blockers found in RC1): 17th of Sep > > * XE 2.0 final (if RC2): 22nd of Sep > > > > Here's my +1 > > > > Thanks > > -Vincent > > > > On Thu, Aug 27, 2009 at 11:02 AM, Vincent Massol<vincent(a)massol.net> > wrote: > > > Hi, > > > > > > Since we've just released 2.0M4 we need to reschedule the date for the > 2.0 > > > release. > > > > > > I'm proposing: > > > > > > * 2.0RC1: 2nd of Sep > > > * If no blocking bug found in RC1: > > > ** 2.0 final: 4th of Sept (it's just a re-release of RC1 in this case) > > > * If blocking bugs found in RC1: > > > ** 2.0RC2: 9th of Sep > > > ** 2.0 final: 11th of Sep (it's just a re-release of RC2 in this case) > > > > > > WDYT? > > > > > > Thanks > > > -Vincent > > > > > > > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > > ------------------------------ > > Message: 9 > Date: Thu, 3 Sep 2009 15:05:41 +0530 > From: Asiri Rathnayake <asiri.rathnayake(a)gmail.com> > Subject: Re: [xwiki-devs] [Proposal] New Release Dates for the 2.0 > Release > To: XWiki Developers <devs(a)xwiki.org> > Message-ID: > <9fd36c290909030235p219b3e98h951b6d1ec9502ad4(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > +1 > > On Thu, Sep 3, 2009 at 2:55 PM, Vincent Massol <vincent(a)massol.net> wrote: > > > Guys, > > > > Seen that we're now the 3rd of Sep and we're not ready to release the > > new colibri skin (lots of remaining issues), I'd like to propose to > > postpone the release by 1 week with the new timetable: > > > > * XE 2.0RC1: 10th of Sep > > * XE 2.0 final (if no RC2): 15th of Sep > > * XE 2.0RC2 (if blockers found in RC1): 17th of Sep > > * XE 2.0 final (if RC2): 22nd of Sep > > > > Here's my +1 > > > > Thanks > > -Vincent > > > > On Thu, Aug 27, 2009 at 11:02 AM, Vincent Massol<vincent(a)massol.net> > > wrote: > > > Hi, > > > > > > Since we've just released 2.0M4 we need to reschedule the date for the > > 2.0 > > > release. > > > > > > I'm proposing: > > > > > > * 2.0RC1: 2nd of Sep > > > * If no blocking bug found in RC1: > > > ** 2.0 final: 4th of Sept (it's just a re-release of RC1 in this case) > > > * If blocking bugs found in RC1: > > > ** 2.0RC2: 9th of Sep > > > ** 2.0 final: 11th of Sep (it's just a re-release of RC2 in this case) > > > > > > WDYT? > > > > > > Thanks > > > -Vincent > > > > > > > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > ------------------------------ > > Message: 10 > Date: Thu, 3 Sep 2009 11:38:05 +0200 > From: Guillaume Lerouge <guillaume(a)xwiki.com> > Subject: Re: [xwiki-devs] [Proposal] New Release Dates for the 2.0 > Release > To: XWiki Developers <devs(a)xwiki.org> > Message-ID: > <1c35d2320909030238x7e54fe9dga05a71e042206e84(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > +1 > Guillaume > > On Thu, Sep 3, 2009 at 11:35 AM, Asiri Rathnayake < > asiri.rathnayake(a)gmail.com> wrote: > > > +1 > > > > On Thu, Sep 3, 2009 at 2:55 PM, Vincent Massol <vincent(a)massol.net> > wrote: > > > > > Guys, > > > > > > Seen that we're now the 3rd of Sep and we're not ready to release the > > > new colibri skin (lots of remaining issues), I'd like to propose to > > > postpone the release by 1 week with the new timetable: > > > > > > * XE 2.0RC1: 10th of Sep > > > * XE 2.0 final (if no RC2): 15th of Sep > > > * XE 2.0RC2 (if blockers found in RC1): 17th of Sep > > > * XE 2.0 final (if RC2): 22nd of Sep > > > > > > Here's my +1 > > > > > > Thanks > > > -Vincent > > > > > > On Thu, Aug 27, 2009 at 11:02 AM, Vincent Massol<vincent(a)massol.net> > > > wrote: > > > > Hi, > > > > > > > > Since we've just released 2.0M4 we need to reschedule the date for > the > > > 2.0 > > > > release. > > > > > > > > I'm proposing: > > > > > > > > * 2.0RC1: 2nd of Sep > > > > * If no blocking bug found in RC1: > > > > ** 2.0 final: 4th of Sept (it's just a re-release of RC1 in this > case) > > > > * If blocking bugs found in RC1: > > > > ** 2.0RC2: 9th of Sep > > > > ** 2.0 final: 11th of Sep (it's just a re-release of RC2 in this > case) > > > > > > > > WDYT? > > > > > > > > Thanks > > > > -Vincent > > > > > > > > > > > _______________________________________________ > > > devs mailing list > > > devs(a)xwiki.org > > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > > -- > Guillaume Lerouge > Product Manager - XWiki > Skype: wikibc > Twitter: glerouge > http://guillaumelerouge.com/ > > > ------------------------------ > > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > > > End of devs Digest, Vol 27, Issue 13 > ************************************ >

16 years

2
1
0 0

[xwiki-devs] [Proposal] New Release Dates for the 2.0 Release

by Vincent Massol

Hi, Since we've just released 2.0M4 we need to reschedule the date for the 2.0 release. I'm proposing: * 2.0RC1: 2nd of Sep * If no blocking bug found in RC1: ** 2.0 final: 4th of Sept (it's just a re-release of RC1 in this case) * If blocking bugs found in RC1: ** 2.0RC2: 9th of Sep ** 2.0 final: 11th of Sep (it's just a re-release of RC2 in this case) WDYT? Thanks -Vincent

16 years

8
12
0 0

[xwiki-devs] [VOTE] Add the IRC Bot application to SVN

by Vincent Massol

Hi, I've rewritten the IRC Bot application to make it more generic and using XWiki 2.0 syntax and the new Observation mechanism. I'm looking for a place where to save the sources. I'd like to propose to put it in platform/applications/ircbot Rationale: * Since we use it it'll be actively maintained * It could be useful for others too It would have its own JIRA project and its own release cycles of course. Here's my +1 Thanks -Vincent

16 years

6
7
0 0

[xwiki-devs] Preparing 2.1 roadmap for architecture features

by Vincent Massol

Hi, In order to prepare what we could in the 2.1 roadmap on the domain of architecture features (ie not user-oriented features), here's a list of stuff I have in mind for working on myself (and/or with some of you): * Services Bridge (between scripts and components) * Velocity JSR223 implementation * Finish xwiki-url * Finish xwiki-action * Finish xwiki-localization * Generic Rendering Markers for Transformations * Move XHTML parser from wikimodel to our code base * Rendering: make script/include/useravatar macros usable standalone too * Component Manager: introduce Realms * Move to JSR299 annotations + move to Guice. (I think this one is too early though - JSR330 public review is for 15th of Sep) * I10n of Renderng module / WYSIWYG module * Implement xwiki-search (rewrite using new archi) (We might want to fix existing lucene plugin first before tackling this one) * App Manager (too big to start now - I think beg of next year) Any other stuff that we'd need to work on from an architecture pov? Thanks -Vincent

16 years

3
4
0 0

[xwiki-devs] Adding pages and panels externally

by Alexandre Souza

Hi, I am development a bash script for adding a lot pages and panels automatically in my xwiki. I got to add pages with 'curl' command, as following: *curl -u Admin:admin -X PUT -d @newpage.html -H "Content-Type: text/plain" http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/Main/pages/NewPage * This works, but I'm having difficulty to add links in a side panel for the pages created. Is it possible make this with 'curl' too? If not, is there another way? Thanks, Alexandre Souza

16 years

2
1
0 0

[xwiki-devs] Translations for XWiki Enterprise 2.0

by Guillaume Lerouge

Hi XWikiers, I know some of you regularly update translations for languages on http://l10n.xwiki.org/ . I've just refreshed the list of translations, which created a slew of new empty strings :-) It would be great if we could fill as much of them as possible before releasing XWiki Enterprise 2.0. I'll handle the French ones. You can find empty translations for your language on http://l10n.xwiki.org/xwiki/bin/view/XE/XWikiCoreResources Thanks in advance for your help, Guillaume -- Guillaume Lerouge Product Manager - XWiki Skype: wikibc Twitter: glerouge http://guillaumelerouge.com/

16 years

1
0
0 0

Re: [xwiki-devs] [xwiki-users] [Vote] Default Color Theme

by PERINAUD Christophe

+1 for (4) > -----Message d'origine----- > De : devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] > De la part de Ecaterina Valica > Envoyé : mercredi 2 septembre 2009 16:38 > À : XWiki Users; XWiki Mailinglist > Objet : Re: [xwiki-devs] [xwiki-users] [Vote] Default Color Theme > > Hi, > > So the final decision is between (2), (4), (B).* > > (2)* > http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/Pr > oposal2/Proposal2.png > > *(4)* > http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/Pr > oposal4/Proposal4.png > > *(B) * > http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/BC > olorTheme/SchemeB.png > * * > > > I preserved the existing votes: > > (4) +1 Caty, +1 Vincent, +1 Ricardo R, +1 Florin, +1 Silvia, > +0.5 Trevor, +1 > Marius > (B) +1 Oana, +1 Thomas M, +1 Sergiu, +0.5 Vincent G, +1 > Philipp, +1 Martijn, > +0.5 Trevor > (2) +1 Lucien, +0.66 Marta, +0.5 Jean C, +1 Gaëtan, +0.66 Raluca, +0.5 > Vincent G, +1 Emilie, > > > For the ones that changed their mind and want to change their > vote just > reply again and reset your vote. > > Thanks, > Caty > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > -------------------------------------------------------------------------------- This e-mail is intended only for the addressee named above. It does not bind the sender, except in the case of an existing written convention with the addressee. This e-mail may contain material that is confidential and privileged for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender and delete all copies. While reasonable precautions have been taken to ensure that this e-mail and any attachments are free from any computer virus or similar defect, no liability will be accepted in that respect. Anyone accessing this e-mail must take their own precautions as to security and virus protection. KBL European Private Bankers S.A., 43 boulevard Royal L-2955 Luxembourg, R.C.S. Luxembourg B 6395, T (352) 47 97 1

16 years

2
1
0 0

[xwiki-devs] [VOTE] Rename xwiki-bridge in xwiki-model

by Vincent Massol

Hi, Since we have some final classes (final in the sense with a good architecture) in xwiki-bridge I'd like to rename it into xwiki-model so that we can start this model module. Note: We'd still have a org.xwiki.model.bridge package for the time being in that xwiki-model module. Here's my +1 Thanks -Vincent

16 years

2
1
0 0

[xwiki-devs] [VOTE] Add the IRC Bot application to SVN

by Guillaume Lerouge

Hi, On Wed, Sep 2, 2009 at 11:02 AM, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote: > [Ricardo Rodriguez] Your EPEC Network ICT Team wrote: > > Hi, Vincent, > > > > Vincent Massol wrote: > >> Hi, > >> > >> I've rewritten the IRC Bot application to make it more generic and > >> using XWiki 2.0 syntax and the new Observation mechanism. I'm looking > >> for a place where to save the sources. > >> > >> I'd like to propose to put it in platform/applications/ircbot > >> > >> Rationale: > >> * Since we use it it'll be actively maintained > >> * It could be useful for others too > >> > >> It would have its own JIRA project and its own release cycles of course. > >> > >> Here's my +1 > >> > I might be misunderstanding something about our process, but aren't new projects supposed to spend some time in the sandbox before they get their own SVN branch? Other than that I'm +1 with having it in our repo, Guillaume > >> Thanks > >> -Vincent > >> > >> > > Thanks for this initiative. We are considering the use of IRC or Jabber > > chat rooms for virtual meetings and this application will help us to > > avoid losing discussions and having the chat room "warned" about what is > > going on in the wiki. > > > > As far as I've understood, you, XWiki devs, are considering to move to > > Jabber. Please, will this or a similar application work with Jabber? > > Yes, we will make it also work with Jabber at some time. > > -- > Sergiu Dumitriu > http://purl.org/net/sergiu/ > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > -- Guillaume Lerouge Product Manager - XWiki Skype: wikibc Twitter: glerouge http://guillaumelerouge.com/

16 years

2
1
0 0

[xwiki-devs] [Vote] Make the colibri skin the default one in XE 2.0 RC1

by Guillaume Lerouge

Hi Thibaut, thanks for your feedback, we need more of it even if we sometimes welcome it a bit roughly :-) On Wed, Sep 2, 2009 at 2:17 AM, Thibaut DEVERAUX <thibaut.deveraux(a)gmail.com > wrote: > To be more precise, personas : > > Jo, > Know what is a wiki. > > "Where is the "edit button??? Ho, at the top ! " > > Mike > Don't know what is a wiki > > "What can I do now?" > Mike is looking arond the page, looking fo something logical. > Mike may not notice the edit button since he is looking near the content. > Now iimagine Mike sees the edit button. > (Interesting : If he scroll he will se that the bar is scrolling to so it > may help him to notice it) > "So there is an edit link, I gess I will edit somehing, but what?" > Mike click on the edit button. > It open the editor with the content of the page. > It take a few miliseconds to mike to understand. > "Ho ok, this is editing the content of the page." > > 9 lines for mike... > > > If the edit button btton was near the content mike would have nticed it > more > easily. > Also He would have linked it more easily with the fact it is editing the > content. > > > This is what makes the difference between the two designs... I happen to agree about the fact that the page action buttons should be located in the content area of the page. Additionally, power users can also get accustomed to keyboard shortcuts and they're even better than the non-moving top bar: 1. fingers don't need to leave the keyboard -> faster 2. always available wherever you are on the page So this global discussion could go on for ages before we come to an ideal solution :-) We'll definitely keep working on improving XWiki's UI / UX in the coming releases (XE 2.1 is scheduled for the end of the year) and sharing the work with the community in order to assess all options and come to an optimal choice. Many corporate users are not familiar with wikis at all and we'll explore all the ways to make the UI / UX easier to understand and use for them. We'll be looking for your feedback during that time and the 2 mails you just wrote will definitely be useful. Now when it comes to releasing XWiki Enterprise 2.0 with or without colibri, I'm definitely in favor of using Colibri. As Vincent stated it, the new skin: - Doesn't have drawbacks toucan doesn't already have - the action bar is in the same location - all important items are in the same location -> no new UX issues (no regressions) - Brings a lot of improvements - scrolling issue fixed - ability to change colors and select a theme - panels no longer go up to the top of the page -> allows for more flexible layouts - new visual identity which is an important part of XWiki Enterprise 2.0 - the page title is displayed automatically (we get a lot of strong feedback from our corporate users on this and they will like it a lot - even though we need to fix the double title issue on a number of pages) So I don't see a compelling reason not to use it. You're right about the fact that it means splitting XWiki's renovation in 2 (new look today, new ergonomics tomorrow) but this isn't an issue by itself as long as we keep working on improving it in the future. Thanks for your feedback, Guillaume > > > 2009/9/2 Thibaut DEVERAUX <thibaut.deveraux(a)gmail.com> > > > Ho that's it. It is a design decision based about scrolling. I forgot > this > > point. > > > > So I understand now. Yet I still have some remarks about this because > what > > you choose now is not neutral at all. > > I don't say it is good or bad. I say everybody have to understand the > > implications. > > > > /***************************** > > Disclaimer : > > All of this is mainly theorical, UX is not an exact science when you > can't > > make tests. Also I can be biaised by my own eperience (I'm definitivly > not a > > newbee user, more probably a geek user). > > The only manner to really be sure about it is, like usual, to make tests > on > > a few real newbee users... > > *****************************/ > > > > > > Situation : > > > > Just imagine you are in a supermarket and you search for butter. > > > > First of all you assume butter is somewhere in the food aera. > > > > Then you may think that butter is with all prooducts based on milk. > > > > Also it should be in a freezer aera. > > > > So you will find easily the butter. > > > > > > Information architecture and ergonomy use a lot a methode called "card > > sorting" to create such logic aeras. They write the elements of the > > interface on paper. Then they ask people to group card they think to be > > linked. Then they make stats on groups to define an architecture of > elements > > grouped in a logic way. > > > > More information : > > French : http://www.ergolab.net/articles/tri-cartes-ergonomie-web.php > > English : > > http://www.boxesandarrows.com/view/card_sorting_a_definitive_guide > > > > > > You understand, I think, what I mean. In a "logic aeras" way the edit > > button and all what is related specifically to the content on the page > > should be near the page. (I dont mind it is moving or not, since it is in > > the content aera) > > > > > > Ok. Now, you will say me that anyone found a solution to get at the same > > time the content related links near the content and at the same time > having > > the content related links always accessible. So : "the menu becomes > > inaccessible once you scroll down". > > > > > > This is right. So they're is a deal... > > > > > > Will I choose something : > > > > * Efficient ? Quicly accessible user bar. > > > > * Newbee friendly ? Put the information where they will search it. > > > > > > > > It really depends on the targeted users : > > > > * If users know the should be an edit button somewhere, choose something > > effcient. > > * If users will use the wiki all the days choose something efficient. > > / > > * If firms have a problematic of adoption and at the same time a lot of > > people not skilled in computers choose something newbee friendly. > > * If yo want anybody can contribute quicly, even if not at ease with > > computers choose something newbee friendly. > > > > > > For my part, not knowing who are the personas, I would have choosen the > > version where the content related actions are in the content aera because > : > > * Imo and according to what I read, scrolling back to someting he has > > already noticed is not the greatest problem for casual users. > > * A newbee oriented design avoid getting people lost since a regular > users > > design only deserve regular users confort. > > > > > > Yet I guess the main clients xwiki are people who have to use regulary > the > > tool or people who know that they here to edit page and that it can be > done > > cliking on an "edit" button somewhere on the page. > > > > > > So... Imo this decision is not about a blind vote in a mailing list where > > evryone is biaised by the fact he know the tool. This decision is to : > > > > * Have its implications evaluated. Best by tests, else by brainstorming > > like we are doing. > > * Being linked with political and marketing orientations. Project leader, > > marketing personas, community... I don't know who.... > > > > > > > > > > > > > > > > > > > > 2009/9/1 Sergiu Dumitriu <sergiu(a)xwiki.com> > > > > Thibaut DEVERAUX wrote: > >> > The skin is still the provisory skin isn't it ? > >> > > >> > I would prefer to wait for the nice version being programmed. > >> > > >> > I think the provisory version has no real advantage on the old one. It > >> is > >> > the same information architecture (worst indeed) with only the > >> minimalist > >> > layout as a plus. > >> > > >> > Imo the minimalist layout is made to work with the exellent ergonomics > >> from > >> > first Caty versions. This is what makes it emotionaly coherent. So I > >> would > >> > prefer to wait the skin being developed. > >> > >> Actually, one of the main reasons why the menu had been moved (at the > >> expense of loosing permanent access to it) was to eliminate the > >> flickering effect when scrolling. Now that a community member provided a > >> nice fix for this issue, it is possible that we will end up not changing > >> the layout in that direction after all. > >> > >> As Vincent said, this skin has the great advantage of being easy to > >> change, and we need this in 2.0 . Please let us know what are the > >> specific bad points from your perspective, what you think is worse than > >> in the previous skin, and what makes the proposed layout (where the menu > >> becomes inaccessible once you scroll down) have better ergonomics than > >> the current one, where you have immediate access to the actions all the > >> time. > >> > >> Thanks in advance for a more detailed feedback. > >> > >> > > >> > > >> > I would propose : > >> > > >> > 1 - Start from the nice proposition > >> > 2 - Work on the menu UX design, wich was the discussion point. (use > >> > "advanced" button ?) > >> > 3 - Develop it... > >> > 4 - relase Colibri skin > >> > > >> > > >> > So unless I missed something and the colibri skin is not still in his > >> old > >> > provisory state, it will be -1 for my part. > >> > > >> > > >> > > >> > 2009/9/1 Th > >> > omas Mortagne <thomas.mortagne(a)xwiki.com> > >> > > >> >> On Tue, Sep 1, 2009 at 14:29, Vincent Massol<vincent(a)massol.net> > >> wrote: > >> >>> On Sep 1, 2009, at 2:28 PM, Guillaume Lerouge wrote: > >> >>> > >> >>>> Hi devs, > >> >>>> I think we should make colibri the default skin in XE 2.0 RC1 if we > >> >>>> want it > >> >>>> to be tested and ready for the release. > >> >>>> > >> >>>> Here's my +1 > >> >>> +1 but only provided we agree on the default colors. Right now I'm > -1 > >> >>> with the current colors. I've had several negative feedbacks about > >> >>> them (too light). > >> >> +1 > >> >> > >> >>> Thanks > >> >>> -Vincent > >> >>> > >> >>> _______________________________________________ > >> >>> devs mailing list > >> >>> devs(a)xwiki.org > >> >>> http://lists.xwiki.org/mailman/listinfo/devs > >> >>> > >> >> > >> >> > >> >> -- > >> >> Thomas Mortagne > >> >> _______________________________________________ > >> >> devs mailing list > >> >> devs(a)xwiki.org > >> >> http://lists.xwiki.org/mailman/listinfo/devs > >> >> > >> > _______________________________________________ > >> > devs mailing list > >> > devs(a)xwiki.org > >> > http://lists.xwiki.org/mailman/listinfo/devs > >> > > >> > >> > >> -- > >> Sergiu Dumitriu > >> http://purl.org/net/sergiu/ > >> _______________________________________________ > >> devs mailing list > >> devs(a)xwiki.org > >> http://lists.xwiki.org/mailman/listinfo/devs > >> > > > > > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > -- Guillaume Lerouge Product Manager - XWiki Skype: wikibc Twitter: glerouge http://guillaumelerouge.com/

16 years

2
1
0 0

[xwiki-devs] [Vote] Default Color Theme

by Ecaterina Valica

16 years

13
15
0 0

[xwiki-devs] [Vote] Make the colibri skin the default one in XE 2.0 RC1

by Guillaume Lerouge

Hi devs, I think we should make colibri the default skin in XE 2.0 RC1 if we want it to be tested and ready for the release. Here's my +1 Guillaume -- Guillaume Lerouge Product Manager - XWiki Skype: wikibc Twitter: glerouge http://guillaumelerouge.com/

16 years

7
12
0 0

[xwiki-devs] jython 2.5.1 rc1 released

by Vincent Massol

for information: http://fwierzbicki.blogspot.com/2009/09/jython-251-release-candidate-1-is-o… Release notes: Jython 2.5.1rc1 New Features - Upgraded to ANTLR 3.1.3 - [ 1859477 ] Dynamically loaded ServletFilters like PyServlet - Built in JSR 223 scripting engine, with LiveTribe JSR 223 implementation for JDK 5 - Jython "-J-classpath cp_args_here" now works as expected for unix shell. Bugs Fixed - [ 645615 ] cannot import through symbolic links - [ 1366 ] parsing of lamda expression fails - [ 1365 ] continuation lines fail in interactive interpreter - [ 1377 ] Event names shadowed by a field name on Java types leads to a NPE - [ 1381 ] Redundant declarations of interface implementation hides overriden methods - [ 1189 ] MD5 hash is incorrectly calculated when string contains non-latin chars and using python md5 lib - [ 1802339 ] Problem printing unicode when stdout intercepted - [ 1145 ] Jython 2.5 compatibility problem with JSR 223 - [ 1400 ] Evaluating expression via JSR 223 ScriptEngine returns null instead of True/False - [ 1413 ] Array data type (PostgreSQL) is not supported (NPE) - [ 1434 ] Cannot get return code from a process started with os.popen with Jython 2.5 (worked in 2.2) - [ 1391 ] socket.getaddrinfo() breaks ftplib FTP client - [ 1409 ] JSR-233 engine version numbers backwards - [ 1408 ] JSR-223 engine doesn't implement I/O redirection - [ 1393 ] TypeError: _new_impl(): expected 1 args; got 0 - [ 1415 ] ast Node creation fails with no arg constructors - [ 1405 ] Executing __run__.py from .jar throws exception(SystemExit: 0) in main when sys.exit(0) is called - [ 1439 ] Can't write() array.array - [ 1139 ] crashes on isinstance - [ 1430 ] Oracle JDBC Connection close - [ 1406 ] Parsing a simple PEP 342 coroutine crashes Jython 2.5 - [ 1407 ] ClassCastException in plain Python coroutine - [ 1424 ] Relative imports do not work in some cases The JSR223 part sounds cool. Maybe we can have a jython macro at last? Thanks -Vincent

16 years

1
0
0 0

Re: [xwiki-devs] [Vote] Default Color Theme

by Guillaume Lerouge

> > Hi, > +1 for 3) > > Guillaume > > > On Tue, Sep 1, 2009 at 6:28 PM, Anca Luca <ancapaula.luca(a)xwiki.com>wrote: > >> I love the Halloween theme, but it's a bit too much for a default theme, >> same as >> Bordo. >> >> +0.5 for each of current (0) & BlueSky (C) as it is. >> >> Happy styling, >> Anca >> >> Ecaterina Valica wrote: >> > Hi, >> > >> > Please vote to set the default Color Theme for XWiki. >> > >> > The existing themes were: >> > >> > *(0) * >> > >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/DefaultColorThe… >> > SchemeDefault.png< >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/DefaultColorThe… >> >[ >> > *Currently Default*] >> > >> > *(A) * >> > >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/AColorTheme/ >> > SchemeA.png< >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/AColorTheme/Sch… >> >[ >> > *Nature*] >> > >> > *(B) * >> > >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/BColorTheme/ >> > SchemeB.png< >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/BColorTheme/Sch… >> > >> > * *[*Nightfall*] >> > >> > *(C)* >> > >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/CColorTheme/ >> > SchemeC.png< >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/CColorTheme/Sch… >> >[ >> > *Blue Sky*] >> > >> > *(D) * >> > >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/DColorTheme/ >> > SchemeD.png< >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/DColorTheme/Sch… >> >[ >> > *Inner Dark*] >> > >> > *(E) * >> > >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/EColorTheme/ >> > SchemeE.png< >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/EColorTheme/Sch… >> >[ >> > *Bordo*] >> > >> > Since then there were added 3 more themes: >> > >> > *(F)* >> > >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/FColorTheme/Pea…<http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/FColorTheme/Pea…> >> > *Peach*] >> > >> > *(G)* >> > >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/GColorTheme/Cho…<http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/GColorTheme/Cho…> >> > *Choco Blues*] >> > >> > *(H)* >> > >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/Halloween/Hallo…<http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/Halloween/Hallo…> >> > *Halloween*] >> > >> > Because Theme *(C) Blue Sky* was mentioned as a candidate for the >> Default >> > Theme, I've done some variations with those colors: >> > >> > *(1)* >> > >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/Proposal1/Propo… >> > >> > *(2)* >> > >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/Proposal2/Propo… >> > >> > *(3)* >> > >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/Proposal3/Propo… >> > >> > *(4)* >> > >> http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/Proposal4/Propo… >> > >> > So please cast your vote or your Theme proposal. >> > >> > Thanks, >> > Caty >> > _______________________________________________ >> > devs mailing list >> > devs(a)xwiki.org >> > http://lists.xwiki.org/mailman/listinfo/devs >> _______________________________________________ >> devs mailing list >> devs(a)xwiki.org >> http://lists.xwiki.org/mailman/listinfo/devs >> > > -- Guillaume Lerouge Product Manager - XWiki Skype: wikibc Twitter: glerouge http://guillaumelerouge.com/

16 years

1
0
0 0

Re: [xwiki-devs] [Vote] Default Color Theme

by PERINAUD Christophe

+1 (3) -------------------------------------------------------------------------------- This e-mail is intended only for the addressee named above. It does not bind the sender, except in the case of an existing written convention with the addressee. This e-mail may contain material that is confidential and privileged for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender and delete all copies. While reasonable precautions have been taken to ensure that this e-mail and any attachments are free from any computer virus or similar defect, no liability will be accepted in that respect. Anyone accessing this e-mail must take their own precautions as to security and virus protection. KBL European Private Bankers S.A., 43 boulevard Royal L-2955 Luxembourg, R.C.S. Luxembourg B 6395, T (352) 47 97 1

16 years

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r23184 - platform/xwiki-plugins/trunk/watchlist/src/main/java/com/xpn/xwiki/plugin/watchlist

by Vincent Massol

On Sep 1, 2009, at 2:25 PM, jvdrean (SVN) wrote: > Author: jvdrean > Date: 2009-09-01 14:25:49 +0200 (Tue, 01 Sep 2009) > New Revision: 23184 > > Modified: > platform/xwiki-plugins/trunk/watchlist/src/main/java/com/xpn/xwiki/ > plugin/watchlist/WatchListStore.java > Log: > Fixed wrong listener name wow, glad my log allowed to catch this! That would have caused some serious problems ;) -Vincent > Modified: platform/xwiki-plugins/trunk/watchlist/src/main/java/com/ > xpn/xwiki/plugin/watchlist/WatchListStore.java > =================================================================== > --- platform/xwiki-plugins/trunk/watchlist/src/main/java/com/xpn/ > xwiki/plugin/watchlist/WatchListStore.java 2009-09-01 12:21:27 UTC > (rev 23183) > +++ platform/xwiki-plugins/trunk/watchlist/src/main/java/com/xpn/ > xwiki/plugin/watchlist/WatchListStore.java 2009-09-01 12:25:49 UTC > (rev 23184) > @@ -92,7 +92,7 @@ > /** > * The name of the listener. > */ > - private static final String LISTENER_NAME = "rightsmanager"; > + private static final String LISTENER_NAME = "watchliststore"; > > /** > * The events to match. > @@ -619,4 +619,4 @@ > { > return LISTENER_NAME; > } > -} > \ No newline at end of file > +}

16 years

1
0
0 0

[xwiki-devs] [Proposal] Define a set of User Experience guidelines for XWiki

by Guillaume Lerouge

Hi Devs, Following-up on Caty's email ( http://markmail.org/message/3vukpehxeiflfjfw) I'd like us to get a bit more organized when it comes to improving XWiki's User Experience. This would allow us to make the product better and to gather more feedback from the community (such as Thibaut's email, see http://markmail.org/message/3bdk4jaziuqs6zvi ). In order to make our product great I think it would be good for us to agree on a set of standards and best practices related to UX. There are 2 levels to this initiative: 1. Agree on a set of broad rules 2. Agree on the implementation specifics for each rule A broad rule is a general rule that has to be followed when designing & coding a new feature: 1. "Always design a feature with one or more specific personas in mind" 2. "Respect consistency -> all UI items in XWiki should look & behave in the same way" Specifics are details related to the implementation of any given rule: 1. Choose the style to use for all buttons (see http://incubator.myxwiki.org/xwiki/bin/view/Standards/ for examples) 2. Define the personas we're targetting (see http://dev.xwiki.org/xwiki/bin/view/Design/ImproveXWikiUserExperience for examples) I'd like to get your feedback on the following points: - Is that a good idea overall? - Do you think we can make it an integral part of our development process? If the feedback is positive I'll start a discussion about the general UX rules we should make XWiki follow, then new ones for the specifics of each rule once we've agreed on some or all of them. Thanks, Guillaume -- Guillaume Lerouge Product Manager - XWiki Skype: wikibc Twitter: glerouge http://guillaumelerouge.com/

16 years

8
11
0 0

[xwiki-devs] [Proposal] Making "Edit this attachment" an advanced feature in the advanced edit mode

by Silvia Rusu

Hi devs, I propose we make "Edit this attachment" in the "Attachments" tab an advanced feature in the advanced edit mode. When trying to use "Edit this attachment": - in IE you get the following message: "Could not initialize a required ActiveX object" - in FF 3.5.2 installing the extension delivers the following message:"FoxWiki 1.0b could not be installed because it is not compatible with Firefox 3.5.2". - installing the extension on an older version of FF requires additional configuration, which the average user may not know how to perform. Under the above circumstances I think "Edit this attachment" will cause confusion for the average user instead of providing a useful tool. WDYT? ----- Silvia Rusu Tester & Documentation Writer - XWiki http://twitter.com/silviarusu -- View this message in context: http://n2.nabble.com/Proposal-Making-Edit-this-attachment-an-advanced-featu… Sent from the XWiki- Dev mailing list archive at Nabble.com.

16 years

6
11
0 0

[xwiki-devs] [Proposal] Remove "History" from the "Choose editor" panel

by Silvia Rusu

Hi Devs, I propose we remove "History" from the "Choose editor" panel in Edit mode. If you look at the "Edit" entry in the XWiki action menu you will see the following sub-menus: - WIKI - WYSIWYG - INLINE FORM - PAGE ACCESS RIGHTS - OBJECTS - CLASS The entries in the "Choose editor" panel are all "Edit" sub-menus, except for "History". I think the "History" tab in View mode should be enough. WDYT? Silvia ----- Silvia Rusu Tester & Documentation Writer - XWiki http://twitter.com/silviarusu -- View this message in context: http://n2.nabble.com/Proposal-Remove-History-from-the-Choose-editor-panel-t… Sent from the XWiki- Dev mailing list archive at Nabble.com.

16 years

6
5
0 0

Re: [xwiki-devs] Blog Plugin Proposal

by Andreas Schaefer

On Monday, August 31, 2009, at 12:46AM, "Vincent Massol" <vincent(a)massol.net> wrote: > >On Aug 31, 2009, at 9:28 AM, Guillaume Lerouge wrote: > >> Hi Andreas, >> >> On Mon, Aug 31, 2009 at 1:11 AM, Andreas Schaefer <schaefera(a)me.com> >> wrote: >> >>> My try to deploy the Blog Plugin together with the updated Blog >>> Application failed miserably today and my dislike of Velocity reach a >>> new high. >>> >>> Because I see the value of the scripting nature of the Blog allowing >>> users to customize their Blog to a quite large degree I don't want to >>> ditch that but I have a lot of problems with Velocity and the way is >>> plastering over issues. I rather fail fast than late with hardly a >>> trail to understand what is going on. >>> >> >> My personal experience with velocity is more of a try & fail, try & >> fail, >> try and succeed one than anything else. > >This is not really related to velocity which is the simplest language >on earth. It's related to any language you type without an IDE to help >you. Try using groovy in wiki pages you'll have the same problem (I >know I have it, I need to preview 10 times to get something right). > >That said, there are some velocity editing support in IntellilJ IDEA >and I think there's also a plugin for Eclipse which might help. You >can also use XEclipse which has syntax highlighting and some >autocompletion for velocity (you'd need to use the 1.2RC1 version). I can agree with that. Velocity might be the simplest language for you but for started I could not find a good Velocity language tutorial. Even though the support I get from IntelliJ is really helpful the strange syntax is making it difficult to code (return values through parameters for example) but the real difficulty comes from the fact that I cannot debug velocity in any efficient way but the real thing I cannot stand is the fact that Velocity just ignore any problems. This might be good for a simple web site but for an application like a blog this is not good in my view. At least with Groovy I have a fairly well defined language and some mailing lists that can help me with problems and it ensures that NPEs, undefined methods etc are handled. >> What I found out is that I was msot >> of the time better off rewriting stuff starting with small chunks >> rather >> than trying to take existing code and reuse it all at once. The >> current blog >> is a fairly complex piece of velocity code (that is, given the lack of >> debugging tools when coding in velocity in the wiki). This is one of >> the >> reasons I think Sergiu's argument that "devs will be able to look at >> the >> code and learn from it" is not entirely true ;-) >> >> What's really important for the blog is that it can be customized >> easily at >> 2 levels: >> >> - Look: an user should be able to use the panels she wants for her >> blog >> - Deployment: an user should be able to create a new space blog or >> global >> wiki blog in any space she wants >> >> Besides that the way the blog is code doesn't matter much for the >> end user. >> >> That said I still think that it might be a good idea to convert the >>> scripted part of the Blog over to Groovy and keep the rest in the >>> Blog >>> Plugin. I don't have any experience with Groovy inside XWiki but for >>> sure the documentation of Groovy outside is excellent compared to >>> Velocity. I will use the next week to get up to speed and try to >>> convert a piece of the Blog over to Groovy. >> >> >> Then go ahead and give it a go :-) >> >> One thing you need to be aware of when using Groovy inside the wiki >> is that >> your pages will haveto be saved using programming rights. This can >> cause a >> number of issues, don't forget to code with an user that has them, >> it will >> save yo ua lot of hassle ;-) > >Yes and we might not be able to include it in the default distribution >since our rule so far was only velocity in the default XE XAR. I rather have a good, robust and reliable Blog application even if I would have to download it separately. But first I need to see how well a Blog in Groovy would work and what the limitations (like the programming rights) mean. To keep it easy I think I will start with implementing what we have in BlogSheet/BlogCode to just list the current entries in a blog. If I can then create a Blog Post Entry with Groovy I should pretty much be able to compare the two. Personally I am more interested to get the stuff going well for my own Blog but I am willing to go the extra mile to provide it to the community. Cheers - Andy

16 years

2
1
0 0

[xwiki-devs] [VOTE] Use PNG instead of GIF for the silk icons

by Sergiu Dumitriu

Hi devs, Short version: we need to replace GIFs with transparent PNGs for the Silk icon set. 3 options: A. use "filter: AlphaImageLoader" in our CSS, time consuming for our devs B. serverside content negotiation to send GIFs only to IE6, doesn't really fix the problem for IE6 C. use a third party library that handles this for us, but does not work under certain security restrictions Long version: Originally, silk icons are PNGs, with alpha transparency. The problem with them is that in IE6 they don't display nice, since they have a gray background. So, instead we're currently using GIFs, but this approach has some big issues: - GIFs are indexed, so they have at most 256 colors out of the millions possible in PNGs. This is not such a big issue, since most icons don't use so many colors. - PNGs are smaller (in bytes) than GIFs. - Since gifs don't have alpha transparency, they have an almost-white border around the colored pixels, which makes them ugly on non-white backgrounds (this is obvious on really dark backgrounds). This is a real blocker for using darker themes in Colibri. Now, switching to PNGs directly is not a good option, since most of our end users are (forced to be) using IE6. Some tricks are possible: A. Change the CSSs to contain a filter which enables the PNG transparency. This can be done in several ways: A1 - manually (hard for developers, breaks CSS validity) A2 - automatically at build time (breaks CSS validity) A3 - dynamically in the SkinAction (won't work if the CSS is served by the container) The advantage is that we can control which images are transformed. The disadvantage is that it might not work under certain security restrictions. B. Implement a kind of content-negotiation trick that sends PNGs or GIFs depending on the user agent. This is easy to do with a few Apache HTTPD settings, but it's not cross-platform at all. We can also do it in the SkinAction, but again, doesn't work if the request does not pass through it. The advantage is that it always works, since it's always an image. The disadvantage is that icons will continue to look ugly in IE6, since they are GIFs. C. Use http://www.twinhelix.com/css/iepngfix/ which automatically fixes all images in IE. The advantages are that it is the most easy solution to implement, with the least amount of effort, it fixes most problems, and requires little maintenance. The disadvantage is that it won't work under certain security restrictions, and that a clean and fast integration will requirer to add some mechanism of identifying which images to fix (it can be incompatible with other tools that do their own PNG fix, like Google Maps). None of the alternatives is perfect, but my personal preference goes to C. -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years

4
5
0 0

Re: [xwiki-devs] [Proposal] Remove "History" from the "Choose editor" panel

by Guillaume Lerouge

> > +1 > Guillaume > > > On Mon, Aug 31, 2009 at 11:56 PM, Jean-Vincent Drean < > jean-vincent(a)drean.org> wrote: > >> +1 >> >> JV. >> >> On Mon, Aug 31, 2009 at 8:31 PM, Sergiu Dumitriu<sergiu(a)xwiki.com> wrote: >> > Silvia Rusu wrote: >> >> Hi Devs, >> >> >> >> I propose we remove "History" from the "Choose editor" panel in Edit >> mode. >> >> >> >> If you look at the "Edit" entry in the XWiki action menu you will see >> the >> >> following sub-menus: >> >> - WIKI >> >> - WYSIWYG >> >> - INLINE FORM >> >> - PAGE ACCESS RIGHTS >> >> - OBJECTS >> >> - CLASS >> >> >> >> The entries in the "Choose editor" panel are all "Edit" sub-menus, >> except >> >> for "History". >> >> >> >> I think the "History" tab in View mode should be enough. >> >> >> >> WDYT? >> > >> > +1 >> > >> > "Edit History" is a bit misplaced. While all the other entries are about >> > real editing of the document, this is about viewing previous edits. >> > >> > -- >> > Sergiu Dumitriu >> > http://purl.org/net/sergiu/ >> > _______________________________________________ >> > devs mailing list >> > devs(a)xwiki.org >> > http://lists.xwiki.org/mailman/listinfo/devs >> > >> _______________________________________________ >> devs mailing list >> devs(a)xwiki.org >> http://lists.xwiki.org/mailman/listinfo/devs >> > > > > -- > Guillaume Lerouge > Product Manager - XWiki > Skype: wikibc > Twitter: glerouge > http://guillaumelerouge.com/ >

16 years

1
0
0 0

[xwiki-devs] [Proposal] Introduce a 'Create' entry in the menu

by Sergiu Dumitriu

Hi devs, I'd like to introduce a 'Create' entry in the XWiki action menu. This would be the first entry (it would appear before 'Edit') and would have the following sub-menus: - Page - Page from Office Document - Space The "Page from Office document" entry replaces the "Import Office Document" entry from the "Actions" menu, which IMHO does not really fit there. This allows to also get rid of the "Create" panel, and have all the features available from the menu. We could include this only in the Colibri skin for the moment, experimentally, to see how it is received by the users. -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years

6
11
0 0

[xwiki-devs] [VOTE] Upgrade to Prototype 1.6.1 RC3

by Sergiu Dumitriu

Hi devs, I'd like to propose to upgrade to Prototype 1.6.1 RC3, released on June 16, because it fixes (among other speed improvements and bug fixes) a pretty important compatibility issue with IE8, which causes http://markmail.org/thread/qp4l7hfxohnbpx7x and badly styled notifications. It also fixes some bugs with Opera and selectors that I've hit and had to work around. Normally I wouldn't include a RC dependency, but given the important bugs it fixes, and the fact that they have pretty extensive tests, I trust that this upgrade won't break anything. My +1. -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years

8
8
0 0

[xwiki-devs] [VOTE] API changes to the bridge module for 2.0RC1

by Vincent Massol

Hi, I'm implementing support for specifying jars attached to pages and using them from the script macro. see http://jira.xwiki.org/jira/browse/XWIKI-3941 for more details. (Note that my own need for this is to rewrite our IRC Bot using the 2.0 Rendering to make it more stable.) For this I need the following changes: * Introduce new CurrentDocumentNameFactory which extends DefaultDocumentNameFactory but instead of using "WebHome" if the page name is not specified, it uses the current document page name. * Introduce AttachmentNameFactory to parse syntax of the form: wiki:space.page@filename * Deprecate in DAB: "String getAttachmentURL(String documentName, String attachmentName);" and instead replace it with "String getAttachmentURL(AttachmentName attachmentName);" * Add in DAB: "List<String> getAttachmentURLs(DocumentName documentName) throws Exception;" to return all attachments * I also want to fix AttachmentName which shouldn't extend DocumentName but instead use it by composition (it's not used right now). Note: In the future, we'll also deprecate all *URL() methods in DAB since the correct way will be to write: - DocumentName (or AttachmentName) - new XWikiDocumentURL(DocumentName) (or new XWikiAttachmentURL(AttachmentName)) - DocumentNameSerializer.serialize(xwikiDocumentURL) --> URL (or AttachmentNameSerializer.serialize(xwikiAttachmentURL)) Here's my +1 to these and to add them in RC1. Note: I'd like to have this in 2.0 final because I think it's cool to have support for XWIKI-3941 but also because we'd need it on xwiki.org too in order to be able to use the IRC Bot I'm fixing. Thanks -Vincent

16 years

4
4
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs