On Mon, Mar 03, 2014 at 11:11:40PM +0000, Mike S wrote: Hi,
> Hi all. Great work on gst. It's really wonderful. It's small, it's fast, > has a c-interface, it's just great. yeah. Paolo created something really nice. I like the I/O model of GST so much more than pharo. :) > Unfortunately, I can't use Blox. I made sure I had tcl/tk installed, and > tcl-devel and tk-devel too. I told the configure script --with-tcl and > --with-tk to both tclConfig.sh and tkConfig.sh and yet it won't work. I > tried building tcl/tk from source myself and telling the configure script > to use the tclConfig.sh and tkConfig.sh I built myself and yet it won't > work. What exactly doesn't work? configure claims that it can't find Tcl/TK? Or does GST fail to load the package with tcl/tk? If it is configure can you please take a look at config.log and search for the tcl/tk results? > Is it possible to use it without Bloxtk, from the command line? I don't > want to use GTK (actually, even that didn't work, even though I had the > cario libs installed). I like tcl/tk and I may be able to contribute to > bloxtk. I feel lost without a squeak/pharo like IDE though. What is the issue with GTK and VisualGST? The tooling is squeak/pharo is really great and we have a lot to catch up. My current focus is improving the VisualGST debugger support (in the last months we already gained full view of all variables, restarting a method/frame, fixes to step over and step into, etc.). The next big thing would be to figure out how to get something like Monticello/Filetree into VisualGST and combine the power of having something like vi and grep but still do a lot of the development inside VisualGST/image. > > Is it possibly to use GST entirely from the REPL? without any GUI? what > methods do I need to find my way around? (for example, in python there's > dir() and help() and in ruby there's .methods and in tcl there's info). Sure. It is smalltalk after all. something inspect. will print a representation of the object something class selectors. will print all selectors (something >> #selector) methodSourceString will print you the method code (something >> #selector) inspect will print the bytecode and some other information about the CompiledMethod. (something lookupSelector: #selector) in case you don't know in which class #selector is defined. _______________________________________________ help-smalltalk mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-smalltalk
