Re: [xwiki-devs] Saving page name with accented character?

2016-06-27 Thread Julio Brum 
Sergiu, thanks for the suggestion. I changed the "-Dfile.encoding" value to
"UTF-8", but the problem continues.

I think the only solution is to install XWiki on a Linux machine ...

Cordialment,
Julio

2016-06-27 13:17 GMT-03:00 Sergiu Dumitriu :

> It may be. Can you configure the tomcat start script to also pass this
> option to the java command:
>
> -Dfile.encoding=utf-8
>
> I'm not sure how to do that on Windows, maybe this can help:
>
> http://stackoverflow.com/a/11343571/620249
>
> On 06/27/2016 11:54 AM, Julio Brum wrote:
> > Sergiu,
> >
> > the operating system encoding is "Cp1252". Is this the problem?
> >
> > Cordialment,
> > Julio
> >
> > 2016-06-25 9:51 GMT-03:00 Sergiu Dumitriu :
> >
> >> What is the operating system encoding? Try putting this in a new wiki
> >> page and view it:
> >>
> >> {{groovy}}
> >> print System.getProperty('file.encoding')
> >> {{/groovy}}
> >>
> >> On 06/23/2016 06:38 PM, Julio Brum wrote:
> >>> I am using the XWiki version 7.4.1 with UTF-8 in Xwiki, tomcat8 and
> >>> Postgres, but every time than I save a page with accent in the name,
> >> XWiki
> >>> change the name. For example, I try to save a page with the name "é"
> and
> >>> XWiki save "%25C3%25A9" Please, why this happens?
> >>>
> >>>
> >>>
> >>> *My settings in windows:*
> >>>
> >>> *tomcat\conf\server.xml:*
> >>>
> >>>  >>>   URIEncoding="UTF-8"
> >>>
> >>> *xwiki.cfg:*
> >>>
> >>> xwiki.encoding=UTF-8
> >>>
> >>> *PostgreSQL:*
> >>>
> >>> CREATE DATABASE wiki
> >>>   WITH OWNER = postgres
> >>>ENCODING = 'UTF8'
> >>>TABLESPACE = pg_default
> >>>LC_COLLATE = 'Portuguese_Brazil.1252'
> >>>LC_CTYPE = 'Portuguese_Brazil.1252'
> >>>CONNECTION LIMIT = -1;
> >>>
> >>> Thanks,
> >>> Julio
> >>
> >> --
> >> Sergiu Dumitriu
> >> http://purl.org/net/sergiu/
> >> ___
> >> devs mailing list
> >> devs@xwiki.org
> >> http://lists.xwiki.org/mailman/listinfo/devs
> >>
> > ___
> > devs mailing list
> > devs@xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/devs
> >
>
>
> --
> Sergiu Dumitriu
> http://purl.org/net/sergiu/
> ___
> devs mailing list
> devs@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
___
devs mailing list
devs@xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs

Re: [xwiki-devs] Saving page name with accented character?

2016-06-27 Thread Sergiu Dumitriu 
It may be. Can you configure the tomcat start script to also pass this
option to the java command:

-Dfile.encoding=utf-8

I'm not sure how to do that on Windows, maybe this can help:

http://stackoverflow.com/a/11343571/620249

On 06/27/2016 11:54 AM, Julio Brum wrote:
> Sergiu,
> 
> the operating system encoding is "Cp1252". Is this the problem?
> 
> Cordialment,
> Julio
> 
> 2016-06-25 9:51 GMT-03:00 Sergiu Dumitriu :
> 
>> What is the operating system encoding? Try putting this in a new wiki
>> page and view it:
>>
>> {{groovy}}
>> print System.getProperty('file.encoding')
>> {{/groovy}}
>>
>> On 06/23/2016 06:38 PM, Julio Brum wrote:
>>> I am using the XWiki version 7.4.1 with UTF-8 in Xwiki, tomcat8 and
>>> Postgres, but every time than I save a page with accent in the name,
>> XWiki
>>> change the name. For example, I try to save a page with the name "é" and
>>> XWiki save "%25C3%25A9" Please, why this happens?
>>>
>>>
>>>
>>> *My settings in windows:*
>>>
>>> *tomcat\conf\server.xml:*
>>>
>>> >>   URIEncoding="UTF-8"
>>>
>>> *xwiki.cfg:*
>>>
>>> xwiki.encoding=UTF-8
>>>
>>> *PostgreSQL:*
>>>
>>> CREATE DATABASE wiki
>>>   WITH OWNER = postgres
>>>ENCODING = 'UTF8'
>>>TABLESPACE = pg_default
>>>LC_COLLATE = 'Portuguese_Brazil.1252'
>>>LC_CTYPE = 'Portuguese_Brazil.1252'
>>>CONNECTION LIMIT = -1;
>>>
>>> Thanks,
>>> Julio
>>
>> --
>> Sergiu Dumitriu
>> http://purl.org/net/sergiu/
>> ___
>> devs mailing list
>> devs@xwiki.org
>> http://lists.xwiki.org/mailman/listinfo/devs
>>
> ___
> devs mailing list
> devs@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
> 


-- 
Sergiu Dumitriu
http://purl.org/net/sergiu/
___
devs mailing list
devs@xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs

Re: [xwiki-devs] Saving page name with accented character?

2016-06-27 Thread Julio Brum 
Sergiu,

the operating system encoding is "Cp1252". Is this the problem?

Cordialment,
Julio

2016-06-25 9:51 GMT-03:00 Sergiu Dumitriu :

> What is the operating system encoding? Try putting this in a new wiki
> page and view it:
>
> {{groovy}}
> print System.getProperty('file.encoding')
> {{/groovy}}
>
> On 06/23/2016 06:38 PM, Julio Brum wrote:
> > I am using the XWiki version 7.4.1 with UTF-8 in Xwiki, tomcat8 and
> > Postgres, but every time than I save a page with accent in the name,
> XWiki
> > change the name. For example, I try to save a page with the name "é" and
> > XWiki save "%25C3%25A9" Please, why this happens?
> >
> >
> >
> > *My settings in windows:*
> >
> > *tomcat\conf\server.xml:*
> >
> >  >   URIEncoding="UTF-8"
> >
> > *xwiki.cfg:*
> >
> > xwiki.encoding=UTF-8
> >
> > *PostgreSQL:*
> >
> > CREATE DATABASE wiki
> >   WITH OWNER = postgres
> >ENCODING = 'UTF8'
> >TABLESPACE = pg_default
> >LC_COLLATE = 'Portuguese_Brazil.1252'
> >LC_CTYPE = 'Portuguese_Brazil.1252'
> >CONNECTION LIMIT = -1;
> >
> > Thanks,
> > Julio
>
> --
> Sergiu Dumitriu
> http://purl.org/net/sergiu/
> ___
> devs mailing list
> devs@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
___
devs mailing list
devs@xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs

Re: [xwiki-devs] [UX][Vote] Future of Main.Welcome

2016-06-27 Thread Ecaterina Moraru (Valica) 
On Wed, Jun 22, 2016 at 2:24 PM, Vincent Massol  wrote:

> Hi Caty,
>
> > On 21 Jun 2016, at 14:58, Ecaterina Moraru (Valica) 
> wrote:
> >
> > Hi,
> >
> > This thread is about deciding on a future for the Main.Welcome page. This
> > page was used as the first gadget's content and was intended to be
> modified
> > by the users. In 8.2M2 we changed the content of Main.WebHome page to
> > provide simple wiki text instead of the Dashboard include, deprecating
> > somehow the purpose of the Welcome page.
> >
> > Problem: In the 'Navigation' panel the "Welcome to your wiki" is
> displayed
> > as a child page of "Home". Users might ask what is the purpose of this
> page.
> >
> > We could either:
> > 1. Keep it
> > 1.A and mark it as hidden: in order to not be displayed in the Navigation
> > tree
> > 1.B and move it to Dashboard: instead of being in the Main space, since
> now
> > it's used only there.
> > 1.C and change the text: from a generic 'Welcome' message, to
> instructions
> > on how to edit the Dashboard (we would need a separate proposal on the
> > content + if we want to display other gadgets)
> >
> > 2. Remove it
> > We could consider that its content is deprecated by the new Main.WebHome
> > page, so no need for this page. So we could delete the page + remove it
> > from Dashboard. Dashboard could highlight more advanced gadgets (needing
> > the separate Dashboard proposal).
> >
> > Let me know what you think,
>
>
> +1 for 2. It’s not needed anymore since it’s been replaced by the new home
> page. It’s better to make the Dashboard useful right away (ie with useful
> content).
>
> Now, I haven’t checked, but if we still generate subwiki’s home pages with
> the Dashboard, I believe we may also want to review this (for some of the
> same reasons we modified the main wiki’s home page, such as easiness of
> editing it) and replace it with a new subwiki home page.
>

When we create subwikis, they have the same content as the main wiki (the
new homepage and panels).

Current Status:
1. Keep it: +1 (Edy), +0.5 (Marius), +0.5 (GD)
1.A and mark it as hidden:
1.B and move it to Dashboard: (Edy), (Marius), (GD)
1.C and change the text: (Marius), (GD)
2. Remove it: +0.5 (Marius), +1 (Vincent)


Some questions:
a. Do we have a procedure for deleting pages from l10n? a way to retire
them? (some property in l10n + removal from the release script = [2])
b. Do we have a procedure when the translations of a page change path?
(like moving from Main space to Dashboard space = [1.B])
c. Do we have a procedure for deprecating the whole content of a page?
(let's say we don't do the move, we keep it in Main, how do we mark that
the whole content is changed in English, but needs to be updated in the
other languages? = [1.C])

Thanks,
Caty


>
> For me we should definitely not have some welcome message in the Dashboard
> app anymore. It’s not its purpose.
>
> Thanks
> -Vincent
>
> > Caty
> ___
> devs mailing list
> devs@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
___
devs mailing list
devs@xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs

Re: [xwiki-devs] Integration of ratings in xwiki-platform

2016-06-27 Thread Eduard Moraru 
Also, with the recent strategy change, shouldn`t we be discussing moving
ratings out of platform and back to contrib?

Thanks,
Eduard

On Mon, Jun 27, 2016 at 5:09 PM, Ecaterina Moraru (Valica) <
vali...@gmail.com> wrote:

> Do we have a strategy for retired projects?
>
> They have been marked as [Retired] in JIRA, but this doesn't prevent users
> from creating issues or add new code there.
> Should we have deleted the contrib sources? Should we at least change
> permissions and restrict creation of issues and code commits? Do we plan to
> maintain in parallel the 2 repos?
>
> Thanks,
> Caty
>
> On Thu, Dec 4, 2014 at 2:29 PM, Victor Rachieru  >
> wrote:
>
> > The new module can be a new version of the one on xwiki-contrib and not
> > break the extensions that have a dependency to the old module.
> >
> > The script service basically remains intact. The methods contained by
> that
> > service maintain the same signatures. Nothing has changed from this point
> > of view.
> > So previous versions of the ratings module (the ones from contrib) can
> use
> > the service just as before without it breaking things.
> >
> > The issue that arises from changing the package name is that any code
> that
> > uses classes from that package explicitly will be broken.
> >
> > Example:
> > -
> > Say you have a java or groovy script in which you
> > want to use a class from the ratings api package or typed variables. That
> > code will be broken due to the fact that packages don't match anymore.
> >
> > org.xwiki.contrib.ratings.Rating myRating = new
> > org.xwiki.contrib.ratings.Rating();
> > or
> > org.xwiki.contrib.ratings.RatingAPI myRating =
> > services.ratings.getRating(doc, author);
> >
> > on the other hand
> >
> > services.ratings.getRating(doc, author).getVote(); should be ok
> >
> >
> > The question is:
> > -
> > Is there somebody who used classes from the api package in their code or
> > the use of this module has been limited to calling the service from
> > velocity and just setting/getting votes?
> >
> > Thanks,
> > Victor
> >
> > On Wed, Dec 3, 2014 at 5:30 PM, Thomas Mortagne <
> thomas.morta...@xwiki.com
> > >
> > wrote:
> >
> > > On Wed, Dec 3, 2014 at 4:11 PM, Victor Rachieru
> > >  wrote:
> > > > Hei devs,
> > > >
> > > > I intend to integrate the ratings application which is now on
> > > xwiki-contrib
> > > > into the xwiki-platform.
> > > >
> > > > This in mainly due to 3 points:
> > > > -
> > > > 1/ give the ability to use ratings in a wiki
> > > > 2/ using it to provide ratings for the Extension Repository
> Application
> > > > (XWIKI-7780)
> > > > 3/ display ratings within Extension Manager (XWIKI-11509)
> > > >
> > > > The first point can be accomplished by using the ratings app as is
> but
> > > the
> > > > other two imply that the ratings app should be a module that is
> > > maintained
> > > > by XWiki. It makes sense that if the Extension Repository App and
> > > Extension
> > > > Manager which are maintained by XWiki depend on the Ratings App, that
> > > this
> > > > itself is maintained by XWiki as well.
> > > >
> > > > The steps needed for this is as follows:
> > > > -
> > > > 1/ create a new module in the xwiki-platform core for the ratings
> > > > - xwiki-platform-core
> > > > -- xwiki-platform-ratings
> > > > --- xwiki-platform-ratings-api
> > > > --- xwiki-platform-ratings-ui
> > > > 2/ change the artifact id from "application-ratings" to
> > > > "xwiki-platform-ratings"
> > > > 3/ change the package from "org.xwiki.contrib.ratings" to
> > > > "org.xwiki.platform.ratings"
> > > >
> > > > Implications
> > > > -
> > > > 1/ clone of the existing code is now in xwiki-platform under a
> > different
> > > > artifact id (having duplicate code, this takes us to #2)
> > > > 2/ the code from xwiki-contrib would probably have to be deemed as
> > > "retired"
> > > > 3/ the applications with a dependency to the xwiki-contrib ratings
> > would
> > > > have to be upgraded to depend on the module from xwiki-platform
> > > > 4/ the script service would remain unchanged (changing the artifact
> id
> > > and
> > > > package name does not affect the service)
> > > > 5/ if by any chance someone has code that uses the classes from the
> > > ratings
> > > > app on contrib, by upgrading, that code will cease to function
> > > >
> > > > Please state you position on this matter.
> > > >
> > > > Links
> > > > -
> > > > http://extensions.xwiki.org/xwiki/bin/view/Extension/Ratings+API
> > > >
> > http://extensions.xwiki.org/xwiki/bin/view/Extension/Ratings+Application
> > > > https://github.com/xwiki-contrib/application-ratings
> > > >
> > > > Thank you,
> > > > Victor
> > > > ___
> > > > devs mailing list
> > > > devs@xwiki.org
> > > > http://lists.xwiki.org/mailman/listinfo/devs
> > >
> > > Either the the new module is a new version and it should keep
> > > retro-compatibility to not instantly

Re: [xwiki-devs] Integration of ratings in xwiki-platform

2016-06-27 Thread Ecaterina Moraru (Valica) 
Do we have a strategy for retired projects?

They have been marked as [Retired] in JIRA, but this doesn't prevent users
from creating issues or add new code there.
Should we have deleted the contrib sources? Should we at least change
permissions and restrict creation of issues and code commits? Do we plan to
maintain in parallel the 2 repos?

Thanks,
Caty

On Thu, Dec 4, 2014 at 2:29 PM, Victor Rachieru 
wrote:

> The new module can be a new version of the one on xwiki-contrib and not
> break the extensions that have a dependency to the old module.
>
> The script service basically remains intact. The methods contained by that
> service maintain the same signatures. Nothing has changed from this point
> of view.
> So previous versions of the ratings module (the ones from contrib) can use
> the service just as before without it breaking things.
>
> The issue that arises from changing the package name is that any code that
> uses classes from that package explicitly will be broken.
>
> Example:
> -
> Say you have a java or groovy script in which you
> want to use a class from the ratings api package or typed variables. That
> code will be broken due to the fact that packages don't match anymore.
>
> org.xwiki.contrib.ratings.Rating myRating = new
> org.xwiki.contrib.ratings.Rating();
> or
> org.xwiki.contrib.ratings.RatingAPI myRating =
> services.ratings.getRating(doc, author);
>
> on the other hand
>
> services.ratings.getRating(doc, author).getVote(); should be ok
>
>
> The question is:
> -
> Is there somebody who used classes from the api package in their code or
> the use of this module has been limited to calling the service from
> velocity and just setting/getting votes?
>
> Thanks,
> Victor
>
> On Wed, Dec 3, 2014 at 5:30 PM, Thomas Mortagne  >
> wrote:
>
> > On Wed, Dec 3, 2014 at 4:11 PM, Victor Rachieru
> >  wrote:
> > > Hei devs,
> > >
> > > I intend to integrate the ratings application which is now on
> > xwiki-contrib
> > > into the xwiki-platform.
> > >
> > > This in mainly due to 3 points:
> > > -
> > > 1/ give the ability to use ratings in a wiki
> > > 2/ using it to provide ratings for the Extension Repository Application
> > > (XWIKI-7780)
> > > 3/ display ratings within Extension Manager (XWIKI-11509)
> > >
> > > The first point can be accomplished by using the ratings app as is but
> > the
> > > other two imply that the ratings app should be a module that is
> > maintained
> > > by XWiki. It makes sense that if the Extension Repository App and
> > Extension
> > > Manager which are maintained by XWiki depend on the Ratings App, that
> > this
> > > itself is maintained by XWiki as well.
> > >
> > > The steps needed for this is as follows:
> > > -
> > > 1/ create a new module in the xwiki-platform core for the ratings
> > > - xwiki-platform-core
> > > -- xwiki-platform-ratings
> > > --- xwiki-platform-ratings-api
> > > --- xwiki-platform-ratings-ui
> > > 2/ change the artifact id from "application-ratings" to
> > > "xwiki-platform-ratings"
> > > 3/ change the package from "org.xwiki.contrib.ratings" to
> > > "org.xwiki.platform.ratings"
> > >
> > > Implications
> > > -
> > > 1/ clone of the existing code is now in xwiki-platform under a
> different
> > > artifact id (having duplicate code, this takes us to #2)
> > > 2/ the code from xwiki-contrib would probably have to be deemed as
> > "retired"
> > > 3/ the applications with a dependency to the xwiki-contrib ratings
> would
> > > have to be upgraded to depend on the module from xwiki-platform
> > > 4/ the script service would remain unchanged (changing the artifact id
> > and
> > > package name does not affect the service)
> > > 5/ if by any chance someone has code that uses the classes from the
> > ratings
> > > app on contrib, by upgrading, that code will cease to function
> > >
> > > Please state you position on this matter.
> > >
> > > Links
> > > -
> > > http://extensions.xwiki.org/xwiki/bin/view/Extension/Ratings+API
> > >
> http://extensions.xwiki.org/xwiki/bin/view/Extension/Ratings+Application
> > > https://github.com/xwiki-contrib/application-ratings
> > >
> > > Thank you,
> > > Victor
> > > ___
> > > devs mailing list
> > > devs@xwiki.org
> > > http://lists.xwiki.org/mailman/listinfo/devs
> >
> > Either the the new module is a new version and it should keep
> > retro-compatibility to not instantly break all extensions using the
> > old app when you upgrade XWiki (but given the fact that we are not
> > going to keep org.xwiki.contrib.ratings package I doubt this is an
> > option) or we make sure the new module and the old module can run at
> > the same time in the same instance which means no conflicts (different
> > script service ids, different pages names when they are completely
> > different from old ones, etc).
> >
> > --
> > Thomas Mortagne
> >

Re: [xwiki-devs] [UX][Proposal] Recommended extensions on e.x.o

2016-06-27 Thread Ecaterina Moraru (Valica) 
On Mon, Jun 27, 2016 at 2:32 PM, Alexandru Cotiuga <
alexandru.coti...@xwiki.com> wrote:

> Good idea, I like it. However, we should be careful if we use both
> recommended property and the ratings display in order to not have a
> recommended application with a low average vote :)
>

Maybe making them more visible it would encourage the voting

Thanks,
Caty


>
> On Mon, Jun 27, 2016 at 1:50 PM, Guillaume Delhumeau <
> guillaume.delhum...@xwiki.com> wrote:
>
> > Looks very good.
> >
> > 2016-06-27 11:57 GMT+02:00 Ecaterina Moraru (Valica)  >:
> >
> > > Hi devs,
> > >
> > > This is a proposal on how we could improve the homepage of
> > > extensions.xwiki.org in order to make it easier for users to discover
> > > useful extensions.
> > >
> > > Homepage:
> > >
> > >
> >
> http://design.xwiki.org/xwiki/bin/download/Proposal/XWikiOrgExtensionsWiki/I2.png
> > >
> > > The main idea is to add a Recommended property to the Extensions class
> in
> > > order to select some extensions that we believe to be of high quality.
> > >
> > > Having this property will help us highlight this selection on the
> > homepage,
> > > by providing a custom livetable (users that will want to browse all
> > > extensions should use the 'Browse' action - that will take them to the
> > > current e.x.o livetable).
> > >
> > > Some notes about the recommended livetable, we should:
> > > - add a filterble Ratings column
> > > - improve the Author column (by providing filtering and a display)
> > > - simplify the date format
> > >
> > > I've tried to make the proposal as simple as possible to implement.
> > >
> > > Let me know what you think,
> > > Caty
> > > ___
> > > devs mailing list
> > > devs@xwiki.org
> > > http://lists.xwiki.org/mailman/listinfo/devs
> > >
> >
> >
> >
> > --
> > Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
> > Research & Development Engineer at XWiki SAS
> > Committer on the XWiki.org project
> > ___
> > devs mailing list
> > devs@xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/devs
> >
> ___
> devs mailing list
> devs@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
___
devs mailing list
devs@xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs

Re: [xwiki-devs] [UX][Proposal] Recommended extensions on e.x.o

2016-06-27 Thread Alexandru Cotiuga 
Good idea, I like it. However, we should be careful if we use both
recommended property and the ratings display in order to not have a
recommended application with a low average vote :)

On Mon, Jun 27, 2016 at 1:50 PM, Guillaume Delhumeau <
guillaume.delhum...@xwiki.com> wrote:

> Looks very good.
>
> 2016-06-27 11:57 GMT+02:00 Ecaterina Moraru (Valica) :
>
> > Hi devs,
> >
> > This is a proposal on how we could improve the homepage of
> > extensions.xwiki.org in order to make it easier for users to discover
> > useful extensions.
> >
> > Homepage:
> >
> >
> http://design.xwiki.org/xwiki/bin/download/Proposal/XWikiOrgExtensionsWiki/I2.png
> >
> > The main idea is to add a Recommended property to the Extensions class in
> > order to select some extensions that we believe to be of high quality.
> >
> > Having this property will help us highlight this selection on the
> homepage,
> > by providing a custom livetable (users that will want to browse all
> > extensions should use the 'Browse' action - that will take them to the
> > current e.x.o livetable).
> >
> > Some notes about the recommended livetable, we should:
> > - add a filterble Ratings column
> > - improve the Author column (by providing filtering and a display)
> > - simplify the date format
> >
> > I've tried to make the proposal as simple as possible to implement.
> >
> > Let me know what you think,
> > Caty
> > ___
> > devs mailing list
> > devs@xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/devs
> >
>
>
>
> --
> Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
> Research & Development Engineer at XWiki SAS
> Committer on the XWiki.org project
> ___
> devs mailing list
> devs@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
___
devs mailing list
devs@xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs

Re: [xwiki-devs] [UX][Proposal] Recommended extensions on e.x.o

2016-06-27 Thread Thomas Mortagne 
Looks good but one node: the authors column is not really supposed to
look like this. You get the user display name and a link when the
author is known so it would look even better ;)

On Mon, Jun 27, 2016 at 12:50 PM, Guillaume Delhumeau
 wrote:
> Looks very good.
>
> 2016-06-27 11:57 GMT+02:00 Ecaterina Moraru (Valica) :
>
>> Hi devs,
>>
>> This is a proposal on how we could improve the homepage of
>> extensions.xwiki.org in order to make it easier for users to discover
>> useful extensions.
>>
>> Homepage:
>>
>> http://design.xwiki.org/xwiki/bin/download/Proposal/XWikiOrgExtensionsWiki/I2.png
>>
>> The main idea is to add a Recommended property to the Extensions class in
>> order to select some extensions that we believe to be of high quality.
>>
>> Having this property will help us highlight this selection on the homepage,
>> by providing a custom livetable (users that will want to browse all
>> extensions should use the 'Browse' action - that will take them to the
>> current e.x.o livetable).
>>
>> Some notes about the recommended livetable, we should:
>> - add a filterble Ratings column
>> - improve the Author column (by providing filtering and a display)
>> - simplify the date format
>>
>> I've tried to make the proposal as simple as possible to implement.
>>
>> Let me know what you think,
>> Caty
>> ___
>> devs mailing list
>> devs@xwiki.org
>> http://lists.xwiki.org/mailman/listinfo/devs
>>
>
>
>
> --
> Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
> Research & Development Engineer at XWiki SAS
> Committer on the XWiki.org project
> ___
> devs mailing list
> devs@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs



-- 
Thomas Mortagne
___
devs mailing list
devs@xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs

Re: [xwiki-devs] [UX][Proposal] Recommended extensions on e.x.o

2016-06-27 Thread Guillaume Delhumeau 
Looks very good.

2016-06-27 11:57 GMT+02:00 Ecaterina Moraru (Valica) :

> Hi devs,
>
> This is a proposal on how we could improve the homepage of
> extensions.xwiki.org in order to make it easier for users to discover
> useful extensions.
>
> Homepage:
>
> http://design.xwiki.org/xwiki/bin/download/Proposal/XWikiOrgExtensionsWiki/I2.png
>
> The main idea is to add a Recommended property to the Extensions class in
> order to select some extensions that we believe to be of high quality.
>
> Having this property will help us highlight this selection on the homepage,
> by providing a custom livetable (users that will want to browse all
> extensions should use the 'Browse' action - that will take them to the
> current e.x.o livetable).
>
> Some notes about the recommended livetable, we should:
> - add a filterble Ratings column
> - improve the Author column (by providing filtering and a display)
> - simplify the date format
>
> I've tried to make the proposal as simple as possible to implement.
>
> Let me know what you think,
> Caty
> ___
> devs mailing list
> devs@xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>



-- 
Guillaume Delhumeau (guillaume.delhum...@xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
___
devs mailing list
devs@xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs

[xwiki-devs] [UX][Proposal] Recommended extensions on e.x.o

2016-06-27 Thread Ecaterina Moraru (Valica) 
Hi devs,

This is a proposal on how we could improve the homepage of
extensions.xwiki.org in order to make it easier for users to discover
useful extensions.

Homepage:
http://design.xwiki.org/xwiki/bin/download/Proposal/XWikiOrgExtensionsWiki/I2.png

The main idea is to add a Recommended property to the Extensions class in
order to select some extensions that we believe to be of high quality.

Having this property will help us highlight this selection on the homepage,
by providing a custom livetable (users that will want to browse all
extensions should use the 'Browse' action - that will take them to the
current e.x.o livetable).

Some notes about the recommended livetable, we should:
- add a filterble Ratings column
- improve the Author column (by providing filtering and a display)
- simplify the date format

I've tried to make the proposal as simple as possible to implement.

Let me know what you think,
Caty
___
devs mailing list
devs@xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs