January 2011 - Pharo-dev - lists.pharo.org

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

[Pharo-project] For a metacello and metacello Repositories taskforces
by StÃ©phane Ducasse Jan. 26, 2011

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

[Pharo-project] Easy access on pharo-project.org
by Torsten Bergmann Jan. 26, 2011

Jan. 26, 2011

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

5 4

[Pharo-project] [update 1.2] #12323
by Marcus Denker Jan. 26, 2011

Jan. 26, 2011

12323 ----- Issue 3572: Failing test on Hudson: MCInitializationTest.testWorkingCopy Issue 3594: Expander needs tweaking to enable resize in a TableLayout (again) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3594 in pharo: Expander needs tweaking to enable resize in a TableLayout
by pharo＠googlecode.com Jan. 26, 2011

Jan. 26, 2011

Status: Accepted Owner: tudor.gi...(a)gmail.com Labels: Milestone-1.2 Type-RequestForEnhancement New issue 3594 by tudor.gi...(a)gmail.com: Expander needs tweaking to enable resize in a TableLayout http://code.google.com/p/pharo/issues/detail?id=3594 The attached change set from Gary makes the following code to work: | container morph1 morph2 morph3 ex1 ex2 ex3 sp1 sp2| morph1 := (PanelMorph new fillStyle: (SolidFillStyle color: Color red)) hResizing: #spaceFill; vResizing: #spaceFill. morph2 := (PanelMorph new fillStyle: (SolidFillStyle color: Color blue)) hResizing: #spaceFill; vResizing: #spaceFill. morph3 := (PanelMorph new fillStyle: (SolidFillStyle color: Color yellow)) hResizing: #spaceFill; vResizing: #spaceFill. ex1 := (UITheme builder newExpander: 'Red' for: morph1) spaceFillWeight: 1; expanded: true. ex2 := (UITheme builder newExpander: 'Blue' for: morph2) spaceFillWeight: 2; expanded: true. ex3 := (UITheme builder newExpander: 'Yellow' for: morph3) spaceFillWeight: 2; expanded: true. sp1 := EdgeGripMorph new target: ex1; edgeName: #bottom; vResizing: #rigid; extent: 24 @ ProportionalSplitterMorph splitterWidth; on: #mouseDown send: #expandedSizingRigid to: ex1. sp2 := EdgeGripMorph new target: ex2; edgeName: #bottom; vResizing: #rigid; extent: 24 @ ProportionalSplitterMorph splitterWidth; on: #mouseDown send: #expandedSizingRigid to: ex2. container := UITheme builder newColumn: { ex1. sp1. ex2. sp2. ex3}. container cellInset: 0. container extent: 400@400. container openInWindow.

1 8

[Pharo-project] [update 1.3] #13021
by Marcus Denker Jan. 26, 2011

Jan. 26, 2011

13021 ----- Issue 3596: 2nd part Headless (again...) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3596 in pharo: 2nd part Headless
by pharo＠googlecode.com Jan. 26, 2011

Jan. 26, 2011

Status: Fixed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3596 by marcus.d...(a)gmail.com: 2nd part Headless http://code.google.com/p/pharo/issues/detail?id=3596 2nd part Headless changes... Attachments: NonInteractiveTools.2.cs 22.2 KB Simulation-Fix.2.cs 2.1 KB

1 5

Re: [Pharo-project] check out my blog "This Context" for Spoon and Naiad news
by Craig Latta Jan. 26, 2011

Jan. 26, 2011

Oh, and of course the Spoon website for artifacts: http://netjam.org/spoon/. thanks again, -C -- Craig Latta www.netjam.org/resume + 31 020 894 6247 + 1 415 287 3547

1 0