Skins

[Ryan Wilson]

I've started the process of converting Sandstone to replace Classic, but I
wanted to pose a question before I got too far into the process:

Since Dusk will remain as a built-in custom option, are we okay if Dusk
inherits some of the style design of Sandstone? If not, Dusk will become
much larger, as it will need to inherit most of the CSS from Classic.

On Sat, Jan 2, 2016 at 8:41 AM Ryan Wilson <theycallmefish at gmail.com> wrote:

> Since I've already been through a lot of the work on Sandstone, I'm
> willing to put in the time for the new standard skins.
>
> On Sat, Jan 2, 2016, 8:25 AM Gervase Markham <gerv at mozilla.org> wrote:
>
>> On 29/12/15 14:20, Frédéric Buclin wrote:
>> > move towards Dusk. So my proposal would be: replace Classic by
>> > Standstone, and make it the new default skin for Bugzilla 6.0 (if done
>> > on time for 6.0, of course). This way 1) skins/standard/ would really be
>> > the place for the default skin, which makes sense, and 2) we could still
>> > offer an alternative to users, aka Dusk (but we would need to see how
>> > the final Standstone implementation would look like to know what to
>> > change in Dusk), and 3) we don't need to support an extra 3rd skin.
>>
>> That sounds good... however, all custom skins, which will have been
>> "based on" Classic, will need to be rewritten to be based on Sandstone.
>> We'll need to warn people.
>>
>> Still, I can see the merit of this plan.
>>
>> Gerv
>>
>>
>> _______________________________________________
>> dev-apps-bugzilla mailing list
>> dev-apps-bugzilla at lists.mozilla.org
>> https://lists.mozilla.org/listinfo/dev-apps-bugzilla
>> -
>> To view or change your list settings, click here:
>> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=$MSGRCPT>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20160202/b7614de3/attachment.html>