I use it for remotely deployed images. Whenever a debugger opens I get an email, connect to the image and examine the problem, fix it and done. Nothing beats the debugger.
But yes a repl would be useful to for different things. Norbert Am 25.09.2013 um 03:14 schrieb "Esteban A. Maringolo" <emaring...@gmail.com>: > What do people use RFB for? > > A remote interactive REPL could be useful too. > > Regards, > > Esteban A. Maringolo > > > 2013/9/24 Marcus Denker <marcus.den...@inria.fr> >> >> On Sep 24, 2013, at 4:08 PM, Mariano Martinez Peck <marianop...@gmail.com> >> wrote: >> >>> Hi guys, >>> >>> I am having this problem and it is very very easy to reproduce for me. And >>> it is in Mac, not Linux. I took a latest Pharo 2.0 image Latest update: >>> #20619, and a Mac VM of Mar 13 2013. Open a workspace and evaluate: >>> >>> Gofer it >>> smalltalkhubUser: 'PharoExtras' project: 'RFB'; >>> configuration; >>> load. >>> (Smalltalk at: #ConfigurationOfRFB) load. >>> (Smalltalk at: #RFBServer) start. >>> Smalltalk snapshot: true andQuit: false >>> >>> And it will freeze. If I save the image with the RFBServer running, my >>> image freezes. If the server is stopped while saving, there is no problem. >>> The hung seems to be AFTER the image save itself, because if I kill the >>> process and start again, the image was saved. Also...if you do SAVE AND >>> QUITE, it has NO PROBLEM. If I do Smalltalk snapshot: true andQuit: true. >>> the image is saved and when I open it back, it is OK. >> >> We need to really re-think if it is a good idea to deploy systems with code >> that is not part of the development cycle of Pharo. >> (read: what people get out of RFB needs to be part of the system itself) >> >> Marcus >
