- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Collect all references to AnObsoleteFoo

by Mariano Martinez Peck

Martin, should be manage obsolete always that way (meaning to put such behavior directly inside Fuel)? If not, could be write your awesome code in the Fuel website? Thanks!!! :) On Sat, Apr 6, 2013 at 8:26 AM, roberto.minelli(a)usi.ch < roberto.minelli(a)usi.ch> wrote: > Martin, your solution is awesome. > > I've seen the presentation at Pharoconf about setting an analyzer to the > serializer and I was thinking in that direction. > > Thanks a lot, > R > > On Apr 5, 2013, at 4:59 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > > > As Fernando said, probably is better for you to substitute the obsolete > class by a ring definition. Look here: > > > > http://ws.stfx.eu/OAVG8IXKWOYA > > > > Don't need to filein the workaround of my previous email. > > > > Martin > > > > > > On Fri, Apr 5, 2013 at 4:47 PM, Martin Dias <tinchodias(a)gmail.com> > wrote: > > Hi, > > I'm sorry for my delay. I didn't stop to think a good solution. There > were interesting answers before mine. But if it's a prototype... maybe this > workaround helps you. I played with this code: > > > > http://ws.stfx.eu/HYWM1ZB9R45K > > > > (the first time I use the shared workspace :-) > > > > if you file in the attached file, it materializes the new A class. > > > > But this will be not useful for you, if either: > > - you don't have the "original class" at materialization time > > - you don't want to know if the class was obsolete at serialization time > > > > HTH > > Martin > > > > > > > > On Tue, Apr 2, 2013 at 7:33 AM, Yanni Chiu <yanni(a)rogers.com> wrote: > > On 02/04/13 12:50 AM, roberto.minelli-BHDiRLqP7qo(a)public.gmane.orgwrote: > > > > Is there any way to "browse" through such references to understand where > are they? > > > > From an inspector, choose the "Explore pointers", making sure you've > selected the object that you're trying to understand what is referencing it. > > > > It takes trial & error, and intuition on which pointers to follow. This > method has often been unsuccessful for me. > > > > Another approach (my memory is fuzzy), was to put a halt at a suitable > place during the Fuel serialization. Then explore the intermediate > structures used by Fuel, to try to find out why Fuel thinks it needs to > serialize that object. > > > > Yet another approach is to put a halt in the Fuel materialization, and > explore the intermediate structures used by Fuel. You might even set up a > mapping of the obsolete class to some temporary class, which allows Fuel to > fully materialize the saved objects. You can then explore the Fuel > intermediate structures, as well as the final de-serialized object > structure. > > > > > > > > > > > -- Mariano http://marianopeck.wordpress.com

April 6, 2013

Re: [Pharo-project] Collect all references to AnObsoleteFoo

by roberto.minelli＠usi.ch

Martin, your solution is awesome. I've seen the presentation at Pharoconf about setting an analyzer to the serializer and I was thinking in that direction. Thanks a lot, R On Apr 5, 2013, at 4:59 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > As Fernando said, probably is better for you to substitute the obsolete class by a ring definition. Look here: > > http://ws.stfx.eu/OAVG8IXKWOYA > > Don't need to filein the workaround of my previous email. > > Martin > > > On Fri, Apr 5, 2013 at 4:47 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > Hi, > I'm sorry for my delay. I didn't stop to think a good solution. There were interesting answers before mine. But if it's a prototype... maybe this workaround helps you. I played with this code: > > http://ws.stfx.eu/HYWM1ZB9R45K > > (the first time I use the shared workspace :-) > > if you file in the attached file, it materializes the new A class. > > But this will be not useful for you, if either: > - you don't have the "original class" at materialization time > - you don't want to know if the class was obsolete at serialization time > > HTH > Martin > > > > On Tue, Apr 2, 2013 at 7:33 AM, Yanni Chiu <yanni(a)rogers.com> wrote: > On 02/04/13 12:50 AM, roberto.minelli-BHDiRLqP7qo(a)public.gmane.org wrote: > > Is there any way to "browse" through such references to understand where are they? > > From an inspector, choose the "Explore pointers", making sure you've selected the object that you're trying to understand what is referencing it. > > It takes trial & error, and intuition on which pointers to follow. This method has often been unsuccessful for me. > > Another approach (my memory is fuzzy), was to put a halt at a suitable place during the Fuel serialization. Then explore the intermediate structures used by Fuel, to try to find out why Fuel thinks it needs to serialize that object. > > Yet another approach is to put a halt in the Fuel materialization, and explore the intermediate structures used by Fuel. You might even set up a mapping of the obsolete class to some temporary class, which allows Fuel to fully materialize the saved objects. You can then explore the Fuel intermediate structures, as well as the final de-serialized object structure. > > > >

April 6, 2013

Re: [Pharo-project] ConfigurationOf

by roberto.minelli＠usi.ch

On Apr 6, 2013, at 10:26 AM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > > On Apr 5, 2013, at 11:58 AM, roberto.minelli(a)usi.ch wrote: > >> Hi, >> >> I build the ConfigurationOf for my current project and it works fine, but I have some doubts. >> My project has dependencies on two other projects, namely Spy and Fuel. >> In my ConfigurationOf I'm loading these two projects before fetching my code. >> >> The point is that, for example, I'm loading Fuel even if it is already loaded in the current image and the same for Spy. >> >> Could you help me in creating a ConfigurationOf which only loads those projects if not already in the image and eventually only updates them to the last version? > > > this is the default behavior of metacello so I do not understand what you mean. Good to know! Thanks. > Did you read the metacello chapter I wrote? > >> >> Thanks in advance, >> R >> >> P.s. Here (http://ws.stfx.eu/QOMGC86FZTG) is my current baseline for the ConfigurationOf. > >

April 6, 2013

Re: [Pharo-project] [Preview] Branch test coverage analysis tool for Pharo 3.0 :)

by ClÃ©ment Bera

Actually, it is quite different than Jejak. Implementation wise, Jejak used Opal so I guess it relies on bytecode modification to do its analysis where my tool relies on ast annotations. This implies some difference in features. It seems that Jejak record all calls, all values and all assignments in a method (which is byte code level feature), whereas I record for each ast node if it was interpreted or not (which is ast level feature). I guess there would be a little difference in the use cases. 2013/4/6 Frank Shearar <frank.shearar(a)gmail.com> > On 6 April 2013 07:47, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Clement built in a couple of hours the following nice branch >> analysecoverage tools :) >> It is dead slow but cool. >> > > By "branch coverage tool" do you mean Jejak? > > frank > > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

April 6, 2013

Re: [Pharo-project] How to define a ConfigurationOf with a #development version that depends on a baseline?

by Marten Feldtmann

In all the discussions about how to manage/organize Smalltalk code - I would like to add, that ENVY (though it's so old) with its config maps, applications, prerequisites is a pretty good example how it works. Take a look at the only available ENVY implementation today (VAST) and think about the way they did it in the eighties ... The ENVY-(concept - not the implementation) is still a master peace in this area - even when compared with VS or Eclipse - and it supports the power of Smalltalk very much. There are questionable parts of ENVY and I do not use these parts of it very often. But even these questionable parts of ENVY have not been better solved by other Smalltalk source code management systems. I've repositories, which are around 10 years old - and ALL code is still there, all versions for all different platforms - down to methods differences within a mouse click and the speed within a LAN is so good. Marten > On Apr 5, 2013, at 11:28 PM, Alexandre Bergel<alexandre.bergel(a)me.com> wrote: > >> Just a question: Is there any plan for a Metacello 2? >

April 6, 2013

Re: [Pharo-project] [Preview] Branch test coverage analysis tool for Pharo 3.0 :)

by Frank Shearar

On 6 April 2013 07:47, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Clement built in a couple of hours the following nice branch > analysecoverage tools :) > It is dead slow but cool. > By "branch coverage tool" do you mean Jejak? frank

April 6, 2013

Re: [Pharo-project] Resuming Issue Tracker Mailing List

by Camillo Bruni

On 2013-04-06, at 10:36, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Apr 6, 2013, at 10:30 AM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > >> what do you mean? >> because I get fog mails. >> > > The old list got a mail for every change done on the trackerâ¦ > > We can do that again: we can subscribe it to all the projects. But it might be a bit > too much. > > People can easily subscribe just themselfs: > -> My Settings > -> Subscribe > -> Select ALL PROJECTS when creating the subscription > Most of it is documented on the wiki, here: https://pharo.fogbugz.com/default.asp?W46

April 6, 2013

Re: [Pharo-project] One SlideShare, One Youtube channel for Pharo?

by stephane ducasse

Ok so we wait that other people reply and we do an organised action. Stef On Apr 6, 2013, at 10:33 AM, Max Leske <maxleske(a)gmail.com> wrote: > +1 > > And I like Vimeo more :) > > On 06.04.2013, at 10:28, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > >> It will be cool to use some service, that allows 'groups'. For example on vimeo you can create a Pharo group and then include there videos of the users. This way you do not have to re-uppload content that is already there, and people get their credit. >> >> uko >> >> On 6 ÐºÐ²ÑÑ. 2013, at 09:48, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >>> Hi guys >>> >>> I would love to have one >>> - slideshare for pharo presentations reachable from the web site. >>> >>> http://www.slideshare.net/search/slideshow?searchfrom=header&q=pharo >>> >>> - videos conference/presentation on Youtube >>> http://www.youtube.com/results?search_query=pharo+st&oq=pharo+st&gs_l=youtu… >>> >>> >>> - "lectures" >>> >>> http://www.jarober.com/blog/blogView?content=st4u_pharo is wonderful :) >>> http://www.jarober.com/blog/blogView?content=st4u_tools >>> http://www.jarober.com/blog/blogView?content=st4u_pharo_net >>> >>> http://www.pharocasts.com >>> >>> What do you think? >>> Does anybody want to take the lead for that? >>> >>> >> >> > >

April 6, 2013

[Pharo-project] [Issue Tracker] Fogbugz down April 7th, 2013 from 0200 to 0700 UTC

by Marcus Denker

On Demand services offline this weekend Our On Demand services will be offline this weekend, April 7th, 2013 from 0200 to 0700 UTC (April 6th, 2200 - April 7th 0300 EDT) for a scheduled maintenance. For more information, please read our status blog at fogcreekstatus.com.

April 6, 2013

Re: [Pharo-project] Resuming Issue Tracker Mailing List

by Marcus Denker

On Apr 6, 2013, at 10:30 AM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > what do you mean? > because I get fog mails. > The old list got a mail for every change done on the trackerâ¦ We can do that again: we can subscribe it to all the projects. But it might be a bit too much. People can easily subscribe just themselfs: -> My Settings -> Subscribe -> Select ALL PROJECTS when creating the subscription > Stef > > On Apr 5, 2013, at 2:46 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > >> Can we please convert this to work with fogbugz asap? I'm finding it >> difficult to track our progress without it... we've been spoiled ;) >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/Resuming-Issue-Tracker-Mailing-List-tp4679712.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > >

April 6, 2013