4 Jun
2014
4 Jun
'14
10:37 a.m.
On Wed, Jun 4, 2014 at 9:44 AM, vincent(a)massol.net <vincent(a)massol.net>
wrote:
Hi Denis,
On 4 Jun 2014 at 09:27:49, Denis Gervalle (dgl(a)softec.lu(mailto:
dgl(a)softec.lu)) wrote:
I do not agree, the panel position is admin choice independently of the
skin. The skin manage the look, and the panel is about exposing
functionalities. This seems to me unrelated even if the panels include a
bit of layout.
On Mon, Jun 2, 2014 at 8:49 AM,
vincent(a)massol.net
wrote:
>
>
>
>
> On 29 May 2014 at 11:23:01, Marius Dumitru Florea (
> mariusdumitru.florea@xwiki.com(mailto:mariusdumitru.florea@xwiki.com))
> wrote:
>
> > On Wed, May 28, 2014 at 4:18 PM, Guillaume "Louis-Marie" Delhumeau
> > wrote:
> > > Hi,
>
we
>
> > > In Flamingo, we
have created the concept of Application Bar, that > have
> > > implemented as a Panel:
> > > http://jira.xwiki.org/browse/XWIKI-10254
>
the
>
> > > I propose to put
the Application Bar by default on the left column.
> >
> > > Since we do not
have a configuration system at the skin level, it
> would be
> > > present for both Colibri & Flamingo. I think it is not a problem
> because I
> > > have managed to make it look good for both (except for the size of > > > icons) :
> > > http://jira.xwiki.org/secure/attachment/27707/appbar.png
>
(see
>
>
> > > WDYT?
>
> > It doesn't look very
well, and the Applications panel is redundant. I
> > don't have a solution though. Need to think about it.
>
> Note that Guillaume forgot to mention that the icons will be larger >
http://design.xwiki.org/xwiki/bin/download/Improvements/Skin4x/homepageDesk…
).
> > Right now they are the ones from the panel in medium width mode because
> > Guillaume has implemented it yet.
>
> > @Guillaume: regarding icon
colors, what would be your plan? Blue and
white
> > colors as on
>
http://design.xwiki.org/xwiki/bin/download/Improvements/Skin4x/homepageDesk…
> > even for the Colibri skin or different coloring depending on the skin?
>
> > I also think that it might
be best to not change Colibri since people
are
> > probably used to it for now. Now we need to find a way to have panels
> > defined differently for each skin for that.
>
>
> I do not really agree. Panels is (at least intended to be) a standalone
> application, that is not directly related to skins. Panels themselves are
> also independent. Linking panel app, panels and skin would not increase
the
modularity of our solution. I do not really
understand why adding that
AppBar panel change anything. If the user want an AppBar, she could
configure it easily in the panel configuration. And regarding the default
distribution, I do not see why in the 6.x release, we couldn't change the
default panel layout. This will have no impact on existing users that are
migrating. I do not see any reason not to have the AppBar in colibri by
default in the new distribution.
[snip]
Some thoughts:
1) Panels are indeed independent of the skin but the position of the
Panels are not, they depend on the skin, especially the default position.
The proof of this is this discussion and the fact that Flamingo requires a
different default Panel layout than Colibri…
2) Changing the default set of panels and their position in 6.x to be good
for Flamingo means that you consider that we cannot have more than 1 skin
at a time. I believe we should go in the direction of being able to have
more than 1 skin at a time.
Again, I dislike the idea to closely link panels choice and layout with
skins. Panels should individually adapt themselves to the current skin, but
changing skin should not change panels. This would be like changing the
look also change the functionalities. For example, a user may impose its
own skin, but this should not disrupt the specific functionalities expose
by the wiki through panels.
3) It could also be nice if a user could install a
skin from
extensions.xwiki.org (like the leothrix one) and upon installing it he
would be able to choose to have the default Panel layout for this skin or
keep his customization.
Basically this is all about having a nice user
experience.
For sure, and IMO for a nice user experience, panel should stay independent
of the skin. Skin should be mainly a matter of look and feel, and no more.
That said, we may imagine a feature of the skin installer that propose to
set default panels for that skin. But it seems to me overkill, since
setting panels is (should be) really easy (with the panel wizard).
Now I agree that this topic is a bit complex but I
still believe we should
brainstorm it to decide where we want to go in the future even if for now
it’s too complex and we decide to support only 1 skin at a time for that
reason (which is a valid reason).
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Denis Gervalle
SOFTEC sa - CEO