December 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] FileStream class>>old* methods

by Alexandre Bergel

This is what I discovered after having discussed with Oscar. Alexandre On 1 Dec 2008, at 21:04, Chris Cunningham wrote: > Yes, these are necessary. They refer to an existsing file (old) > versus a non-existant file (the new prefixed methods). There are > several uses of it, but in my images there are many, many uses of > it. Of course, I really wanted to use #readOnlyFileNamed: in most > of the cases that I've created - just missed that desired method > when I found the old version. > > Chris > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 2, 2008

Re: [Pharo-project] Monticello configuration still broken

by Adrian Lienhard

Thanks for reporting. I created http://code.google.com/p/pharo/issues/detail?id=368 Adrian On Dec 2, 2008, at 14:11 , Hilaire Fernandes wrote: > I try to load Magma r41.1 throught Monticello configuration. > This last one is still broken in Pharo and I need to apply the usual > fixes MonticelloConfigurations-cmm.44.mcz, Monticello-SR.315.mcz > to get it loaded (was previously reported). > > For Pharo to be a developer friendly environment, it is a must to > include these fixes, even waiting for a better solution, because > newbies will get burn there. > > -- > 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

Dec. 2, 2008

Re: [Pharo-project] About ecompletion

by Romain Robbes

Hi Damien, The work is part of a prototype and was more focused on the evaluation part. As such there are a bunch of dependencies that would need to be resolved beforehand as my prototype is quite large. But I believe the algorithms are described clearly enough in the paper. The one which provides the more "Bang for the Buck" would be "Recently Modiï¬ed Method Bodies" which proposes as completion entries the methods calls in the bodies of methods which were recently changed (ordered by time, ie most recent first). A further (but small) improvement would be to merge it with type inference when the information is available. Such as algorithm would be quite small to implement. If you want some more details we can of course talk further about it. Cheers, Romain On Dec 2, 2008, at 1:56 PM, Damien Cassou wrote: > Hi Romain, > > On Tue, Dec 2, 2008 at 12:11 PM, Romain Robbes > <romain.robbes(a)lu.unisi.ch> wrote: >> Dear all, >> >> I uplooaded the paper at: >> http://www.inf.unisi.ch/phd/robbes/papers/ASE2008-completion.pdf > > Do you have packages that I can install inside dev images to enhance > code completion? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Romain Robbes http://www.inf.unisi.ch/phd/robbes

Dec. 2, 2008

[Pharo-project] Monticello configuration still broken

by Hilaire Fernandes

I try to load Magma r41.1 throught Monticello configuration. This last one is still broken in Pharo and I need to apply the usual fixes MonticelloConfigurations-cmm.44.mcz, Monticello-SR.315.mcz to get it loaded (was previously reported). For Pharo to be a developer friendly environment, it is a must to include these fixes, even waiting for a better solution, because newbies will get burn there. -- http://blog.ofset.org/hilaire

Dec. 2, 2008

Re: [Pharo-project] Removing a trait from a class

by StÃ©phane Ducasse

Adrian I got some problems during the last smalltalk party at paris. my pair programmer quitted the image without saving and when I reloaded the changes it was a mess. I could not remove methods from a class. The methods were not in the method dictionary but their names showed up in the browser.... The class organizer had them in. I would love to check the classorganizer concept :) I could not remove the traits from the class. Stef On Dec 2, 2008, at 11:26 AM, Adrian Lienhard wrote: > Hi Hilaire, > > Which UI tools do you use? Omnibrowser or the old browser that is > shipped with the Core image. > Could you try to reproduce the problem in a newer version of Pharo? > (10050 is *very* old). > > I'd like to take a look then. It's strange because we have been > using traits for two years now without seeing this problem. So it > may indeed be a problem related to the UI that somehow brings traits > into an inconsistent state. > > Adrian > > > On Dec 2, 2008, at 11:08 , Hilaire Fernandes wrote: > >> I can't remove a trait from a class using UI tools. (pharo 10050) >> How can I remove it programmatically ? >> >> Next with this same class, message from this trait are not reachable, >> the MNU is raised but the hierarchy is not right as IFIETayage1 is >> not >> a subclass of IFIExoMorph. However IFIExoMorph is using the same >> trait >> as IFIEtayage. >> It looks like there is mismatch in the classes with traits. (see >> screenshot) >> >> Now I realize my last istoa release suffer from this problem :) >> >> Hilaire >> >> -- >> http://blog.ofset.org/hilaire >> <bug-trait.png>_______________________________________________ >> 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 >

Dec. 2, 2008

Re: [Pharo-project] About ecompletion

by Damien Cassou

Hi Romain, On Tue, Dec 2, 2008 at 12:11 PM, Romain Robbes <romain.robbes(a)lu.unisi.ch> wrote: > Dear all, > > I uplooaded the paper at: > http://www.inf.unisi.ch/phd/robbes/papers/ASE2008-completion.pdf Do you have packages that I can install inside dev images to enhance code completion? -- Damien Cassou http://damiencassou.seasidehosting.st

Dec. 2, 2008

[Pharo-project] Trying to install Magma r41.1 throught Monticello installation 1.5+

by Hilaire Fernandes

I am CC to the Magma list as it may be more a problem from SqueakMap dependencies. On a fresh update Pharo image, I install Magma r41.1 with: Installer universe install: 'Magma 1.41(r41.1)'. At first MC1.5+ is first installed, at it is marked as a prerequisit. But an error ius raised, indeed it looks like MC1.5+ override of the method httpGetDocument: url args: args accept: mimeType request: requestString is incompatible with Pharo -- http://blog.ofset.org/hilaire

Dec. 2, 2008

Re: [Pharo-project] About ecompletion

by Romain Robbes

Dear all, I uplooaded the paper at: http://www.inf.unisi.ch/phd/robbes/papers/ASE2008-completion.pdf Cheers, Romain On Dec 2, 2008, at 10:48 AM, StÃ©phane Ducasse wrote: > How Program History Can Improve Code Completion > Romain Robbes ~ Michele Lanza > ASE 2008 (12% acceptance) ~ to appear ~ IEEE CS, 2008 > > his pageweb is not up to date > I can send you his Phd > > > On Dec 1, 2008, at 12:50 PM, Damien Cassou wrote: > >> On Sun, Nov 30, 2008 at 7:16 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> I wanted to share that with you. I'm reading the PhD of Romain >>> Robbes and >>> he has an excellent chapter on measuring different strategies for >>> code >>> completion. >>> One of the best algorithm is to keep a list with the recently >>> modified >>> methods >>> and the messages they send. >>> >>> His benchmark shows a drastic improvement even compared with >>> ecompletion >>> with RoelTyper. >>> >>> So david do you store the recently modified methods globally for >>> all the >>> browsers? >>> Is it easily accessible? >>> >>> He also mentioned that we get even better results by combining >>> RoelTyper and then this approach... any taker? this is important to >>> have >>> much better >>> editing tools. >> >> I guess Romain already did something to be able to compare the >> results. Where is his work? >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > -- Romain Robbes http://www.inf.unisi.ch/phd/robbes

Dec. 2, 2008

Re: [Pharo-project] Removing a trait from a class

by Adrian Lienhard

Hi Hilaire, Which UI tools do you use? Omnibrowser or the old browser that is shipped with the Core image. Could you try to reproduce the problem in a newer version of Pharo? (10050 is *very* old). I'd like to take a look then. It's strange because we have been using traits for two years now without seeing this problem. So it may indeed be a problem related to the UI that somehow brings traits into an inconsistent state. Adrian On Dec 2, 2008, at 11:08 , Hilaire Fernandes wrote: > I can't remove a trait from a class using UI tools. (pharo 10050) > How can I remove it programmatically ? > > Next with this same class, message from this trait are not reachable, > the MNU is raised but the hierarchy is not right as IFIETayage1 is not > a subclass of IFIExoMorph. However IFIExoMorph is using the same trait > as IFIEtayage. > It looks like there is mismatch in the classes with traits. (see > screenshot) > > Now I realize my last istoa release suffer from this problem :) > > Hilaire > > -- > http://blog.ofset.org/hilaire > <bug-trait.png>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 2, 2008

Re: [Pharo-project] free fonts

by Adrian Lienhard

of course we won't do that. Adrian On Dec 2, 2008, at 10:52 , StÃ©phane Ducasse wrote: > +1 > On Nov 30, 2008, at 4:39 PM, David Mitchell wrote: > >> Please don't include any font with ambiguous licensing! Wouldn't want >> to bring back a fonts clause to the license! >> >> On Sun, Nov 30, 2008 at 5:33 AM, Adrian Lienhard <adi(a)netstyle.ch> >> wrote: >>> >>> On Nov 30, 2008, at 10:35 , StÃ©phane Ducasse wrote: >>> >>>> http://www.pinvoke.com/font/ >>>> >>>> I think that for the demo mode we should get a better font since >>>> italic "" >>>> is not working well. >>> >>> Yes, and not only for the demo font, but *all* default fonts >>> should be >>> reconsidered now that we have the machinery in place. >>> >>> I don't think that the fonts of www.pinvoke.com/font/ are >>> particularly well >>> suited. >>> >>> From a mail I sent on September 22, considering the code font I >>> wrote: >>> >>> I think Bitstream Vera Sans Mono would be quite good. >>> I slightly prefer Monaco, which is shipped with OS X, but I don't >>> know its >>> license (http://en.wikipedia.org/wiki/Monaco_(typeface)) >>> >>> For an evaluation of programmer fonts see http://www.lowing.org/fonts/ >>> Another list can be found here: >>> http://wiki.macromates.com/Main/AlternativeFonts >>> The latter list, for example includes >>> http://www.ms-studio.com/FontSales/anonymous.html which looks nice >>> too. >>> >>> Adrian >>> >>> >>>> >>>> Now it would be great to have a set of free font for pharo. >>>> >>>> stef >>>> >>>> _______________________________________________ >>>> 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 >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 2, 2008