From: Dave Rose Date: 2007-03-19T23:44:49+09:00 Subject: Re: Ideas about Smalltalk-like IDE for Ruby Rick Denatale wrote: > On 3/18/07, richard.j.dale@gmail.com wrote > in another thread proposing items for a Google SOC project. > >> How do we save state in between sessions? > This is an intriguing idea. I'd love to have a Smalltalk-like IDE for > Ruby. I think that there are issues which make this an interesting > (i.e. difficult) task, so it might be worthwhile to discuss those > issues. > > > Another feature of most Smalltalk environments is that the running > state is persistent, When you leave the environment you can save the > memory image, and when you come back everything is as it was, > http://talklikeaduck.denhaven2.com/ ...i still have to program in BASIS BASIC VPRO5...which is an IDE that most of you have have an already biased opinion because its BASIC ... but it still beats the pants off ruby's Breakpoint and IRB... i've actually perfected a technic i call stream-of-conscience program creation (yes, i've already planned what the forest of the program will look like) i can not only edit and run the same program in it's own workspace without ever having to 'save' the program...and it's just as dynamic interpretive as Ruby...It uses (yikes) line stmt numbers and old time non OO bnf fortran like syntac processing...And it has some major unique run-time debuging aids... like 'goto' to a specific stmt, escape traps and single stepping that in total combine to a freedom to debug/process each program segment as it built. I can always 'clear' out or 'reset' some or all of the variables and start any or all of program segments over with the 'goto' verb. As each program segment is perfected i can then combine their current values in each of the variables with the whole program's process while that is still incomplete until all of the subsegments are built and done with whole program. This interactive testing is much like extreme programming but using the computer as my partner and is like Ruby unit testing but done manually using the console commands 'goto' and 'gosub' to re-unit test each program segment. I don't know how ruby stores it's parse tree but in VPRO5 it's stored with (appended to) the original stmt (that's 'inline' with the rest of the program) and the interpreter accepts console mode command of 'goto' and 'gosub' along with the console cmds of 'clear' and 'reset' Files and also be closed or opend at will too. At any time i can also 'save' my program in tokenized form and 'save' my variables separately too... to restart the whole process where it left off... -- Posted via http://www.ruby-forum.com/.