in-tools.com - Topic: Script Bay Console

kanter3 on Script Bay Console

Thu, 26 Oct 2017 19:45:51 -0400

Thanks a lot for this infoormations

Harbs on Script Bay Console

Mon, 07 Mar 2011 11:28:22 -0500

I can make the KBSC appear as a tool tip on the run button. Problem with return is that it's a line return in the editor... Return does run scripts that are selected in the script list section...

John Hawkinson on Script Bay Console

Mon, 07 Mar 2011 11:24:16 -0500

Yeah, sure. And Cmd-R is of course the keybinding in the ESTK. Though I'm also quite fond of ENTER/RETURN if it doesn't break the UI violation. Over in UI land, it'd be nice if it was fairly discoverable (I don't think everyone knows they can hit Cmd-R in the ESTK...), but maybe that's not too important for the target market.

Harbs on Script Bay Console

Sun, 06 Mar 2011 05:07:11 -0500

John Hawkinson said:

Also key is the ability to easily edit what you're evaluating and run it again, without having to click a mouse button or somesuch.

Would a KBSC work for that? (command/control R or something)

Harbs on Script Bay Console

Sun, 06 Mar 2011 05:05:12 -0500

The way I see it there are two fundementally different ways to go about this type of thing:

One method is a command line type of console which outputs directly into the same window. This is the way that the "javascript shell" works.

The second method is like the ESTK where the script editor and output is totally separate.

I see the ESTK way as more useful for script writing than a terminal window. It sounds like you're more interested in the first method.

Maybe I can make a toggle to convert the editor window to a terminal window and back. Hmm...

John Hawkinson on Script Bay Console

Sun, 06 Mar 2011 03:53:59 -0500

Hey, Harbs.

At least for my application, the output from these oneliners (maybe more like 3-liners because Javascript s such a broken language...) tends to be a lot bigger than the script itself. So of the two options you presented, having a vertically divided section sounds like the way to go. Perhaps when fully reduced, it just reverts to the standard bottom status line that Script Bay has right now.

Also key is the ability to easily edit what you're evaluating and run it again, without having to click a mouse button or somesuch.

For my workflow/brain, it makes much more sense for the output to appear beneath the evaluated expression that caused it. But some people's minds might think differently.

Oh, also, it is nice to have a history of what has been typed, just like the ESTK's (or Ruderman's Javascript shell). For those who didn't read the post, my idea was based on a desire to port Jesse Ruderman's JavaScript shell to InDesign. Try it in your browser, it's pretty neat!

Harbs on Script Bay Console

Sun, 06 Mar 2011 03:11:50 -0500

John Hawkinson brought up a nice idea about adding a output area to Script Bay on the InDesign scripting forum. Basically, the idea would be to have some place where a script could output data similar to the ESTK javascript console.

I'm trying to figure out the best way to implement such a feature. I'd like to implement it in such a way where it would be there when you need it, but doesn't take away too much space from the script editor.

One idea I had was to make the script editor a vertically divided section where the bottom would be the console. The console would be able to be closed, so it would take away minimal space from the script editor when closed.

Another idea would be to make the console a drop-down area from a button somewhere around the editor area (probably on the top).

I'd love to hear opinions on how to do this!