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

Re: [Pharo-project] Standardisation of Interfaces within Pharo/Squeak ...

by Adrian Lienhard

This is http://code.google.com/p/pharo/issues/detail?id=657 Please use the issue tracker to report/discuss problems (in addition to the mailing list). Also note that any help is welcome, even if it is only to check if a proposed fix works. Cheers, Adrian On May 11, 2009, at 20:30 , Mariano Martinez Peck wrote: >> >> >> And i can't close that window "World->System->About" at 1024x768 >> resolution .... hmmm .... >> > > Yes. Me too. I have to do ctrl + w. > > >> >> tnx, Guido Stepken >> >> _______________________________________________ >> 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

May 11, 2009

Re: [Pharo-project] Standardisation of Interfaces within Pharo/Squeak ...

by Mariano Martinez Peck

> > > And i can't close that window "World->System->About" at 1024x768 > resolution .... hmmm .... > Yes. Me too. I have to do ctrl + w. > > tnx, Guido Stepken > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 11, 2009

[Pharo-project] Standardisation of Interfaces within Pharo/Squeak ...

by stepken

Hello! Don't know, how much sense it makes, when i ask for "standardisation", portability .... There are a few (less active) projects floating around in the world wide waiste, e.g. SPORT: http://sourceforge.net/projects/sport/ http://camp.smalltalk.org/ Even within Squeak i had several incompatibilities with .pr files. I really hate that. We here have/had the smtalltalk elite at work, seeming being unable to solve such standard problems ... Second problem: Monticello is not failsafe. I slowed down my internet connection and pulled the plug from time to time during download of updates ... What happened? .... Errors, unresolvable ... I had to shut down Pharo, to repeat the update. I would call that "not transactional ...", "failsafe", "whatever" ....... Please ... you mastersmalltalkers ... this is a minimum standard to be fullfilled nowadays ... And i can't close that window "World->System->About" at 1024x768 resolution .... hmmm .... tnx, Guido Stepken

May 11, 2009

[Pharo-project] [ANN] 10302

by StÃ©phane Ducasse

- issue 799: Speed up of highBit and lowBit for SmallInteger http://code.google.com/p/pharo/issues/detail?id=799 http://bugs.squeak.org/view.php?id=7113 - Issue 796 Patch for issue http://code.google.com/p/pharo/issues/detail?id=796 Float rounded is inexact - Issue 800: Fix issue http://code.google.com/p/pharo/issues/detail?id=800 mantis http://bugs.squeak.org/view.php?id=6986 Mantis 6986: SystemNavigation browseAllMethodsInCategory: does it wrong - issue 802: Fix for http://code.google.com/p/pharo/issues/detail?id=802 Mantis http://bugs.squeak.org/view.php?id=6983 There is no way to store Float nan as a literal. So Float nan isLiteral should answer false. Note that there are still literal representation of Float infinity, like 1.0e1000. However, since Float infinity is not able to print literaly, and isLiteral is intended for print, this fix will answer false for infinite Floats too. Tx nicolas! Stef

May 11, 2009

Re: [Pharo-project] Towards Pharo 1.0

by StÃ©phane Ducasse

But hilaire the closure got integrated so now they are in. I think that third party tools should have a look and try and report problems. Stef On May 11, 2009, at 6:17 PM, Hilaire Fernandes wrote: > I don't know how well tested/stable could be the closure change > (expecially with third party packages as seaside, Magma or other DB > backend) but if unsure it may be wise to keep it for a latter > release, people may want first stability for a 1.0 to start > productivity project with. > > Hilaire > > > 2009/5/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >>> > > Hi guys > > Here are the discussions we forgot to get on the list :) > > > >> I was thinking that I would not do the license cleaning for 1.0 > > > > Yes, I agree. We can do this in 1.1, which can follow shortly after > > 1.0. Any objections from Marcus, Mike? > > > > What is the status of "Main EToys removal, reorganize > > MorphicExtras-"? Do you plan to do more for 1.0? > > > > Apart from that we have left on our list (http://code.google.com/p/pharo/wiki/Milestones > > ): > > > > - default in-image font(s) > > - Package management system with stable and unstable distributions > > - Remove SqueakMap and Installer from core > > > > - All tests green > > - Clean up package and class category organization > > - Pharo one-click image (including developer tools, GettingStarted > > information, screenshots, ...) > > - New sources file > > > > Are we going to integrate the new preference system/browser in 1.0? > > > >> Now we are waiting for eliot closures changes. > > > > What kind of changes are theses? Did he say something about when > > they will be ready? > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > http://blog.ofset.org/hilaire > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 11, 2009

[Pharo-project] [ANN] 10301

by StÃ©phane Ducasse

- More collection tests - fixed trait merging Stef

May 11, 2009

Re: [Pharo-project] Towards Pharo 1.0

by Hilaire Fernandes

I don't know how well tested/stable could be the closure change (expecially with third party packages as seaside, Magma or other DB backend) but if unsure it may be wise to keep it for a latter release, people may want first stability for a 1.0 to start productivity project with. Hilaire 2009/5/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >>> > > Hi guys > > Here are the discussions we forgot to get on the list :) > > > >> I was thinking that I would not do the license cleaning for 1.0 > > > > Yes, I agree. We can do this in 1.1, which can follow shortly after > > 1.0. Any objections from Marcus, Mike? > > > > What is the status of "Main EToys removal, reorganize > > MorphicExtras-"? Do you plan to do more for 1.0? > > > > Apart from that we have left on our list ( > http://code.google.com/p/pharo/wiki/Milestones > > ): > > > > - default in-image font(s) > > - Package management system with stable and unstable distributions > > - Remove SqueakMap and Installer from core > > > > - All tests green > > - Clean up package and class category organization > > - Pharo one-click image (including developer tools, GettingStarted > > information, screenshots, ...) > > - New sources file > > > > Are we going to integrate the new preference system/browser in 1.0? > > > >> Now we are waiting for eliot closures changes. > > > > What kind of changes are theses? Did he say something about when > > they will be ready? > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- http://blog.ofset.org/hilaire

May 11, 2009

[Pharo-project] Traits Merging problem

by StÃ©phane Ducasse

Hi I want to report that if you try to merge code containing traits you get a DNU. I get a reproduceable bug: try to merge the collectiontext in the PharoTaskForces project. Stef

May 11, 2009

Re: [Pharo-project] Error when trying to create a package

by Keith Hodges

Alexandre Bergel wrote: > The temporary variable is there in case that Installer is not > installed. It assumes that ScriptLoader is present. > > Cheers, > Alexandre > Installer is intended to be the first and only dependency in a minimal system. i.e. you are using ScriptLoader to do Installer's job Keith

May 11, 2009

Re: [Pharo-project] Error when trying to create a package

by Keith Hodges

Alexandre Bergel wrote: > This is what we've been doing for long time... > > Alexandre > > > Yes I know, that's why it is so annoying. Keith

May 11, 2009