----- "Igor Stasenko" <[email protected]> wrote: | Dale, i wanted to ask you, how easy OB-Tools could be targeted to | make | own remote debugger/browser? | And is your code free for use (under MIT)? | I'm just considering the how much of my blood could take to implement | these tools for use them in Hydra... :)
Igor, OB-Tools is under the MIT license - all of the hard work was done by Lukas. For GLASS, the work involved adapting the debugger commands to the GemStone Process/Context model. In GLASS, the debugger runs on the server-side and we use Morphic on the client-side to display all of the OB windows, so it wasn't necessary to anything (okay just a bit of process fiddling:) to get the Debugger windows to display on the remote client. For Hydra, I would think that remote access to the process/context model would be the ticket - and this would be straightforward with the OTDebugger. With that said, I'm not too familiar with the inter-vm communication model. If I had another debugger to do, I would definitely start with the OTDebugger:) Dale _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
