Thanks for all the hard work Gus.
I can try building a Jenkins version with your pull requests, or if you have
.war, I can try it with the active-choices-plugin, which relies on the DOM
structure created in the build with parameters screen. CSS changes won't break
the plug-in, but moving tables, divs, inputs, might break it.
CheersBruno
From: Gus Reiber <[email protected]>
To: Jenkins Developers <[email protected]>
Cc: [email protected]
Sent: Thursday, July 23, 2015 10:31 AM
Subject: Re: Jenkins UX
Awesome, awesome, awesome feedback all around.
So if I can summarize the feedback so far, it sounds to me like Kanstantsin is
the most skeptical, but few if any of you are 100% sold, which is how it should
be. Possible sources of discontent seem to break down like this:
- Don't forget about Tom's work and the existing SimpleTheme plugin
- Color, font, and border choices: Seems like maybe we like the simple black
and white better, with less borders, less margins and smaller text (though that
is not a consensus)
- Collapse mechanism: The idea of clear segmentation seems to be generally
embraced (Kanstantsin being the exception), but the sort of pegged ToC tracking
that Bootstrap uses might be prefered.
- Console log should be better, too (I totally agree with that, but didn't
choose that piece of the GUI as a starting point so am punting on thinking
about that for the moment)
Most of my goal here is to show the sorts of tangible benefits that an overhaul
of a GUI can bring that go beyond what can be done against the current Jenkins
DOM with CSS alone. KK, Daniel, Tom and I agree that is the case enough to
start organizing ourselves into both code and outreach to start making that
case through forums and demos like this, and pull requests which we are
starting to create.
As I see it, we will want to break down pull requests along this topic into
manageable bites, the first of which being largely infrastructure and only
minimal visual changes, if at all. It is my belief that the first step of doing
any modernizing of the config page is to pull it out of tables and refactor
hudson-behavior to function with a semantic and logically nested DOM structure,
such that new styles of input elements can be folded into both core config
items and plugin configuration without a lot of the crazy DOM wackery that
happens today. Also, I think PrototypeJS and YUI are essentially dead
technologies, so we will need to cast off those shackles.
...thus our first PR is likely to be all about enabling DOM changes to the
jelly resources files in the form directory (even prior to the actual DOM
changes).
Anyway, in the next few days, KK and Daniel will be looking to set up a hangout
in which at least some of us might be able to get together and examine the ins
and outs of this technical web.
...expect a seperate note from them with more specifics, shortly.
On Thursday, July 16, 2015 at 9:03:49 AM UTC-7, Gus Reiber wrote:
As threatened, but at long last, I have a demo video and associated blog
post.... not really posted to a blog, but, still something that can be read and
comment on....
Please take a look, and send feedback:video:http://youtu.be/1Qn4jEwAeGc
post:https://docs.google.com/document/d/1sjd_Yl7wzyxVoaFurSGAVfgWNSwlnSLJztx7uexdgxE/edit?usp=sharing
On Monday, June 22, 2015 at 4:37:17 AM UTC-7, Gus Reiber wrote:
Hey all,
Been a long time since my last post, as I had been cramming getting a
prototype built for JUCs DC and London. I am happy to report Tom and my
presentation was well received in DC. Now we are off to the UK.
Now that we have a simifunctional prototype, we will be working to figure out
how to best post it so community members can provide feedback.
Thanks again for your interest. Please stay tuned.
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/a77c5054-7888-415c-9ae5-be73aa9e9af3%40googlegroups.com.
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/1535303428.364268.1437604671217.JavaMail.yahoo%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.
