- Pharo-dev - lists.pharo.org

Re: [Pharo-project] An idea about Pluggable widgets

by Alain Plantec

Hi Igor, I'm not sure to understand. As an example: TrafficLight is my model with an action for the red light. If I build a view for it, I can use a Button with #performAction: Button>> performAction ^ model performAction So, my TrafficLight must implement a #performAction method. Now, if I want also an action for the green light performed when another button is pressed. It means that I've to implement a specific model class for the red and another for the green ? cheers Alain for example, I have a simple UI with two buttons Le 07/04/2011 15:26, Igor Stasenko a Ã©crit : > I have an idea how to refactor the pluggable morphs mess. > > The main principle behind all pluggables, that you have a model (which > is held in instance variable), > and then morph having additional ivars to speak with this model, which > the selector names you should use > to access certain state from model. > > For example: > > AlignmentMorph subclass: #PluggableButtonMorph > instanceVariableNames: 'model label getStateSelector actionSelector > getLabelSelector getMenuSelector shortcutCharacter askBeforeChanging > triggerOnMouseDown offColor onColor feedbackColor > showSelectionFeedback allButtons arguments argumentsProvider > argumentsSelector gradientLook enabled actionBlock getColorSelector > getEnabledSelector' > classVariableNames: 'UseGradientLook' > poolDictionaries: '' > category: 'Morphic-Pluggable Widgets' > > > as you can see it is crowded with all those ivars, where part of them > used to speak with model, > and part of them used for keeping flags and additional parameters > which you can customize when creating a button. > getStateSelector actionSelector getLabelSelector getMenuSelector > arguments argumentsProvider argumentsSelector gradientLook > actionBlock getColorSelector getEnabledSelector > > and this is really messy.. > Take a look at code: > > performAction > "Inform the model that this button has been pressed. Sent by the > controller when this button is pressed. If the button's actionSelector > takes any arguments, they are obtained dynamically by sending the > argumentSelector to the argumentsProvider" > > enabled ifFalse: [^self]. > askBeforeChanging ifTrue: [model okToChange ifFalse: [^ self]]. > self actionBlock ifNotNil: [ ^ self actionBlock value]. > actionSelector ifNotNil: > [actionSelector numArgs == 0 > ifTrue: [model perform: actionSelector] > ifFalse: > [argumentsProvider ifNotNil: > [arguments := argumentsProvider perform: argumentsSelector]. > model perform: actionSelector withArguments: arguments]] > > > Now think if we could replace this with simple: > > > performAction > "Inform the model that this button has been pressed. Sent by the > controller when this button is pressed. If the button's actionSelector > takes any arguments, they are obtained dynamically by sending the > argumentSelector to the argumentsProvider" > > enabled ifFalse: [^self]. > model performAction. > > > so, in this case, we just put an obligation onto model to perform any > action in response to button clicked, > and button no longer cares about crappy logic how it should send a > message to model > (via action block, via actionSelector ... and whether it should pass > any additional arguments or not..) > > So, in all places which using things in a way like: > > getListItems > ^ model perform: getListItemsSelector > > now will be replaced with clean: > > getListItems > ^ model getListItems > > So, a pluggable morph no longer cares about keeping all those > selectors and maintain an obscure logic whether selector is nil or not > nil etc etc.. > Let model handle it! > > Then you may ask, what if i have a model, which doesn't implements > such protocol (required for specific pluggable widget). > The answer is simple: > - create a pluggable model class for given widget, which wraps around > your object and can keeps all those messy 'getLabelSelector' > 'getMenuSelector' , > inside and mediates between your model and widget. > > The benefit of it that widgets code will be much more cleaner. > And another benefit is that you know what exact protocol is needed if > you want to use your object as a model to given widget (list, button > etc). > And in most of the cases, you don't need to use this messy > 'getXYZSelector', because you can simply answer to messages sent by > widget and provide > necessary data. > But if you wanna go messy, you just use wrapper model, which contains > all those 'getXYZSelectors' which you can set to whatever you like. >

April 7, 2011

Re: [Pharo-project] Issue 2269 in pharo: Smalltalk appendChangesTo: 'myfile.sources'

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #4 on issue 2269 by marcus.d...(a)gmail.com: Smalltalk appendChangesTo: 'myfile.sources' http://code.google.com/p/pharo/issues/detail?id=2269 (No comment was entered for this change.)

April 7, 2011

Re: [Pharo-project] Issue 2265 in pharo: to check MCWorkingCopyBrowser from Squeak

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #4 on issue 2265 by marcus.d...(a)gmail.com: to check MCWorkingCopyBrowser from Squeak http://code.google.com/p/pharo/issues/detail?id=2265 (No comment was entered for this change.)

April 7, 2011

Re: [Pharo-project] Issue 2262 in pharo: Pragma Package

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #5 on issue 2262 by marcus.d...(a)gmail.com: Pragma Package http://code.google.com/p/pharo/issues/detail?id=2262 (No comment was entered for this change.)

April 7, 2011

Re: [Pharo-project] Issue 2254 in pharo: sorted and sorted: should be moved to TSortable

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #4 on issue 2254 by marcus.d...(a)gmail.com: sorted and sorted: should be moved to TSortable http://code.google.com/p/pharo/issues/detail?id=2254 (No comment was entered for this change.)

April 7, 2011

Re: [Pharo-project] Issue 2235 in pharo: Character Ä is represented as new line

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #9 on issue 2235 by marcus.d...(a)gmail.com: Character Ä is represented as new line http://code.google.com/p/pharo/issues/detail?id=2235 (No comment was entered for this change.)

April 7, 2011

Re: [Pharo-project] Issue 2176 in pharo: Integrated DirectoryEntry>>attributes

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #4 on issue 2176 by marcus.d...(a)gmail.com: Integrated DirectoryEntry>>attributes http://code.google.com/p/pharo/issues/detail?id=2176 (No comment was entered for this change.)

April 7, 2011

Re: [Pharo-project] Issue 1907 in pharo: Set with nil

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.3 Comment #23 on issue 1907 by marcus.d...(a)gmail.com: Set with nil http://code.google.com/p/pharo/issues/detail?id=1907 (No comment was entered for this change.)

April 7, 2011

Re: [Pharo-project] Metacello chapter

by Serge Stinckwich

Yes this is usual way to propose changes with github. On Thu, Apr 7, 2011 at 7:59 PM, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > I don't know how other authors work. > Not having write access to the repo, I have to fork, make my changes and then ask the admin of the repo (you + who else) to pull (=> merge) changes I made. > > Noury > On 7 avr. 2011, at 09:18, StÃ©phane Ducasse wrote: > >> and so what? I still do not understand it. >> may be noury should be added to the project. >> >> >> On Apr 7, 2011, at 3:28 AM, Serge Stinckwich wrote: >> >>> https://github.com/SquareBracketAssociates/PharoByExample-english/pull/3 >>> >>> On Thu, Apr 7, 2011 at 3:10 AM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>>> Cool. BTW, I have a pending pull request on the Socket chapter. >>>> >>>> what is it? >>>> what do you mean? >>>> what do you need? >>>> >>>> Stef >>>> >>>> >>> >>> >>> >>> -- >>> Serge Stinckwich >>> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam >>> Every DSL ends up being Smalltalk >>> http://doesnotunderstand.org/ >> >> > > Noury Bouraqadi > http://car.mines-douai.fr/noury > -- > -6th National Conference on > âControl Architecture of Robotsâ > 24-25 may 2011, Grenoble area, France > http://car2011.inrialpes.fr/ > > -19th ESUG International Smalltalk Conference > 22-26 August 2011, Edinburgh, UK > http://www.esug.org/Conferences/2011 > > -19Ã¨mes JournÃ©es Francophones sur les SystÃ¨mes Multi-Agents (JFSMAâ11) > http://www.univ-valenciennes.fr/congres/jfsma2011/ > 17-19 Octobre 2011, Valenciennes, France > > > > > > > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

April 7, 2011

Re: [Pharo-project] Decode url form with Zinc-HTTP

by HernÃ¡n Morales Durand

One more thing, I've tried to install in the new released Pharo with CogVM: Gofer new squeaksource: 'ZincHTTPComponents'; package: 'ConfigurationOfZincHTTPComponents'; load. (Smalltalk at: #ConfigurationOfZincHTTPComponents) perform: #load and loading manually the latest Zinc-HTTP from the Monticello Browser. either way I get errors (attached debugger output from the ConfigurationOf script). What is the proper way to install or update to the latest version, Cheers, 2011/4/7 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > Cool. Thanks Sven! > > 2011/4/7 Sven Van Caekenberghe <sven(a)beta9.be>: >> HernÃ¡n, >> >> From the class comment of ZnUrl: >> >> [...] >> >> Â Â Â Â The methods in accessing protocols do not do any encoding, those in printing do. >> >> [...] >> >> Taking your example: >> >> Â (ZnUrl fromString: >> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26…') pathSegments >> >> Â Â Â Â an OrderedCollection('entrez' 'eutils' 'esearch.fcgi?db=nuccore&term=science[journal]+AND+breast+cancer+AND+2009[pdat]') >> >> (ZnUrl fromString: >> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26…') path >> >> Â Â Â Â 'entrez/eutils/esearch.fcgi?db=nuccore&term=science[journal]+AND+breast+cancer+AND+2009[pdat]' >> >> (ZnUrl fromString: >> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26…') printString >> >> Â Â Â Â 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26…' >> >> If you inspect a ZnUrl instance you will notice that the internal Smalltalk representation is unencoded. But its #printString and the argument to #fromString: are. You could programmatically build up a ZnUrl using accessors and supplying unencoded (path) elements. >> >> HTH, >> >> Sven >> >> On 06 Apr 2011, at 22:38, HernÃ¡n Morales Durand wrote: >> >>> Hi Sven, >>> >>> In WebUtils one can decode an URL this way >>> >>> ( WebUtils decodeUrlEncodedForm: >>> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26…' >>> ) keys anyOne >>> >>> resulting in >>> >>> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi?db=nuccore&term=s…' >>> >>> In Zinc-HTTP I didn't find a method for decoding an encoded HTTP address: >>> >>> ( ZnUrl fromString: >>> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26…' >>> ) .... ? >>> >>> but there is #unescapePercents in Network package (by the way if it's >>> the opposite of #encodeForHTTP shouldn't be #decodeFromHTTP ?) >>> >>> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi%3Fdb%3Dnuccore%26…' >>> unescapePercents >>> >>> 'http://eutils.ncbi.nlm.nih.gov/entrez/eutils/esearch.fcgi?db=nuccore&term=s…' >>> >>> but I want to maximize package dependency and not system dependency. >>> Is there a way to decode url's in Zinc-HTTP without use >>> #unescapePercents ? >>> >>> Cheers, >>> >>> -- >>> HernÃ¡n Morales >>> Information Technology Manager, >>> Institute of Veterinary Genetics. >>> National Scientific and Technical Research Council (CONICET). >>> La Plata (1900), Buenos Aires, Argentina. >>> Telephone: +54 (0221) 421-1799. >>> Internal: 422 >>> Fax: 425-7980 or 421-1799. >>

April 7, 2011