My only concern would be to test this with bigger installations as well. When having 1000 jobs in one instance innocent looking 200 bytes of information per job may make a big difference :-D.
Regards Mirko -- Sent from my phone http://illegalstateexception.blogspot.com http://github.com/mfriedenhagen/ https://bitbucket.org/mfriedenhagen/ On Feb 24, 2012 7:40 PM, "domi" <[email protected]> wrote: > I also think that having this option on every model object would be a > really good idea. > e.g. this could be useful in the executor list too > /Domi > > > On 24.02.2012, at 00:26, Kohsuke Kawaguchi wrote: > > > Hmm, that's interesting. It is relatively easy to build this on top of > > what we have. > > > > Definitely worth experimenting. Any thoughts on this from others? > > > > 2012/2/24 Dean Yu <[email protected]>: > >> It would be great if the menu could be activated from any link to a > model > >> object, not just from the breadcrumb bar. For example, there have been > many > >> times I wished I could quickly jump to the configuration or console of > a job > >> from the upstream/downstream jobs section of a page. We could get rid > of a > >> lot of custom dashboard view columns if the menu could be activated > from the > >> links in the views. > >> > >> This would mean refactoring all model object links in Jelly files to > use a > >> modellink.jelly template, but it would be a consistent experience. > >> > >> -- Dean > >> > >> > >> On 2/20/12 7:15 PM , "Kohsuke Kawaguchi" <[email protected]> > wrote: > >> > >>> As per the discussion in [1], I implemented the enhanced breadcrumb. > >>> The code is currently in a branch [2]. The screenshot is attached. > >>> > >>> Breadcrumb is now sticky --- when you scroll down, it sticks to the > >>> top of the page and never goes out of the viewport. Hovering the mouse > >>> over it will show the menu, and when you move your mouse out of the > >>> menu, it'll disappear automatically. The breadcrumb itself is still > >>> clickable as it has been. > >>> > >>> As you see in the screenshot, the breadcrumb now occupies more space > >>> (or easiler access to the context menu), and it's bordered. > >>> > >>> I'm not a UX guy, and I'm not too crazy about borders here (it appears > >>> somewhat out of style with the rest of Jenkins UI, although foldable > >>> sidepanel might change that.) With that said, I ended up adding it to > >>> create a boundary for sticky breadcrumb. > >>> > >>> Internally, it ses sidepanel.groovy/jelly to generate the menu > >>> contents by default, which lets us instantly activate this feature for > >>> all those objects that people have been writing. But model classes can > >>> override this behavior and completely take over the menu generation if > >>> so choose. > >>> > >>> Future enhancements include submenus. > >>> > >>> Does this sound like what we want? Feedbacks from graphics/UX guys > >>> (and I'm looking at Manfred!) would be especially appreciated. > >>> > >>> [1] > >>> > https://wiki.jenkins-ci.org/display/JENKINS/FOSDEM+UI+Enhancement+discussion+n > >>> otes > >>> [2] https://github.com/jenkinsci/jenkins/tree/breadcrumb > >> > > > > > > > > -- > > Kohsuke Kawaguchi > >
