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

[Pharo-project] next steps... to we create a release candidate and open a 1.1 alpha?
by StÃ©phane Ducasse Oct. 7, 2009

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

[Pharo-project] [update] #10469
by StÃ©phane Ducasse Oct. 7, 2009

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

[Pharo-project] Fwd: problem with updating checkBoxes in morph
by StÃ©phane Ducasse Oct. 7, 2009

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

[Pharo-project] Linux so
by Schwab,Wilhelm K Oct. 7, 2009

Oct. 7, 2009

Hello all, Some dumb questions related to my ongoing migration away from Windows. Something that I have found useful is to write numerical analysis code (internally using templates, streams, etc.) in C++, and then compile them as extern "C" something like extern "C" _export void DoSomething(float * data, int rows, int columns) { // C++ specifics are legal herein; arguments // and return type must be legal for C - e.g. no references // and no classes; structs are ok. } On Windows with MinGW, the exporting of the function above seems to be almost magically easy. Do similar tricks work on Linux? On Linux, I intend to use gcc and Code::Blocks, unless somebody has a better idea. I bring this up in part because some things (tight loops) are best left to statically typed languages, C++ has a slight edge over Smalltalk on syntax for translating equations, I already have a lot of working C++ code, and I might be able to ease into getting GSL talking to Pharo before having to tackle the entire interface. I am hoping to add something to an evolving library, recompile, and perhaps after restarting Pharo have access to the new function(s) with fairly little hassle. Is that reasonable to ask? Any advice or warnings? Bill

1 0

[Pharo-project] [ANN] SmalltalkParty in Paris on 28 november
by Noury Bouraqadi Oct. 7, 2009

Oct. 7, 2009

Hi, For the 8th year, the French Smalltalk Users Group is holding a SmalltalkParty in Paris on Saturday the 28th november 2009. All Smalltalkers are welcome. The entrance is free. More on-line http://community.ofset.org/index.php/Smalltalk_Party_Paris_2009 Noury http://vst.ensm-douai.fr/noury/ -------------- -17Ã¨mes JournÃ©es Francophones sur les SystÃ¨mes Multi-Agents (JFSMAâ09). Lyon, 19-21 Octobre 2009 http://bat710.univ-lyon1.fr/~sycosma/JFSMA09/ -8Ã¨me SmalltalkParty. Paris, 28 novembre 2009. http://community.ofset.org/index.php/Smalltalk_Party_Paris_2009 -2nd International Workshop on Agent Technology for Disaster Management (ATDM'09), Nagoya, Japan, Dec. 13rd, 2009 http://doesnotunderstand.org/wikka.php?wakka=ATDM2009 -16Ã¨me ConfÃ©rence francophone sur les Langages et ModÃ¨les Ã Objets (LMO). Pau 2010 http://lmo-conference.org/2010 -ESUG 18th International Smalltalk Conference - Barcelona, Spain 2010 http://www.esug.org/Conferences/2010

1 0

[Pharo-project] Examples for UITheme
by Cyrille Delaunay Oct. 7, 2009

Oct. 7, 2009

Hi, I have added comments to the UITheme classe description and into the examples methods, to evaluate directly the examples. I have saved that in 'PharoInBox' in squeaksource.

3 6

[Pharo-project] I introduced two new tags
by StÃ©phane Ducasse Oct. 7, 2009

Oct. 7, 2009

milestone-1.0-devImage to make sure that we do not miss 1.0 issue but related to the image Stef

1 0

Oct. 7, 2009

Hi guys could we have a summary on the alternatives related to number parser http://code.google.com/p/pharo/issues/detail?id=1258 so that we can take a decision? Stef

1 0

[Pharo-project] problem with updating checkBoxes in morph
by Cyrille Delaunay Oct. 7, 2009

Oct. 7, 2009

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).

3 6

[Pharo-project] [update] #10468
by Damien Cassou Oct. 7, 2009

Oct. 7, 2009

10468 ----- Issue 275: TODO: remove OldSocket -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

2 3