- Pharo-dev - lists.pharo.org

[Pharo-project] First commit to Pharoinbox. Need advice.
by HwaJong Oh Jan. 27, 2011

Jan. 27, 2011

My last package is Balloon-hjo.72.mcz. It is small testing & refactoring on Ballloon supporting collections. I wonder this type of work is acceptable? Best Regards -- 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.

4 11

Re: [Pharo-project] [squeak-dev] check out my blog "This Context" for Spoon and Naiad news
by Juan Vuletich Jan. 27, 2011

Jan. 27, 2011

Craig Latta wrote: > Hi all-- > > Spoon 3 is nearing release (scheduled for the moment of equinox on > 20 March), featuring the first usable version of Naiad, Spoon's change > management system. Please check out my blog "This Context"[1] for news, > and the Spoon IRC channel[2] and mailing list[3] for discussion. > > > thanks! > > -C > > [1] http://thiscontext.wordpress.com > [2] irc://irc.freenode.net/#spoon > [3] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/spoon > > -- > Craig Latta > www.netjam.org/resume > + 31 020 894 6247 > + 1 415 287 3547 > It is great to know Spoon is alive! Cheers, Juan Vuletich

1 0

[Pharo-project] [ANN 1.2] re-built Core 1.2 RC2 #12324
by Marcus Denker Jan. 27, 2011

Jan. 27, 2011

https://gforge.inria.fr/frs/download.php/28189/PharoCore-1.2rc2-12324.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] [update 1.2] #12324
by Marcus Denker Jan. 27, 2011

Jan. 27, 2011

12324 ----- RC2 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3489 in pharo: Pharo 1.2-dev still uses Preferences in BaseSoundSystem
by pharo＠googlecode.com Jan. 27, 2011

Jan. 27, 2011

Status: Accepted Owner: Torsten....(a)astares.de New issue 3489 by Torsten....(a)astares.de: Pharo 1.2-dev still uses Preferences in BaseSoundSystem http://code.google.com/p/pharo/issues/detail?id=3489 Evaluate "Beeper beep" and you get a DNU since BaseSoundSystem>>beep calls Preferences>>soundsEnabled which is not there.

1 20

Re: [Pharo-project] [ANN 1.3] pre-build Core 1.3a#13021
by Marcus Denker Jan. 27, 2011

Jan. 27, 2011

On Jan 27, 2011, at 11:07 AM, laurent laffont wrote: > Shouldn't we have Pharo 1.3 (Dev) added on Hudson too ? Early feeback seems better to me. > Yes, this is on the TODO. Especially for the Full image, continuous integration is needed. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] [ANN 1.3] pre-build Core 1.3a#13021
by Marcus Denker Jan. 27, 2011

Jan. 27, 2011

On Jan 27, 2011, at 10:50 AM, StÃ©phane Ducasse wrote: > Marcus I like the idea of have 1.3 green all the time. > So we should move in bug entry the tests that are red. > Yes, and I want to tag "1.3" just those entries that -> are ready for inclusion -> are showstoppers and failing tests The idea is that the daily build should be as close as possible to a release. (a release should consist of pressing one button, with *everything* automatized). Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] [ANN 1.3] pre-build Core 1.3a#13021
by Marcus Denker Jan. 27, 2011

Jan. 27, 2011

https://gforge.inria.fr/frs/download.php/28188/PharoCore-1.3-13021.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 2

[Pharo-project] [ENH] About NonInteractive UI manager
by Igor Stasenko Jan. 27, 2011

Jan. 27, 2011

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.

10 18

Jan. 26, 2011

hi guys I really think that this is important that we to the point where the idea of repositories for distributions is working. Getting this idea working is really important since it will enable all the rest to fall naturally in place (hudson checking....) So could you (torsten, Miguel, dale...) try to come up with an agenda of the next steps that should be achieved to arrive to the point where: - a user can publish a configuration into a distribution and all the packages get copied and published there - get a browser browsing the configurations of that distribution? Stef (busy but cannot do otherwise). "if you knew today was your last day on earth, what would you do different? ... especially if, by doing something different, today might not be your last day on earth" Calvin&Hobbes

1 0