September 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] feedback on CLFramework

by nullPointer

StÃ©phane Ducasse-2 wrote: > > In VisualWorks you use the builder and it generates a class for you > a bit in the same way then you code the missing code. > > You said: > >> Of course, but I donÂ´t know do it of another way. Literal array is >> very >> complicated for me. >> Xml serialization and Moose serialization donÂ´t be possible. The code >> generated is HUGE > > and in VW all the interface is generated using the UIBuilder. > so I'm wondering why this is working > IÂ´m not sure of understand good that... The only class than works in UIBuilder for create the UI (#specMorph) is CLViewDesigner class. That class create the #specMorph and #specEvents methods, in a child of CLView class. All examples in CLFramework be CLView kinds. In the #specEvents is returned a Dictionary where exists a relation between morph, type of event and handler of that event. All that is more more readable than VW mechanism, where not is easy understand it. StÃ©phane Ducasse-2 wrote: > > I do not know exactly the VW framework details but we can cerytainly > interpret the following literal array. > > [.....] > I understand is possible create a interpreter for that code, with #perform: message. But the difficult seems GeneratE that code, not reader. Not is equal a result like that...? |CanvasMorph btnAction1 ...... | "CanvasMorph" CanvasMorph := Morph new. CanvasMorph color: Color red; borderWidth: 5; etc.... "btnAction1" btnAction1 := CLButton new. btnAction1 text: 'Accept'; position: 10@10; roundedCorners: true. [...............] CanvasMorph addAllMorphs: #( btnAction1 btnAction2 [etc....] ) Is a dummy example, but the result code is more cleaned, and readable. And seems equal of hard.Another environments ( equal or much more competents than VW ) using that mechanism. My knowledge of Smalltalk and programming in general is very limited and poor. I want listen another ways of do.I want learn. But i have understand it before :D Regards -- View this message in context: http://n2.nabble.com/Re-feedback-on-CLFramework-tp3718474p3720135.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 27, 2009

Re: [Pharo-project] feedback on CLFramework

by StÃ©phane Ducasse

On Sep 27, 2009, at 11:09 AM, nullPointer wrote: > > > StÃ©phane Ducasse-2 wrote: >> >> I can tell you I cannot read your code well. >> So if you want to really have fun with Smalltalk, change. >> > > But IÂ´m cannot read then with that format. I have fun with > Smalltalk, but > for fun i need > donÂ´t write the code of apocalyptic way :)) > Exists the possibility of give format in browser, selecting the option > "Pretty print", in the right. > The format of that option seems the same than you want, and donÂ´t > change the > original code. > Despite I will try to read the book of Kent Beck. In the long term it will not work. I can tell you. If everybody reading your code always feels like me it will not work. >> if you store them as literal arrays probably but inside a string I do >> not see why. >> > > But how i can store the state of a object in a Array? exists some > mechanism > already do it for that or is needed implement it? Seems difficult. for User Interface object you only need to store icons and image all the rest is what: classname, number, string, boolean and symbols...so we already now how to store them. in literal arrays. Do you need more? The advantage of a array like spec is that it is independent of your implementation objects so they will not break each time you change an instance variable. VW used that since 1996 or even before. They could also produce a web based interface and we could do the same by pluging a seaside aware interpreter. > Well, the application is in alpha state... and not usable for serious > purposes. I did warn of that :(( This is not a problem. I just wanted to tell you. But this is good that you publish it anyway.

Sept. 27, 2009

Re: [Pharo-project] Sunit3.2

by StÃ©phane Ducasse

I have the impression that Sunit should be an API specification not a implementation common to all the dialect. So I would really like to see if nial has some tests for SUnit3.2 and which ones pass and fail on pharo. Stef On Sep 27, 2009, at 11:06 AM, Damien Cassou wrote: > On Sun, Sep 27, 2009 at 10:55 AM, Lukas Renggli <renggli(a)gmail.com> > wrote: >> I tried to merge the changes with mcz packages that Niall prepared. >> As >> it says in the commit comment the code is broken. The difference of >> SUnit in Pharo is so substantial that almost every method was a >> conflict. I spent a few hours and tried to merge the changes >> manually, >> but in the end it did not work as expected. There are some subtle >> bugs >> in the SUnit code and some tools we have in Squeak are broken >> afterwards. > > What about replacing Pharo's SUnit by Nial's and then re-add lost > features? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 27, 2009

[Pharo-project] [update] #10461

by StÃ©phane Ducasse

- Issue 973: Cleaning better MessageTally - Issue 1234: MessageTally tallySends: [3.14159 printString] broken http://code.google.com/p/pharo/issues/detail?id=1234

Sept. 27, 2009

Re: [Pharo-project] feedback on CLFramework

by nullPointer

StÃ©phane Ducasse-2 wrote: > > I can tell you I cannot read your code well. > So if you want to really have fun with Smalltalk, change. > But IÂ´m cannot read then with that format. I have fun with Smalltalk, but for fun i need donÂ´t write the code of apocalyptic way :)) Exists the possibility of give format in browser, selecting the option "Pretty print", in the right. The format of that option seems the same than you want, and donÂ´t change the original code. Despite I will try to read the book of Kent Beck. StÃ©phane Ducasse-2 wrote: > > if you store them as literal arrays probably but inside a string I do > not see why. > But how i can store the state of a object in a Array? exists some mechanism already do it for that or is needed implement it? Seems difficult. StÃ©phane Ducasse-2 wrote: > > So far I could not build an interface with two buttons. > Well, the application is in alpha state... and not usable for serious purposes. I did warn of that :(( Regards -- View this message in context: http://n2.nabble.com/Re-feedback-on-CLFramework-tp3718474p3720070.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 27, 2009

Re: [Pharo-project] Sunit3.2

by Damien Cassou

On Sun, Sep 27, 2009 at 10:55 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > I tried to merge the changes with mcz packages that Niall prepared. As > it says in the commit comment the code is broken. The difference of > SUnit in Pharo is so substantial that almost every method was a > conflict. I spent a few hours and tried to merge the changes manually, > but in the end it did not work as expected. There are some subtle bugs > in the SUnit code and some tools we have in Squeak are broken > afterwards. What about replacing Pharo's SUnit by Nial's and then re-add lost features? -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Sept. 27, 2009

Re: [Pharo-project] feedback on CLFramework

by StÃ©phane Ducasse

I watch the video and this is cool >> PS. I added recently the CLSplitterPanel widget -> >> http://www.youtube.com/watch?v=qbd9bbfxNB4 In VisualWorks you use the builder and it generates a class for you a bit in the same way then you code the missing code. You said: > Of course, but I donÂ´t know do it of another way. Literal array is > very > complicated for me. > Xml serialization and Moose serialization donÂ´t be possible. The code > generated is HUGE and in VW all the interface is generated using the UIBuilder. so I'm wondering why this is working for example I could paste the following without any problem in a methods. Then we could easily code a simple interpreter that perform: the message on an instance for example #(#{UI.ActionButtonSpec} #layout: #(#{Graphics.LayoutFrame} 115 0.35 30 0 180 0.35 53 0 ) #name: #removeButton #model: #removePattern #label: #(#{Kernel.UserMessage} #key: #Remove #defaultString: 'Remove' #catalogID: #pdp) #defaultable: true ) f := LayoutFrame new with: #(115 0.35 30 0 180 0.35 53 0) => ActionButton new layout: f; name: #removeButton I do not know exactly the VW framework details but we can cerytainly interpret the following literal array. windowSpec "UIPainter new openOnClass: self andSelector: #windowSpec" <resource: #canvas> ^#(#{UI.FullSpec} #window: #(#{UI.WindowSpec} #label: #(#{Kernel.UserMessage} #key: #ContextListPolicyEditor #defaultString: 'Context list policy editor' #catalogID: #pdp) #min: #(#{Core.Point} 528 401 ) #max: #(#{Core.Point} 1024 768 ) #bounds: #(#{Graphics.Rectangle} 592 427 1120 828 ) #flags: 4 #menu: #menuBar ) #component: #(#{UI.SpecCollection} #collection: #( #(#{UI.LabelSpec} #layout: #(#{UI.AlignmentOrigin} 0 0.175 5 0 0.5 0 ) #name: #PatternListLabel #label: #(#{Kernel.UserMessage} #key: #Patterns #defaultString: 'Patterns' #catalogID: #pdp) ) #(#{UI.SequenceViewSpec} #properties: #(#{UI.PropertyListDictionary} #dragOkSelector #wantToDrag: #dragEnterSelector #dragEnter: #dragOverSelector #dragOver: #dragStartSelector #doDrag: #dropSelector #drop: #dragExitSelector #dragLeave: ) #layout: #(#{Graphics.LayoutFrame} 2 0 30 0 0 0.35 -60 1 ) #name: #patternList #model: #patternList #menu: #menu #useModifierKeys: true #selectionType: #highlight ) #(#{UI.ActionButtonSpec} #layout: #(#{Graphics.LayoutFrame} 25 0.35 30 0 90 0.35 53 0 ) #name: #newButton #model: #newPattern #label: #(#{Kernel.UserMessage} #key: #New #defaultString: 'New' #catalogID: #pdp) #defaultable: true ) #(#{UI.ActionButtonSpec} #layout: #(#{Graphics.LayoutFrame} 115 0.35 30 0 180 0.35 53 0 ) #name: #removeButton #model: #removePattern #label: #(#{Kernel.UserMessage} #key: #Remove #defaultString: 'Remove' #catalogID: #pdp) #defaultable: true ) #(#{UI.InputFieldSpec} #layout: #(#{Graphics.LayoutFrame} 13 0.35 105 0 -9 0.75 128 0 ) #name: #patternNameInput #model: #patternName ) #(#{UI.ActionButtonSpec} #layout: #(#{Graphics.LayoutFrame} 8 0.75 105 0 87 0.75 128 0 ) #name: #colorButton #model: #selectColor #label: #(#{Kernel.UserMessage} #key: #PickColor #defaultString: 'Pick Color' #catalogID: #pdp) #defaultable: true ) #(#{UI.TextEditorSpec} #layout: #(#{Graphics.LayoutFrame} 13 0.35 160 0 -8 1 -155 1 ) #name: #TextEditor1 #model: #patternString #tabRequiresControl: true ) #(#{UI.LabelSpec} #layout: #(#{Graphics.LayoutOrigin} 13 0.35 85 0 ) #name: #Label1 #label: #(#{Kernel.UserMessage} #key: #Name #defaultString: 'Name' #catalogID: #pdp) ) #(#{UI.LabelSpec} #layout: #(#{UI.AlignmentOrigin} 0 0.675 137 0 0.5 0 ) #name: #Label3 #label: #(#{Kernel.UserMessage} #key: #PatternString #defaultString: 'Pattern String' #catalogID: #pdp) ) #(#{UI.GroupBoxSpec} #layout: #(#{Graphics.LayoutFrame} 6 0.35 65 0 -2 1 -145 1 ) #name: #GroupBox1 #label: #(#{Kernel.UserMessage} #key: #Pattern #defaultString: 'Pattern' #catalogID: #pdp) ) #(#{UI.InputFieldSpec} #layout: #(#{Graphics.LayoutFrame} 12 0.35 -118 1 0 0.679924 -92 1 ) #name: #matchSelectorInputField #model: #matchSelector #type: #symbol ) #(#{UI.InputFieldSpec} #layout: #(#{Graphics.LayoutFrame} 6 0.68 -118 1 -8 1 -92 1 ) #name: #conversionSelectorInputField #model: #conversionSelector #type: #symbol ) #(#{UI.LabelSpec} #layout: #(#{Graphics.LayoutOrigin} 12 0.35 -137 1 ) #name: #Label4 #label: #(#{Kernel.UserMessage} #key: #MatchSelector #defaultString: 'Match Selector' #catalogID: #pdp) ) #(#{UI.LabelSpec} #layout: #(#{Graphics.LayoutOrigin} 6 0.68 -137 1 ) #name: #Label5 #label: #(#{Kernel.UserMessage} #key: #ConversionSelector #defaultString: 'Conversion Selector' #catalogID: #pdp) ) #(#{UI.ActionButtonSpec} #layout: #(#{Graphics.LayoutSizedOrigin} -100 0.5 -33 1 80 23 ) #name: #okButton #model: #accept #label: #(#{Kernel.UserMessage} #key: #Ok #defaultString: 'Ok' #catalogID: #pdp) #defaultable: true ) #(#{UI.ActionButtonSpec} #layout: #(#{Graphics.LayoutSizedOrigin} 20 0.5 -33 1 81 23 ) #name: #cancelButton #model: #cancel #label: #(#{Kernel.UserMessage} #key: #Cancel #defaultString: 'Cancel' #catalogID: #pdp) #defaultable: true ) #(#{UI.LabelSpec} #layout: #(#{Graphics.LayoutOrigin} 12 0.35 -82 1 ) #name: #Label2 #label: #(#{Kernel.UserMessage} #key: #DisplayAllLimit #defaultString: 'Display all limit' #catalogID: #pdp) ) #(#{UI.SpinButtonSpec} #layout: #(#{Graphics.LayoutFrame} 90 0.35 -83 1 150 0.35 -60 1 ) #name: #displayAllLimitField #model: #displayAllLimit #type: #number #formatString: '0' #low: 1 #high: 100 #interval: 1 ) #(#{UI.ActionButtonSpec} #layout: #(#{UI.AlignmentOrigin} -10 1 -10 1 1 1 ) #name: #HelpButton #model: #help #label: #(#{Kernel.UserMessage} #key: #Help #defaultString: 'Help' #catalogID: #pdp) #defaultable: true ) #(#{UI.DividerSpec} #layout: #(#{Graphics.LayoutFrame} 0 0 -48 1 0 1 -44 1 ) #name: #Divider1 ) ) ) )

Sept. 27, 2009

Re: [Pharo-project] Sunit3.2

by Lukas Renggli

Hi Stef, I tried to merge the changes with mcz packages that Niall prepared. As it says in the commit comment the code is broken. The difference of SUnit in Pharo is so substantial that almost every method was a conflict. I spent a few hours and tried to merge the changes manually, but in the end it did not work as expected. There are some subtle bugs in the SUnit code and some tools we have in Squeak are broken afterwards. A better strategy would probably be to apply the changes manually as they are described on the slides of Niall. Merging the code definitely does not work. Lukas 2009/9/27 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > lukas > > what should we do? > > SUnit-lr.76.mczFilename: Â Â Â Â SUnit-lr.76.mcz > Author: > Timestamp: Â Â Â 13 September 2009 1:07:41 pm > UUID: Â df933429-8228-4ae9-938b-3565231fd2f5 > Ancestors: Â Â Â SUnit-adrian_lienhard.75.mcz > Message: > > Trying to merge the SUnit 3.2 changes, but the difference of Pharo > with SUnit 3.1 seems to be so substantial that nearly half of the > complete code base conflicts with the SUnit 3.2 code. This code should > incorporate the code, but it somehow seems to be subtly broken. > Downloads: Â Â Â Web: 5 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

Sept. 27, 2009

[Pharo-project] Sunit3.2

by StÃ©phane Ducasse

lukas what should we do? SUnit-lr.76.mczFilename: SUnit-lr.76.mcz Author: Timestamp: 13 September 2009 1:07:41 pm UUID: df933429-8228-4ae9-938b-3565231fd2f5 Ancestors: SUnit-adrian_lienhard.75.mcz Message: Trying to merge the SUnit 3.2 changes, but the difference of Pharo with SUnit 3.1 seems to be so substantial that nearly half of the complete code base conflicts with the SUnit 3.2 code. This code should incorporate the code, but it somehow seems to be subtly broken. Downloads: Web: 5

Sept. 27, 2009

[Pharo-project] I would like to have feedback on Compiler PopUp plague

by StÃ©phane Ducasse

http://code.google.com/p/pharo/issues/detail?id=1224 if somebody can have a look about what I did it would be cool stef

Sept. 27, 2009