Author Topic: Scripting HE 1.50: need Tools > Execute: Last used script.  (Read 2931 times)

Offline Stefan

  • Administrator
  • Hero Member
  • *****
  • Posts: 775
  • Karma: +6/-0
    • View Profile
Scripting HE 1.50: need Tools > Execute: Last used script.
« on: November 29, 2011, 12:38:49 pm »
Playing around with alpha 1.50 scripting feature i have found an need:

Under Tools menu i have
Execute <<current open document>>
Execute...  (to browse for an script)

At least it would be helpful to have
Execute last script
or rather
Execute <<name of last script>>

for an quicker access of the current used script.
Stefan, HippoEDIT beta tester 
HippoEDIT - the editor programmers wants to code thyself when they are dreaming.        -Don't just edit. HippoEDIT!-

Offline alex

  • Developer
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2184
  • Karma: +37/-3
    • View Profile
    • HippoEDIT
Re: Scripting HE 1.50: need Tools > Execute: Last used script.
« Reply #1 on: November 29, 2011, 08:01:52 pm »
I can add this, but I think standard way for often used scripts, to create script tool.

Offline Stefan

  • Administrator
  • Hero Member
  • *****
  • Posts: 775
  • Karma: +6/-0
    • View Profile
Re: Scripting HE 1.50: need Tools > Execute: Last used script.
« Reply #2 on: November 29, 2011, 11:53:23 pm »
[...] but I think standard way for often used scripts, to create script tool.
Maybe. For often used/stored scripts. But tools should not be the standard way to organize scripts anyway. Only one way. Because to much fussiness. I would only recommend tools if i would need an shortcut.

My imagine of that menu is as:
  • Execute... "Browse for an script"  (start in \Scripts\ folders)
  • Execute last used script (name or tool tip with script name)
  • Execute > "pop-up with an history of the last ten scripts"
  • My Scripts > "pop-up with list of scanned files in scripts folder with sub-folders as pop-up menus"  (OK, ok, nearly the same as browse ;-) )
  • Set current doc in view as "last script" to execute  (just for temporary wrote scripts) Maybe as an replacement for your "Execute <current doc in view>"?

I find this more useful then "Execute <current doc in view>" because till now i never wanted to execute an script on its doc itself.



"Execute last used script" is for
* the script one would currently edit. Maybe not stored as script yet, and not at all set up as tool right now.
* using an stored script quickly again, without looking (browsing) for the right one over and over again. But just executing the last used script.


I can set it up as an tool, yes. But tomorrow i had to exchange the file name in that tool with the next script file.
But right now i just want to execute the script i am testing on over and over again.

Offline alex

  • Developer
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2184
  • Karma: +37/-3
    • View Profile
    • HippoEDIT
Re: Scripting HE 1.50: need Tools > Execute: Last used script.
« Reply #3 on: November 30, 2011, 12:20:59 am »
Quote
But tools should not be the standard way to organize scripts anyway. Only one way.
This is a standard way. Another standard way is to use plugin scripts.

Quote
Execute... "Browse for an script"  (start in \Scripts\ folders)
This is how it is now. Using of specific folder as start up folder is wrong. It should be last folder used for browsing for script.

Quote
Execute last used script (name or tool tip with script name)
Execute > "pop-up with an history of the last ten scripts"
OK, I can agree on recent script, that would be enough.

Quote
My Scripts > "pop-up with list of scanned files in scripts folder with sub-folders as pop-up menus"  (OK, ok, nearly the same as browse ;-) )
I will not go this way. We have already discussed this with you, and do want to repeat my arguments here. Tools management should be used instead. Or if you want automatic arrangement - script plugins.
 
Quote
Set current doc in view as "last script" to execute  (just for temporary wrote scripts) Maybe as an replacement for your "Execute <current doc in view>"?
I think current command is fine. It is not only for starting of current open script but also as solution for Shell Execute for current file.

 

Related Topics

  Subject / Started by Replies Last post
1 Replies
1791 Views
Last post February 17, 2009, 08:09:58 am
by JJK
18 Replies
9026 Views
Last post June 17, 2016, 11:09:59 pm
by alex
2 Replies
5341 Views
Last post October 07, 2009, 01:50:53 pm
by alex
1 Replies
2813 Views
Last post September 27, 2009, 07:47:24 pm
by Stefan
3 Replies
3929 Views
Last post September 06, 2012, 11:52:32 pm
by alex