- Pharo-dev - lists.pharo.org

Re: [Pharo-project] About SourcedMethodReference
by StÃ©phane Ducasse Nov. 11, 2010

Nov. 11, 2010

On Nov 9, 2010, at 10:57 PM, Igor Stasenko wrote: > I think identity is better. It forcing more strict rules: no more than > one method reference > in system necessary for representing same method. I'm not sure I understand exactly what you mean. In the recent message or in the versions, you get mulitple version of the "same" methods but different methodreference. > > On 9 November 2010 23:48, Luc Fabresse <luc.fabresse(a)gmail.com> wrote: >> Hi all, >> When SourcedMethodReference have been introduced, some tests in >> SystemNavigationTest turned yellow. >> The tests are currently expecting a MethodReference. >> If I modify the tests to exepect a SourcedMethodReference, the problem is >> now on: >> SourcedMethodReference>>= >> ^self == aMethodReference. >> Why this has been redefined in SourcedMethodReference? >> I think that the super class (MethodReference) implementation is >> semantically better. No? >> >> MethodReference>>= anotherMethodReference >> "Answer whether the receiver and the argument represent the >> same object." >> ^ self species == anotherMethodReference species >> and: [(self classSymbol = anotherMethodReference classSymbol) >> and: [(self classIsMeta = anotherMethodReference classIsMeta) >> and: [self methodSymbol = anotherMethodReference methodSymbol]]] >> #Luc >> > > > > -- > Best regards, > Igor Stasenko AKA sig. >

2 1

[Pharo-project] Weird OB accept behavior
by Schwab,Wilhelm K Nov. 11, 2010

Nov. 11, 2010

I am using a 1.1.1 image with SystemBrowser defaultOpenBrowser OBSystemBrowserAdaptor I am debugging some code that I have not used for a while, so a few growing pains would not be a surprise. What DOES surprise me is the following: (1) select #plotFrom:to:using:keepGoing:plots: and accept the code; no errors are reported; fair enough (or is it?). (2) edit the source (even just adding a harmless new line) and accept, and the compiler (correctly, it appears) complains that arguments are already defined. I suspect the arguments are indeed stomping on instance variables that I added during the past year, and that confusion is the source of some seriously strange looking behavior. The point is that accept is apparently doing nothing or failing silently until I actually edit the source. I greatly prefer the error messages to silence; I assume the silence is related to a desire to get code loaded intact rather than having MC bark mid-load?? Bill

2 3

[Pharo-project] Finding Family-tree of images
by HwaJong Oh Nov. 11, 2010

Nov. 11, 2010

I have a hibbit of saving new version of images when i feed unsecure about something. So i end up a lot of disk space taken by them. I felt it is time for me to clean up the redundance in my disk. I wanted to have a sense of family tree of the images. l := (FileStream fileNamed:'Squeak4.0-basic-pocketcube-morphic.changes') contents lines. s := l select: [:each| each beginsWith: '----SNAPSHOT----']. i := OrderedCollection new. (s collect: [:ea| ea substrings at: 7 ]) do: [:e| (i includes: e) ifFalse: [i addLast: e.]. ]. i Now i have images names in time order. But still i need to run this code on every images not listed in evaluated result. How do you handle this problem? Best regards HwaJong Oh -- View this message in context: http://forum.world.st/Finding-Family-tree-of-images-tp3037106p3037106.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 1

[Pharo-project] deprecated message #sortBy: in Metacello
by Hilaire Fernandes Nov. 10, 2010

Nov. 10, 2010

When using the ConfigurationOfDrGeo to load DrGeo code and dependencies in latest 1.2 pharo core image, I get a Metacello first load, then I got a deprecated message error on the message sortBy: MetacelloMCProject>>versions ^self map values asArray sortBy: [:a :b | a <= b ] Does it mean the wrong Metacello is bootstrapped in the image? Or something else? Hilaire -- Dr. Geo, to discover geometry on Linux, Windows, MAC and XO http://community.ofset.org/index.php/DrGeo

2 2

Re: [Pharo-project] About SourcedMethodReference
by StÃ©phane Ducasse Nov. 10, 2010

Nov. 10, 2010

>> >> >>> Why do you want to remove MethodReference? >> >> The work was initiated from Benjamin's work on a new browser for 'recent changes', which basically needs to manipulate source references. >> >> MethodReference is being used to this end in various parts of the system but it represents various different things: class comment reference, method source reference, class definition reference, etc.. In addition, it always represents a reference to the current source. To retrieve older versions of the source, you need to walk the changes stream yourself. Last but not least, various different tools are walking the changes file with different implementations. >> >> From that experience, the idea arose to create a sourcereference model that explicitly models the different source elements (methods, class comments, definitions, etc) and that has explicit timestamping. At the same time, we don't want to break existing tools and have embedded the exisiting MethodReference in that model. >> > > +1 > > and please, keep in mind to delegate retrieving an actual source code > to some abstract layer. > So, then we can bind any remote storage to it, like database or file > system whatever. Yes we should probably have a look at method trailer with you but first we should build the infrastructure and test it. Stef

1 0

Re: [Pharo-project] Smalltalks 2010
by StÃ©phane Ducasse Nov. 10, 2010

Nov. 10, 2010

no idea ask the organizer On Nov 10, 2010, at 11:08 AM, Torsten Bergmann wrote: > Will "Smalltalks 2010" in Argentina be recorded to provide > the sessions on the web later or streamed to the web similar > to ESUG? > > Thx > T. > -- > GRATIS! Movie-FLAT mit Ã¼ber 300 Videos. > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome >

2 1

[Pharo-project] About SimpleMorphic
by Juan Vuletich Nov. 10, 2010

Nov. 10, 2010

Hi Folks, I apologize for not answering the original messages properly, I had mail deliver disabled, so I can't. I have enabled it, so I'll answer properly from now on. To Hillarie: If you don't use Polymorph, but want to build your own Morphs from scratch, SimpleMorphic is simpler, easier to understand, tweak and fix. To Doru: Let's do a comparison: Size of 4 core classes (Morph, MorphExtension, PasteUpMorph and WorldState) Pharo / Squeak / Cuis totalIvars: 39 / 46 / 26 totalClassVars: 15 / 10 / 5 totalInstMethods: 1170 / 1764 / 663 totalClassMethods: 55 / 71 / 16 Size of the whole Morph hierarchy Pharo / Squeak / Cuis totalClasses: 197 / 331 / 58 totalIvars: 649 / 1063 / 257 totalClassVars: 54 / 138 / 28 totalInstMethods: 6651 / 9186 / 2115 totalClassMethods: 303 / 858 / 127 SimpleMorphic is much smaller. Core classes are simpler and easier to understand, fix and extend. The most important part is that this is not blind removal of unused code. A lot of the functionality has been redesigned to make it simpler, and the removal was done with great care to result in a consistent system. This work started in 2004, so we're talking of about 6 years of careful work. All this means that SimpleMorphic does not support all the features that Pharo or Squeak might support. Please use the browsers and other tools in Cuis to check what it indeed can do. Talking about complexity, let's take for example, morph layout. This is started with #doLayoutIn: in Pharo and #doLayoutIfNeeded in SimpleMorphic. In Pharo, this method calls #adjustLayoutBounds: (19), #layout:in: (149), #layoutProportionallyIn: (10), #computeCellArrangement:in:horizontal:target: (87), #computeGlobalCellArrangement:in:horizontal:wrap:spacing: (31), #computeCellSizes:in:horizontal: (30), #computeExtraSpacing:in:horizontal:target: (136), #layoutLeftToRight:in: (91), #layoutTopToBottom:in: (91), #placeCells:in:horizontal:target: (70). The numbers in parenthesis are the sum of the lines of code of the implementors. Total lines of code for layout (taking only these most important methods) is 714. I doubt there are many people who really understand all of this code. In SimpleMorphic (Cuis), this calls #layoutSubmorphsIn: (10), #applyLayoutFrameIn: (11), #layout:in: (24). Total lines of code is 45. I believe any smalltalker could understand these in just minutes. I hope this makes makes it clearer to you what SimpleMorphic is. Cheers, Juan Vuletich

8 13

Re: [Pharo-project] Added Issue 3223 : Replace all sends to compile: in SystemNavigationTest by compileSilently:
by StÃ©phane Ducasse Nov. 10, 2010

Nov. 10, 2010

tx! On Nov 9, 2010, at 10:07 PM, Luc Fabresse wrote: > Fix in pharo task forces Tests-LucFabresse.242 > > #Luc

1 0

Nov. 10, 2010

> Why do you want to remove MethodReference? To be able to have MethodReferenceWithSource which will be renamed MethodReference and in the same time not put the system on its knees. ;) Right now MethodReference and friend sucks even if I already fixed a lot of Feature Envy. I do not like the logic to read change files with case statement #Comment .... all the bad logic it implies. There is a lack of real objects there. When you read the code of RecentMessages or recovery you can faint and re fixed a lot of Feature Envy, Duplicated code in 1.2. A lot is happening in 1.2 under the surface and a lot more will happen in 1.3. We want a real declarative model of source code. Veronica will start to work on that. We want to store also **all** the code of all the version in a database so that we can do real versions queries. Now the changes made on MethodReference are to make sure that we can have two methodReference with the same selector, class, but a different timestamp and source code. Like what we see in versions and recent changes, but done in a much better way. Benjaman rewrote completely recentMessages and this is great we can filter recentMessages based on time, class, packages..... and without the changes in MethodReference we had to put isKindOf and other nasty checks all over the place. So in summary, we want to put in place an infrastructure for building next generation tools. Ideally we will have ClassDefinition MethodDefinition InstanceVariableDefinition and migrate all the tools to them. We will experiment with that and certainly build a robust infrastructure for that. I hope it explains. We wrote a document explaining that. But now we should build it. Stef

1 0

Nov. 10, 2010

tx! I asked again inria to get a date for the web dav server. I hope to have an answer soon. On Nov 10, 2010, at 11:15 AM, Fabrizio Perin wrote: >

1 0