On Dec 20, 2005, at 9:49 AM, J. Landman Gay wrote:
Jacque is having trouble remembering when the last "single script
window" was the maximum, so can't really make too much trouble for
you. ;) I think that was back in HyperCard 1.0, yes? Like, 20 years
ago?
I have enough windows open when an app is running, I don't want a
plethora of new ones just because I'm debugging.
I want a purpose-built debugging window that shows variables, the
calling chain, and the currently executing code in a single
window that will go away when execution ends.
That sounds kind of cool to me, actually. I have a hard time
working on my Powerbook, where screen real estate is scarce. A one-
window composite would be ideal.
On Dec 20, 2005, at 10:54 AM, Mark Wieder wrote:
Well, you're certainly not going to get an argument from me. It's not
a case of keep-things-as-they-are or go back to a editing just a
single script at a time. I think a tabbed script editor window with
tabs for each script you're editing or debugging would suit my needs.
The windows-all-over-the-screen thing gets to be a pain.
I guess I wasn't being clear. I would never want to be restricted to
just one script editor window. I just want a single debugging window
with an integrated variable watcher panel and execution context panel
(which would let me switch between the scripts in the calling chain.
Bonus points for being able to enter arbitrary expressions to watch
their value as execution proceeds.
gc
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
