Hello there.
Flamingo is a skin based on Bootstrap, and this framework offers a free but
reduced set of icons [1] coming from Glyphicons.com [2].
For this reason, when I started the implementation of Flamingo, I used the
free Glyphicons from Bootstrap.
A few months later, we introduced the Icon Theme Application [3], in order
to replace our Silk icons [4] by more accurate ones, depending on the
configuration of the wiki.
Unfortunately, the icons provided by Bootstrap were not a good candidate to
replace Silk, because a lot of icons were missing. Instead, we have decided
to use Font Awesome [5], which looks more like Glyphicons.
However, we haven't changed Flamingo to drop glyphicon, so we have an
inconsistency between what we propose to developers via the Icon Theme
Application, and what we have in the skin. It means a developer cannot,
using our best practices, re-use the same icons that the normal UI.
So the only option I see is to use the Icon Theme Application in Flamingo
too. We have an issue for this [6].
But it means:
- Flamingo won't look good if the Font Awesome Theme is not installed on
the wiki
- It's a matter of taste or habit, but I think Font Awesome does not look
as good than Glyphicons in the skin. See:
-- http://jira.xwiki.org/secure/attachment/33143/mockup.png
-- http://jira.xwiki.org/secure/attachment/33144/mockup-drawer.png
- Some Velocity macros [7] (that might be used by extensions) expect to
work with Glyphicons. By changing this we create a breaking change.
I am not satisfied with the first results. It may be improved, but keep in
mind that every changes that we made in the XWiki Icon Set affect all Icon
Themes (Font Awesome and Silk).
What do you think ?
Thanks,
Guillaume
[1] http://getbootstrap.com/components/#glyphicons
[2] http://glyphicons.com/
[3]
http://extensions.xwiki.org/xwiki/bin/view/Extension/Icon+Theme+Application
[4] http://www.famfamfam.com/lab/icons/silk/
[5] http://fontawesome.io/
[6] http://jira.xwiki.org/browse/XWIKI-12595
[7] For example
https://github.com/xwiki/xwiki-platform/blob/76ff57ec6a6fca48bc5f3f563f575b…
used by http://platform.xwiki.org/xwiki/bin/view/ExtensionPoint/Edit+Actions
--
Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
Hi devs,
I'm proposing to add this new property to the *XWikiPreferences* class
since there are many authenticators, listed on
http://platform.xwiki.org/xwiki/bin/view/Features/Authentication and most
of them require the overriding of the *xwiki.authentication.authclass*
property in the *WEB-INF/xwiki.cfg* file and the restart of the wiki. So
the *authclass* is meant to keep the value of the
*xwiki.authentication.authclass
*property*.*
Please keep in mind that *xwiki.cfg* was the historical file containing the
configuration options, we're moving away from it and this can be the moment
to improve this functionality by removing the *restart wiki* step which is
often a pain for the user.
Thanks,
Alex
Hi Guillaume,
Thanks for starting this thread.
----------------------------------------------------------
Current Drawer analysis:
Languages ( L / G )
---
Home ( G ) [N]
---
Administer wiki ( L ) [A] [W]
---
Wiki Index ( G ) [I] [W]
Page Index ( L ) [I]
User Index ( L / G ) [I]
Applications Index ( L) [I]
---
Create wiki ( G ) [A] [W]
---
Delete wiki ( L ) [A] [W]
L = Local/Wiki setting/action/effect
G = Global/Farm setting/action/effect
N = Navigation
A = Action
W = Wiki entity
----------------------------------------------------------
Some examples of grouping:
1. Local / Global effect grouping (ex. Main/Subwiki actions should be
grouped)
2. Entities grouping (Wiki related actions should be grouped: create,
administer, delete, etc.)
3. Index grouping (group all index applications together)
4. Navigation grouping (to Main wiki or other wikis)
5. Actions grouping
6. other?
So the main question is what grouping would we want to prioritize first:
1-5?
----------------------------------------------------------
Some things to consider:
A. Naming consistency:
A1. Across wiki: we need to consider the terms usage. For example Home vs.
Homepage; Wiki vs. Subwiki; Settings vs. Administration; Wiki Index vs.
Browse all wikis vs. Show all wikis
-- We need to align these usages and pick the one most relevant for the end
user and correct as terminology
A2. Across the menu: this implies having all entries plural/singular or
having the same additional text (ex. do we mark Indexes the same way?
Administer wiki / Delete this wiki / Create a new wiki, etc.)
B. Explicit (vs. Cryptic)
-- how explicit should we make the labels vs. icons usage
C. Quick access to local actions
-- in subwikis we should optimize for local actions and try to display them
first, since some teams might have dedicated wikis and the main wiki could
be used just as a portal or as a farm
D. Order most used actions first
-- for example 'Delete wiki' is not a very used action
E. Navigation vs. Actions grouping
E1. Actions removal
-- for example we could even remove 'Delete wiki' action and consider that
the wiki management actions can be accessed just from Wiki Index
-- this would mean that 'Administrate wiki' would be removed too, and we
use that action a lot in the initial configuration phases, so that would
increase the time to reach Administration
E2. Adding more wiki navigation
-- For example http://jira.xwiki.org/browse/XWIKI-12538 talks about having
a way to add quick access to other subwikis (ideally as favorites, since
listing all wikis does not scale)
----------------------------------------------------------
Proposals grouping feedback:
Current. -1 (Local/Global), -2 (Wiki grouping), +3 (Indexes), partial 4
(Navigation), -5 (Actions) || +A2 (Naming consistency), -C (Quick access)
P1. -1 (Local/Global), partial 2 (Wiki grouping), +3 (indexes), partial 4
(Navigation), partial 5 (Actions) || +A2 (Naming consistency), -C (Quick
access)
P2. partial 1 (Local/Global), -2 (Wiki grouping), partial 3 (Indexes), -4
(Navigation), -5 (Actions) || +A2 (Naming consistency), +C (Quick access)
P3. partial 1 (Local/Global), -2 (Wiki grouping), +3 (Indexes), -4
(Navigation), -5 (Actions) || +A2 (Naming consistency), +C (Quick access)
P4. -1 (Local/Global), partial 2 (Wiki grouping), +3 (Indexes), -4
(Navigation), +5 (Actions) || +A2 (Naming consistency), partial C (Quick
access)
----------------------------------------------------------
The problem is that when you approach an usability problem using these kind
of grouping / grading it's very easy to fall in the 'technicalities' trap
and not think about the user perspective.
So although I understand why I proposed P1-4, for users it will not make
sense. That's why I like P5, because the grouping comes natural and is more
explicit, although is not using the consistent terminology.
P5: +1 (Local/Global), -2 (Wiki grouping), -3 (Indexes), partial 4
(Navigation), -5 (Actions) || -A2 (Naming consistency), -A1 (Across wiki),
+B (Explicit), +C (Quick access to local), ? D (Most used actions)
Things to fix for P5:
- Think where to fit the "Languages"
- A1 + A2: we need to think about the naming of Indexes (especially Wiki
Index in this case) and fix them in drawer and across; replace Settings
with Administration; fix the "Go to ..."; consistent actions naming.
Additionally we should fix A1 (see http://jira.xwiki.org/browse/XWIKI-9363)
----------------------------------------------------------
Before starting this thread I tried to rethink about a new solution and I
came up with
P6: -1 (Local/Global), +2 (Wiki grouping), +3 (Indexes), +4 (Navigation),
+5 (Actions) || +A2 (Naming consistency), -A1 (Across wiki), -B
(Cryptic/Iconography), -C (Quick access), ? D (Most used actions), +E2
(More navigation)
i) Having Indexes listed before local actions (will give a -C for quick
access), but the advantage is that the menu composition will change less if
we visit main wiki vs. subwikis. P5 also have this propety.
ii) I've grouped and added more navigation by providing the list of wikis.
There are several problems with this approach:
ii.1 - not scalable for large number of wikis (even though I've put an
accordion there)
ii.2 - cryptic actions (icon usage for Create, Administration, Delete wiki)
ii.3 - mobile issues (because the icons are very small and we will need a
different layout for mobiles or we might have problems with large wiki
names)
----------------------------------------------------------
Thanks,
Caty
On Wed, Oct 26, 2016 at 11:42 AM, Miroslav Galajda <
miroslav.galajda(a)gmail.com> wrote:
> Hi, I vote for P5 proposal.
>
> Mirec
>
> On 26 October 2016 at 10:28, Guillaume Delhumeau <
> guillaume.delhumeau(a)xwiki.com> wrote:
>
> > No opinion?
> >
> > 2016-10-24 18:09 GMT+02:00 Guillaume Delhumeau <
> > guillaume.delhumeau(a)xwiki.com>:
> >
> > > Hello dear developers and XWiki users.
> > >
> > > I would you to take a look at the issue http://jira.xwiki.org/browse/
> > > XWIKI-13070.
> > >
> > > The problem is that the current order (that I have implemented based on
> > my
> > > intuition) seems to not be clear for our users. The main point is that
> > the
> > > menu mixes up global items (Home wiki, Wiki Index) and local ones
> > > (Administer Wiki, Page Index, Delete wiki, etc...).
> > >
> > > Caty and Oliver have made some proposals that you could find in the
> > issue.
> > >
> > > They are called P1, P2, P3, P4 and P5.
> > >
> > > I propose you to express your preferences so we can implement it based
> on
> > > a consensus.
> > >
> > > Here are mine:
> > >
> > > P1: There is a logical order and separation between item. However, it
> > > seems the more used actions (Wiki Index, Page Index) are less visible
> > than
> > > some other (Delete Wiki, Create Wiki...)
> > >
> > > P2: The order and the separation are logic. The "delete wiki" action is
> > > still very visible but all other items are good.
> > >
> > > P3: Same than P2. Except that having "Wiki Index" along with "User,
> Page
> > > and Application Index" mixes up local and global items.
> > >
> > > P4: Why not, but maybe the 3 first actions should be placed after the
> > > other ones, since they would be less used. Same remark about the mixing
> > of
> > > local and global items.
> > >
> > > P5: A clear distinction between local and global scope. More used items
> > > are located first. This is my favorite one.
> > >
> > >
> > > So +1 for P5, +0 for the other options so far.
> > >
> > > Now, what about you?
> > >
> > > Thanks,
> > > Guillaume
> > >
> > > PS: I send this message to both devs and users mailing lists, because I
> > > think users are directly concerned by this topic.
> > >
> > > --
> > > Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com)
> > > Research & Development Engineer at XWiki SAS
> > > Committer on the XWiki.org project
> > >
> >
> >
> >
> > --
> > Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com)
> > Research & Development Engineer at XWiki SAS
> > Committer on the XWiki.org project
> > _______________________________________________
> > users mailing list
> > users(a)xwiki.org
> > http://lists.xwiki.org/mailman/listinfo/users
> >
> _______________________________________________
> users mailing list
> users(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
>
Hello dear developers and XWiki users.
I would you to take a look at the issue
http://jira.xwiki.org/browse/XWIKI-13070.
The problem is that the current order (that I have implemented based on my
intuition) seems to not be clear for our users. The main point is that the
menu mixes up global items (Home wiki, Wiki Index) and local ones
(Administer Wiki, Page Index, Delete wiki, etc...).
Caty and Oliver have made some proposals that you could find in the issue.
They are called P1, P2, P3, P4 and P5.
I propose you to express your preferences so we can implement it based on a
consensus.
Here are mine:
P1: There is a logical order and separation between item. However, it seems
the more used actions (Wiki Index, Page Index) are less visible than some
other (Delete Wiki, Create Wiki...)
P2: The order and the separation are logic. The "delete wiki" action is
still very visible but all other items are good.
P3: Same than P2. Except that having "Wiki Index" along with "User, Page
and Application Index" mixes up local and global items.
P4: Why not, but maybe the 3 first actions should be placed after the other
ones, since they would be less used. Same remark about the mixing of local
and global items.
P5: A clear distinction between local and global scope. More used items are
located first. This is my favorite one.
So +1 for P5, +0 for the other options so far.
Now, what about you?
Thanks,
Guillaume
PS: I send this message to both devs and users mailing lists, because I
think users are directly concerned by this topic.
--
Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project
Hi devs,
I’m referring to those artifacts:
http://maven.xwiki.org/releases/org/xwiki/contrib/markdown/
Rationale: So that XWiki Rendering can be used with Markdown syntax without having to add the XWiki remote Maven repository.
Is it ok with everyone to push contrib artifacts to Maven Central (it's the first time we'd do this!)?
Right now we have only commons and rendering artifacts, see http://repo2.maven.org/maven2/org/xwiki/
I'm asking since we cannot undo this…
Thanks
-Vincent
PS: We have the same question for Mediawiki artifacts (except mediawiki-xml which depends on platform) now that they are in contrib too: http://maven.xwiki.org/releases/org/xwiki/contrib/mediawiki/
Hello devs,
I want to publish a macro to interact with salesforce.
It will be a few macros with groovy code and some samples to show how to
use them.
- a repository on xwiki-contrib called "macro-salesforce"
- no e.x.o page yet, as I will release the app once it's commited (it's not
fully ready as it still needs some cleanup)
- username: ldubost
Thanks,
Ludovic
--
*Ludovic Dubost*
*Founder and CEO*
ludovic(a)xwiki.com
skype: ldubost
Blog: http://blog.ludovic.org
<https://r.clb.pt/r/a381866da7040c7d0e2c752c06945349?d=http%3A%2F%2Fblog.lud…>
Hello devs,
I want to publish a macro to interact with elastic search and kibana4.
It will be a two macros with groovy code and some samples to show how to
use them.
- a repository on xwiki-contrib called "macro-elasticsearch"
- no e.x.o page yet, as I will release the app once it's commited (but it's
ready)
- username: ldubost
Thanks,
Ludovic
--
*Ludovic Dubost*
*Founder and CEO*
ludovic(a)xwiki.com
skype: ldubost
Blog: http://blog.ludovic.org
<https://r.clb.pt/r/9a7b6e136c9008b49ba6caeefdd7dc35?d=http%3A%2F%2Fblog.lud…>
FYI, there might be some stuff to improve/fix in CKEditor.
Thanks
-Vincent
> Begin forwarded message:
>
> From: Akiyoshi Yamakawa
> Subject: Re: [XWiki] Feedback form reply
> Date: 22 October 2016 at 16:48:10 GMT+2
> To: Vincent Massol <vincent(a)massol.net>
>
> Hi Vincent
>
> Thank you for taking time to reply me,
> and sorry for late response from me.
>
> Your advice is very helpfull and the following problems are solved:
> (1) url link target=_blank
> (2) Character foreground color and background color buttons in CkEditor
> (3) About PDF export , Japaese Characters(multi byte) output seems incorrect
> like another Wiki products like DekiWiki, etc.
> But copying/pasting to MS-Word or Libre Office Writer as html document and
> using it's PDF output is sufficient for me.
>
> It's going very well for me about Xwiki !!
> Thak you and your team all and Xwiki community!!
>
> Best Regards,
> Akiyoshi Yamakawa(Okinawa Japan)
>
>
> 2016-09-12 16:16 GMT+09:00 Vincent Massol <vincent(a)massol.net <mailto:vincent@massol.net>>:
> Hi Akiyoshi
>
> I’ve noticed your remark about XWiki in the feedback form:
>
> “
> On Xwiki8.2.1, link function of ckeditor doesn't work well. There is no setting in ckeditor link dialog about setting target="_blank". I feel it is better to use Xwiki7.4.x with ckeditor Extension & customize application-ckeditor-webjar-1.3.x.jar to full functional ckeditor. My main reason to use ckeditor is to avoid wiki tag setting like ||target="_blank" . Most of users want to use ckeditor Full function version, not want to use wikitag.
> "
>
> Answer:
> Please check http://extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration#H… <http://extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration#H…>
>
> Note:
> When you have some question about XWiki you could ask it on the forum/user mailing list, see http://dev.xwiki.org/xwiki/bin/view/Community/MailingLists <http://dev.xwiki.org/xwiki/bin/view/Community/MailingLists>. This is the place where all xwiki developers and users are and you’ll get the best support there! :)
>
> Thanks for your feedback, that helps us a lot!
> -Vincent
> XWiki committer
>
>