9 Nov
2012
9 Nov
'12
11:07 a.m.
On 11/09/2012 10:46 AM, Ecaterina Moraru (Valica) wrote:
On Thu, Nov 8, 2012 at 10:00 PM, Jerome Velociter
<jerome(a)velociter.fr>wrote;wrote:
I see a couple of immediate benefits in adopting LESS over keeping the
functionnality in velocity :
- we can benefit from the upstream customization of bootstrap (I'm
talking about this :
https://github.com/twitter/bootstrap/blob/master/less/variables.less)
- it's more "standard" and than our velocity macros/variables
- there's no way to implement "generic mixins" in velocity (in a way
that's not awkward to declare)
But indeed, in the end that's an implementation decision, I'm just
dropping the idea here.
Jerome
Caty, This is great. I'm very looking forward
this. Some remarks : -
The skin will break the system of panels (in particular the panel
wizard), since there is no left panel anymore. For me this is not a
problem, we just have to agree on that. - I think it would be a good
time to think about the introduction of a pre-processor like LESS to
ease the customization/derivation of such a skin. (BTW bootstrap
itself uses LESS for that purpose). - This will be also be a good
time to re-work and generally harmonize the markup of some UI
components. Any timeline for the implementation ?
The implementation could be decided for the 5.x timeline, but we need
to find a main developer to be in charge of this and really evaluate
the amount of work needed. There are several implementation decision
that needs to be voted if we decide to go with this skin, like you
said panels, menus, administration layout, rewriting some
application's layout, etc. Regarding LESS, Bootstrap works with LESS
(both server and client side) and there is also another project that
replaces LESS with Sass to work with Bootstrap. This is another
implementation decision, since we could adopt LESS or even Bootstrap
or just make a separation of skins, by having a really
"base"/"core"/"api" skin (that in general should contain
just the
basis, like typography, grids, reset, forms, etc. and that we would
need to write) and another skin on top of it (that should define the
layout, skin colors and additional styling) that could be more easily
changed. We could use LESS or just expand our velocity macros (to have
more 'mixins' like functionality) and more
"ColorThemes"/"Skin" variables.
Thanks, Caty
Definitely +1 Thanks, Jerome On 11/08/2012 05:59
PM, Ecaterina Moraru
(Valica) wrote:
_______________________________________________ devs mailing list
devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
Hi devs, I've been working in the 4.3 Roadmap
for a new skin
proposal. You can see it at
http://incubator.myxwiki.org/**xwiki/bin/view/Improvements/**Skin4x<http…
I recommend looking at the "Annotations Overview" gallery in order
to see the different elements of the skin and some explanations.
I've made also separate pages for different components of the skin.
For example, you can see more information about how the menus work
at
http://incubator.myxwiki.org/**xwiki/bin/view/Improvements/**Skin4xMenus<…
For each component you can also see how the elements scale and see
the responsive layout. For the record, the proposal is made by using
Bootstrap (
http://twitter.github.com/**bootstrap/<http://twitter.github.com/bootstr…
). Thanks, Caty ______________________________**_________________
devs mailing list devs(a)xwiki.org
http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/ma…
______________________________**_________________ devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/ma…