March 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] looking for media to illustrate one important idea :)

by phil＠highoctane.be

Speaking of the consortium, I think we could at least get the system listed on: http://www.orsys.fr I used to deliver a hell of a lot of trainings over there under this heading: http://www.orsys.fr/orsys.asp?mode=surdomaine&code=3 and that subheading: http://www.orsys.fr/orsys.asp?mode=surdomaine&code=3#OU I think we could add a "Formation Pharo Smalltalk" with: Pharo Essentials * Learning to program with Pharo * Pharo for the web * Understanding the Pharo infrastructure Pharo Advanced * Seaside * Seaside REST * DCVS with Monticello * Pharo FileSystem * Pharo Sockets * Crafting Morphic UIs with Spec Pharo Experts * Integrating Amber, Pharo, and MongoDB (e.g. Smalltalkhub style) * Metacello * VM * Creating new languages in Pharo with PetitParser and friends If one can come up with a decent list of trainings taking inspiration from the PHP list for example, we can for sure get an appointement with the superior powers over there and get the courses listed in the catalog. Whoever wants to deliver the trainings in french, please tell me, so that we can arrange stuff. There is enough material in the PBE and Deep into Pharo books to do what I listed above. Also, we can think of a one-day seminar on why Pharo matters for the industry. (covering legal aspects, IP, etc). The fact that INRIA backs up Pharo and that Orsys is a thriving french business in Paris would help in leveraging our value. Now, maybe could we get this on a Consortium list in order to enlist partners who want to get in the boat. Is there a consortium members wiki? Rgds, Philippe 2013/3/25 Esteban A. Maringolo <emaringolo(a)gmail.com>: > 2013/3/25 stephane ducasse <stephane.ducasse(a)free.fr>: >> I'm looking for labor and many tasks :) > > Something like a space launch control center would do it? > >>> Stephane: Does it need to be shown as a picture? It can be in words as >>> long as it takes less than 1000 words... :) >> >> :) >> >> I'm trying to make people using pharo understanding that the consortium and the association >> are a huge opportunity to make the future better. > > I look forward to know why :) > > Regards! >

March 26, 2013

Re: [Pharo-project] HOPomodoro (was Contribution CI Semantics)

by Sean P. DeNigris

philippeback wrote > I used standard buttons but then moved to UIManager kind of things. Why not Spec? ----- Cheers, Sean -- View this message in context: http://forum.world.st/HOPomodoro-was-Contribution-CI-Semantics-tp4678266p46… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 26, 2013

Re: [Pharo-project] Suggestion about Phexample and StateSpecs(Mocketry) integration

by Tudor Girba

Hi, I agree with Camillo. When implementing anything you need to think of the costs associated with assessing it. Cheers, Doru On Mar 25, 2013, at 10:28 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-03-25, at 21:24, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > >> Hello >> >> I think you read about Mocketry and know that It provides same "should >> syntax" DSL like project Phexample. >> >> There is problem between two projects. We both implement #should message in >> Object class. So when somebody want Phexample Mocketry become broken and >> vice versa. >> >> In the past I actually only read about Phexample tests reusage idea with >> #given message. And I didn't know that It provides "should syntax" too. >> Now I read about it and look at code (thank's Yuriy Tymchuk) and I have >> some suggestions about it. >> >> First few words about state of Mocketry project. >> >> Mocketry is not based on SSpec (I was google such wrong opinion). It is >> just implement SSpec idea about executable specifications and "should >> syntax". >> And specifications part with DSL was extracted from Mocketry to StateSpecs >> project. So Mocketry is only about mocks and behaviour specs. >> >> Idea of executable specifications is not about replacement "assert syntax" >> with "should syntax". It is about building reusable first class objects >> which can validate domain objects. For example there are EqualitySpec, >> ElementsCountSpec, ClassSpec. All this specs present "valid state" of >> objects. They know how to validate objects. >> State specs can be used in tests, UI and any other domain where you want >> put descriptions about what it mean "valid object". >> I start use StateSpecs in Presenty to build object editor. With specs I put >> requirements on model aspects. >> I am sure Magritte provides something similar in description objects. >> >> So StateSpecs solve very general problem: how to describe validation rules >> for objects and how to make such descriptions reusable. >> To make it convenient and readable StateSpecs provides two kind of DSL: >> >> - should syntax to immediately check object state >> - first class words to create spec instances with more readable way: >> Instance of: SomeClass, Equal to: #some, Containing item: arrayItem and >> others >> >> First option can be used in tests instead #assert: expressions. Last can be >> used in mock message arguments. >> >> StateSpecs provide very simple way to extend it DSL based on pragmas: >> >> Instance of: aClass >> <syntax: #(be an instance of:)> >> ^ClassSpec for: aClass >> >> Equal to: anObject >> <syntax: #(equal:)> >> <syntax: #(be equal:)> >> ^self return: (EqualitySpec pattern: anObject) >> >> Containing item: anObject >> <syntax: #(include:)> >> ^ElementContainmentSpec requiredElement: anObject >> >> And with this you can write: >> >> object should be an instance of: SomeClass >> object should equal: #some >> object should be equal: #some >> array should include: item. >> >> So with such approach both kind of DSL extended at one place. >> >> Ok. Now my main suggestion. Let's Phexample use StateSpecs for "should >> syntax". >> I can provide all "should protocol" of Phexample in StateSpecs. So it will >> be transparent for current users. It just few extra pragmas and classes in >> StateSpecs-DSL package. Maybe it is already done by Yuriy Tymchuk. >> With such integration both projects will just improved. >> >> What do you think? > > humm I have ambigous feelings about that. > Definitely StateSpec looks more mature and can be used in a more flexible way. > But I am not a big fan of the pragma magic. Why? > It breaks all tools for me :/. If I see a message send I want to be able to: > - browse it, so I can see who implements it? > - debug it directly to get to the real method. > > SateSpec does indeed help writing readable code by allowing almost grammatically > correct sentences. However I don't think this is the way to program. I am a big > fan of stupid english: > > `foo should isKindOf: Bar` vs. `foo should be an instance of: Bar` > > If I want to figure out how the first one works, I can simply browse the > implementors of #should and/or #isKindOf: where is the StateSpec version I am > lost. I have to rely on "contains string literal" to get the sources, for me > that is very strange. > > So personally I would go for the simple solution that doesn't introduce yet > another indirection meta-level using the pragmas. > > For me, complex DSLs only work if you write the proper debugging tools for it. > > Sorry for so much negative energy :) but you can try to convince me otherwise :) > > > > -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."

March 26, 2013

Re: [Pharo-project] Suggestion about Phexample and StateSpecs(Mocketry) integration

by Denis Kudriashov

Hello 2013/3/26 Camillo Bruni <camillobruni(a)gmail.com> > Definitely StateSpec looks more mature and can be used in a more flexible > way. > But I am not a big fan of the pragma magic. Why? > It breaks all tools for me :/. If I see a message send I want to be able > to: > - browse it, so I can see who implements it? > - debug it directly to get to the real method. > > SateSpec does indeed help writing readable code by allowing almost > grammatically > correct sentences. However I don't think this is the way to program. I am > a big > fan of stupid english: > > `foo should isKindOf: Bar` vs. `foo should be an instance of: Bar` > > If I want to figure out how the first one works, I can simply browse the > implementors of #should and/or #isKindOf: where is the StateSpec version I > am > lost. I have to rely on "contains string literal" to get the sources, for > me > that is very strange. > I think main thing you want is easilly explore all available should syntax. And StateSpecs can be easilly adopted for such task. We can just move all methods with syntax pragmas to single class. So you can open this class and see what available. To get implementors of some "should expression" you should use senders search of syntax words instead of implementors. Syntax words in StateSpecs is just method literals ( <syntax: #(be an instance of:)>, #() is just array of symbols). Interesting that StateSpecs has more explicit syntax system. How you can explore in Phexample expression: object should be true ? You have separate PheMatcher>>be and PheMatcher>>true methods and there is no places in code where you can see that this messages can and should be used together. But with StateSpecs you should put pragma with explicit expression like: Equal>>true: anObject <syntax: #(be true)> ^self return: (IdentitySpec pattern: true) So with StateSpecs you have full syntax expression at one place which can be easy explored. And for example to support Phexample mesage #beTrue you should just add another pragma: Equal>>true: anObject <syntax: #(be true)> <syntax: #(beTrue)> ^self return: (IdentitySpec pattern: true) So with Phexample you can browse implementors of "single word should expressions". But with Phexample if you browse implementors of #be like messages you have no idea how it can be used. In StateSpecs you should use senders. And with StateSpecs if you browse "any syntax word implementors" by senders seach you will see all possible usage cases. And if I move all methods with syntax pragmas to single class you can easilly see all possible expressions in one place. `foo should isKindOf: Bar` vs. `foo should be an instance of: Bar` > With StateSpecs it should be foo should be a kind of: Bar And as I said before It is simple task to support all Phexample expressions by StateSpecs pragmas Best regards, Denis

March 26, 2013

Re: [Pharo-project] looking for media to illustrate one important idea :)

by phil＠highoctane.be

Consortium: +1 Yesterday, Goran told us at the Squeak monday Hangout on G+ that he was scripting the build of images for hosting on Amazon EC2 and similar using Pharo, his domain model, OSProcess and Chef. Now, that's business :-) Phil 2013/3/25 stephane ducasse <stephane.ducasse(a)free.fr>: > > On Mar 25, 2013, at 9:08 PM, "Esteban A. Maringolo" <emaringolo(a)gmail.com> wrote: > >> 2013/3/25 Pavel Krivanek <pavel.krivanek(a)gmail.com>: >>> or do you know how Egyptians created their obelisks? Hundreds of them >>> were sitting in a pit and were beating again and again with small >>> stones for moths and years, millimetre by millimetre >> >> I don't think that helps in the methaphor of a lot of people making >> small contributions to produce a greater outcome because... egyptians >> were slaves who died doing those obelisks. Are Igor, Camillo, Esteban, >> Sven, etc. going to die? I hope not. :) >> > > I'm looking for labor and many tasks :) > >> I don't know why Stephane needs that, but I understood what he wants >> to communicate. >> I'm trying to imagine something that represents that and then look for >> a picture of it online. >> >> Stephane: Does it need to be shown as a picture? It can be in words as >> long as it takes less than 1000 words... :) > > :) > > I'm trying to make people using pharo understanding that the consortium and the association > are a huge opportunity to make the future better. > > Stef

March 26, 2013

Re: [Pharo-project] HOPomodoro (was Contribution CI Semantics)

by phil＠highoctane.be

Ben & Sean added to the repo. I didn't had this effect, but the buttons were not resizing well. In fact, I used standard buttons but then moved to UIManager kind of things. We need to write something on that UIManager beast... Phil 2013/3/25 DeNigris Sean <sean(a)clipperadams.com>: >> philippeback: >> I started this little thing, anyone welcome to improve it... >> >> http://smalltalkhub.com/#!/~philippeback/HOPomodoro > > Cool idea! I fixed the layout for the Morph and the control button so it doesn't look like: > > > > > Cheers, > Sean > > p.s. if you add me to the repo, I'll commit myself next time ;) > >

March 26, 2013

Re: [Pharo-project] HOPomodoro (was Contribution CI Semantics)

by phil＠highoctane.be

I knew a slew of ideas would come :-) And save the image with the pomodoro time stamp. I have written a bunch of shell scripts for doing something like that, like: opw : open pharo workspace x rli: run latest image lsli: list latest image so, I do now: opw xxx rli or pharo `lsli` save NEWNAME Phil 2013/3/25 Sean P. DeNigris <sean(a)clipperadams.com>: > Benjamin Van Ryseghem-2 wrote >> What I thought was cool is a pomodoro which block the ui during pauses, >> log the changes during sessions, and commit in the package-cache at the >> end of each iteration :P > > Wow, I like that a lot! The beauty of turtles all the way down... not even > thinkable with a web timer. > > b.t.w. > Gofer it > smalltalkhubUser: 'philippeback' project: 'HOPomodoro'; > package: 'HighOctane-Pomodoro'; > load > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/HOPomodoro-was-Contribution-CI-Semantics-tp4678266p46… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

March 26, 2013

Re: [Pharo-project] Suggestion about Phexample and StateSpecs(Mocketry) integration

by Yuriy Tymchuk

I think that we can implement all basic messages like isTrue, isKindOf: , so you'll be able to write it and browse it. Also people will be able to decide in what form they want to write tests. I think that it's nice to have such flexible tool as StateSpec ÐÐ°Ð´ÑÑÐ»Ð°Ð½Ð¾ Ð· iPhone 25 Ð±ÐµÑ. 2013 Ð¾ 22:28 Camillo Bruni <camillobruni(a)gmail.com> Ð½Ð°Ð¿Ð¸ÑÐ°Ð²(Ð»Ð°): > > On 2013-03-25, at 21:24, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > >> Hello >> >> I think you read about Mocketry and know that It provides same "should >> syntax" DSL like project Phexample. >> >> There is problem between two projects. We both implement #should message in >> Object class. So when somebody want Phexample Mocketry become broken and >> vice versa. >> >> In the past I actually only read about Phexample tests reusage idea with >> #given message. And I didn't know that It provides "should syntax" too. >> Now I read about it and look at code (thank's Yuriy Tymchuk) and I have >> some suggestions about it. >> >> First few words about state of Mocketry project. >> >> Mocketry is not based on SSpec (I was google such wrong opinion). It is >> just implement SSpec idea about executable specifications and "should >> syntax". >> And specifications part with DSL was extracted from Mocketry to StateSpecs >> project. So Mocketry is only about mocks and behaviour specs. >> >> Idea of executable specifications is not about replacement "assert syntax" >> with "should syntax". It is about building reusable first class objects >> which can validate domain objects. For example there are EqualitySpec, >> ElementsCountSpec, ClassSpec. All this specs present "valid state" of >> objects. They know how to validate objects. >> State specs can be used in tests, UI and any other domain where you want >> put descriptions about what it mean "valid object". >> I start use StateSpecs in Presenty to build object editor. With specs I put >> requirements on model aspects. >> I am sure Magritte provides something similar in description objects. >> >> So StateSpecs solve very general problem: how to describe validation rules >> for objects and how to make such descriptions reusable. >> To make it convenient and readable StateSpecs provides two kind of DSL: >> >> - should syntax to immediately check object state >> - first class words to create spec instances with more readable way: >> Instance of: SomeClass, Equal to: #some, Containing item: arrayItem and >> others >> >> First option can be used in tests instead #assert: expressions. Last can be >> used in mock message arguments. >> >> StateSpecs provide very simple way to extend it DSL based on pragmas: >> >> Instance of: aClass >> <syntax: #(be an instance of:)> >> ^ClassSpec for: aClass >> >> Equal to: anObject >> <syntax: #(equal:)> >> <syntax: #(be equal:)> >> ^self return: (EqualitySpec pattern: anObject) >> >> Containing item: anObject >> <syntax: #(include:)> >> ^ElementContainmentSpec requiredElement: anObject >> >> And with this you can write: >> >> object should be an instance of: SomeClass >> object should equal: #some >> object should be equal: #some >> array should include: item. >> >> So with such approach both kind of DSL extended at one place. >> >> Ok. Now my main suggestion. Let's Phexample use StateSpecs for "should >> syntax". >> I can provide all "should protocol" of Phexample in StateSpecs. So it will >> be transparent for current users. It just few extra pragmas and classes in >> StateSpecs-DSL package. Maybe it is already done by Yuriy Tymchuk. >> With such integration both projects will just improved. >> >> What do you think? > > humm I have ambigous feelings about that. > Definitely StateSpec looks more mature and can be used in a more flexible way. > But I am not a big fan of the pragma magic. Why? > It breaks all tools for me :/. If I see a message send I want to be able to: > - browse it, so I can see who implements it? > - debug it directly to get to the real method. > > SateSpec does indeed help writing readable code by allowing almost grammatically > correct sentences. However I don't think this is the way to program. I am a big > fan of stupid english: > > `foo should isKindOf: Bar` vs. `foo should be an instance of: Bar` > > If I want to figure out how the first one works, I can simply browse the > implementors of #should and/or #isKindOf: where is the StateSpec version I am > lost. I have to rely on "contains string literal" to get the sources, for me > that is very strange. > > So personally I would go for the simple solution that doesn't introduce yet > another indirection meta-level using the pragmas. > > For me, complex DSLs only work if you write the proper debugging tools for it. > > Sorry for so much negative energy :) but you can try to convince me otherwise :) > > > >

March 25, 2013

Re: [Pharo-project] [Vm-dev] Re: Reproducible VM crash when loading FFI

by Camillo Bruni

Thanks for the findings! I opened an issue http://bugs.pharo.org/issues/id/10134 with the contents of your solution. I think for completeness we should implement both solution, and of course use the one that does not #becomeForward: in the standard case. On 2013-03-25, at 19:52, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Hi Guille, > > thanks for this. The problem is that Pharo's > recreateSpecialObjectsArray uses newCompactClassesArray to recreate the > compact classes array and on Cog that is not supported. Cog caches the > compactClassesArray (specialObjectsArray at: 29) in every jitted method > prolog to reduce the time taken to derive the receiver's class in message > lookup. The Pharo 2.0 code for recreating the specialObjectsArray can > therefore create a dangling pointer where the only reference to the old > compactClassesArray is in machine code, and the machine code GC doesn't > cope with there being roots in machine code. Note that Cog also caches the > characterTable and class SmallInteger in machine code. > > There are two solutions to this. > One would be to reuse the compactClassesArray (my recommendation). So that > recreateSpecialObjectsArray looks like > > ... > "An array of the 255 Characters in ascii order. > Cog inlines table into machine code at: prim so do not regenerate it." > newArray at: 25 put: Character characterTable. > ... > "A 32-element array with up to 32 classes that have compact instances. > Cog inlines table into machine code class lookup so do not regenerate it." > newArray at: 29 put: self compactClassesArray. > ... > > where compactClassesArray, like Character characterTable, answers the > existing object. > > The second solution (rather hackish) is to void all machine code on > installing the new specialObjectsArray. e.g. > recreateSpecialObjectsArray > "Smalltalk recreateSpecialObjectsArray" > "To external package developers: > **** DO NOT OVERRIDE THIS METHOD. ***** > If you are writing a plugin and need additional special object(s) for your > own use, > use addGCRoot() function and use own, separate special objects registry " > "The Special Objects Array is an array of objects used by the Squeak > virtual machine. > Its contents are critical and accesses to it by the VM are unchecked, so > don't even > think of playing here unless you know what you are doing." > "Replace the interpreter's reference in one atomic operation. > Void machine code to avoid crashing Cog." > | newSpecialObjectsArray | > newSpecialObjectsArray := self newSpecialObjectsArray. > self specialObjectsArray becomeForward: newSpecialObjectsArray. > Smalltalk vm voidCogVMState > > > this is my fault for not ensuring recreateSpecialObjectsArray was properly > commented. I had commented the inlining of Character table, but not the > inlining of the CompactClasses array. Apologies. > > HTH, > Eliot > > On Sat, Mar 23, 2013 at 10:19 AM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Hi! >> >> In my quest to crash the vm, i've found an ugly common case :(. >> I am trying to port the opendbx driver to 2.0, but I'm getting vm crashes >> when my configuration loads FFI :(. I updated my configuration to load >> version 1.7 of FFI (which I assume is the latest). >> >> I tried to do it in Pharo 2.0 with latest pharovm, and with eliot's Cog >> 2701 from his website, failing in both cases. >> The snippet of code that gets a sistematic crash is: >> >> Gofer it >> smalltalkhubUser: 'DBXTalk' project: 'DBXTalkDriver'; >> package: 'ConfigurationOfOpenDBXDriver'; >> load. >> ((Smalltalk at: #ConfigurationOfOpenDBXDriver) project version:#stable) >> load >> >> >> This snippet crashes always with a segmentation fault (at least the >> fifteen times i tried :), with several different output in the console... >> >> Surprisingly, if I load FFI alone and not from the OpenDBXDriver >> configuration, it loads well... :/ >> >> So I'm deferring the OpenDBX port a bit longer :( >> >> Thanks! >> Guille >> > > > > -- > best, > Eliot

March 25, 2013

Re: [Pharo-project] HOPomodoro (was Contribution CI Semantics)

by Sean P. DeNigris

Benjamin Van Ryseghem-2 wrote > What I thought was cool is a pomodoro which block the ui during pauses, > log the changes during sessions, and commit in the package-cache at the > end of each iteration :P Wow, I like that a lot! The beauty of turtles all the way down... not even thinkable with a web timer. b.t.w. Gofer it smalltalkhubUser: 'philippeback' project: 'HOPomodoro'; package: 'HighOctane-Pomodoro'; load ----- Cheers, Sean -- View this message in context: http://forum.world.st/HOPomodoro-was-Contribution-CI-Semantics-tp4678266p46… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 25, 2013