After talking with Tom a bit yesterday, he suggested that it makes sense for us to divide up the look refresh effort into neat and compact sub-tasks that will make for if not atoms, molecules, that the community can easily choose to embrace independently of other elements of the UI effort.
I think our initial list of project tasks looks something like this: *1) Replacing table based layout structure* with Bootstrap's responsive columns (Tom and Kevin seem like they have pretty much rocked this one already) *2) Adopt LESS* as a means of segregating and targeting style enhancements to manageable sub-sections of the GUI *3)* *Adopt a new base-font* and typography scheme to make the GUI more device friendly and modern looking *4)* *Adopt a new icon library*, likely based on a glyph-font library like Font-Awesome to enhance performance and device friendliness *5) Apply Bootstrap or Bootstrap-like DOM* and class naming conventions to UI widgets like panels, tabs, tables and form elements to modernize the look and make future skinning easier to drive via CSS *6)* *Give main tables dynamic client-side controls* to enable more responsive data view manipulation *7)* *Examine menu* construction mechanisms for ways to highlight common tasks and shorten click-counts *8) Look for additional ways to improve, *perhaps by moving e more controls into the client to further enhance responsiveness and a modern feel to the GUI Although I have put these in the rough order that I think it will make sense for use to pursue each initiative, my hope/belief is that a lot of them could be done in parallel and most could be done not-at-all with minimal ramifications to the other sub-projects in the effort. Please feel free to smack me and correct me if my list seems not right, or if it is already better articulated somewhere else. ...or if you have other stuff you would like to add or change. On Thu, Jun 19, 2014 at 1:58 PM, Daniel Beck <[email protected]> wrote: > > On 19.06.2014, at 21:23, Ulli Hafner <[email protected]> wrote: > > > Maybe there should be an option to disable the people view at all (or > move it from core into a plugin). > > Already filed at https://trello.com/c/oJnGvleL > > -- > 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]. > 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.
