August 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] Adding Polymorph text adornment to NewTextMorph

by Fernando olivero

Name: SLICE-Issue-2746-NewTextMorphUsesPolymorphAddornments-FernandoOlivero.1 Author: FernandoOlivero Time: 4 August 2010, 10:26:14 am UUID: ad45b9eb-1683-4157-9b7e-15cf7b204743 Ancestors: Dependencies: Morphic-FernandoOlivero.672 Polymorph text addornment and other minor refactorings to NewTextMorph and related classes.

Aug. 4, 2010

[Pharo-project] Gofer support for Universes

by Miguel Enrique CobÃ¡ MartÃnez

StÃ©phane, Lukas, I have uploaded Gofer-Core-MiguelCoba.124 Gofer-Tests-MiguelCoba.117 to PharoInbox repository on squeaksource. They are based on the versions of gofer in Pharo 1.0 Gofer-Core-MarkusDenker.117 Gofer-Tests-MarkusDenker.116 and add universes support to gofer. What do you think, are they worth integrating to mainstream gofer? Does this functionality belongs to Gofer? I know of GoferProjectLoader, but it isn't part of PharoCore, so that discards it right now. What is the procedure to merge it to trunk gofer, if so decided, so that a Gofer upgrade in any Pharo image gets this new version? Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Aug. 4, 2010

[Pharo-project] [ANN] Pharo Metacello Universes

by Miguel Enrique CobÃ¡ MartÃnez

Hi all, I have created three new repositories on squeaksource: http://www.squeaksource.com/UniverseForPharo10 http://www.squeaksource.com/UniverseForPharo11 http://www.squeaksource.com/UniverseForPharo12 They are the repositories for the current versions of Pharo. The idea is that each new release add a new UniverseForXXX repository and populates it with the current UniverseForXXX packages of the stable release. Right now they are mostly empty, but should be populated by the community and the ConfigurationOfXXX maintainers. Most ConfigurationOfXXX packages in http://www.squeaksource.com/MetacelloRepository should be copied to UniverseForPharo10. Which versions? The last known version that is working correctly on Pharo 1.0. This will be the official universe for Pharo1.0. No ConfigurationOfXXX should be stored on UniverseForPharo10 if it is not working correctly on Pharo10. Then two things can follow: - If the package already has ConfigurationOfXXX package versions that work in Pharo 1.1, those versions should be copied to UniverseForPharo11. - If the ConfigurationOfXXX only works for Pharo1.0 and the maintainer want to create the configuration for Pharo 1.1, he/she must copy the last working configuration for the package from UniverseForPharo10 to UniverseForPharo11. There he/she can start modifying the package until it works correctly in Pharo1.1 (use the blessing: tags wisely to avoid marking a broken configuration as released) This will permit to populate the UniverseForPharo11 based on the last working package versions from UniverseForPharo10. From that point they will likely diverge because of maintenance releases to the packages in any UniverseForXXX repository. The same will must be done to migrate from UniverseForPharo11 to UniverseForPharo12. You get the idea. With time, MetacelloRepository should be deprecated in favor of this UniverseForXXX repositories. Anyone is free to copy a working version from a previous Universe to a new Universe. They have read/write permissions to all. This setup will avoid the problems we are having right now with the in-image changes that are rendering the ConfigurationOfXXX unusable in distinct releases of Pharo. What this means to the end user: - For released version of Pharo They will have to use gofer this way: Gofer new squeaksource: 'UniverseForPharo10'; "Or UniverseForPharo11" project: 'ConfigurationOfMagma'; load. ConfigurationOfMagma project latestVersion load. - For next releases of Pharo Gofer loadFromUniverse: 'Magma'. "Or with GoferProjectLoader" ConfigurationOfMagma project latestVersion load. All this depends on conventions to find the appropriate universe for each pharo release, and also in the support from tools (like gofer in this example or the GoferProjectLoader if it is part of the core image). The universe functionality of the tools right now rely on the SystemVersion current majorMinorVersion string for deciding which repository to connect to. This could be improved surely but for now it works. I'm loading a new version of Gofer to PharoInbox with this functionality added so if you want to load directly from the universes with gofer do: Gofer upgrade. Gofer loadFromUniverse: 'YourPackageAlreadyInAUniverse'. But wait to this change to be treated by Stephane or Lukas before attempt it. Right now there is only Magma in the three repositories, but it shouldn't be hard for the maintainers of the other Configurations to help populate the universes from Pharo1.0, Pharo1.1 and Pharo1.2. This will benefit us as a community because the universes for the released pharo versions will be mostly untouched (only maintenance releases) and people will have the freedom to modify the configuration in the unstable (currently UniverseForPharo12) universe without affecting the users of the stable versions. Also, this will avoid to have a lot of conditionals inside the ConfigurationOfXXX classes, because a given class will target a specific Pharo release (the version on the newest universes could even delete the methods for the old universe, because will likely won't work in the new universe, deleting unnecessary and legacy code from the configuration) Comments and improvements welcome -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Aug. 4, 2010

Re: [Pharo-project] update to OCompletion

by Lukas Renggli

> 1) If you hilite an expresion and press ) - in eCompletion it surrounds that selection with the matching characters, OC doesn't seem to I removed that, because no popular editor I tried does this (Eclipse, TextMate). Lukas > 2) If you type [ - you get [], but then when you press backspace it removes the [] as well as an additional character before the [ - which is not ideal (again eCompletion doesn't do that) > > Should I log a bug for these? > > On 2 Aug 2010, at 23:38, Romain Robbes wrote: > > > Hi All, > > I just committed: > http://squeaksource.com/OCompletion/Ocompletion-RomainRobbes.64.mcz > > the changes are: > > -incorporated Lukas' smart characters algorithm (thanks Lukas!) > -removed enter to insert a completion; only tab works now. > -delayed the switch to eCompletion's completion algorithm, hence the slowdown when using the down arrow happens only after the third time pressing it (after OCompletion's all of OCompletion's menu items). > > Cheers, > Â Â Â Â Romain > > -- > Romain Robbes > http://romain.robb.es > rrobbes(a)dcc.uchile.cl > > > _______________________________________________ > 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 > -- Lukas Renggli www.lukas-renggli.ch

Aug. 4, 2010

Re: [Pharo-project] How detect a primitve?

by James Ladd

> See CompiledMethod >> #primitive. > > > Levente Thank you. Funny how you can't see things right in front of you sometimes. I was thinking isPrimitive. Rgs, James.

Aug. 4, 2010

Re: [Pharo-project] Refactor source method is grayed out?

by Tim Mackinnon

Lucas - I can't repeat this in a Pharo 1.1 image - so maybe we should put it down to some oCompletion/eCompletion bad interaction (or unload weirdness). Tim On 3 Aug 2010, at 12:23, Lukas Renggli wrote: > I am using the images from hudson.lukas-renggli.ch. I don't know how > oCompletion depends/overrides on eCompletion, so indeed it might make > a difference. > > Lukas > > On Tuesday, August 3, 2010, Tim Mackinnon <tamackinnon(a)gmail.com> > wrote: >> Lucas, which image are you using - and I will load it up and try >> again (I am using the seaside 3.0rc image - although I did unload >> oCompletion from it and then load eCompletion - maybe that makes a >> difference?). I appreciate your patience on this by the way - often >> I'm not sure which things are supposed to work (or work differently >> from how I expect). >> >> Tim >> >> On 3 Aug 2010, at 11:24, Lukas Renggli wrote: >> >> >> I played a bit with the selection an the enabling of the menus this >> morning, however I found it quite confusing if the closest matching >> expression is automatically picked. >> >> I could not reproduce the issue you report with the spaces. In my >> image when I select a full expression whitespaces at start and end do >> not matter. >> >> Lukas >> >> On Tuesday, August 3, 2010, Tim Mackinnon <tamackinnon(a)gmail.com> >> wrote: >> >> Lukas - I logged it as issue 2742 (now that I know its a bit picky, >> I'll select extra spaces as a workaround). >> >> Some day I will learn how some of this works so that I can try and >> help out (from my time spent in Dolphin where RB is tightly >> integrated, it was cool messing around with parse nodes to drive >> better UI tools). >> >> Tim >> >> >> >> I don't see that difference with the space, but it is true that you >> need to select a valid expression to get the menu items enabled. In >> that regard, the conditions could probably be relaxed a bit. >> >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> _______________________________________________ >> 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 >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> >> _______________________________________________ >> 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 >> > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 4, 2010

Re: [Pharo-project] update to OCompletion

by Tim Mackinnon

Actually correction on #1 - eCompletion suffers from that one as well - I'm sure they should both be able to surround a selection with characters no matter which side of the selection you are on. Tim On 4 Aug 2010, at 01:28, Tim Mackinnon wrote: > If the eCompletion tweaks look good from Lucas' point of view - they > also apply to oCompletion as well - however I noticed that there > seem to be a few additional bugs in oCompletion (at least compared > to eCompletion). > > 1) If you hilite an expresion and press ) - in eCompletion it > surrounds that selection with the matching characters, OC doesn't > seem to > 2) If you type [ - you get [], but then when you press backspace it > removes the [] as well as an additional character before the [ - > which is not ideal (again eCompletion doesn't do that) > > Should I log a bug for these? > > On 2 Aug 2010, at 23:38, Romain Robbes wrote: > >> Hi All, >> >> I just committed: >> http://squeaksource.com/OCompletion/Ocompletion-RomainRobbes.64.mcz >> >> the changes are: >> >> -incorporated Lukas' smart characters algorithm (thanks Lukas!) >> -removed enter to insert a completion; only tab works now. >> -delayed the switch to eCompletion's completion algorithm, hence >> the slowdown when using the down arrow happens only after the third >> time pressing it (after OCompletion's all of OCompletion's menu >> items). >> >> Cheers, >> Romain >> >> -- >> Romain Robbes >> http://romain.robb.es >> rrobbes(a)dcc.uchile.cl >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 4, 2010

Re: [Pharo-project] update to OCompletion

by Tim Mackinnon

If the eCompletion tweaks look good from Lucas' point of view - they also apply to oCompletion as well - however I noticed that there seem to be a few additional bugs in oCompletion (at least compared to eCompletion). 1) If you hilite an expresion and press ) - in eCompletion it surrounds that selection with the matching characters, OC doesn't seem to 2) If you type [ - you get [], but then when you press backspace it removes the [] as well as an additional character before the [ - which is not ideal (again eCompletion doesn't do that) Should I log a bug for these? On 2 Aug 2010, at 23:38, Romain Robbes wrote: > Hi All, > > I just committed: > http://squeaksource.com/OCompletion/Ocompletion-RomainRobbes.64.mcz > > the changes are: > > -incorporated Lukas' smart characters algorithm (thanks Lukas!) > -removed enter to insert a completion; only tab works now. > -delayed the switch to eCompletion's completion algorithm, hence the > slowdown when using the down arrow happens only after the third time > pressing it (after OCompletion's all of OCompletion's menu items). > > Cheers, > Romain > > -- > Romain Robbes > http://romain.robb.es > rrobbes(a)dcc.uchile.cl > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 4, 2010

Re: [Pharo-project] update to OCompletion

by Tim Mackinnon

Am I missing something here - in a fresh 1.1 one click image if I do: ConfigurationOfOCompletion project latestVersion load I get an endless stream of errors: The method Boolean and:and: has been deprecated. use and: Select Proceed to continue, or close this window to cancel the operation.??????? On 3 Aug 2010, at 16:31, StÃ©phane Ducasse wrote: > I have no problem. I ***love*** metacello and the garanty it offers > to load packages coherently > > Stef > > On Aug 3, 2010, at 5:29 PM, Mariano Martinez Peck wrote: > >> >> >> On Tue, Aug 3, 2010 at 5:20 PM, Romain Robbes <romain.robbes(a)gmail.com >> > wrote: >>> Message: 7 >>> Date: Tue, 3 Aug 2010 11:20:03 +0200 >>> From: St?phane Ducasse <stephane.ducasse(a)inria.fr> >>> Subject: Re: [Pharo-project] update to OCompletion >>> To: Pharo-project(a)lists.gforge.inria.fr >>> Message-ID: <94557FA5-8F73-42B7-8537-3882867A80B5(a)inria.fr> >>> Content-Type: text/plain; charset=us-ascii >>> >>> thanks romain (and sorry for my stupid suggestion - good that you >>> corrected it) >>> Your tools are really important. >>> Is there a ConfigurationOfOCompletion or just loading OCompletion >>> works? >> >> >> Yes, Mariano made a ConfigurationOfOCompletion. Otherwise, just >> loading the latest OCompletion package on top of the old one should >> work too. >> >> >> My conf says you also need Shout and RoelTyper ;) but maybe >> they are optional >> >> >> Romain >> >> -- >> Romain Robbes >> http://romain.robb.es >> rrobbes(a)dcc.uchile.cl >> >> >> _______________________________________________ >> 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

Aug. 4, 2010

[Pharo-project] Extract method dialog is too small to see what your typing

by Tim Mackinnon

I've logged 2747 - the extract method dialog window is just too small to be used - and its worse when you type a : for a selector (Pharo 1.1)

Aug. 3, 2010