On Jun 18, 2012, at 12:46 AM, Igor Stasenko wrote: > On 17 June 2012 23:17, Stéphane Ducasse <[email protected]> wrote: >>> Guys, we should hack this together. >>> When is next sprint? :) >> >> Next friday? >> > > Yeah,.. > because i still found things which i fail to understand in SystemNavigation: > some while ago we kind of decided that best would be to match the protocol(s) > of > CompiledMethod and RGMethodDefinition, so you can use either one or > another or mix of them > as a model for browsers/lists etc including SystemNavigation.
> > But it looks like we're still not there: > > methods := Object methodDict values. > SystemNavigation default browseMessageList: methods name: 'Object methods' > > fails miserably.. > but if i convert it to #methodReference, it works: > > methods := (Object methodDict values). > methods := methods collect: #methodReference. > SystemNavigation default browseMessageList: methods name: 'Object methods' > > and i feel like i was fooled: we replaced one wrapper - > MethodDefinition (or what was that?) > with another with just different name. But we still cannot use > CompiledMethod as a model for lists > etc.. > so can someone enlighten me, what is then changed, except a name(s)? This is just that the code to fill up the list is just using the wrong initialization (it should not wrap ring objects) There is no need for Ring objects there. Ring objects are only needed for remote package browsing, method versions, change recorder. Now we should just sit with ben and look at the filling up of the tools. > I am still clueless, why system tools cannot speak directly with > object(s) under the question, if necessary? See above. > > > -- > Best regards, > Igor Stasenko. >
