- Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: [update] 10470
by StÃ©phane Ducasse Oct. 9, 2009

Oct. 9, 2009

- Issue 1288: CompiledMethod>>#refersToLiteral: returns true for method's own selector fixed a lot of tests. Thanks johan Stef

1 0

[Pharo-project] [ANN] New Aconcagua & Chalten packages
by Gabriel Cotelli Oct. 9, 2009

Oct. 9, 2009

Hi, I'm glad to announce a new release of Aconcagua and Chalten packages that are now Pharo compatible: *[ Aconcagua 2.7 ]* (Aconcagua-HernanWilkinson.2.7.mcz<http://www.squeaksource.com/Aconcagua/Aconcagua-HernanWilkinson.2.7.mcz> ) Changes to fix issues due to changes in Number hierarchy in Pharo (Thanks Hernan for Merging!). http://www.squeaksource.com/Aconcagua *[ Chalten 1.5 ]* (Chalten-GabrielOmarCotelli.1.5.mcz<http://www.squeaksource.com/Chalten/Chalten-GabrielOmarCotelli.1.5.mcz> ) Updated to depend on new Aconcagua version http://www.squeaksource.com/Chalten Regards, Gabriel

3 3

Re: [Pharo-project] Selection in new file list / file system api
by Torsten Bergmann Oct. 8, 2009

Oct. 8, 2009

Colin wrote on squeak-dev: >I've been working on a new filesystem API built on top of the >FilePlugin primitives. >... >if anybody wants to take a look it's here: >http://source.wiresong.ca/mc/Filesystem-cwp.22.mcz Damien also proposed a very small API that allows you to browse the file system easily including tests, just check http://code.google.com/p/pharo/issues/detail?id=1146 Bye Torsten -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 1

[Pharo-project] RFBServer problem
by Dennis Schetinin Oct. 8, 2009

Oct. 8, 2009

Using pharo1.0-10466-BETAweb09.10.1 + RFB-DamienCassou.28 (latest): the image stops to respond after closing connection remotely. Stopping the server (via VNC) leaves image ok. -- Dennis Schetinin

1 0

[Pharo-project] calling for a fixer :)
by StÃ©phane Ducasse Oct. 8, 2009

Oct. 8, 2009

does anyone want to fix SystemNavigationTest>>testIsUnsentMessage Stef

4 11

Re: [Pharo-project] Hierarchy browsers & implementers of
by StÃ©phane Ducasse Oct. 8, 2009

Oct. 8, 2009

I suggest you to read the chapter on the Smalltalk model in the Squeak or pharo by example book the key is: when you look for a message you look in the CLASS of the receiver then its superclasses. So when you look for new sent to Array you should look in the Array class superclasses and you will see it contains Behavior before ProtoObject Stef PS: you can sent to the mailing-list just register to it. You do not need to have a google account. On Oct 7, 2009, at 1:00 PM, Petr VÃ¡cha wrote: > Hi again, > when try to find out that Array>>new: bug I found one thing that I > think > may be very confusing - somehow mangled information from hierarchy > browsers > (see figure). > > Array>>new: calls primitive and uses self>>basicNew: call as fallback. > Array does not implement basicNew: so I tried to find implementors of > it. Behavior has this implementation. However, when you show hierarchy > of Array, it ends in ProtoObject with no Behavior involved. I think > this to be is somewhat confusing for beginners especially when they > are trying to get into method lookup chain. > > Petr Vacha > > > <pharo-browsers.jpg>

3 3

[Pharo-project] Loading Gemstone Variable (Indexable) classes into Pharo via Monticello
by rkrock＠locksleycreeksoftware.com Oct. 8, 2009

Oct. 8, 2009

I have the following in Gemstone: FristClass which is a indexableSublass of Object. SecondClass which is a subclass of FirstClass. When I save this to Monticello and then load it into Pharo, the load fails on the 'recompile' because the SecondClass is not of type #variable. The load works when I modify the method MCClassDefinition>>createClass to use the superclass' type when the superclass type is #variable. --- current way ---- ... type: type; ... --- hacked way ---- .... type: ((superClass typeOfClass isSymbol not and: [superClass typeOfClass isVariable]) ifTrue: [superClass typeOfClass] ifFalse: [type]); .... With this I was sucessfully able to important the code into Pharo. I am able to go from Pharo to GemStone with no problems. Is there a general solution to this problem? It obviously will not occur very often. Regards, Reg

2 1

Oct. 7, 2009

Begin forwarded message: > From: pharo-project-owner(a)lists.gforge.inria.fr > Date: October 6, 2009 8:47:09 PM GMT+02:00 > To: stephane.ducasse(a)free.fr > Subject: next steps... to we create a release candidate and open a > 1.1 alpha? > > You are not allowed to post to this mailing list, and your message has > been automatically rejected. If you think that your messages are > being rejected in error, contact the mailing list owner at > pharo-project-owner(a)lists.gforge.inria.fr. > > > From: stephane ducasse <stephane.ducasse(a)free.fr> > Date: October 6, 2009 8:47:04 PM GMT+02:00 > To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> > Subject: next steps... to we create a release candidate and open a > 1.1 alpha? > > > Hi guys > > I would like to know what are the important bugs or fixes to be > integrated that cannot wait for 1.1. > And it would be nice to tag a release candidate (really soon now). > > We get a pharo sprint the 17 and I would like to get a lot of the > pending fixes integrated > since then and that people can kill some problems on 1.1 > > Stef > > >

4 8

Oct. 7, 2009

10469 ----- - Issue 1287: Polymorph Diff enh - UITheme better comment and auto exec examples! - Issue 985: Speed-up SqNumberParser (Mantis 6976) Merge a few #raisedToInteger: refactoring from trunk for optimizing SqNumberParser. This is related to http://code.google.com/p/pharo/issues/detail?id=985 - Issue 1235: UIManager #request:initialAnswer: returns nil on Cancel instead of empty string

2 3

Oct. 7, 2009

Begin forwarded message: > From: "Gary Chambers" <gary(a)pinesoft.co.uk> > Date: October 7, 2009 12:40:16 PM GMT+02:00 > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: RE: [Pharo-project] problem with updating checkBoxes in morph > > The button inherits from three-phase button and, for "compatability" > also does not call the Morph method for mouseDown (except when > disabled). That is why the event is never triggered. > > Most morphs of the pluggable variety expect to work with proper > model objects, not always easy with a (potentially dynamic) > collection. > Perhaps an intermediate model would be appropriate for each checkbox > that holds the selection state and end-model (some kind of "context" > it seems from his original post). On state change an event could be > triggered (preferred over change/update). > > Perhaps he should be using radio buttons, given the implication of > "one-of-many" (is the same class, just different appearance). > > -----Original Message----- > From: StÃ©phane Ducasse [mailto:stephane.ducasse@inria.fr] > Sent: 07 October 2009 11:23 AM > To: Gary Chambers > Subject: Fwd: [Pharo-project] problem with updating checkBoxes in > morph > > did you notice this strange behavior with checkboxes? >> In this example, when you click on the check box, all the other >> checkboxes should be updated and selected. >> This works when you click on the checkbox label BUT NOT on the >> checkbox button. > > > stef > Begin forwarded message: > >> From: Cyrille Delaunay <cy.delaunay(a)gmail.com> >> Date: October 7, 2009 10:10:07 AM GMT+02:00 >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Re: [Pharo-project] problem with updating checkBoxes in >> morph >> Reply-To: Pharo-project(a)lists.gforge.inria.fr >> >> => this is a small exemple of my problem that you can run in your >> own image (also available in the class side of UITheme by merging >> the 'Polymorph-Widgets' package in the PharoInBox repository) : >> >> exampleProblemUpdatingCheckboxes >> "little example to show the problem with the method >> #on:send:to:with for a CheckboxMorph : >> In this example, when you click on the check box, all the other >> checkboxes should be updated and selected. >> This works when you click on the checkbox label BUT NOT on the >> checkbox button. >> " >> "self exampleProblemUpdatingCheckboxes" >> | builder dialog checkboxes | >> checkboxes := OrderedCollection new. >> builder := ExampleBuilderMorph new. >> dialog := (builder newPluggableDialogWindow: 'Example :') >> useDefaultOKButton . >> >> dialog contentMorph: ( >> dialog newGroupboxForAll: { >> checkboxes add: >> (dialog newCheckboxFor: >> (ValueHolder new contents: false) >> getSelected: #contents >> setSelected: #contents: >> label: '1' >> help: ''). >> checkboxes add: >> (dialog newCheckboxFor: >> (ValueHolder new contents: false) >> getSelected: #contents >> setSelected: #contents: >> label: '2' >> help: ''). >> checkboxes add: >> (dialog newCheckboxFor: >> (ValueHolder new contents: false) >> getSelected: #contents >> setSelected: #contents: >> label: '3' >> help: ''). >> } >> ); model: nil. >> checkboxes do: [:each | each on: #click send: >> #updateCheckboxes:a:b: to: self withValue: checkboxes ]. >> builder openModal: dialog. >> >> => and the method : >> >> updateCheckboxes: collectionOfCheckboxes a:a b:b >> >> collectionOfCheckboxes do: [:each | each buttonMorph selected: >> true]. >> >> >> 2009/10/6 Igor Stasenko <siguctua(a)gmail.com> >> I'm a bit wonder, why you sending a #buttonMorph to checkbox morph, >> trying to intercept >> a messages? >> As to me this is a wrong approach, because you as a user of checkbox, >> should not care >> about its internals, and speak directly with checkbox public layer , >> but not with its internal components. >> >> 2009/10/6 Cyrille Delaunay <cy.delaunay(a)gmail.com>: >> > here is the code of the method creating the checkboxes: >> > checkBoxes := OrderedCollection new. >> > builder := ExampleBuilderMorph new. >> > dialog := (builder newPluggableDialogWindow: 'Context to import :') >> > useDefaultOKButton . >> > dialog contentMorph: ( >> > dialog newRow: { >> > dialog newGroupboxForAll: >> > (self allContexts collect: [:each | (checkBoxes add: (dialog >> > newCheckboxFor: >> > (ValueHolder new >> > contents: (collectionWithItemsToCheck includes: each)) >> > getSelected: #contents >> > setSelected: #contents: >> > label: each asString >> > help: '') >> > ). >> > ]) >> > } >> > ); >> > model: nil. >> > checkBoxes do: [:each | each on: #click send: >> #updateDependenciesFor:i:a: >> > to: self withValue: each label asString]. >> > => That code make what I want when I click on the label, but with: >> > checkBoxes do: [:each | each buttonMorph on: #click send: >> > #updateDependenciesFor:i:a: to: self withValue: each label >> asString]. >> > => nothing happen when I click on the checkbox button. >> > >> > 2009/10/6 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> >> >> >> can you send some text :) >> >> >> >> On Oct 6, 2009, at 2:02 PM, Cyrille Delaunay wrote: >> >> >> >> > I join a screenshot of my code. >> >> > >> >> > 2009/10/6 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> >> > cyrille >> >> > >> >> > do you have a piece of code to illustrate your problem? >> >> > Let me rephrase our discussions: >> >> > >> >> > you can get the associated checkbox event (set by >> >> > on: #click send: #amessage to: receiver) raised only >> >> > when you click on the label but not on the tick. >> >> > >> >> > And that >> >> > checkbox buttonMorph on: #click send: #amessage to: >> receiver, >> >> > is not working on click >> >> > but checkbox buttonMorph on: #mouseDown send: #amessage to: >> >> > receiver, >> >> > is. >> >> > >> >> > >> >> > Stef >> >> > >> >> > >> >> > >> >> > On Oct 6, 2009, at 12:08 PM, Cyrille Delaunay wrote: >> >> > >> >> > > Hi, >> >> > > >> >> > > Here is what I want to do: >> >> > > >> >> > > - I have checkbox: ChekboxMorph new >> >> > > - A checkbox is made of a label and a button >> >> > > - I want to do a specific action when there is a mouse click >> on the >> >> > > button >> >> > > >> >> > > For that: >> >> > > >> >> > > - I saw that there is a method #on:send:to: in Morph with >> wich we >> >> > > can do: >> >> > > >> >> > > checkbox on: #click send: #amessage to: receiver >> >> > > >> >> > > Problem: >> >> > > >> >> > > - when I do >> >> > > checkbox on: #click send: #amessage to: receiver, >> >> > > all is ok. >> >> > > - when I do >> >> > > checkbox buttonMorph on: #click send: #amessage to: >> >> > receiver, >> >> > > to consider the click on the button, it doesn't work, the >> event is >> >> > > never handled (whereas #mouseDown for example is handled). >> >> > > >> >> > > >> >> > > _______________________________________________ >> >> > > 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 >> >> > >> >> > <checkboxes.tiff>_______________________________________________ >> >> > 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 >> > >> > >> > _______________________________________________ >> > 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 > > > > Click here to report this email as spam. > > > > > Ã¼ Consider your responsibility to the environment - think before you > print! > > ******************************************************************************************************************************************* > > This email is from Pinesoft Limited. Its contents are confidential > to the intended recipient(s) at the email address(es) to which it > has been addressed. It may not be disclosed to or used by anyone > other than the addressee(s), nor may it be copied in anyway. If > received in error, please contact the sender, then delete it from > your system. Although this email and attachments are believed to be > free of virus, or any other defect which might affect any computer > or IT system into which they are received and opened, it is the > responsibility of the recipient to ensure that they are virus free > and no responsibility is accepted by Pinesoft for any loss or damage > arising in any way from receipt or use thereof. > > ******************************************************************************************************************************************* > > Pinesoft Limited are registered in England, Registered number: > 2914825. Registered office: 266-268 High Street, Waltham Cross, > Herts, EN8 7EA >

1 0