[JIRA] (JENKINS-17418) Enhancement to all Groovy Editing Interfaces to allow easy use of External Groovy Editors
Title: Message Title JT Moree commented on JENKINS-17418 Re: Enhancement to all Groovy Editing Interfaces to allow easy use of External Groovy Editors +1 on improving the groovy editor experience. It is extremely painful to use since the bootstrap based layout of the application wont let me widen the editor. I can make it taller but not wider. I can use the DOM editor to remove (class="col-md-offset-2 col-md-20") but it is not a permanent fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.148252.136467088.1244.1564084920259%40Atlassian.JIRA.
[JIRA] (JENKINS-17418) Enhancement to all Groovy Editing Interfaces to allow easy use of External Groovy Editors
Title: Message Title Lucie Votypkova assigned an issue to vjuranek Jenkins / JENKINS-17418 Enhancement to all Groovy Editing Interfaces to allow easy use of External Groovy Editors Change By: Lucie Votypkova Assignee: Lucie Votypkova vjuranek Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.148252.136467088.20407.1563973920306%40Atlassian.JIRA.
[JIRA] (JENKINS-17418) Enhancement to all Groovy Editing Interfaces to allow easy use of External Groovy Editors
Frank Merrow created JENKINS-17418 Enhancement to all Groovy Editing Interfaces to allow easy use of External Groovy Editors Issue Type: Improvement Affects Versions: current Assignee: vjuranek Components: groovy, groovy-postbuild, scriptler Created: 30/Mar/13 7:14 PM Description: In all cases the Jenkins Groovy editors are limited. No, I am not asking for more features for the editor itself, but it occurs to me that a fairly simple enhancement to all of these interfaces could make it very easy to hop in/out of your favorite Groovy Editor; Mine is Netbeans. Like most editors, Netbeans monitors the disk to notice if the file has been changed outside the editor. So if Script Console for instance would after 5 seconds of no typing, save the file to %JENKINS_HOME%/GroovyScript/ScriptConsole.groovy (or whatever) ... I could then stop typing and almost immediately have the current script in Netbeans (assuming Netbeans currently had that file open). Similarly then, once I finish all my auto-tab, intellisensed changes in Netbeans, I hit "save" and the Groovy Console could then pull back in my changes and I could run them. I could easily jump back and forth without all the usual copy/paste nonsense. Script Console could even offer the previous script back on the start of a new session. Groovy Postbuild has the additional issue that Postbuild is on a job by job basis, so it save area might be %JENKINS_HOME%/GroovyScript/%ITEM_ROOTDIR.groovy. (The name isn't important, but you get the idea). Scriptler in a sense already has the files saved, but in an XML file with lots of other metadata that gets in the way. It might save a "clean" version of the groovy in %JENKINS_HOME%/GroovyScript/Scripter.groovy. It would not need to offer all the scripts this way . . . only the script currently being edited. Environment: All Groovy Editors: Script Console, groovy-postbuild, scriptler (others?) Project: Jenkins Priority: Minor Reporter: Frank Merrow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17418) Enhancement to all Groovy Editing Interfaces to allow easy use of External Groovy Editors
Frank Merrow updated JENKINS-17418 Enhancement to all Groovy Editing Interfaces to allow easy use of External Groovy Editors Change By: Frank Merrow (30/Mar/13 7:17 PM) Description: InallcasestheJenkinsGroovyeditorsarelimited.No,Iamnotaskingformorefeaturesfortheeditoritself,butitoccurstomethatafairlysimpleenhancementtoalloftheseinterfacescouldmakeitveryeasytohopin/outofyourfavoriteGroovyEditor;MineisNetbeans.Likemosteditors,Netbeansmonitorsthedisktonoticeifthefilehasbeenchangedoutsidetheeditor.SoifScriptConsoleforinstancewouldafter5secondsofnotyping,savethefileto%JENKINS_HOME%/GroovyScript/ScriptConsole.groovy(orwhatever)...IcouldthenstoptypingandalmostimmediatelyhavethecurrentscriptinNetbeans(assumingNetbeanscurrentlyhadthatfileopen).Similarlythen,onceIfinishallmyauto-tab,intellisensedchangesinNetbeans,IhitsaveandtheGroovyConsolecouldthenpullbackinmychangesandIcouldrunthem.Icouldeasily makechangesineithereditoraswasmostconvenientand jumpbackandforthwithoutalltheusualcopy/pastenonsense.ScriptConsolecouldevenofferthepreviousscriptbackonthestartofanewsession.GroovyPostbuildhastheadditionalissuethatPostbuildisonajobbyjobbasis,soitsaveareamightbe%JENKINS_HOME%/GroovyScript/%ITEM_ROOTDIR.groovy.(Thenameisntimportant,butyougettheidea).Scriptlerinasensealreadyhasthefilessaved,butinanXMLfilewithlotsofothermetadatathatgetsintheway.Itmightsaveacleanversionofthegroovyin%JENKINS_HOME%/GroovyScript/Scripter.groovy.Itwouldnotneedtoofferallthescriptsthisway...onlythescriptcurrentlybeingedited. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
