October 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Metacello bleedingEdge question

by Dale Henrichs

Will do ... do't forget `MetacelloMCVersionValidator populateReasonCodeDescriptions` ... Dale ----- Original Message ----- | From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Tuesday, October 2, 2012 11:56:26 AM | Subject: Re: [Pharo-project] Metacello bleedingEdge question | | I discussed with andre and we would like to collect some rules. | In fact we would like also to extract the rules from the history of | configuration :) | | - Baseline should have a blessing base line | - Version should have a development | I imagine a lot more of them/ | If you had ideas just send them. | | Stef | | | On Oct 1, 2012, at 11:54 PM, Dale Henrichs wrote: | | > Not sure whether or not these are doable with Slime, but they are | > good ideas | > | > Dale | > | > ----- Original Message ----- | > | From: "Alexandre Bergel" <alexandre.bergel(a)me.com> | > | To: Pharo-project(a)lists.gforge.inria.fr | > | Sent: Monday, October 1, 2012 1:30:44 PM | > | Subject: Re: [Pharo-project] Metacello bleedingEdge question | > | | > | > I was thinking in terms of Slime for Seaside. | > | > One PhD student is working on rule and I was thinking that it | > | > would | > | > be fun to have a kind of | > | > Metacello checker. | > | > do you have some rule of thumb where to look for potential | > | > problems? | > | > Because it can be a fun experience. | > | | > | I had this idea of a checker for Metacello (that can be used with | > | Versionner before committing), but never got the traction to do | > | it. | > | Some rules: | > | - two packages in a graph of dependencies may rely on a | > | different | > | version of a third package | > | - identifying cycles in packages | > | - very important: checking whether the dependencies defined in | > | Metacello matches with the actual source code. Said in other | > | words, do I miss some dependencies in a configuration? | > | | > | Cheers, | > | Alexandre | > | | > | -- | > | _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | > | Alexandre Bergel http://www.bergel.eu | > | ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | > | | > | | > | | > | | > | | > | | |

Oct. 2, 2012

Re: [Pharo-project] [Another sad day] a nice example of the mess with json in FileTree

by StÃ©phane Ducasse

>> No it was quite ok :) >> Working at home, good music, view on my garden, flower and butterfly. >> >> Stef > Sounds like a Halloween trailer. > Everything is peaceful and idyllic, then; JSON! yes totally scary, orange and black, and screaming :)

Oct. 2, 2012

Re: [Pharo-project] Metacello bleedingEdge question

by StÃ©phane Ducasse

I discussed with andre and we would like to collect some rules. In fact we would like also to extract the rules from the history of configuration :) - Baseline should have a blessing base line - Version should have a development I imagine a lot more of them/ If you had ideas just send them. Stef On Oct 1, 2012, at 11:54 PM, Dale Henrichs wrote: > Not sure whether or not these are doable with Slime, but they are good ideas > > Dale > > ----- Original Message ----- > | From: "Alexandre Bergel" <alexandre.bergel(a)me.com> > | To: Pharo-project(a)lists.gforge.inria.fr > | Sent: Monday, October 1, 2012 1:30:44 PM > | Subject: Re: [Pharo-project] Metacello bleedingEdge question > | > | > I was thinking in terms of Slime for Seaside. > | > One PhD student is working on rule and I was thinking that it would > | > be fun to have a kind of > | > Metacello checker. > | > do you have some rule of thumb where to look for potential > | > problems? > | > Because it can be a fun experience. > | > | I had this idea of a checker for Metacello (that can be used with > | Versionner before committing), but never got the traction to do it. > | Some rules: > | - two packages in a graph of dependencies may rely on a different > | version of a third package > | - identifying cycles in packages > | - very important: checking whether the dependencies defined in > | Metacello matches with the actual source code. Said in other > | words, do I miss some dependencies in a configuration? > | > | Cheers, > | Alexandre > | > | -- > | _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > | Alexandre Bergel http://www.bergel.eu > | ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > | > | > | > | > | >

Oct. 2, 2012

Re: [Pharo-project] Concept demonstration - Interactive Roassal for constructing models

by Mariano Martinez Peck

On Tue, Oct 2, 2012 at 8:08 PM, Ben Coman <btc(a)openinworld.com> wrote: > Following on from recent pharo-project 'Roassal Survey' posts which asked > for features for Roassal to be a universal diagram tool, I have cobbled > together a concept demo. I was quite surprised and pleased that I was able > to achieve this over the weekend - which I think is a testament to the > potential power of the clean design that Alexandre has achieved for > Roassal. Glamour also helped ease the way. > > Operation is quite basic - only interactively adding nodes and applying > different layouts. Adding edges between nodes is still to go. Previously > Roassal has been used only for scripting, so there are some bugs in the way > I've forced it to operate, but I thought I'd release as early as possible > to garner feedback and interest. Perhaps I get lucky and a Fuel expert > finds this interesting. Sorry, I couldn't follow. Let's say I am a Fuel expert, what should I say/do/watch/review/help/test ? > Help with moving the drawings to file and back would be appreciated. > > The attached package Glamour-Roassal-Interactive-**BenComan.3 is based > off Moose 4.7, tested against a fresh copy downloaded 2012-10-03 which > contained: > ConfigurationOfRoassal.**AlexandreBergel.605 > ConfigurationOfGlamour.**TudorGirba.98 > > cheers -ben > -- Mariano http://marianopeck.wordpress.com

Oct. 2, 2012

Re: [Pharo-project] Bad behaviour at startup

by Denis Kudriashov

Hello. Thank's for fix. I check it for latest pharo (from jenkins). It's work. Now debugger appears when ZnServer can't start during pharo startup. Best regards, Denis 2012/9/30 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Thanks Sven. I created an issue. > > BTW esteban was making progress on a simpler integration process and it > will easier for non core people to commit :). > > Stef > On Sep 29, 2012, at 9:02 PM, Sven Van Caekenberghe wrote: > > > Name: Zinc-HTTP-SvenVanCaekenberghe.307 > > Author: SvenVanCaekenberghe > > Time: 29 September 2012, 9:00:49.72 pm > > UUID: 9387492b-daa2-4ebf-a49d-44950586bda3 > > Ancestors: Zinc-HTTP-SvenVanCaekenberghe.306 > > > > Modified ZnServer class>>#startUp: to use a deferred startup action to > start all registered servers; this should allow for normal error handling > when something goes wrong initializing server sockets (thanks Igor Stasenko > for the fix; thanks Denis Kudriashov for the error report) > > >

Oct. 2, 2012

[Pharo-project] Concept demonstration - Interactive Roassal for constructing models

by Ben Coman

Following on from recent pharo-project 'Roassal Survey' posts which asked for features for Roassal to be a universal diagram tool, I have cobbled together a concept demo. I was quite surprised and pleased that I was able to achieve this over the weekend - which I think is a testament to the potential power of the clean design that Alexandre has achieved for Roassal. Glamour also helped ease the way. Operation is quite basic - only interactively adding nodes and applying different layouts. Adding edges between nodes is still to go. Previously Roassal has been used only for scripting, so there are some bugs in the way I've forced it to operate, but I thought I'd release as early as possible to garner feedback and interest. Perhaps I get lucky and a Fuel expert finds this interesting. Help with moving the drawings to file and back would be appreciated. The attached package Glamour-Roassal-Interactive-BenComan.3 is based off Moose 4.7, tested against a fresh copy downloaded 2012-10-03 which contained: ConfigurationOfRoassal.AlexandreBergel.605 ConfigurationOfGlamour.TudorGirba.98 cheers -ben

Oct. 2, 2012

Re: [Pharo-project] [update 2.0] #20319

by Camillo Bruni

On 2012-10-02, at 17:21, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 20319 > ----- > > Issue 6750: New Zinc version: fixing startup behavior of ZnServer > http://code.google.com/p/pharo/issues/detail?id=6750 > > Issue 6734: Adding some morph navigation through keymappings > http://code.google.com/p/pharo/issues/detail?id=6734 nice that fixes the tab-cycling of the find&replace dialog!

Oct. 2, 2012

[Pharo-project] [update 2.0] #20319

by Marcus Denker

20319 ----- Issue 6750: New Zinc version: fixing startup behavior of ZnServer http://code.google.com/p/pharo/issues/detail?id=6750 Issue 6734: Adding some morph navigation through keymappings http://code.google.com/p/pharo/issues/detail?id=6734 -- Marcus Denker -- http://marcusdenker.de

Oct. 2, 2012

Re: [Pharo-project] [Another sad day] a nice example of the mess with json in FileTree

by Dale Henrichs

Oct. 2, 2012

[Pharo-project] pharo-2.0-tests Â» mac - Build # 388 - Failure!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Oct. 2, 2012