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

[Pharo-project] how do I rename a package?

by Oscar Nierstrasz

I discovered to my astonishment that there is no contextual menu item in either the MC browser or the OB system browser to rename a package! I know how to move all classes and methods from one package to another programmatically, but shouldn't there be a way to rename a package? http://scg.unibe.ch/wiki/faq/pharofaq/howToMoveCodeBetweenPackages Couldn't figure out how to do this. - on

June 18, 2009

[Pharo-project] font spacing problems with merge, patch browser etc

by Oscar Nierstrasz

Hi Folks, The merge tool, patch browser and others no longer have enough space to show the version information for both old and new versions. Now there is a ridiculous little scroll space for two lines if version information. Does anyone know how to fix this? https://www.iam.unibe.ch/scg/svn_repos/SqueakByExample/PharoBook/Monticello… - on

June 18, 2009

[Pharo-project] Monticello merge tool fail - need strikethrough for deleted code - be friendly to red-green colour blind people!

by Oscar Nierstrasz

Hi Folks, While updating the Monticello chapter of Pharo By Example to the current Pharo GUI, I discovered that diffs in the merge tool (and elsewhere) no longer show deleted code struck through, but only in red, with new code in green. This is a major fail for colour blind people! It also does not show when printed in grey-scale. Can we have the strike-through back? It is an important visual cue. - on

June 18, 2009

Re: [Pharo-project] idea to have a better methodFinder :)

by Alain Plantec

PragmaCollector could be very useful for the purpose of collecting pragma for a MethodFinder (or other client) I can provide more help if needed. Alain Marcus Denker a Ã©crit : > On 17.06.2009, at 16:16, Bernardo Ezequiel Contreras wrote: > > >> where can i find Pragma? do you have a link? >> because i couldnt find it. >> >> > > Pragma is a class. Can be found in Squeak 3.9 and Pharo, it was > introduced to Smalltalk > in VisualWorks, I think, and brought to Squeak by Lukas in 3.9 (put on > top of a property > interface for methods inspired by Tweak). > > The idea is the following: In Smalltalk, there is a special syntax for > Primitives: > > + aNumber > > <primitive: 1> > ^ super + aNumber > > > Why not provide a more general concept where we can use the <selector: > arg> syntax to put meta-annotations > in methods? And that's what pragmas are. (Conversely, in Squeak 3.9 > and Pharo, primitives are pragmas and not > special syntax). > > tt > <hello: #world> > > > is perfectly fine. For what can this now be used? One idea is meta- > annotations. For example, SLint is a useful > code-critic tool. But sometimes, it's wrong. So you can put a Pragma > that communicates to SUnit: please don't > report the problem X, because I decided it is none. > Another example would be the MethodFinder. The example-mode of the > method finder allows you to give an example > and executes all methods of the system to find one that does what your > example requests. > > e.g. 3. 4. 7 > > it finds 3 + 4, 3 bitOr: 4 and 3 bitXor: 4. > > Of course, executing just every method could lead to problems if the > method has side-effects. (Like, quitting the > image). Thus, the MethodFinder has lists of methods that should not be > called (#noteDangerous). Of course, this > means that all selectors are hard-coded. And one can not use this > valuable information for other cases. > One thing to think about would be to add a "this method has a bad side- > effect" annotation. (maybe. Maybe this will > not scale and just clutter the system. But it's worth a try). > > Back to Pragma: on the class-side there are some convenience methods, > e.g. > > Pragma allNamed: #primitive: in: SmallInteger > > returns all pragmas in class SmallInteger. (and the pragma references > the method it is installed in, which in > turn knows it's class and selector). > > 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 > > >

June 18, 2009

Re: [Pharo-project] BlockContextTest

by Gabriel Cotelli

This is the list of methods missing in BlockClosure but covered by the BlockContextTest: - copyStack - bottomContext - findContextSuchThat: - tempNamed: - tempNamed:put: I don't known if has sense to implement that... On Wed, Jun 17, 2009 at 4:28 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Hi Gabriel > > Could you post a list of these methods? Probably it makes sense to > copy some of them over to BlockClosure to preserve compatibility for > external clients (we had this before, e.g., #argumentCount, IIRC which > is used by GLORP or Seaside). > > Else these tests can be removed. > > Adrian > > On Jun 17, 2009, at 02:28 , Gabriel Cotelli wrote: > > > Hi, > > > > I'm looking the failing tests... some tests defined in > > BlockContextTest > > relies on behavior not implemented in BlockClosure (but implemented > > in the > > old BlockContext)... > > > > If the only senders of this methods are in this test cases can I > > remove > > them? > > > > If I don't miss anything BlockContext should not be used anymore... > > > > Waiting for your comments... > > Gabriel > > _______________________________________________ > > 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 18, 2009

Re: [Pharo-project] Can not make the right mouse button work

by Hernan Wilkinson

I should have said that I'm using Ubuntu...(When I copy the image to a windows system, after some time, yes some time, it started to work...) 2009/6/17 Nicolas Chillo <nchillo(a)gmail.com> > Take a look at the VM Mouse Mapping attributes (In windows> right click in > the squeak icon from taskbar). > Activate the 3 Buttons mouse and it should work. > > Nicolas > > > 2009/6/17 Hernan Wilkinson <hernan.wilkinson(a)gmail.com> > >> Hi, in the latest image I can not make the right mouse button work.... >> Preferences swapMouseButtons returns false as in the previous image that >> worked... any idea? >> >> Thanks, >> Hernan. >> >> _______________________________________________ >> 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 18, 2009

Re: [Pharo-project] Can not make the right mouse button work

by Nicolas Chillo

Take a look at the VM Mouse Mapping attributes (In windows> right click in the squeak icon from taskbar). Activate the 3 Buttons mouse and it should work. Nicolas 2009/6/17 Hernan Wilkinson <hernan.wilkinson(a)gmail.com> > Hi, in the latest image I can not make the right mouse button work.... > Preferences swapMouseButtons returns false as in the previous image that > worked... any idea? > > Thanks, > Hernan. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 17, 2009

[Pharo-project] Can not make the right mouse button work

by Hernan Wilkinson

Hi, in the latest image I can not make the right mouse button work.... Preferences swapMouseButtons returns false as in the previous image that worked... any idea? Thanks, Hernan.

June 17, 2009

Re: [Pharo-project] BlockContextTest

by Michael Roberts

They are on the wiki in the baseline test page. Mike On Wednesday, June 17, 2009, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > Tonight I prepare the list and post it... > > On Wed, Jun 17, 2009 at 4:28 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > > Hi Gabriel > > Could you post a list of these methods? Probably it makes sense to > copy some of them over to BlockClosure to preserve compatibility for > external clients (we had this before, e.g., #argumentCount, IIRC which > is used by GLORP or Seaside). > > Else these tests can be removed. > > Adrian > > On Jun 17, 2009, at 02:28 , Gabriel Cotelli wrote: > >> Hi, >> >> I'm looking the failing tests... some tests defined in >> BlockContextTest >> relies on behavior not implemented in BlockClosure (but implemented >> in the >> old BlockContext)... >> >> If the only senders of this methods are in this test cases can I >> remove >> them? >> >> If I don't miss anything BlockContext should not be used anymore... >> >> Waiting for your comments... >> Gabriel >> _______________________________________________ >> 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 17, 2009

Re: [Pharo-project] idea to have a better methodFinder :)

by Marcus Denker

On 17.06.2009, at 16:16, Bernardo Ezequiel Contreras wrote: > > where can i find Pragma? do you have a link? > because i couldnt find it. > Pragma is a class. Can be found in Squeak 3.9 and Pharo, it was introduced to Smalltalk in VisualWorks, I think, and brought to Squeak by Lukas in 3.9 (put on top of a property interface for methods inspired by Tweak). The idea is the following: In Smalltalk, there is a special syntax for Primitives: + aNumber <primitive: 1> ^ super + aNumber Why not provide a more general concept where we can use the <selector: arg> syntax to put meta-annotations in methods? And that's what pragmas are. (Conversely, in Squeak 3.9 and Pharo, primitives are pragmas and not special syntax). tt <hello: #world> is perfectly fine. For what can this now be used? One idea is meta- annotations. For example, SLint is a useful code-critic tool. But sometimes, it's wrong. So you can put a Pragma that communicates to SUnit: please don't report the problem X, because I decided it is none. Another example would be the MethodFinder. The example-mode of the method finder allows you to give an example and executes all methods of the system to find one that does what your example requests. e.g. 3. 4. 7 it finds 3 + 4, 3 bitOr: 4 and 3 bitXor: 4. Of course, executing just every method could lead to problems if the method has side-effects. (Like, quitting the image). Thus, the MethodFinder has lists of methods that should not be called (#noteDangerous). Of course, this means that all selectors are hard-coded. And one can not use this valuable information for other cases. One thing to think about would be to add a "this method has a bad side- effect" annotation. (maybe. Maybe this will not scale and just clutter the system. But it's worth a try). Back to Pragma: on the class-side there are some convenience methods, e.g. Pragma allNamed: #primitive: in: SmallInteger returns all pragmas in class SmallInteger. (and the pragma references the method it is installed in, which in turn knows it's class and selector). Marcus -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

June 17, 2009