- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #9 on issue 3583 by marcus.d...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 So what is the next step?

Jan. 26, 2011

Re: [Pharo-project] [ENH] About NonInteractive UI manager

by Igor Stasenko

On 26 January 2011 17:44, Yanni Chiu <yanni(a)rogers.com> wrote: > On 26/01/11 9:27 AM, Igor Stasenko wrote: >> >> UIManager, during image startup, checks if image runs headless, and if >> so, then it switching to non-interactive mode. >> The non-interactive mode means that any request to UI manager which >> normally leads to some user interaction now will trigger an error >> (ErrorNonInteractive). >> If you run image headful again, it will switch to usual UI manager >> back, so don't expect to have this error when running headful image. >> And be careful when testing/writing your code: image will run using >> different ui manager depending on startup conditions. > > This is great work! > > I will test it out shortly, but I'm wondering about the VNC scenario. I run > on a remote Linux server with "-headless". VNC is not started in the image. > If I suspect a problem, then I use the Seaside app at /tools/vnc to start > the VNC server. Then I attach to the image with a VNC client, and proceed to > debug. > > I suspect this scenario will be broken. The problem is that the "-headless" > flag does not mean there is no interactive UI needed. It means that there is > no local display. Well, the aim of this changes is to offer the default scenario for core images which have nothing like VNC loaded. Sure thing VNC could intrude (see my previous post) and change this in any way it likes it. The point it that we had almost nothing to offer to people who not using VNC until now. > If there is a way the flip the switch, in the running > image, then the /tools/vnc code could flip that switch. > Yes, sure there is the way to flip the switch. The simpest way of doing that is to do following: UIManager default: nil. And of course the discussion about nice API around this stuff is welcome. If you have any better ideas how to make image with VNC server to play nicely with new changes, feel free to present it. For instance, one idea is to have VNC server running , but if there is no connections then use non-interactive UI manager, and only if there user connected then use interactive mode. Also, varoius different hooks /extensions could be made , like providing a choice what to do on unhandled error, i.e. instead of quitting the image, one could send a email and kill the process which raised an error :) > -- > Yanni > -- Best regards, Igor Stasenko AKA sig.

Jan. 26, 2011

Re: [Pharo-project] [ENH] About NonInteractive UI manager

by Igor Stasenko

On 26 January 2011 17:30, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Sounds cool. > > Just a couple of questions: > - should I as a UI developer take care of anything in particular to make sure that I do not bypass the mechanism? all calls directed to ui manager will be intercepted properly. if you using things like World/Hand/Display, then of course there is no any guarantees, but normally your application should not use it outside of morphic boundaries. I mean that if your application having morph subclasses, then of course you can use these globals directly in it. And for applications like Seaside, you normally should not directly use that and pass all UI requests to UI manager. > - when we access the image through RFB, will we get the UI? > no. When RFB is present in system, it should prevent from switching UI manager to non-interactive one. I imagine there should be some kind of hooks, so RFB can influence the decision whether use UI or not. I imagine a proper , non-intrusive way of hooking into this logic with RFB is to subclass the MorphicUIManager with own subclass and override the #onSnapshot: in order to prevent switching to non-interactive manager. > Cheers, > Doru > > > On 26 Jan 2011, at 15:27, Igor Stasenko wrote: > >> Hello pharoers, >> >> the last two days we worked hard with Marcus to incorporate this new >> stuff into image, and now we're done. >> All images past #13021 now have non interactive ui manager >> (NonInteractiveUIManager). >> We fixed almost all broken tests caused by introducing it (there are >> only few minor ones left). >> Probably there could be more infrastructure around that in future >> (like redirecting Transcript output to some file/stdout while running >> headless), but first things first. >> >> >> Couple of words, what new stuff gives to you: >> >> - suppose you want to run image headless. Suppose that you probably >> run an arbirary (or not so) piece of code, >> which not always clear how well it goes.. and it could lead to >> unwanted popups, like asking user to confirm something, >> or even opening a debugger window, actually anything which leads to >> one unwanted effect: making your image to wait for user's input or >> other form of intervention, >> which is completely what you don't wanna see on server image, because >> it should run fully automated. >> >> How it works: >> >> UIManager, during image startup, checks if image runs headless, and if >> so, then it switching to non-interactive mode. >> The non-interactive mode means that any request to UI manager which >> normally leads to some user interaction now will trigger an error >> (ErrorNonInteractive). >> If you run image headful again, it will switch to usual UI manager >> back, so don't expect to have this error when running headful image. >> And be careful when testing/writing your code: image will run using >> different ui manager depending on startup conditions. >> >> (Note: some VMs on some platforms filtering out the VM command line >> parameters and image can't detect that it runs headless. To prevent >> that, add extra -headless arg as last one in argument list. >> >> For example: >> >> Â squeak -headless myImage.image myscript.st -headless >> >> ). >> >> To test if image running headless, a new protocol was introduced: >> >> Smalltalk isHeadless >> and >> Smallalk isInteractive >> >> (which are antonyms). >> >> >> Error handling: >> >> In case if there an unhandled error occurs, the default behavior is: >> - print stack trace on log >> - quit image Â ( or save a new version of image and then quit) Â - this >> is controlled by preference, found in 'settings->Headless mode' group. >> >> So, sometimes to track the error, you can turn this preference on, >> then you can open saved instance of image and check with UI & debugger >> what causing the error. >> This is what you want to avoid to be default behavior on server, >> because on server you need 24/7 service available without your >> intervention :) >> So, the normal setup for background images now will be to fire a fresh >> image if current one dies ( and send mail with pharodebug.log contents >> to root :) ) >> >> P.S. I hope these changes will make life for setting up headless >> workflow much easier, because now we can easily track down all issues >> which you can't see. >> Because before that by default you having a hanging image, which doing >> something or not (and you have no idea, because it headless). >> >> P.P.S. For squeakers, if you want to harvest the changes, take the >> changesets from here: >> >> http://code.google.com/p/pharo/issues/detail?id=3593 >> http://code.google.com/p/pharo/issues/detail?id=3596 >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > -- > www.tudorgirba.com > > "Value is always contextual." > > > > > -- Best regards, Igor Stasenko AKA sig.

Jan. 26, 2011

Re: [Pharo-project] [ENH] About NonInteractive UI manager

by Yanni Chiu

On 26/01/11 9:27 AM, Igor Stasenko wrote: > UIManager, during image startup, checks if image runs headless, and if > so, then it switching to non-interactive mode. > The non-interactive mode means that any request to UI manager which > normally leads to some user interaction now will trigger an error > (ErrorNonInteractive). > If you run image headful again, it will switch to usual UI manager > back, so don't expect to have this error when running headful image. > And be careful when testing/writing your code: image will run using > different ui manager depending on startup conditions. This is great work! I will test it out shortly, but I'm wondering about the VNC scenario. I run on a remote Linux server with "-headless". VNC is not started in the image. If I suspect a problem, then I use the Seaside app at /tools/vnc to start the VNC server. Then I attach to the image with a VNC client, and proceed to debug. I suspect this scenario will be broken. The problem is that the "-headless" flag does not mean there is no interactive UI needed. It means that there is no local display. If there is a way the flip the switch, in the running image, then the /tools/vnc code could flip that switch. -- Yanni

Jan. 26, 2011

Re: [Pharo-project] [ENH] About NonInteractive UI manager

by Tudor Girba

Sounds cool. Just a couple of questions: - should I as a UI developer take care of anything in particular to make sure that I do not bypass the mechanism? - when we access the image through RFB, will we get the UI? Cheers, Doru On 26 Jan 2011, at 15:27, Igor Stasenko wrote: > Hello pharoers, > > the last two days we worked hard with Marcus to incorporate this new > stuff into image, and now we're done. > All images past #13021 now have non interactive ui manager > (NonInteractiveUIManager). > We fixed almost all broken tests caused by introducing it (there are > only few minor ones left). > Probably there could be more infrastructure around that in future > (like redirecting Transcript output to some file/stdout while running > headless), but first things first. > > > Couple of words, what new stuff gives to you: > > - suppose you want to run image headless. Suppose that you probably > run an arbirary (or not so) piece of code, > which not always clear how well it goes.. and it could lead to > unwanted popups, like asking user to confirm something, > or even opening a debugger window, actually anything which leads to > one unwanted effect: making your image to wait for user's input or > other form of intervention, > which is completely what you don't wanna see on server image, because > it should run fully automated. > > How it works: > > UIManager, during image startup, checks if image runs headless, and if > so, then it switching to non-interactive mode. > The non-interactive mode means that any request to UI manager which > normally leads to some user interaction now will trigger an error > (ErrorNonInteractive). > If you run image headful again, it will switch to usual UI manager > back, so don't expect to have this error when running headful image. > And be careful when testing/writing your code: image will run using > different ui manager depending on startup conditions. > > (Note: some VMs on some platforms filtering out the VM command line > parameters and image can't detect that it runs headless. To prevent > that, add extra -headless arg as last one in argument list. > > For example: > > squeak -headless myImage.image myscript.st -headless > > ). > > To test if image running headless, a new protocol was introduced: > > Smalltalk isHeadless > and > Smallalk isInteractive > > (which are antonyms). > > > Error handling: > > In case if there an unhandled error occurs, the default behavior is: > - print stack trace on log > - quit image ( or save a new version of image and then quit) - this > is controlled by preference, found in 'settings->Headless mode' group. > > So, sometimes to track the error, you can turn this preference on, > then you can open saved instance of image and check with UI & debugger > what causing the error. > This is what you want to avoid to be default behavior on server, > because on server you need 24/7 service available without your > intervention :) > So, the normal setup for background images now will be to fire a fresh > image if current one dies ( and send mail with pharodebug.log contents > to root :) ) > > P.S. I hope these changes will make life for setting up headless > workflow much easier, because now we can easily track down all issues > which you can't see. > Because before that by default you having a hanging image, which doing > something or not (and you have no idea, because it headless). > > P.P.S. For squeakers, if you want to harvest the changes, take the > changesets from here: > > http://code.google.com/p/pharo/issues/detail?id=3593 > http://code.google.com/p/pharo/issues/detail?id=3596 > > -- > Best regards, > Igor Stasenko AKA sig. > -- www.tudorgirba.com "Value is always contextual."

Jan. 26, 2011

Re: [Pharo-project] First commit to Pharoinbox. Need advice.

by StÃ©phane Ducasse

+1 > Refactorings and more tests are certainly welcome! > > Here's a few comments: > While I like keeping common functionality in one place, I'm not sure creating a new helper object for each at:/at:put: access is a good idea. Nor keeping the helper cached to avoid this. Have you considered using a Trait instead? To me it seems like a good use-case for one. > > To the tests: > - setUp uses at:put:. testAt asserts the values set in setUp. Thus, is it not really just another at:put: test? Does it test something not covered by the other at:put: test(s)? > - testAtPutLargeInteger uses a static integer. This is not ideal, as the range of SmallInteger depends on platform (I realize though, that it is large enough for it not to fail on 64bit as well). > Using f.ex SmallInteger maxVal + staticInteger is more intention revealing. > Although, max/minVal actually returns a constant at the moment rather than a platform-specific value, and thus would fail on 64bit. I'd consider this a bug which it'd be nice if a test exposed :) > - testWriteXYEndianOn uses 256*256*256. etc. Probably down to preference, but I think they'd looks nicer using the bitShift: (or #<< if you prefer less parenthesis) operator. > > Cheers, > Henry >

Jan. 26, 2011

Re: [Pharo-project] First commit to Pharoinbox. Need advice.

by StÃ©phane Ducasse

On Jan 26, 2011, at 12:40 PM, HwaJong Oh wrote: > > Thank you for your detailed advice. > Although i could only comply bitShift: adivce. Using trait was unsuccessful. > super send is not possible with traits and applying PointArrayTrait on > ShortPointArray makes strange error. super send are possible with traits. Tell us what was your problem. Stef > > New version is out. (Balloon-hjo.73) > -- > View this message in context: http://forum.world.st/First-commit-to-Pharoinbox-Need-advice-tp3237535p3237… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Jan. 26, 2011

Re: [Pharo-project] Easy access on pharo-project.org

by StÃ©phane Ducasse

Good ideas! On Jan 26, 2011, at 11:14 AM, Torsten Bergmann wrote: > We have the shortcut to the collaborative book: > > http://book.pharo-project.org > > > Would it be possible: > > 1. to access the build server > https://pharo-ic.lille.inria.fr/hudson/ > > under a simple name like: > > http://hudson.pharo.org or > http://ci.pharo.org (ci = continuos integration) > > 2. to access the issue tracker > http://code.google.com/p/pharo/issues > under > > http://issues.pharo-project.org or > http://bugs.pharo-project.org > > 3. to access the wiki > http://code.google.com/p/pharo/w/list > under > http://wiki.pharo-project.org > > 4. And the book page > http://pharo-project.org/documentation/tutorials-books > has no reference to the collaborative book > http://book.pharo-project.org > > Thx > T. > -- > GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit > gratis Handy-Flat! http://portal.gmx.net/de/go/dsl >

Jan. 26, 2011

Re: [Pharo-project] Issue 3599 in pharo: Serial Port

by pharo＠googlecode.com

Comment #2 on issue 3599 by ryd...(a)gmail.com: Serial Port http://code.google.com/p/pharo/issues/detail?id=3599 Hasn't mr. Schwab been talking about this too? The scratch source code license is available as part of the download at http://info.scratch.mit.edu/Source_Code. Afaict it's not MIT compatible, since it contains both non-commercial and copyleft clauses for derived works.

Jan. 26, 2011

Re: [Pharo-project] [ENH] About NonInteractive UI manager

by Sven Van Caekenberghe

On 26 Jan 2011, at 16:12, Igor Stasenko wrote: > I found that it doesn't works with Cog VM on Macs. > > On Hudson build server, which runs on linux it works well out of the > box (but that using Sqeuak VM though). OK, Thanks. I found the Cog VM's acting strange sometimes, especially in the headless case, a hanging headless VM is hard to debug (NonInteractive UI manager will hopefully change that in the future). The latest unix VM (4.4.7 2356) worked better for me. Sven

Jan. 26, 2011