Hmmm... I was hoping that the fact that their plugin would not display
the new styles by default would be enough of an encouragement.
Anyway... yes... maybe we could scan the plugin and open tickets on them.
On 08/06/2014 04:14, Michael Neale wrote:
Only risk is that it works so well that plugin maintainers don't feel
the need to change anything ;) I guess we can always crawl the repos
for plugins that use img and open a generic ticket for each (or
something like that).
On Sun, Jun 8, 2014 at 4:56 AM, Tom Fennelly <[email protected]
<mailto:[email protected]>> wrote:
On 07/06/2014 16:17, Daniel Beck wrote:
On 07.06.2014, at 13:14, domi<[email protected]> <mailto:[email protected]>
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 a topic in
the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-dev/zDaX4yiWLLw/unsubscribe.
To unsubscribe from this group and all its topics, send an email
to [email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
Michael D Neale
home: www.michaelneale.net <http://www.michaelneale.net>
blog: michaelneale.blogspot.com <http://michaelneale.blogspot.com>
--
You received this message because you are subscribed to a topic in the
Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-dev/zDaX4yiWLLw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
[email protected]
<mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
