- Pharo-dev - lists.pharo.org

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

Re: [Pharo-project] Fwd: Issue 1129 in pharo: UIManager #request: and #multilineRequest do not distinguish between empty and cancel

by StÃ©phane Ducasse

I know now waht andreas propose is more a process to make sure that other places where this should be changed will be noticed automatically Stef On Sep 27, 2009, at 9:51 AM, Damien Cassou wrote: > On Sat, Sep 26, 2009 at 7:39 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> I kind of agree on this one. >> So what is the preferred solution. >> Now this is important to be able to distinguish an empty string >> from a >> cancel. > > I'm not sure. I think the fixes are small enough to apply everywhere > to avoid > complicating the API. To fix external packages, you just have to > change the #isEmpty > test after the #request by #isEmptyOrNil. I already did it for part > of the Pharo > image (see issue #1233 ). > > I vote for closing this report again. > > > -- > 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

Re: [Pharo-project] feedback on CLFramework

by StÃ©phane Ducasse

>> > Sorry, but i donÂ´t like that format of code. For me is not readable. > I donÂ´t > know when starts a block or if is a loop or condition block.That > problem is > more big when exists various identations. IÂ´m coming of VB and C# > and that > way seems anarchist for me :) my cerebellum is limited for that way > of > write code. smalltalk allows you to write nice and compact code so take it as a opportunity. In python you would be forced to use tab at the right place. [:each | .... ] [:each| ... ] > Why my format not is "Smalltalkish" way? read all the code in the image and you will see nowhere do: [ :ecah | ] or (expression) ifTrue: [ ] ifFalse: [ ] > Perhaps IÂ´m wrong (i have short > time with that language) but I believe indeed than Smalltalk donÂ´t > have a > style defined (Thanks to God) Read Kent beck book (best Smalltalk pattern) have a look at Smalltalk with Style on my web page. I can tell you I cannot read your code well. So if you want to really have fun with Smalltalk, change. >> > Yes. IÂ´m not add comments basically for my poor english. > Today i could try it. Is a relax work for sunday :) just write subject verb complement and code. I'm responsible for XXXX I collaborate with YY and ZZ Here are three important methods: - - - Here is a way to invoke me. >> Keep working. >> I still believe that a windowSpec based on a literal array is better >> than a byte array. >> >> > > 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 fails > with complex composite morphs. if you store them as literal arrays probably but inside a string I do not see why. > The one way for me is a mechanism where each > morph write his state in a stream. All states togethers will build > the final > morph. I believe that mechanism works, is elegant and readable. And > is easy > detect problems too, but i need a little more of time for do it. I > want > implement various widgets ( a grid is MUCH needed ) and last, before > of 1.0 > version, the serialization mechanism. > > Thanks for the feedback :) > > PS. I added recently the CLSplitterPanel widget -> > http://www.youtube.com/watch?v=qbd9bbfxNB4 So far I could not build an interface with two buttons. > > > Regards > > > > > -- > View this message in context: http://n2.nabble.com/Re-feedback-on-CLFramework-tp3718474p3718991.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > 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

Re: [Pharo-project] key pressed

by Tudor Girba

Thanks for the replies. Actually, I am in the code of selectedItem: of a list and I would like to add to the current selection if Shift is pressed. The problem is that I do not have access there at the event. Cheers, Doru On 27 Sep 2009, at 03:14, Schwab,Wilhelm K wrote: > +1 to Sig's comments. Another problem with looking at the current > state vs. state from an event is that the current state is just > that, and often differs (covertly and frustratingly) from the user's > intentions. Such problems often arise with mouse cursor positions. > > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr > ] On Behalf Of Igor Stasenko > Sent: Saturday, September 26, 2009 6:25 PM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] key pressed > > 2009/9/27 Tudor Girba <tudor.girba(a)gmail.com>: >> Hi, >> >> How can I check whether a certain key is pressed (for example, a >> modifier like Shift)? >> > Depends on context. In Morphic, just take an event (mouse event or > keyboard event) and send #shiftPressed, or #controlKeyPressed, or > whatever. > > Another way is to ask the Sensor for same things, but i wouldn't do > that, because to my opinion this is the wrong way, because Sensor is > low-level object, which should be hidden from the eyes of developer, > and normally, if you need to use it, it means that you doing > something wrong :) > > >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "If you interrupt the barber while he is cutting your hair, you will >> end up with a messy haircut." >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "One cannot do more than one can do."

Sept. 27, 2009

Re: [Pharo-project] cairo support

by StÃ©phane Ducasse

ok cool! On Sep 27, 2009, at 9:49 AM, Damien Cassou wrote: > On Fri, Sep 25, 2009 at 7:59 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> should we push rome or the cairo graphics package? >> I kno wthat they are not at the same level of abstarction but I >> prefer >> to ask. >> Or should rome be based on the cairo graphics package? > > I'm in favor of pushing the CairoGraphics package and porting Rome > to it. > > -- > 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