26 Mar
2007
26 Mar
'07
9:32 a.m.
On 3/26/07, Vincent Massol <vincent(a)massol.net> wrote:
Hi Sergiu and everyone,
Regarding 3 we have already voted to move skins in a skin directory in
svn. I'd be +1 to not distribute the dodo skin anymore with the xwiki
distribution but as a download on the Code Zone (we'll only distribute the
albatross skin). The finch skin would also be released on the code zone
only.
Re the deprecation, I think we should simply state on the Code Zone (on
the page for the skin) that we recommend to use the albatross skin and that
this dodo skin is the old skin and is deprecated, etc.
We could also send an email to those that own a wiki on the farm telling
them that we changed the skin and the core platform, and they should upgrade
to the new skin to be able to use the new features. But this after the
1.0final deployment on the farm.
Only issue in all this is that we need to make a XAR for the skin, as part
of the build part, as I proposed some time ago. We
said we had to check if
the skin loading mechanism was still working for that.
For now, I think we should keep the 3 skins as part of the 1.0 release as
we don't have much time to work on all this and we have lots of bugs to fix.
We can already recommend to use the albatross skin on the skins page on
xwiki.org.
Agree, the 1.0 should not be changed anymore. We can remove the skin from
the trunk only.
WDYT?
Thanks
-Vincent
On Mar 26, 2007, at 12:04 AM, Sergiu Dumitriu wrote:
Hi,
It is getting harder to maintain 3 different skins. We should decide now
whether (or for how long) we keep upgrading the 'dodo' skin. I know it is
still widely used on the farm, so completely removing it is not a valid
option.
Here are some possibilities regarding the 'dodo' skin:
1. Keep things as they are now, with casual upgrades in the skin, and all
the resources available.
2. Declare it as deprecated, we no longer provide improvements to the
skin, just fixes when changes in the core cause malfunctions in the skin. We
keep the resources in the main AppRes.properties. It will still be part of
the trunk and the official builds.
3. Declare it as deprecated as above, but move it out of the trunk, in a
'skins' svn directory, along with the associated resources (afterwards we
clean up all the resource files). It will still be deployed on the farm, but
we encourage all the users to upgrade to the new skin.
I think that on the long run, number 3 is the better option, especially if
we expect major changes in the way skins work (UI extensions, wizards,
improved resources).
--
http://purl.org/net/sergiu