Hi Gus; The screenshots are from standard job build forms using Uno-Choice parameters. Especially the Uno-Choice Dynamic Reference parameter can directly render any arbitrary HTML. In one case (the screenshot with the chemical structure) it's a simple iframe displaying a widget from NCBI, in the other it's a locally rendered D3 interactive plot. The D3 graph configuration can be found here: http://162.243.246.75:8080/job/TEST_D3_SCATTERPLOT/configure
The most recent version of the plugin can be found here: https://groups.google.com/forum/#!topic/biouno-developers/REx4-sk_xSs As we speak, we are in the process of releasing it to the Jenkins community. Best regards Ioannis On Wednesday, February 18, 2015 at 3:31:35 PM UTC-5, Gus Reiber wrote: > > Awesome. > Thanks Ioannis. > > You are absolutely correct that we are stuck a bit in last decades web > technologies as far as client-side user presentation is concerned. > > Can I ask you or maybe Bruno, how are those graphs embedded into this page? > ...and what page is this I am looking at (I am assuming it is a custom > plugin action page or a specialized view for a custom item type)? > > Looks like I need to go grab the plugin kick the tires directly. > > On Wed, Feb 18, 2015 at 12:19 PM, Ioannis Moutsatsos <[email protected] > <javascript:>> wrote: > >> Gus thanks for opening this discussion on these ideas. >> >> I am a Jenkins user and developer with a somewhat unusual pedigree. My >> main interest is using Jenkins as a workflow and integration engine for >> research applications in life-sciences and bioinformatics. >> Jenkins proved to be more than capable in this 'off the beaten path' >> application, but the user interface as it exists in the vanilla job build >> forms almost killed any prospect of advanced users since most web >> application users are used to richer controls and enhanced interactivity >> with their web application forms. >> >> Enter the Uno-Choice plugin >> <https://wiki.jenkins-ci.org/display/JENKINS/Uno+Choice+Plugin> as >> discussed earlier >> <https://groups.google.com/forum/#!topic/jenkinsci-dev/qUBLhE-4ybY>in >> this thread by Bruno @kinow of the BioUno.org project. >> Working with him we were able to significantly enhance the type and >> interactivity of some crucial UI controls so that we can now start building >> *advanced >> web analytic applications on Jenkins*. >> >> I envision >> <https://groups.google.com/forum/#!topic/biouno-developers/uQSANvdkVG4>Jenkins >> >> job forms and reports with rich UI and we have just started scratching the >> surface (see some attached screenshots). I'm currently exploring how D3 >> graphical elements as well as Shiny R applications can be integrated and >> used from within Jenkins. >> Please, keep an open mind toward integrating and learning from such rich >> graphical UI tools as you embark on additional Jenkins UI enhancements. >> >> Thank you and all the great people at CloudBees for continuing to support >> and enhance Jenkins for all! >> >> Best regards >> Ioannis >> >> >> On Wednesday, February 18, 2015 at 11:27:12 AM UTC-5, Gus Reiber wrote: >>> >>> At the end of last summer, my friend and co-worker, Tom Fennelly >>> <https://github.com/tfennelly>, along with the help of Kevin Burke >>> <https://github.com/kevinburke>, Daniel Beck >>> <https://github.com/daniel-beck>, and others began the first steps of >>> improving and modernizing the Jenkins user experience. In addition to some >>> of the superficial enhancements, these changes are meant to add a bit of >>> responsiveness and cross-device usability to the Jenkins GUI, as well as >>> adding a means of creating and swapping new CSS based display themes. This >>> effort is best summarized by this article from Jenkins-ci.org, and this >>> thread from the Jenkinsci-users group: >>> >>> - *User Interface Refresh >>> <http://jenkins-ci.org/node/501#disqus_thread>:* http://jenkins-ci. >>> org/node/501#disqus_thread >>> - *Any comments on the UI changes in 1.572 >>> >>> <https://groups.google.com/forum/#!searchin/jenkinsci-users/ui$20tom/jenkinsci-users/ULEV87g9iac/LaTt5J2tHV8J>:* >>> https://groups.google.com/forum/#!searchin/jenkinsci-users/ui$20tom/ >>> jenkinsci-users/ULEV87g9iac/LaTt5J2tHV8J >>> >>> <https://groups.google.com/forum/#!searchin/jenkinsci-users/ui$20tom/jenkinsci-users/ULEV87g9iac/LaTt5J2tHV8J> >>> >>> As part of our second wave effort here at CloudBees, I am looking at >>> ways of improving the usability of the Jelly based form controls used in >>> the item creation and configuration pages and the responsiveness and >>> interactivity of the main dashboard grid control. >>> >>> In my investigations so far, I believe there are essentially 3 >>> non-exclusive paths forward for enhancing these elements: >>> >>> 1. *CSS only --* Building on the last round of enhancements, we can >>> offer a set of theme extensions that will allow the Jenkins users and >>> community to customize basic layout, iconography, and typeface to tailor >>> Jenkins to their own tastes. >>> 2. *UI component expansion and refactoring --* By modifying and >>> adding to the existing set of Jelly files and their corresponding data >>> binding rules we can significantly modernize the way Jenkins views and >>> configs draw themselves and potentially streamline plugin creation. >>> 3. *Client side MVC veneers --* In a manner similar to what >>> CloudBees has recently done with the new Workflow visualization, we can >>> rethink our approach to new feature UIs by using a REST API based >>> architecture coupled with client-side rendering widgets. This would >>> allow >>> us to use newer framework libraries like Angular.js and newer component >>> libraries like Bootstrap and JQuery UI to add greater richness to the >>> Jenkins user experience. >>> >>> These are likely not the only paths forward, but merely the first I can >>> think of. With that reality in mind, I am hoping to reach out to you the >>> Jenkins community to help ground and sculpt our thinking about what is both >>> possible and desirable. >>> >>> If you are at all interested in the Jenkins user experience, I would >>> love to get your feedback of any sort on this thread, which could be as >>> simple as a "+1" or as involved as a PHD thesis or as much as you have time >>> to type into a response box. >>> >>> To the extent that it helps conversation along, I also have a handful of >>> questions to which I would love responses: >>> >>> 1. For plugin builders, can you tell me a bit about creating the UI >>> portion of your plugin (did you use the data binding form controls, what >>> was hard, what did you have to invent)? >>> 2. For regular Jenkins users, what are the UX areas of Jenkins you >>> would most like to see improved (I think it is the item create/config >>> and >>> the dashboard/job list grid, but would love to hear others and general >>> feedback)? >>> 3. For UXers and other Jenkins contributors, how do my 3 forward >>> paths seem (are there others, do you have experience with any yourself, >>> do >>> any seem scary)? >>> 4. Has anyone tried to make their own themes with the new >>> capabilities Tom has added or would you appreciate and handful of canned >>> options to choose between? >>> 5. Has anyone started using Workflow on a regular basis, and in >>> particular used the new workflow progress visualization enough to offer >>> feedback? >>> >>> >>> Again, if any of you all are at all interested in the Jenkins UX, we at >>> CloudBees are interested in helping move this ball forward and would love >>> to hear your feedback. >>> >>> Thanks for your help, >>> Gus >>> >> -- >> 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/6BdWZt35dTQ/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/73bbb30e-862a-4c95-9c3f-6290a763bd82%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/73bbb30e-862a-4c95-9c3f-6290a763bd82%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> 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/a2abb0fe-5839-460c-ac11-780daaa2a244%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
