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

Re: [Pharo-project] Examples for UITheme

by StÃ©phane Ducasse

which file in the inbox? You see been more precise make sure that we are not losing time. Stef On Oct 2, 2009, at 4:32 PM, Cyrille Delaunay wrote: > 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. > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 7, 2009

Re: [Pharo-project] Examples for UITheme

by StÃ©phane Ducasse

which one? because I cannot find it Thanks On Oct 2, 2009, at 4:44 PM, Cyrille Delaunay wrote: > It's done :) > > 2009/10/2 Marcus Denker <denker(a)acm.org> > > On 02.10.2009, at 10:32, Cyrille Delaunay wrote: > > > 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. > > Can you add an entry in the issue tracker for that? > > Marcus > > > > > -- > Marcus Denker - http://marcusdenker.de > PLEIAD Lab - Computer Science Department (DCC) - University of Chile > > > _______________________________________________ > 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

Oct. 7, 2009

[Pharo-project] I introduced two new tags

by StÃ©phane Ducasse

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

Oct. 7, 2009

[Pharo-project] About number parser

by StÃ©phane Ducasse

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

Oct. 7, 2009

Re: [Pharo-project] problem with updating checkBoxes in morph

by Cyrille Delaunay

=> 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 >

Oct. 7, 2009

Re: [Pharo-project] next steps... to we create a release candidate and open a 1.1 alpha?

by StÃ©phane Ducasse

yes this is why I'm holding the horses :) now I think that we could have a release candidate soon and do not wait for the sprint and we can iterate. the first things is to really go over the issues list and retag it. stef On Oct 7, 2009, at 9:36 AM, Adrian Lienhard wrote: > > On Oct 7, 2009, at 09:23 , StÃ©phane Ducasse wrote: > > [...] > >> ok but I would really like to integrate all the cool fixes of >> nicolas. >> so this is why I was thinking about 1.1 alpha. too > > Then we could open a new stream already now. We just have to take care > that we don't forget to finish 1.0! ;) > We also need to think about the process: if there is a fix we will > have to decide whether it is critical and hence also needs to go into > the maintenance stream of 1.0. So one fix suddenly needs to be > integrated twice... > > Adrian > >> >> Stef >> >> _______________________________________________ >> 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

Oct. 7, 2009

Re: [Pharo-project] next steps... to we create a release candidate and open a 1.1 alpha?

by Adrian Lienhard

On Oct 7, 2009, at 09:23 , StÃ©phane Ducasse wrote: [...] > ok but I would really like to integrate all the cool fixes of nicolas. > so this is why I was thinking about 1.1 alpha. too Then we could open a new stream already now. We just have to take care that we don't forget to finish 1.0! ;) We also need to think about the process: if there is a fix we will have to decide whether it is critical and hence also needs to go into the maintenance stream of 1.0. So one fix suddenly needs to be integrated twice... Adrian > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 7, 2009

Re: [Pharo-project] next steps... to we create a release candidate and open a 1.1 alpha?

by StÃ©phane Ducasse

apparently there is a bug in senders would be good to investigate that. >> ok. I think we should seriously check the remaining errors/failures > before marking them. > >> I would like to see a few process things discussed >> -how we maintain 1.0 stable branch >> -how we maintain 1.1 alpha. i.e do we try out some other package meta >> system? that could be worth some hacking at the start of the cycle to >> see the mechanism. It is not something to mess around with when we >> get >> near beta. > > We can use the current update stream as the 1.0 stable branch and > create a new stream, maybe based on another mechanism, for 1.1 alpha. > > I think we should get all tests green and the remaining issues fixed > before declaring a release candidate. There are also 3 OmniBrowser > issues in the list and I wonder whether somebody plans to fix them? If > we concentrate on these tasks in the next days and during the sprint, > I am sure we are able to get a reasonable RC1 within the next 14 days. ok but I would really like to integrate all the cool fixes of nicolas. so this is why I was thinking about 1.1 alpha. too Stef

Oct. 7, 2009

Re: [Pharo-project] next steps... to we create a release candidate and open a 1.1 alpha?

by Adrian Lienhard

Hi Mike, On Oct 6, 2009, at 22:36 , Michael Roberts wrote: > i would mark the decompiler tests as 1.1. I would also mark the > debugger highlight bug as 1.1. I think these are going to take time. I agree. Do you want to update the tracker? > then we have to review the sunits and see what is realistic to fix and > what is 'unknown'. I noticed that after the recent closure fixes there are a couple of new failures and errors. For instance AuthorTest>>#testDeprecatedSendsRemoved (I guess the reported senders of a selector changed with some closure changes). see http://code.google.com/p/pharo/wiki/BaselineTestResults > For everything we don't understand mark and > comment #expectedFailures. what would be really helpful would be any > writeup on the issue tracker for analysis on sunit failures if folks > have time. ok. I think we should seriously check the remaining errors/failures before marking them. > I would like to see a few process things discussed > -how we maintain 1.0 stable branch > -how we maintain 1.1 alpha. i.e do we try out some other package meta > system? that could be worth some hacking at the start of the cycle to > see the mechanism. It is not something to mess around with when we get > near beta. We can use the current update stream as the 1.0 stable branch and create a new stream, maybe based on another mechanism, for 1.1 alpha. I think we should get all tests green and the remaining issues fixed before declaring a release candidate. There are also 3 OmniBrowser issues in the list and I wonder whether somebody plans to fix them? If we concentrate on these tasks in the next days and during the sprint, I am sure we are able to get a reasonable RC1 within the next 14 days. Cheers, Adrian > cheers, > Mike > > 2009/10/6 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >> >> 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 >> >> >> >> >> >> _______________________________________________ >> 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

Oct. 7, 2009

Re: [Pharo-project] [update] #10468

by StÃ©phane Ducasse

On Oct 6, 2009, at 11:55 PM, Damien Cassou wrote: > On Tue, Oct 6, 2009 at 12:44 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> cool damien nice to see you integrating fixes :) > > I also enhanced the release process in the middle :-). I saw that :) > The message > that appears at the very end was something like: > > You now have to > 1) ./upFile <changeset> > ... > > <changeset> is now replaced by the name of the changeset file :-) > > -- > 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

Oct. 7, 2009