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

Re: [Pharo-project] accessors

by Cameron Sanders

> perhaps private accessors could go into a different category? Oh yeah, one could do that. (sorry, i'm in a goofy mood ;) It turns out that I nearly always implement them for my code. So I do agree that it is a good policy, in general. Such a rewrite would likely (inevitably?) introduce some bugs. It would marginally slow down some of the code. I am not involved in any core code, so I will bow out of this thread. -Cam PS: what is your debugging situation? You want to find out what all code may be modifying an object? On May 14, 2009, at 1:13 PM, Steve Wirts wrote: > > > On Thu, May 14, 2009 at 1:10 PM, Cameron Sanders <camsanders01(a)roadrunner.com > > wrote: > > That is not always the best policy. If you provide public accessors > for your private model elements (representation), the next thing you > know people start using them! And then your model interfaces is > constrained. > > ? or am i just talking trash ? > > > On May 14, 2009, at 12:55 PM, Steve Wirts wrote: > > > Hi Folks, > > > > Would it be inappropriate to request that an effort be made at some > > point to try to provide accessors for all instance/class instance > > variables, and try to get rid of inappropriate direct variable > > accessing where possible? > > > > The "chasing variables" function is handy but seems more cumbersome > > than just putting a halt in a setter. > > > > I know this would be a lot of work but maybe it could be automated. > > > > Just tell me to shut up and go away if I'm being a nuisance. > > Oh, and please stick around... to draw attention away from my pesky > questions. > > > > > > > Steve :) > > > -cam > > _______________________________________________ > 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 14, 2009

Re: [Pharo-project] accessors

by Alexandre Bergel

I kind of agree with Steve, however, it is hard to see how this will increase the quality of source code. Alexandre On 14 May 2009, at 19:10, Cameron Sanders wrote: > > That is not always the best policy. If you provide public accessors > for your private model elements (representation), the next thing you > know people start using them! And then your model interfaces is > constrained. > > ? or am i just talking trash ? > > > On May 14, 2009, at 12:55 PM, Steve Wirts wrote: > >> Hi Folks, >> >> Would it be inappropriate to request that an effort be made at some >> point to try to provide accessors for all instance/class instance >> variables, and try to get rid of inappropriate direct variable >> accessing where possible? >> >> The "chasing variables" function is handy but seems more cumbersome >> than just putting a halt in a setter. >> >> I know this would be a lot of work but maybe it could be automated. >> >> Just tell me to shut up and go away if I'm being a nuisance. > > Oh, and please stick around... to draw attention away from my pesky > questions. > >> >> >> Steve :) > > > -cam > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 14, 2009

Re: [Pharo-project] accessors

by Steve Wirts

perhaps private accessors could go into a different category? On Thu, May 14, 2009 at 1:10 PM, Cameron Sanders < camsanders01(a)roadrunner.com> wrote: > > That is not always the best policy. If you provide public accessors > for your private model elements (representation), the next thing you > know people start using them! And then your model interfaces is > constrained. > > ? or am i just talking trash ? > > > On May 14, 2009, at 12:55 PM, Steve Wirts wrote: > > > Hi Folks, > > > > Would it be inappropriate to request that an effort be made at some > > point to try to provide accessors for all instance/class instance > > variables, and try to get rid of inappropriate direct variable > > accessing where possible? > > > > The "chasing variables" function is handy but seems more cumbersome > > than just putting a halt in a setter. > > > > I know this would be a lot of work but maybe it could be automated. > > > > Just tell me to shut up and go away if I'm being a nuisance. > > Oh, and please stick around... to draw attention away from my pesky > questions. > > > > > > > Steve :) > > > -cam > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 14, 2009

Re: [Pharo-project] accessors

by Cameron Sanders

That is not always the best policy. If you provide public accessors for your private model elements (representation), the next thing you know people start using them! And then your model interfaces is constrained. ? or am i just talking trash ? On May 14, 2009, at 12:55 PM, Steve Wirts wrote: > Hi Folks, > > Would it be inappropriate to request that an effort be made at some > point to try to provide accessors for all instance/class instance > variables, and try to get rid of inappropriate direct variable > accessing where possible? > > The "chasing variables" function is handy but seems more cumbersome > than just putting a halt in a setter. > > I know this would be a lot of work but maybe it could be automated. > > Just tell me to shut up and go away if I'm being a nuisance. Oh, and please stick around... to draw attention away from my pesky questions. > > > Steve :) -cam

May 14, 2009

Re: [Pharo-project] [ANN][Dev-Images] May 2009 versions

by Henrik Sperre Johansen

If you're talking about dragging a window, this is fixed in 304, so either update (dev image is 303), or switch off fastDragWindowsForMorphic preference. Cheers, Henry On 14.05.2009 18:18, Schwab,Wilhelm K wrote: > Damien, > > I fired it up, added a workspace and started to drage same - complete hang. That's on linux. > > Any other takers? > > Bill > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > >

May 14, 2009

[Pharo-project] accessors

by Steve Wirts

Hi Folks, Would it be inappropriate to request that an effort be made at some point to try to provide accessors for all instance/class instance variables, and try to get rid of inappropriate direct variable accessing where possible? The "chasing variables" function is handy but seems more cumbersome than just putting a halt in a setter. I know this would be a lot of work but maybe it could be automated. Just tell me to shut up and go away if I'm being a nuisance. Steve :)

May 14, 2009

Re: [Pharo-project] [ANN][Dev-Images] May 2009 versions

by Schwab,Wilhelm K

Damien, I fired it up, added a workspace and started to drage same - complete hang. That's on linux. Any other takers? Bill

May 14, 2009

Re: [Pharo-project] Couldn't find an icon so...

by Schwab,Wilhelm K

It would be great for the VMs to have the icons. So far, I can't even get gnome to use mine. Windows probably would take the ico, but I'm trying to kick that particular addition :) Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Henrik Johansen Sent: Thursday, May 14, 2009 7:21 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Couldn't find an icon so... Schwab,Wilhelm K skrev: > Hello all, > > Sorry to have dropped out for a whlie - nothing against Pharo. I am hopefully getting ready to ramp up some "real" work on Pharo, and toward that end, have a couple of questions. The first is a trivial concern that I have partially addressed with the attached icons. All I did was take the logo and chop off the lighthouse itself. So far it has been useless to me, but perhaps you will do better with it. > I made an icon too some time ago, with just the lighthouse, no encircling O. They're attached to comment 4 in http://code.google.com/p/pharo/issues/detail?id=192 IMHO, it's a bit more recognizable at smaller dimensions than the one you sent (I did some manual work cleaning up the 16x16 one, for example), which can be nice. If I were to do it again though, I'd make a dimensions/16 pixel border on top/bottom, using all 16px high leaves list view feeling cluttered. If you plan on using ResHacker to add them to squeak.exe, read comment 5 as well :) Sorry I can't help with the second part :) Cheers, Henry _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 14, 2009

[Pharo-project] Pharo/Squeak/Smalltalk party in SW of France...

by Hilaire Fernandes

Any one for such a party in SW of France ? It could come with a Pharo bug smashing party as well. Hilaire -- http://blog.ofset.org/hilaire

May 14, 2009

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

by Mariano Martinez Peck

Wow!!! What an excellent job! This really help us. I hope you continue with your work (although you have already finished the paper), add features and take into account the ideas others tell you. In my opinion this could be in the Pharo dev image by default. Again, congratulations for your work. Mariano On Tue, May 12, 2009 at 7:07 AM, Romain Robbes <romain.robbes(a)lu.unisi.ch>wrote: > Dear Pharo users, > > OCompletion is an extension to ECompletion. Like ECompletion, it > completes > the names of methods as you write them in order to save you some > typing. > The O in OCompletion stands for Omniscient and Omnipresent. > > OCompletion is much more accurate than ECompletion. We tested it on the > development history of several projects > (see http://www.inf.unisi.ch/phd/robbes/papers/ASE2008-completion.pdf) > > Across several hundred thousands tests of the completion, OCompletion's > algorithm scores a 70 (out of 100), while the eCompletion's algorithm > scores a 12. To achieve this level of accuracy, it learns from your > usage > of squeak and proposes to you methods you are more likely to use. > > OCompletion shows a small, non-instrusive completion menu with potential > completions as you type method names. You don't need to call it > explicitely > with tab. Just press tab to insert a match, or the down arrow to > select the next > match. > > To install it on Squeak or Pharo, simply execute the following line in > your image: > > Installer squeaksource project: 'OCompletion'; install: 'OCLoader' > > Cheers, > Romain > > -- > Romain Robbes > http://www.inf.unisi.ch/phd/robbes > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 14, 2009