- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Fixes for Numbers are ready (toward ANSI)

by Nicolas Cellier

2009/6/11 Alain Plantec <alain.plantec(a)free.fr>: > Nicolas Cellier a Ã©crit : >> 2009/6/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >>> thanks nicolas >>> BTW did you got feedback about this one? >>> http://code.google.com/p/pharo/issues/detail?id=860&colspec=ID%20Type%20Sta… >>> >> >> None yet. I only see 3 explanations: >> - everyone is busy, dead, in hollidays, in the garden, etc... >> - everyone disabled the preference for generating the error log >> - I'm the only one doing bugs, no one else ever seen a slow Notifier >> > :) > Hi Nicolas, > sorry for the stupid question but what are you asking testers to do ? > I've loaded the 4 .cs, verified that the preference is on and evaluated 0/0. > seen a notifier, click on proceed and get a SqueakDebug.log. > and then what ? > thanks > Alain > The speed should increase, that's what the patch is all for. I don't know what test Stef wants exactly, I see two possibilities: -1) review the changes -2) install the changes and do normal activity, report if any trouble Nicolas > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 12, 2009

Re: [Pharo-project] Fwd: to go beta?

by Serge Stinckwich

On Fri, Jun 12, 2009 at 3:19 AM, Adrian Lienhard<adi(a)netstyle.ch> wrote: > That's a good question I was also thinking about today... > > I suggest the following steps: > > 1. Review all issues in the tracker and decide for each whether it is > important for 1.0. > 2. We concentrate on completing these 1.0-tagged items. New issues > should only be tagged with 1.0 if they are critical bugs (i.e., no new > improvements get integrated anymore!) > 3. As soon as we have completed all items that change the behavior of > the system (i.e., that are not bugfixes) we declare beta > 4. As soon as all items are done, we declare gamma and after a while > without newly reported problems we release 1.0 What could be great is a release during next ESUG conference in september. -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

June 12, 2009

Re: [Pharo-project] a plea for "save and quit"

by Hernan Wilkinson

I like this one too.I don't like "Save" ..> "Save", "Save as".. etc, to much cliks (or moves) just to save On Thu, Jun 11, 2009 at 9:17 AM, Alain Plantec <alain.plantec(a)free.fr>wrote: > Tudor Girba a Ã©crit : > > "Save" > > "Save as..." > > "Save and quit" > > ----- > > "Quit > Hi all, > I like this simple proposition. > We still have 'recover lost changes' in the case of unwanted quit > without saving. > alain > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 12, 2009

Re: [Pharo-project] multiple native windows

by Carlos Crosetti

I tried wxsqueak. Demos ar really good, and populating a grid with miliions of rows is very fast, however you have to turn your mind to build so defensively... I crashed the wm 3 to 4 times in around 4 hours - effort,m then I gave up. -----Mensaje original----- De: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr]En nombre de Mariano Martinez Peck Enviado el: Jueves, 11 de Junio de 2009 12:25 p.m. Para: Pharo-project(a)lists.gforge.inria.fr Asunto: Re: [Pharo-project] multiple native windows Perhaps you can join forces with the rest of the present alternatives. For example, squeakgtk I think there is a lot of people that wants native windows so that being able to create desktop applications. Cheers, Mariano 2009/6/11 Steve Wirts <stevewirts(a)gmail.com> If the primitives existed in pharo that would allow someone to create and control native windows, I would be more than happy to take the time to try and massage morphic into working cleanly/elegantly with multiple windows. On Thu, Jun 11, 2009 at 10:44 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: On Thu, Jun 11, 2009 at 4:38 PM, Michael Rueger<m.rueger(a)acm.org> wrote: > Also the GTK bindings and Newspeak use native windows (I > think?). Newspeak uses either native or morphic windows, depending on the wishes of the user. -- 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 _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 12, 2009

Re: [Pharo-project] Fwd: to go beta?

by Gabriel Cotelli

I will try to rewrite this week the last dirty method (according to my count)... so the 1.0 should be license clean... . After this maybe I could help with some bugs. On Thu, Jun 11, 2009 at 5:19 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > That's a good question I was also thinking about today... > > I suggest the following steps: > > 1. Review all issues in the tracker and decide for each whether it is > important for 1.0. > 2. We concentrate on completing these 1.0-tagged items. New issues > should only be tagged with 1.0 if they are critical bugs (i.e., no new > improvements get integrated anymore!) > 3. As soon as we have completed all items that change the behavior of > the system (i.e., that are not bugfixes) we declare beta > 4. As soon as all items are done, we declare gamma and after a while > without newly reported problems we release 1.0 > > Adrian > > On Jun 11, 2009, at 21:59 , StÃ©phane Ducasse wrote: > > >> > >> Marcus, Adrian, Mike > >> how do we proceed to go beta? > >> take the 1.0 fixes and integrate them. > >> put a deadline and do it? > >> > >> 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 >

June 11, 2009

[Pharo-project] [update] #10335

by Marcus Denker

#10335 ====== Issue 645: Project exportSegmentWithChangeSet:fileName:directory: calls: writeStackText:in:registerIn: Issue 642: Project enterAsActiveSubprojectWithin: calls: okayToEnterProject Issue 644: Project displayZoom: calls: playProjectTransitionFrom:to:entering: Issue 641: Debugger abandon: calls: controller Issue 646: Parser parse:class: calls: parseError Issue 702: check Preferences overrides from closure changes Issue 746: missing package for Closure and friends Issue 878: fixes for newparser parsability -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

June 11, 2009

Re: [Pharo-project] Fixes for Numbers are ready (toward ANSI)

by Alain Plantec

Nicolas Cellier a Ã©crit : > 2009/6/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> thanks nicolas >> BTW did you got feedback about this one? >> http://code.google.com/p/pharo/issues/detail?id=860&colspec=ID%20Type%20Sta… >> > > None yet. I only see 3 explanations: > - everyone is busy, dead, in hollidays, in the garden, etc... > - everyone disabled the preference for generating the error log > - I'm the only one doing bugs, no one else ever seen a slow Notifier > :) Hi Nicolas, sorry for the stupid question but what are you asking testers to do ? I've loaded the 4 .cs, verified that the preference is on and evaluated 0/0. seen a notifier, click on proceed and get a SqueakDebug.log. and then what ? thanks Alain

June 11, 2009

Re: [Pharo-project] Fwd: to go beta?

by Adrian Lienhard

That's a good question I was also thinking about today... I suggest the following steps: 1. Review all issues in the tracker and decide for each whether it is important for 1.0. 2. We concentrate on completing these 1.0-tagged items. New issues should only be tagged with 1.0 if they are critical bugs (i.e., no new improvements get integrated anymore!) 3. As soon as we have completed all items that change the behavior of the system (i.e., that are not bugfixes) we declare beta 4. As soon as all items are done, we declare gamma and after a while without newly reported problems we release 1.0 Adrian On Jun 11, 2009, at 21:59 , StÃ©phane Ducasse wrote: >> >> Marcus, Adrian, Mike >> how do we proceed to go beta? >> take the 1.0 fixes and integrate them. >> put a deadline and do it? >> >> Stef >> >> >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 11, 2009

Re: [Pharo-project] Fixes for Numbers are ready (toward ANSI)

by StÃ©phane Ducasse

On Jun 11, 2009, at 10:02 PM, Nicolas Cellier wrote: > 2009/6/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> thanks nicolas >> BTW did you got feedback about this one? >> http://code.google.com/p/pharo/issues/detail?id=860&colspec=ID%20Type%20Sta… > > None yet. I only see 3 explanations: > - everyone is busy, dead, in hollidays, in the garden, etc... Dead busyz dead = stef > - everyone disabled the preference for generating the error log > - I'm the only one doing bugs, no one else ever seen a slow Notifier > > Maybe I should submit to squeak-dev, but the list seems rather quiet > these times. > > Nicolas > > >> >> On Jun 11, 2009, at 9:24 PM, Nicolas Cellier wrote: >> >>> I cumulated the changes in this order: >>> >>> http://code.google.com/p/pharo/issues/list?id=874 >>> PharoInbox/SLICE-Mantis6985-Issue874-Integer-bitAt-nice.1 >>> add Integer #bitAt: >>> >>> http://code.google.com/p/pharo/issues/list?id=875 >>> PharoIbox/SLICE-Mantis6601-Issue875-Float-hash-nice.1 >>> fix Float hash >>> >>> http://code.google.com/p/pharo/issues/list?id=876 >>> PharoInbox/SLICE-Mantis3374-Issue876-Arithmetic-Equality-transitive- >>> Part1-nice.1 >>> PharoInbox/SLICE-Mantis3374-Issue876-Arithmetic-Equality-transitive- >>> Part2-nice.1 >>> fix number equal transitivity (and further change Fraction hash) >>> >>> http://code.google.com/p/pharo/issues/detail?id=681 >>> PharoInbox/SLICE-Mantis6982-Issue681-Number-readFrom-nice.1 >>> connect SqNumberParser in Number readFrom: (with backward >>> compatibility) >>> >>> http://code.google.com/p/pharo/issues/list?id=879 >>> PharoInbox/SLICE-Issue879-ANSI-FloatCharacterization-nice.1 >>> add ANSI Float Characterization >>> >>> Please review :) >>> >>> Nicolas >>> >>> _______________________________________________ >>> 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 >

June 11, 2009

Re: [Pharo-project] Fixes for Numbers are ready (toward ANSI)

by Nicolas Cellier

2009/6/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > thanks nicolas > BTW did you got feedback about this one? > http://code.google.com/p/pharo/issues/detail?id=860&colspec=ID%20Type%20Sta… None yet. I only see 3 explanations: - everyone is busy, dead, in hollidays, in the garden, etc... - everyone disabled the preference for generating the error log - I'm the only one doing bugs, no one else ever seen a slow Notifier Maybe I should submit to squeak-dev, but the list seems rather quiet these times. Nicolas > > On Jun 11, 2009, at 9:24 PM, Nicolas Cellier wrote: > >> I cumulated the changes in this order: >> >> http://code.google.com/p/pharo/issues/list?id=874 >> PharoInbox/SLICE-Mantis6985-Issue874-Integer-bitAt-nice.1 >> add Integer #bitAt: >> >> http://code.google.com/p/pharo/issues/list?id=875 >> PharoIbox/SLICE-Mantis6601-Issue875-Float-hash-nice.1 >> fix Float hash >> >> http://code.google.com/p/pharo/issues/list?id=876 >> PharoInbox/SLICE-Mantis3374-Issue876-Arithmetic-Equality-transitive- >> Part1-nice.1 >> PharoInbox/SLICE-Mantis3374-Issue876-Arithmetic-Equality-transitive- >> Part2-nice.1 >> fix number equal transitivity (and further change Fraction hash) >> >> http://code.google.com/p/pharo/issues/detail?id=681 >> PharoInbox/SLICE-Mantis6982-Issue681-Number-readFrom-nice.1 >> connect SqNumberParser in Number readFrom: (with backward >> compatibility) >> >> http://code.google.com/p/pharo/issues/list?id=879 >> PharoInbox/SLICE-Issue879-ANSI-FloatCharacterization-nice.1 >> add ANSI Float Characterization >> >> Please review :) >> >> Nicolas >> >> _______________________________________________ >> 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 >

June 11, 2009