- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.2] #12215
by Marcus Denker Oct. 25, 2010

Oct. 25, 2010

[update 1.2] #12215 12215 ----- Issue 3158: Deprecate translation support protocol Issue 3157: Text entry dialog window badly compute minimumWidth Issue 3025: SystemVersionTest>>testDowngrade use a deprecated method Issue 3029: The Menus of the Source panes reverted to the old complex ones... Issue 3025: SystemVersionTest>>testDowngrade use a deprecated method -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] what happened with Shout colors in Pharo 1.1?
by Simon Denier Oct. 25, 2010

Oct. 25, 2010

On 23 oct. 2010, at 19:13, Mariano Martinez Peck wrote: > > To customize colors, two solutions: > 1) hack SHTextStylerST80>>defaultStyleTable > > did you do this? can you share? Well that's the standard mechanism which was already in place. Just take a look at the comment to learn the format. It's a bit cumbersome to use though. To change style for instance vars/class vars (instVar ( blue muchDarker ) ) (classVar ( blue muchDarker ) ) To change style for class (actually it's more like access to global variables) (poolConstant ( blue muchDarker ) ) (globalVar ( blue muchDarker ) ) > > 2) load latest Shout and use Settings (then you should be able to save/load your style), since there is now a Settings interface > > > The problem is that I have my own style also....and when you save an style I think you save it completly...I guess you cannot merge, so I will loose my own changes. > Anyway, can you export and share the style so that I can take a look? Yes, we talked about that with Alain at Esug. It would be cool if the 'choose packages' button, which filters entries in the settings, would also apply to saving style. That way we could only save partial settings. Anyway, there's not much to change through the Settings browser. Easier to show there: Before: After: -- Simon

3 2

[Pharo-project] [update 1.2] #12214
by Marcus Denker Oct. 25, 2010

Oct. 25, 2010

12214 ----- Issue 3156: StandardWindow should not redefine #initialExtent Issue 2899: Slice creation should add dirty packages are dependent Issue 2766: World Screen capture should be adapted to Pharo Issue 2256: #sortBy: should be deprecated (minus the deprication call in sortBy:.. will come later) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Smells looking at collections
by StÃ©phane Ducasse Oct. 25, 2010

Oct. 25, 2010

>> >>> >>>> 2) well, this is difficult to get the money for the butter and the butter - we are trying. >>> >>> If you can compose classes the way you can add a trait to a class now with class and optional method level instance+class variable mapping, then you're done. It would be a lot simpler to use it _and_ it would also be a lot easier to implement it. Especially the tools part. >> >> I'm interested to hear more about that. so can you explain what you meant because I did not understand it. >> Tell us more. The problem we faced was >> - offset access = you cannot reuse bytecode of a trait because the order of the offset can be different in each trait users > > If you mean that a CompiledMethod of a trait cannot be added to the class' method dictionary, than that's not an issue. The current Trait implementation was changed, because shared CompiledMethods caused other problems. no this is not what I meant > If you mean that the same bytecodes can't be used, than that's neither a problem, because you can and should be compile the method again. Sharing trailer bytes may cause problems. > So adding a method from a trait to a class is simply recompiling it in the class' context. this is what we wanted to avoid. Also because you may have to recompile all the other methods of the class hierarchy because if a trait add an instance variable then you should recompile the subclasses when a trait get added with a state in the superclass. > Instance variables should be used by name during compilation. If there's a name collision then use the instance variable map I mentioned above. what is that the instance variable map? take the time to write an example >> - initialization of instances variables at the trait level and the composition at the class levele > > You can always rename a trait's method in your class. So if the trait has an #initialize method, then simply rename it to #initializeFooBar and send it from the class' #initialize method. Yes this is what the javascript implementation does but this is not that nice but may be there is no better solution. So indeed we could think about adding state. > > > Levente > >> >>> >>>> 3) again if nobody does anything and we just all cry on ourselves then nothing will happen. >>> >>> Tools are a must. No tools - no users. >> >> Exact. >> >>>> So for now identifying traits and learning is the way. Then we can refactor, redesign >>> >>> Well, Traits are in Squeak since 2006, IIRC they were available a few years earlier. So in the last X (at least 4) years the only good candidate to become a Trait was Magnitude. >> >> Come on. >> I will not answer to such statement because I'm positive thinking. >> >> 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

4 4

Re: [Pharo-project] akuhn/SUnit: run faster tests first & step through tests
by StÃ©phane Ducasse Oct. 25, 2010

Oct. 25, 2010

Lack of maintainers, too many unwanted features, lack of explanation, large changes... And this is not that several persons did not look at the code. It got more than the average. Now I'm thinking that with discussion and care we should really get another testing framework with the same API that SUnit because if we want that PharoSunit is the same as Sunit then we are doomed to be backward compatible and no real improvements. Stef On Oct 23, 2010, at 10:58 PM, Adrian Kuhn wrote: > Sad to hear that. > > Technical difficulties, or just lack of customers? ^^ > > --AA > > On Oct 23, 2010, at 08:05 , StÃ©phane Ducasse wrote: > >> It was too difficult to integrate. >> >> Stef >> >> On Oct 23, 2010, at 2:01 PM, Niko Schwarz wrote: >> >>> What's the status of akuhn/SUnit? I couldn't find his code in 1.2 core. >>> >>> Niko >>> >>> On Wed, Feb 3, 2010 at 1:13 PM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>> this loads well in the latest 1,1 core :) >>>> so now we should really have a look and these cool changes >>>> >>>> Stef >>>> >>>> On Jan 6, 2010, at 2:38 PM, Adrian Kuhn wrote: >>>> >>>>> SystemChangeNotifier uniqueInstance >>>>> noMoreNotificationsFor: TestCase. >>>>> Gofer it >>>>> disablePackageCache; >>>>> squeaksource: 'akuhn'; >>>>> package: 'SUnit'; >>>>> package: 'SUnitGUI'; >>>>> load. >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> >>> -- >>> http://scg.unibe.ch/staff/Schwarz >>> twitter.com/nes1983 >>> Tel: +41 076 235 8683 >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >

3 2

[Pharo-project] [ANN] ImageMap PharoKernel-12196
by Pavel Krivanek Oct. 25, 2010

Oct. 25, 2010

Hi, I generated the PharoKernel ImageMap (hypertext representation of the image content). You can see it here: http://goo.gl/nY2o The source code is here: http://goo.gl/J4T0 CSS style is here: http://goo.gl/Pxw2 Use it carefully, for 2,2MB image it generates 77,6MB of HTML files :-) Cheers, -- Pavel

4 9

Re: [Pharo-project] Smells looking at collections
by StÃ©phane Ducasse Oct. 25, 2010

Oct. 25, 2010

Eliot the main interest is in not having the responsibility to initialize the state of traits by the composite. Now since we know that doing for real is difficult this is why with did Nile: we build from scratch a real lib using traits and we wanted to see if we wanted state. The results were not really positive. Now also what people may not know is that the implementation of traits we have was a complete rewrite of the one of nathanael because proto are good but are proto. We try to keep xp for the research. Now I would like to take the time to rethink traits and its implementation. Stef On Oct 25, 2010, at 4:07 AM, Eliot Miranda wrote: > Hi Levente, > > in my experience playing with the Dan and Alan Borning's multiple inheritance implementation getting things to work was one thing, reasonably straighforward, but getting tool support right (file-out format so that things filed back in correctly, etc) was another, an dth ebulk of the work. Looking at your proposal below I see no problem getting it to work but see lots of problems integrating it, e.g. with Monticello, etc. Traits is already integrated with Monticello, supported with tests, etc. As such it is a much less risky or effortful proposition than a new scheme. So with that in mind are there important functional benefits of your scheme's direct state access as compared with traits that use accessors to access state that each user of a trait must implement? i.e. what are the key benefits you see in direct inst var access? > > best > Eliot > > 2010/10/24 Levente Uzonyi <leves(a)elte.hu> > On Sun, 24 Oct 2010, StÃ©phane Ducasse wrote: > > > > 2) well, this is difficult to get the money for the butter and the butter - we are trying. > > If you can compose classes the way you can add a trait to a class now with class and optional method level instance+class variable mapping, then you're done. It would be a lot simpler to use it _and_ it would also be a lot easier to implement it. Especially the tools part. > > I'm interested to hear more about that. > > so can you explain what you meant because I did not understand it. > > Okay, here is an example of my class composition idea. It works like Traits, but it supports state and there's no distinction between a trait and a class. Let's say I have a class named BidirectionalLink which can be used as a link in a linked list (with a head element). This will be used as a stateful trait. It's definition is like this: > > Object subclass: #BidirectionalLink > instanceVariableNames: 'next previous' > classVariableNames: '' > poolDictionaries: '' > category: 'ClassCompositionExample' > > It has a few methods: > > BidirectionalLink >> next > ^next > > BidirectionalLink >> next: aBidirectionalLink > next := aBidirectionalLink > > BidirectionalLink >> previous > ^previous > > BidirectionalLink >> previous: aBidirectionalLink > previous := aBidirectionalLink > > BidirectionalLink >> unlink > previous next: next. > next previous: previous > > BidirectionalLink >> linkAfter: aBidirectionalLink > previous := aBidirectionalLink. > next := aBidirectionalLink next. > aBidirectionalLink next: self. > next previous: self > > I have an existing class, let's call it ODatedEntry :). It has the following definition: > > ECSelectorEntry subclass: #ODatedEntry > instanceVariableNames: 'date' > classVariableNames: '' > poolDictionaries: '' > category: 'Ocompletion' > > As you can see, it inherits some state and behavior from ECSelectorEntry. My goal is to use the instances of this class in a linked list. So these objects should implement the same protocol with the same behavior as BidirectionalLink. I can't make it a subclass of BidirectionalLink, because I also need the behavior and state from ECSelectorEntry and we don't have multiple inheritance. So I'll compose the two classes. First I add the necessary instance variables to the class. Let's call them nextEntry and previousEntry: > > ECSelectorEntry subclass: #ODatedEntry > instanceVariableNames: 'date nextEntry previousEntry' > classVariableNames: '' > poolDictionaries: '' > category: 'Ocompletion' > > Then do the composition: > > ECSelectorEntry subclass: #ODatedEntry > uses: BidirectionalLink > instanceVariableNames: 'date nextEntry previousEntry' > classVariableNames: '' > poolDictionaries: '' > category: 'Ocompletion' > > Now this doesn't work, because ODatedEntry doesn't have instance variables named next and previous, but the methods of BidirectionalLink would like to use them. Of course I could have used those names in the previous step and (with a working implementation) this would just work out of the box. But the example is about the instance variable mapping. Let's say ~ is the composition operator which defines variable mapping for a class or a method. Then I can write the following: > > ECSelectorEntry subclass: #ODatedEntry > uses: BidirectionalLink ~ { #nextEntry -> #next. #previousEntry -> #previous } > instanceVariableNames: 'date nextEntry previousEntry' > classVariableNames: '' > poolDictionaries: '' > category: 'Ocompletion' > > This means: take all methods from BidirectionalLink, but replace the variable named next with nextEntry and previous with previousEntry. > So now ODatedEntry understands #next, #next:, #previous, #unlink, etc. > > This is the basic concept. There are some open questions, like: > - what happens when a composed method (or a method sent by a composed method, etc) has a super send? > - will the class also get the methods of the superclasses of the "trait"? > - how does it work on the class side? > - what about class variables? > - what if I don't want to use all methods, just a few? > > > > Tell us more. The problem we faced was > - offset access = you cannot reuse bytecode of a trait because the order of the offset can be different in each trait users > > If you mean that a CompiledMethod of a trait cannot be added to the class' method dictionary, than that's not an issue. The current Trait implementation was changed, because shared CompiledMethods caused other problems. > > no this is not what I meant > > If you mean that the same bytecodes can't be used, than that's neither a problem, because you can and should be compile the method again. Sharing trailer bytes may cause problems. > So adding a method from a trait to a class is simply recompiling it in the class' context. > > this is what we wanted to avoid. > Also because you may have to recompile all the other methods of the class hierarchy because if a trait add an instance > variable then you should recompile the subclasses when a trait get added with a state in the superclass. > > My idea is that traits don't add instance variables. The user of the trait maps the trait's variables to their own by name. So if a trait gets > a new variable, then only the trait and subclasses have to be recompiled. The recompilation is postponed until a method of the trait which uses the new instance variable is added to a class. > > > Instance variables should be used by name during compilation. If there's a name collision then use the instance variable map I mentioned above. > > what is that the instance variable map? > take the time to write an example > > See above. > > > Levente > > > - initialization of instances variables at the trait level and the composition at the class levele > > You can always rename a trait's method in your class. So if the trait has an #initialize method, then simply rename it to #initializeFooBar and send it from the class' #initialize method. > > Yes this is what the javascript implementation does but this is not that nice but may be there is no better solution. > > So indeed we could think about adding state. > > > > > > Levente > > > > 3) again if nobody does anything and we just all cry on ourselves then nothing will happen. > > Tools are a must. No tools - no users. > > Exact. > > So for now identifying traits and learning is the way. Then we can refactor, redesign > > Well, Traits are in Squeak since 2006, IIRC they were available a few years earlier. So in the last X (at least 4) years the only good candidate to become a Trait was Magnitude. > > Come on. > I will not answer to such statement because I'm positive thinking. > > 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

Oct. 25, 2010

why not :) could you send them to the list so that we can see them? On Oct 18, 2010, at 10:15 PM, Tudor Girba wrote: > How about getting the scripts from the Hudson integration (builder) of Lukas and translating them into Smalltalk? > > Cheers, > Doru > > > On 18 Oct 2010, at 21:52, stephane ducasse wrote: > >> Hi >> >> we would like to exercise a bit our scripting engine :) so if you have ideas of scripts that we should be able to write let us know. >> >> Stef >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "No matter how many recipes we know, we still value a chef." > > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

3 2

[Pharo-project] export information to PDF
by name name Oct. 24, 2010

Oct. 24, 2010

Hello, Could you tell me how can I export (or where I can found ) information that I can get with a getter into a .pdf file? Thanks

3 2

Re: [Pharo-project] After loading a package...all changes with "revision changed"
by Mariano Martinez Peck Oct. 24, 2010

Oct. 24, 2010

OK....found the problem. I think these are method recategorization. They say "revision changed" but since you don't see the category in the MC merge/changes browser, then you don't undrerstand why. In my case, the category changes were due to overrides. There is a package GlorpPostLoad which seems to have several overrides in Glorp package.... cheers mariano On Mon, Oct 4, 2010 at 12:57 PM, Gary Chambers <Gary.Chambers(a)pinesoft.co.uk > wrote: > Should be possibleâ¦ Iâll try to get some time to have a goâ¦ > > > > *From:* Mariano Martinez Peck [mailto:marianopeck@gmail.com] > *Sent:* 27 September 2010 9:51 PM > *To:* Pharo-project(a)lists.gforge.inria.fr > *Subject:* Re: [Pharo-project] After loading a package...all changes with > "revision changed" > > > > Gary, BWT, it would be nice to have a way to filter (hde) all those methods > as "revision changed" when seeing the changes. > After that, I am able to see only the really changed methods :) > > On Mon, Sep 27, 2010 at 10:42 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > > > > 2010/9/26 Javier PimÃ¡s <elpochodelagente(a)gmail.com> > > > > We had a similar problem in squeaknos package, but just for some kind of > classes. It was caused by having an initialize class method in classes > derived from ExternalStructure, maybe it's because of the same reason? look > there, you may get some answers. > > > Thanks. It is good to know I am not the only one. This bug is REAAAAALY > annoying since you cannot see your changes. > > I've checked and I have no #initialize at class level :( > > The only thing I found is class side #new implementd something like: > > new > > ^super new initialize. > > can this be the problem? > > where could I put a halt to see the problem ? > > thanks in advance > > mariano > > > > regards, > javier. > > 2010/9/26 Norbert Hartl <norbert(a)hartl.name> > > > > FYI I encountered the same problem in gemstone. The only thing I know is > that all loaded packages were created in pharo that showed this behaviour. > It didn't show up in a reproducable manner and some packages were clean > again after a few package updates. And for some month now I didn't see it. > > > > Norbert > > > Am 25.09.2010 um 21:12 schrieb Mariano Martinez Peck < > marianopeck(a)gmail.com>: > > > > On Sat, Sep 25, 2010 at 9:02 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > > On Sep 25, 2010, at 8:25 PM, Mariano Martinez Peck wrote: > > > Hi. I am having a probem with Glorp and I really have no idea what can > be. The problem is that I load the package Glorp and just after loading, I > do a "changes" in the MC Browser and I see a lot of classes with a lot of > changes and all of them like "revison changed". This is annoying since it > doesn't let me easily see what I have really changed. > > > > To reproduce: > > > > - Load the package "Glorp" from http://www.squeaksource.com/SqueakDBX > > - Open a MC Browser, select Glorp package and press the "Changes" button > agains the ss repo. And you will see :) > > May be the image used to save the package got a problem and changed the > timestamp of the methods. > So when you merge you get changed methods. > > > I've just tried commiting and load them in a clean image...same problem. > > And if it were what you say...is there a solution? > > thanks > > mariano > > > > > > > Any help is really appreaciated. > > > > Thanks > > > > Mariano > > > _______________________________________________ > > 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 > > > > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > Click here <https://www.mailcontrol.com/sr/wQw0zmjPoHdJTZGyOCrrhg==> to > report this email as spam. > > > <http://www.pinesoft.co.uk/> > > > > Ã¼ *Consider your responsibility to the environment - think before you > print!* > > > ******************************************************************************************************************************************* > > This email is from Pinesoft Limited. Its contents are confidential to the > intended recipient(s) at the email address(es) to which it has been > addressed. It may not be disclosed to or used by anyone other than the > addressee(s), nor may it be copied in anyway. If received in error, please > contact the sender, then delete it from your system. Although this email and > attachments are believed to be free of virus, or any other defect which > might affect any computer or IT system into which they are received and > opened, it is the responsibility of the recipient to ensure that they are > virus free and no responsibility is accepted by Pinesoft for any loss or > damage arising in any way from receipt or use thereof. > > > ******************************************************************************************************************************************* > > > Pinesoft Limited are registered in England, Registered number: 2914825. > Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA > > >

1 0