On Monday, June 2, 2014 11:50:03 AM UTC+1, Tom Fennelly wrote:
>
>
> As suggested by others, I think it would be a good idea to bite off
> smaller chunks where we can so as to make progress. So, maybe we could
> start by adding Doony and then look at making some of the above
> improvements, right?
>
I created a branch and merged Doony. It's more-or-less "as is" at the
moment.
Next steps (also see Kevin's notes below):
1. The ProgressCircle does not seem to be working atm... need to fix
that.
2. Go through doony.css looking for potentially ambiguous CSS. Where
relevant, see if we can add class/id metadata to jelly scripts so as to fix
potential css issues.
3. As with #1, go through doony.js looking for
potentially ambiguous/troublesome jQuery selectors etc etc
4. Related to #2, review doony.js and see what needs to be improved.
It's doing some funky things atm that maybe could be done in a better way
e.g.
- How it's replacing the bouncy/floaty balls.
- How it's getting the next build number after the "Build Now" button
is pressed.
- How it's deciding if it's on the "job" related page or not based on
the active url in the browser.
5. Remove dependency on jQuery (??).
6. Normalize CSS i.e. merge doony.css into jenkins core style.css,
removing existing style.css rules where we can.
7.
Kevin (Burke) and I had a quick chat on Skype yesterday afternoon. Here
are Kevin's detailed notes and thoughts
<https://gist.github.com/kevinburke/9d4f127a7005eaa9d970> on what changes
are in Doony and how we can use/evolve that work. Very useful info...
thanks Kevin !!!
--
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.
