11 Jan
2011
11 Jan
'11
12:41 p.m.
Hello devs,
I would like we start to think about how we should implement space
pretty names in XE. Ideally, I would like to implement space pretty
names in the course of XWiki 3.0.
Here is an (open) list of options :
1. We use the space WebHome title.
Pros: It's easy to implement, we don't need new UI.
Cons: Can create a confusion between the space and it's home page,
since they have the same title.
2. We add a new field in XWikiPreferences and each space have their
titles in WebPreferences page.
Pros: The home page title can be different than the space title
Cons: It means the WebPreferences page becomes mandatory for spaces
with a pretty name
3. We add a new class, XWiki.SpaceClass, that holds metadata about the
space (pretty name, type of space, etc.). Each space have its
XWiki.SpaceClass object either in the WebHome or in WebPreferences
Pros : It's open to even more space metadata, like categories, or any
other metadata we want
Cons: It adds complexity. If it's stored in WebPreferences page, then same as 2.
Today I'm more inclined towards 1. In my opinion this is an elegant
solution that does not add complexity and that is not hard to
understand for users of XWiki.
Jerome.
11 Jan
11 Jan
5:38 p.m.
Hi Jerome,
Since were are using 1) since a while now on our customers wiki, I think my
feedback could be useful.
I completely agree with you that it is simple solution, and even if I will
expose some cons, this does not means I am against.
So, lets go with cons of 1):
- In the breadcrumb, using pretty names of both space and WebHome could
cause repetitions.
- while building a navigation panel, You may need a title for the space,
for example, to title an accordion, and a title for WebHome, for example to
put inside this accordion.
- you may want a space without a WebHome page, after all, there is no
express requirement for such a page, and many of our customers dislike the
URL of WebHome pages. So saying that a cons of 2) is the requirement for a
WebPreferences page, is also a cons of 1) in regards to WebHome.
To solve these 'issues' while using the title of WebHome for the title of a
space, we have used 2 'tricks' that I am not completely proud of, and that
are sometimes difficult to be understand by our customers:
- We use a translation of 'Home' for the title of a WebHome pages. We use
this in breadcrumbs and navigation panels in place of the real title.
- We hide from navigation panels WebHome pages that are not readable by the
current user, but we allow taking titles from these WebHome pages for titles
of spaces. So we have a somewhat 'hidden' WebHome. This is were thinks gets
tricky for editors, since they need to see these WebHome pages just for
editing space title.
This is my experience with 1). From it, I would be incline to think twice
before using WebHome titles for spaces. Hope this helps.
Denis
On Tue, Jan 11, 2011 at 12:41, Jerome Velociter <jerome(a)xwiki.com> wrote:
Hello devs,
I would like we start to think about how we should implement space
pretty names in XE. Ideally, I would like to implement space pretty
names in the course of XWiki 3.0.
Here is an (open) list of options :
1. We use the space WebHome title.
Pros: It's easy to implement, we don't need new UI.
Cons: Can create a confusion between the space and it's home page,
since they have the same title.
2. We add a new field in XWikiPreferences and each space have their
titles in WebPreferences page.
Pros: The home page title can be different than the space title
Cons: It means the WebPreferences page becomes mandatory for spaces
with a pretty name
3. We add a new class, XWiki.SpaceClass, that holds metadata about the
space (pretty name, type of space, etc.). Each space have its
XWiki.SpaceClass object either in the WebHome or in WebPreferences
Pros : It's open to even more space metadata, like categories, or any
other metadata we want
Cons: It adds complexity. If it's stored in WebPreferences page, then same
as 2.
Today I'm more inclined towards 1. In my opinion this is an elegant
solution that does not add complexity and that is not hard to
understand for users of XWiki.
Jerome.
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Denis Gervalle
SOFTEC sa - CEO
eGuilde sarl - CTO
5050
days inactive
5050
days old
1 comments
2 participants
participants (2)
-
Denis Gervalle -
Jerome Velociter