On 07/06/2014 16:17, Daniel Beck wrote:
On 07.06.2014, at 13:14, domi <d...@fortysix.ch> wrote:
I'm sure plugins which do not look nice with the new style will be changed soon.
It'd be best if core provided CSS/JS equivalent images (it doesn't need to use
them itself) so plugins referencing these resources would automatically inherit
the new design as much as possible. They could then gradually adopt use of
CSS/JS instead of images when it makes sense.
Forcing all plugins that use affected core resources to choose between looking
outdated and requiring the latest and greatest as minimum compatible version
would be a bad idea.
Maybe we could do this:
1. Provide CSS based icons (I think we can eliminate the Javascript
completely).
2. Migrate core Jenkins to use the CSS based icons. We've already done
this on our branch.
3. Provide a plugin that can be added to perform the JS screen-scraping
hacks to transform non Jenkins core icon <img>s (e.g. from plugins)
to the new CSS style.
I think this would encourage plugin maintainers to migrate to the new
CSS resources (because their plugins will have the old style by
default), while at the same time provide an interm option for people to
have the new style throughout their Jenkins install.
wdyt?
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
