Hi devs,
One problem users are facing in the Administration is that the fields are
advanced and not well documented. One of the simplest ways to improve this
is to provide hints for all the entries (an example for the Profile
Preferences
http://design.xwiki.org/xwiki/bin/download/Improvements/UserRoles/customPre…
).
I've investigated the status of our default sections found in
Administration at
http://design.xwiki.org/xwiki/bin/view/Proposal/AdministrationHints
You can also see the Status column that displays the 'coverage' of hints.
I've also provided images of how it currently looks in the Section column.
Now, providing hints for Administration fields is not that easy since we
need to reach some agreements:
Q1: Labels and Hints come in pairs. When adding new keys do we:
- stick with the current naming for the Label and just add a '*.hint' key
for the Hint or
- should we deprecate the Label key and use for both the new translations
naming convention?
Q2: We should decide on a convention for Hint. We are currently using:
hint, tip, explanation, description. I prefer 'hint' since it's in our
Vertical Form standard, but Bootstrap for example is using 'help-block'.
Q3: Where do we put them? The majority of the keys are found in
ApplicationResources.properties. Should we extract them and create
Translations pages for them in the appropriate module?
Q4: Should we implement http://jira.xwiki.org/browse/XWIKI-7783 for the
cases where we extract the values from classes?
Q5: What about the content of the Hint message? Ideal it would be nice for
the owner of the module to help provide the Hint text since some fields are
advanced and even I don't know what they are doing. We could have a person
responsible for reviewing the final text in order to have the same 'tone'.
Q6: It's very nice to stop from time to time and refactor things, but do we
consider the effort of doing this to be of worth? This question applies for:
- refactoring on one side and
- adding hints on the other.
Thanks,
Caty
Hi Guys,
I'm trying to compile xwiki-enterprise in Netbeans by using bundled maven.
All modules compiled successfully except Web module.
I got the following problem. I went to the website, I did not find the
file 6.1-SNAPSHOT/xwiki-commons-crypto-store-6.1-SNAPSHOT.jar Did I make
any mistake or misunderstanding here?
Downloaded:
http://nexus.xwiki.org/nexus/content/groups/public-snapshots/org/xwiki/plat…
(612 B at 2.9 KB/sec)
Downloading:
http://nexus.xwiki.org/nexus/content/groups/public-snapshots/org/xwiki/comm…
Failed to execute goal on project xwiki-enterprise-web: Could not resolve
dependencies for project
org.xwiki.enterprise:xwiki-enterprise-web:war:6.1-SNAPSHOT: Could not find
artifact org.xwiki.commons:xwiki-commons-crypto-store:jar:6.1-SNAPSHOT in
xwiki-snapshots (
http://nexus.xwiki.org/nexus/content/groups/public-snapshots) -> [Help 1]
Hongxin
Dear XWiki experts,
I've been trying to undelete documents programmatically and I must say I failed thus far.
I need to do this so as to implement the undeletion of 450 documents.
Given the full name of the document, which currently shows when /view/-ed, that it has been deleted and offers me to restore or really delete, I am calling:
xwiki.getDeletedDocuments(fullName, "en");
however, thus far, the result of this call has been an array of size zero.
I would have expected to call the undelete method on the last of these DeletedDocuments.
Is this not the right way to act?
thanks in advance.
Paul
Hi devs/contributors/everyone,
This is an interesting article forwarded to me by Ludovic:
http://buytaert.net/a-method-for-giving-credit-to-organizations-that-contri…
I’ve been thinking a bit about it and the simplest solution I could think of (if we ever wanted to do something in this direction) would be:
* Add a new custom field in JIRA called “Sponsored By”. Since all our commits have associated JIRAs this should work fine to recognize everyone.
* Then we can easily query JIRA on a wiki page to provide visibility about companies and individuals sponsoring the development of XWiki.
* For example we could have a new page available in the Contribute menu of the top level horizontal menu called Sponsors which would:
- list all committers: link to the Hall of Fame page (http://dev.xwiki.org/xwiki/bin/view/Community/HallOfFame)
- list all Supporters: link to http://www.xwiki.org/xwiki/bin/view/Main/Supporters
- list all sponsors: query JIRA and list all sponsors including # of issues sponsored with ability to clean on each sponsor and go in JIRA itself to see the details
WDYT?
Would you be interested in this?
Thanks
-Vincent
Hi devs.
I am implementing the Color Theme Editor for Flamingo! And this is a
preview:
http://design.xwiki.org/xwiki/bin/download/Proposal/ColorThemeforFlamingo/f…
Since the current color theme application is strongly linked to Colibri,
and the new application will be strongly linked to Flamingo, I propose the
following:
1/ move xwiki-platform-colorthemes in xwiki-platform-colibri and state that
this application is only compatible with colibri-based skin.
2/ create the new application in xwiki-platform-flamingo
3/ the new color theme application will actually propose more than colors
(fonts, less code, etc...), so I propose to call it
xwiki-platform-flamingo-themes.
4/ in the administration, we have a page that propose which color theme we
want to use. Since the new application will not be compatible with the old
one, I propose to add an extension point (such as what we have to configure
search suggest sources) in order to propose the themes corresponding to the
selected skin (ie: xobjects of ColorThemes.ColorThemeClass for colibri and
skins based on colibri, and xobjects of FlamingoThemeCode.ThemeClass for
flamingo).
5/ modify SkinAction that currenlty executes velocity code on a skin file
if the mime type is CSS or JS, to also execute velocity on files suffixed
by .less.vm, because I need it for my application. To see what it looks
like, please look at
https://github.com/gdelhumeau/xwiki-platform/commit/49aca5733f4a820f3d1327c…
. The alternative is to create a new action which is too much IMO.
6/ when colibri will be deprecated on removed from XE, we will do the same
for the old color theme application.
WDYT?
Thanks,
Guillaume