- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo splash

by StÃ©phane Ducasse

On May 15, 2009, at 3:12 PM, Damien Cassou wrote: > Thank you, I think that will be useful for the Pharo release. > > 2009/5/15 Torsten Bergmann <astares(a)gmx.de>: >> Sorry for bloating your mailbox but in case >> someone is in the need for a splash screen >> for presenting Pharo you will find one attached. >> >> Otherwise delete this mail. This is also in >> preparation of a Win32 setup bundle. >> >> On Win32 you can enable the splash using the >> Squeak/Pharo.ini file (see [1]) >> >> Thx >> T. >> >> [1] http://www.squeakvm.org/win32/settings.html >> >> -- >> Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + >> Telefonanschluss fÃ¼r nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > 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 >

May 15, 2009

Re: [Pharo-project] Inspect it wrong shortcut

by Mariano Martinez Peck

On Fri, May 15, 2009 at 4:25 PM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > 2009/5/14 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > Can someone confirm this ? > > This is fixed in recent versions. > Are you sure? It still doesn't work for me. Note that inspect it is the only one that doesn't work. It seems that inspect is inverse to all the other. When the rest of the shortcuts work with ctrl, inspect it work with alt and viceversa. Greetings, Mariano > > -- > 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 >

May 15, 2009

Re: [Pharo-project] Helping getting pharo license-clean

by Yoshiki Ohshima

> I also applied all of yoshiki's etoys changes to 3.10.2. The > algorithm that Yoshiki seemed to follow when cleaning etoys is: > - If the method can be easily deleted, delete it > - Otherwise, use the historical image [1] to revert to the > latest version before the problematic author > - Fix any bugs this causes > > I think we can use the same procedure. Perhaps Yoshiki will > comment. Perhaps^^; Does Pharo have ScaledDecimal and it is used? If so, that would be the biggest piece that would be removed. There wouldn't be any serious bugs that would cause major trouble otherwise. > On Wed, Apr 22, 2009 at 11:10:12AM +0200, stephane ducasse wrote: > > I need your guidance for the MIT conversion effort of Pharo > > Do you have some cycles to help me and telling me how to proceed? > > I'm on holidays (so working remotely so I may allocate some time on > > that). > > I can help you after school gets out in a week. I need to > do a quick count of how many lines of code need to be fixed in > squeak for submission to SFLC. I can do the same for Pharo. I > don't know how strenuous you want to be in your license > conversion. What is the reason for Pharo to go with SFLC? > You should chat with Randal Schwartz about what you need to > decide before you can start relicensing, and what you need to > document in case your relicense needs to be reviewed in the > future. Yoshiki and Juan did not do this and thus we have no > evidence yet that Yoshiki's relicense is strong enough. There will be no such evidence. There will be no evidence for a statement like "there is no white crow". -- Yoshiki

May 15, 2009

[Pharo-project] vw inspired gui tool

by Steve Wirts

Folks, Attached is a very simple gui tool inspired from a tool that used to exist in VW smalltalk years ago. I suspect it could be rewritten as a single function. Please incorporate into Pharo if you think it's useful. Steve

May 15, 2009

[Pharo-project] Helping getting pharo license-clean

by StÃ©phane Ducasse

Hi all (and matthew we need your guidance/help) We really want to get pharo 1.0 license clean. It would be bad that 1.0 is not. But 1.0 should get out before summer. Here is a collection of all the information I collected on the topic: Here what matthew wrote I've done the first step and done a full audit, using Yoshiki's tools [1], of all the code in Squeak 3.10.2, with the exception of four packages: - Monticello - SUnit, TestRunner, and SUnitImproved - Universes - Traits I also applied all of yoshiki's etoys changes to 3.10.2. The algorithm that Yoshiki seemed to follow when cleaning etoys is: - If the method can be easily deleted, delete it - Otherwise, use the historical image [1] to revert to the latest version before the problematic author - Fix any bugs this causes I think we can use the same procedure. Perhaps Yoshiki will comment. So, to help with the relicense, grab the historical image[1], check out the license audit [2], leave a note on mantis about what you think you'll work on, and start rolling out change sets. For your convenience, all of the license audits are included both in the relicensing tools download and on mantis. I'll try to keep both up to date as we progress with the relicense [1] The tools I've been using to do the relicense: http://ftp.squeak.org/4.0alpha/squeak4.0-relicensingTools.zip see also: http://lists.squeakfoundation.org/pipermail/squeak-dev/2008-September/13158… http://www.squeaksource.com/MethodAuthorship.html [2] The 4.0 relicense mantis issue: http://bugs.squeak.org/view.php?id=6989 The most up-to-date list of ok contributors is at http://www.squeaksource.com/311/MethodAuthorship-kph.17.mcz See the class-side methods in Authorship, category data here is another email from matthew On Wed, Apr 22, 2009 at 11:10:12AM +0200, stephane ducasse wrote: > I need your guidance for the MIT conversion effort of Pharo > Do you have some cycles to help me and telling me how to proceed? > I'm on holidays (so working remotely so I may allocate some time on > that). I can help you after school gets out in a week. I need to do a quick count of how many lines of code need to be fixed in squeak for submission to SFLC. I can do the same for Pharo. I don't know how strenuous you want to be in your license conversion. The next 3 steps in the license conversion process are, in no particular order: - get a document from yoshiki documenting how etoys was relicensed (and, by extension, cuis). The board will overview it with the help of SFLC and determine if it is good enough. - The board will publish a statement about what is and is not a trivial-enough change to ignore. - I will count up the lines of code to be converted, and determine how many of them are trivial and non-trivial You should chat with Randal Schwartz about what you need to decide before you can start relicensing, and what you need to document in case your relicense needs to be reviewed in the future. Yoshiki and Juan did not do this and thus we have no evidence yet that Yoshiki's relicense is strong enough. I documented the priorities for squeak 4.0 in this email: http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-February/134083… You should probably figure out your priorities for the relicense as well, so you know whose standards you need to meet. Since that email was written, Randal has indeed heard back from SFLC, but I haven't heard what they had to say yet. -- Matthew Fulmer -- http://mtfulmer.wordpress.com/

May 15, 2009

Re: [Pharo-project] style preserving for code file out ?

by Lukas Renggli

Yeah, we don't want to store methods as text, just plain strings is perfectly fine. Lukas On Fri, May 15, 2009 at 7:36 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Fri, May 15, 2009 at 4:48 PM, Alain Plantec <alain.plantec(a)free.fr> wrote: >> another way of asking this question would be "can I remove this feature ?" > > +1 > > -- > 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 > -- Lukas Renggli http://www.lukas-renggli.ch

May 15, 2009

Re: [Pharo-project] style preserving for code file out ?

by Damien Cassou

On Fri, May 15, 2009 at 4:48 PM, Alain Plantec <alain.plantec(a)free.fr> wrote: > another way of asking this question would be "can I remove this feature ?" +1 -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

May 15, 2009

Re: [Pharo-project] Inspect it wrong shortcut

by Damien Cassou

2009/5/14 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Can someone confirm this ? This is fixed in recent versions. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

May 15, 2009

Re: [Pharo-project] Excluding classes from Test Coverage

by Mariano Martinez Peck

On Fri, May 15, 2009 at 2:05 PM, Oscar Nierstrasz <oscar(a)iam.unibe.ch>wrote: > > Just checked in as > http://www.squeaksource.com/PharoInbox/SUnitGUI-onierstrasz.38.mcz > > Now you can declare classes to exclude from coverage analysis by > defining #classNamesNotUnderTest on the class side of your test to > return an array of names of those classes. > > http://scg.unibe.ch/wiki/faq/pharofaq/howToCheckTestCoverage Wow! I didn't know http://scg.unibe.ch/wiki/faq/pharofaq It is really useful!!! What about putting a link to it in http://www.pharo-project.org/documentation/faq Best, Mariano > > > - on > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 15, 2009

Re: [Pharo-project] [ANN] OCompletion improves the accuracy of eCompletion

by Damien Cassou

2009/5/15 Hernan Wilkinson <hernan.wilkinson(a)gmail.com>: > Yes, I tried it on a pharo-dev image. I thought that there could be a > conflict between ecomp and ocomp but I also thought that ocomp would disable > ecomp when loading... anyway, I did not have the time to check that so I > went to the previous image. Try the very latest Pharo (please stop using the name pharo-dev (I know I'm still doing it but that's a mistake :-))(this looks like Lisp)) which now has OCompletion installed: http://pharo-project.org/download. > (BTW I also tried to load ocomp on a pharo-core image and I could not > because there is no Installer class. I could not either with the monticello > brower... ) Installer is not installed by default. ScriptLoader new installingInstaller. > So, the performance issue was when typing class names. For example, I typed > 'Ar' press tab and it took a lot to show the valid names. Selected Array and > the started to delete it and it also took a lot of time to delete each > character. I tried the same thing on an pharo-dev image without ocomp and > worked fine... so there must be something going on. Can't reproduce on latest Pharo. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

May 15, 2009