January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] PluggableTextMorph >> getText proposed modification

by StÃ©phane Ducasse

Hi guys I would really like to get your feedback on this change because it seems to me that menu are not good enough. Stef On Jan 12, 2010, at 6:14 AM, Ralph Boland wrote: > In my (Squeak) project I modified PluggableTextMorph >> getText to be > as follows: > > getText > "Retrieve the current model text" > > | newText | > getTextSelector isNil ifTrue: [^Text new]. > newText := (getTextSelector numArgs = 1) > ifTrue: [model perform: getTextSelector with: self] > ifFalse: [model perform: getTextSelector]. > newText ifNil: [^Text new]. > ^newText shallowCopy > > > The change allows the getTextSelector to pass an additional argument: self. > I made this change because I wanted to know which PluggableTextMorph > was asking for text. > This is useful when one has large numbers of similar PluggableTextMorphs. > Note that the method PluggableTextMorph >> acceptTextInModel > already does this so I didn't need to modify it. > Thus I think my change makes PluggableTextMorph more consistent. > > Any chance of this change being made a part of the Pharo image? > > Frankly, I would prefer that all the GUI objects that have get/set messages > had this capability. For CheckBoxes I earlier added the capability to return > either self or some arguments (by subclassing this time). > I am happy with the result. > > Another way I could do this would be to create a holder for the > PluggableTextMorph > (or other gui object) that would respond to the getText and > acceptTextInModel messages > and would know which PluggableTextMorph is speaking to it (since there > would be only one). > The holder would replace the model in the PluggableTextMorph and have > a reference to the original model to which it could forward messages. > Again this would allow me to have a large number of similar PluggableTextMorphs. > One could create a PluggableTextMorphHolder class for this or create > a single holder > class that could work with different Morph classes (only one at a timeof course) > (by responding to messages from all of them). It would be nice of > course if these > GUI holders already existed in Squeak/Pharo so I didn't have to invent them. > > Which approach do you think is better? > > Regards, > > Ralph Boland > > > -- > I've been middle class and I've been poor. > Middle class is better. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 13, 2010

Re: [Pharo-project] [ANN] WorkingSet

by Mariano Martinez Peck

It doesn't replace Algernon yet, in my opinion. They are similar tools, and maybe, this tool will eventually replace Algernon. But, so far, for me thay are still complementary tools. When I want to search a class or a method of a class I think that with Algernon is quicker. It has the autocompletion, and you can also open that class in a new browser or in the last used. In addition, it lets you see the methods, categories, and other stuff. Romain: If you want to try algernon, at least to get ideas, evaluate: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfAlgernon'; load. (Smalltalk at: #ConfigurationOfAlgernon) project lastVersion load. Once, installed, jut shift + enter On Wed, Jan 13, 2010 at 8:50 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > On Jan 13, 2010, at 2:56 AM, Romain Robbes wrote: > > > > > On Jan 12, 2010, at 5:59 PM, Simon Denier wrote: > > > >> > >> Yes! Many thanks Romain, I wanted something like that for the past 6 > months (cf ESUG'09 ;)) > >> > >> It's good to see that now, dev tools are also starting to move. > >> > >> Two remarks: > >> - it seems like it replaces a bit Algernon in its features and user > interaction. Am I right? Is this intended? > > > > hum ... I didn't try Algernon, actually. What I know is that it replaces > my antique "Teleporter", which was included in BrowserBooster. > > > >> - do you plan to have multiple working sets (only one being active at > any time)? This would allow one for switching between different > contexts/projects while working in a image, and perhaps even sharing with > other users (a bit like Mylyn) > > > > Yes, that would be nice. It's on the radar :-) > > > >> Future work: integration in the browser :) > >> > > > > How do you envision that? I tried to not be too browser-specific, as > these things are moving targets. > > I would not integrate that in browser because it makes the state machine of > this brittle tools brittler and like that you > can focus on working set functionality vs browser bugs :) > > > > > Romain > > > >> > >> > >> On 11 janv. 2010, at 16:42, Romain Robbes wrote: > >> > >>> Dear list, > >>> > >>> I've been working on a small tool to help people navigate their code in > Pharo. > >>> WorkingSet tracks the entities you've changed recently, and lets you > access them quickly. > >>> > >>> Load WorkingSet with: > >>> Gofer new > >>> squeaksource: 'WorkingSet'; > >>> package: 'WorkingSet'; > >>> load. > >>> > >>> Once loaded, press CMD-1 to activate or dismiss it. A User interface > pops up, with the following key mappings: > >>> -H to get this help message. > >>> -1-9 to select a recently changed class or method (depending on which > list is highlighted). > >>> -TAB to select methods, or the text field. > >>> -Left/Right arrow keys to select classes, methods, or text field. > >>> -Up/Down arrow keys to select an item in the list of classes or > methods. > >>> -ENTER in the text field to navigate to the entity you typed. > >>> -ENTER or SPACE in a class or method list to select the selected item. > >>> -U to browse the users of an entity (methods: senders, classes: > references). > >>> -S to browse the siblings of an entity (methods: implementors, classes: > hierarchy). > >>> -K to close all windows opened by WorkingSet. > >>> -L & R to shift the WorkingSet window left or right. (in case you use > several screens). > >>> -ESC or CMD-1 to dismiss WorkingSet. > >>> > >>> The text field allows you to enter classes and methods which are not > present in your working > >>> set. You can enter multiple classes/methods at once by separating them > with spaces. > >>> > >>> Enjoy! > >>> Romain > >>> -- > >>> Romain Robbes > >>> http://www.inf.unisi.ch/phd/robbes > >>> > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> -- > >> Simon > >> > >> > >> > >> > >> _______________________________________________ > >> 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 > > > > > > _______________________________________________ > > 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 >

Jan. 13, 2010

Re: [Pharo-project] clone vs shallowCopy

by Levente Uzonyi

On Wed, 13 Jan 2010, Lukas Renggli wrote: >> #clone and #shallowCopy have a difference in their semantics. If the vm >> cannot allocate enough space for the new object, #clone raises an error >> immediately, while #shallowCopy signals the low space semaphore, so the >> image or the user can do something, then retries the copying. > > Do we really need that? > I think #shallowCopy is enough. > It would be cool to merge #clone and #shallowCopy, and all the > different #deepCopy* instances. Also the implementation of #deepCopy > might need some cleanup, it seems to be rather complicated for such a > trivial task of copying a object graph. The implementation of #deepCopy seems to be pretty straightforward. I wonder how it could be simpler. Levente > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 13, 2010

Re: [Pharo-project] clone vs shallowCopy

by StÃ©phane Ducasse

Yeah so I accept any code and else we will do it slowly step by step. On Jan 13, 2010, at 8:54 AM, Lukas Renggli wrote: >> #clone and #shallowCopy have a difference in their semantics. If the vm >> cannot allocate enough space for the new object, #clone raises an error >> immediately, while #shallowCopy signals the low space semaphore, so the >> image or the user can do something, then retries the copying. > > Do we really need that? > > It would be cool to merge #clone and #shallowCopy, and all the > different #deepCopy* instances. Also the implementation of #deepCopy > might need some cleanup, it seems to be rather complicated for such a > trivial task of copying a object graph. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 13, 2010

Re: [Pharo-project] I cannot believe that Browser is relying on Object>>initialExtent

by StÃ©phane Ducasse

hold on :) we will kill a lot of them one at a time with a nice chainsaw :) Stef On Jan 13, 2010, at 8:58 AM, Lukas Renggli wrote: > And #defaultColor and #inform: and #modelSleep and #modelWakeUp and > #modelWakeUpIn: and ... > > 2010/1/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> argh....... >> May be not putting everything in Object would help. >> >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 13, 2010

Re: [Pharo-project] clone vs shallowCopy

by Lukas Renggli

> Now it would be nice to clean that because in VW you have copy, shallowCopy and postCopy and it works. > They removed veryDeepCopy and other friends even when they were at the time were they could burn engineering time > on that. +10 > So for me clone is one too many. > And worse cloning and object cannot be a shallowCopy semantics. it should be more a veryDeepInnerVeryCopy (I could not resist sorry) > Of course we already clean and remove the veryDeepInnerCopy.... No comment. The strange thing about #shallowCopy is in SequenceableCollection. It overrides #shallowCopy and does not return a shallowCopy. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 13, 2010

Re: [Pharo-project] Undo/Redo [was: Re: Object Buffer (implementation tryout)]

by StÃ©phane Ducasse

Did someone get a look in production at the Undo frameworks developed by alessandro warth? On Jan 13, 2010, at 7:18 AM, John M McIntosh wrote: > Yes, it's in the category "Sophie-Undo" > > If I consider the class AbstractUndoRecord > We hung 67 subclasses off it, which gives you an idea of the complexity of we what were doing (60 some UI actions), but also the fact it could handle it.. > > UndoManager class comment: > > UndoManager manages execution and storing of UndoRecords through #doAndAddRecord:. > It allows hierarchical grouping of UndoRecords through #openRecordGroup, #openRecordGroupNamed: and #closeRecordGroup. > Undo and redo is invoked by #undo and #redo. > > See UndoManagerTest for someExamples. > > Structure: > undoHistory OrderedCollection -- holds UndoRecords for undo > redoHistory OrderedCollection -- holds UndoRecords for redo > maxHistoryLength Integer -- Old UndoRecords in undoHistory are removed to keep it within given limits (0 for no Limit) > groupStack OrderedCollection -- temporary dataStructure to manage hierarchical grouping of UndoRecords > by #openRecordGroup and closeRecordGroup > historyInvalid Boolean -- flag to indicate, that the history is invalid and it must be deleted including the groupStack > > > On 2010-01-12, at 9:52 PM, Martin McClure wrote: > >> John M McIntosh wrote: >> >> [...] >>> >>> PS if anyone is interested the Undo/Redo Logic that Impara did for >>> Sophie was very well received, easy to use, and we could build a book >>> from scratch >>> then undo the entire creation, then redo it. This sounds complex, it >>> was. However the framework made it easy, one piece at a time... >>> Perhaps someone should harvest that since it *was* generic. >> >> Ooh, nice. A good undo/redo framework would be *so* *very* good to have. >> I'm afraid I can't be the one to harvest it, not anytime soon anyhow, >> but I hope someone picks it up. >> >> >> Regards, >> >> -Martin > > > > AbstractUndoRecord #() > SophieAddContentRootRecord #('contentRoot' 'book') > SophieAddDeleteStickyRecord #('sticky' 'page') > SophieAddStickyRecord #() > SophieDeleteStickyRecord #() > SophieAddEmbedBookRecord #('book' 'bookToEmbed') > SophieAddLeafNodeRecord #('book' 'leafNode' 'contentIndexPosition') > SophieAddStickiesRecord #('stickies' 'book') > SophieApplyFrameLocationStyleAttributesRecord #('bookModel' 'anchor' 'styleAttributes' 'oldStyleAttributes' 'page') > SophieApplyPageTemplateRecord #('page' 'template' 'undoData' 'redoData' 'allRemovedFrames') > SophieApplyParagraphStyleAttributesRecord #('book' 'marker' 'styleAttributes' 'oldStylesAttributes') > SophieApplyParagraphStyleRecord #('book' 'marker' 'style' 'oldStyles') > SophieApplyStyleToRangeRecord #('book' 'marker' 'styleAttributes' 'oldRangesStylesCollection') > SophieBookExtentUndoRecord #('bookModel' 'newExtent' 'oldExtent') > SophieBookStatisticRecord #('book' 'newStatistic' 'oldStatistic') > SophieDeleteContentRangeRecord #('book' 'marker' 'positionAfter' 'partialTree') > SophieEmbeddedBookUndoRecord #('ebook' 'embeddedBookResource' 'embeddedBookMapEntry') > SophieEmbeddedLinkedToBookUndoRecord #('ebook' 'embeddedBookMapEntry' 'embeddedBookResource') > SophieFrameRecord #('bookModel' 'frame') > SophieFrameZOrderRecord #('page' 'forward') > SophieFrameStyleUndoRecord #('bookModel' 'frame' 'attributes' 'state') > SophieFrameToTemplateRecord #('bookModel' 'frame' 'page' 'zIndex' 'reversed') > SophieInsertCharacterRecord #('book' 'character' 'position' 'positionAfter' 'style') > SophieInsertPageBreakRecord #('book' 'position' 'marker') > SophieInsertParagraphBreakRecord #('book' 'position' 'marker' 'characterStyle') > SophieLinkActionRecord #('book' 'target' 'action' 'actionIndex') > SophieLinkActionAddRecord #() > SophieLinkActionRemoveRecord #() > SophieLinkRecord #('book' 'target') > SophieFrameTriggerCleanupRecord #('cleanupStuff') > SophieLinkActionCloneRecord #('source' 'oldActions') > SophieMarkerAddDeleteRecord #('marker' 'book') > SophieMarkerAddMarkersRecord #() > SophieMarkerAddRecord #() > SophieMarkerDeleteRecord #('actions' 'markerSet') > SophieMarkerRangeRecord #('book' 'marker' 'newStart' 'newStop' 'oldStart' 'oldStop') > SophiePageRecord #('bookModel' 'page') > SophieFlowOrderChangeRecord #('frame' 'index' 'flow') > SophiePageStyleRecord #('styleAttributes') > SophiePageUndoRecord #('spine' 'index' 'page') > SophieInsertPageRecord #() > SophieMovePageRecord #('oldIndex') > SophiePasteFromImporterRecord #('book' 'importer' 'position' 'marker' 'partialTree') > SophiePromoteTemplateOverridesRecord #('book' 'pageTemplateFrame' 'page' 'frameMap' 'deletedTemplateFrames' 'overrideFrames' 'templateFrameFramesFromOverideFrames' 'frameOverrides' 'frameStyleOverrides' 'frameActionsOverrides' 'oldTemplateFrameFrames' 'oldPageFlowMap' 'oldTemplateFlowMap' 'oldPageTemplate' 'newTemplateFrameFrames' 'newPageFlowMap' 'newPageTemplate' 'allRemovedFrames' 'removedOverrideFrameContents') > SophieRegisterFlowRecord #('spine' 'flowID' 'content' 'contentID' 'flow') > SophieRemoveContentRootRecord #('contentRoot' 'book') > SophieRemoveFlowRecord #('spine' 'flow') > SophieRemoveFrameRecord #('bookModel' 'page' 'frame' 'wasLocalOverride') > SophieRemoveLeafNodeRecord #('book' 'leafNode' 'oldContentIndexPosition') > SophieRemovePagesRecord #('spine' 'indices' 'pages') > SophieReplaceLibraryTemplateRecord #('book' 'template' 'newTemplate') > SophieReplaceTemplateRecord #('book' 'template' 'oldTemplateCopy' 'newTemplate') > SophieResourceUndoRecord #('resources') > SophieResourceDeleteRecord #('player') > SophieResourceImportStreamRecord #('resourceManager' 'mimeType' 'stream') > SophieResourceImportURIRecord #('resourceManager' 'uri') > SophieResourceLinkToURIRecord #() > SophieResourceStoreRecord #('book' 'object' 'metaKey') > SophieSpineStateDeltaRecord #('book' 'spine' 'addedPages' 'removedPages') > SophieSpineStateRecord #('book' 'spine' 'prevState' 'postState') > SophieTimelineUndoRecord #('timelinePlayer') > SophieTimelineUndoAbstractEventsRecord #('events') > SophieTimelineUndoAddEventsRecord #() > SophieTimelineUndoDeleteEventsRecord #() > SophieTimelineUndoAddTimeline #('timeline' 'book') > SophieTimelineUndoDeleteTimeline #() > SophieTimelineUndoEventsMoveRecord #('undoData') > SophieTriggerObjectCleanupRecord #('triggerObject' 'undoInformations') > SophieUpdateLibraryStyleRecord #('book' 'newStyle' 'styleName' 'oldStyle') > UndoRecord #('undoable' 'doMessage' 'undoMessage' 'description') > SophieFrameUndoRecord #('bookModel' 'frame') > SophieLibraryResourceUndoRecord #('bookModel') > SophiePageInvalidationRecord #('bookModel' 'page') > SophieFrameAlignmentUndoRecord #('groupFrame' 'framesAndOldPositions' 'framesAndNewPositions') > SophieTriggerMarkerUndoRecord #('bookModel' 'marker') > UndoRecordWithPostMessage #('postMessage') > UndoRecordGroup #('description' 'subRecords') > SophieFrameGroupUndoRecord #('frameGroup' 'bookModel') > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 13, 2010

Re: [Pharo-project] Undo/Redo [was: Re: Object Buffer (implementation tryout)]

by StÃ©phane Ducasse

http://code.google.com/p/pharo/issues/list?thanks=1801 On Jan 13, 2010, at 7:18 AM, John M McIntosh wrote: > Yes, it's in the category "Sophie-Undo" > > If I consider the class AbstractUndoRecord > We hung 67 subclasses off it, which gives you an idea of the complexity of we what were doing (60 some UI actions), but also the fact it could handle it.. > > UndoManager class comment: > > UndoManager manages execution and storing of UndoRecords through #doAndAddRecord:. > It allows hierarchical grouping of UndoRecords through #openRecordGroup, #openRecordGroupNamed: and #closeRecordGroup. > Undo and redo is invoked by #undo and #redo. > > See UndoManagerTest for someExamples. > > Structure: > undoHistory OrderedCollection -- holds UndoRecords for undo > redoHistory OrderedCollection -- holds UndoRecords for redo > maxHistoryLength Integer -- Old UndoRecords in undoHistory are removed to keep it within given limits (0 for no Limit) > groupStack OrderedCollection -- temporary dataStructure to manage hierarchical grouping of UndoRecords > by #openRecordGroup and closeRecordGroup > historyInvalid Boolean -- flag to indicate, that the history is invalid and it must be deleted including the groupStack > > > On 2010-01-12, at 9:52 PM, Martin McClure wrote: > >> John M McIntosh wrote: >> >> [...] >>> >>> PS if anyone is interested the Undo/Redo Logic that Impara did for >>> Sophie was very well received, easy to use, and we could build a book >>> from scratch >>> then undo the entire creation, then redo it. This sounds complex, it >>> was. However the framework made it easy, one piece at a time... >>> Perhaps someone should harvest that since it *was* generic. >> >> Ooh, nice. A good undo/redo framework would be *so* *very* good to have. >> I'm afraid I can't be the one to harvest it, not anytime soon anyhow, >> but I hope someone picks it up. >> >> >> Regards, >> >> -Martin > > > > AbstractUndoRecord #() > SophieAddContentRootRecord #('contentRoot' 'book') > SophieAddDeleteStickyRecord #('sticky' 'page') > SophieAddStickyRecord #() > SophieDeleteStickyRecord #() > SophieAddEmbedBookRecord #('book' 'bookToEmbed') > SophieAddLeafNodeRecord #('book' 'leafNode' 'contentIndexPosition') > SophieAddStickiesRecord #('stickies' 'book') > SophieApplyFrameLocationStyleAttributesRecord #('bookModel' 'anchor' 'styleAttributes' 'oldStyleAttributes' 'page') > SophieApplyPageTemplateRecord #('page' 'template' 'undoData' 'redoData' 'allRemovedFrames') > SophieApplyParagraphStyleAttributesRecord #('book' 'marker' 'styleAttributes' 'oldStylesAttributes') > SophieApplyParagraphStyleRecord #('book' 'marker' 'style' 'oldStyles') > SophieApplyStyleToRangeRecord #('book' 'marker' 'styleAttributes' 'oldRangesStylesCollection') > SophieBookExtentUndoRecord #('bookModel' 'newExtent' 'oldExtent') > SophieBookStatisticRecord #('book' 'newStatistic' 'oldStatistic') > SophieDeleteContentRangeRecord #('book' 'marker' 'positionAfter' 'partialTree') > SophieEmbeddedBookUndoRecord #('ebook' 'embeddedBookResource' 'embeddedBookMapEntry') > SophieEmbeddedLinkedToBookUndoRecord #('ebook' 'embeddedBookMapEntry' 'embeddedBookResource') > SophieFrameRecord #('bookModel' 'frame') > SophieFrameZOrderRecord #('page' 'forward') > SophieFrameStyleUndoRecord #('bookModel' 'frame' 'attributes' 'state') > SophieFrameToTemplateRecord #('bookModel' 'frame' 'page' 'zIndex' 'reversed') > SophieInsertCharacterRecord #('book' 'character' 'position' 'positionAfter' 'style') > SophieInsertPageBreakRecord #('book' 'position' 'marker') > SophieInsertParagraphBreakRecord #('book' 'position' 'marker' 'characterStyle') > SophieLinkActionRecord #('book' 'target' 'action' 'actionIndex') > SophieLinkActionAddRecord #() > SophieLinkActionRemoveRecord #() > SophieLinkRecord #('book' 'target') > SophieFrameTriggerCleanupRecord #('cleanupStuff') > SophieLinkActionCloneRecord #('source' 'oldActions') > SophieMarkerAddDeleteRecord #('marker' 'book') > SophieMarkerAddMarkersRecord #() > SophieMarkerAddRecord #() > SophieMarkerDeleteRecord #('actions' 'markerSet') > SophieMarkerRangeRecord #('book' 'marker' 'newStart' 'newStop' 'oldStart' 'oldStop') > SophiePageRecord #('bookModel' 'page') > SophieFlowOrderChangeRecord #('frame' 'index' 'flow') > SophiePageStyleRecord #('styleAttributes') > SophiePageUndoRecord #('spine' 'index' 'page') > SophieInsertPageRecord #() > SophieMovePageRecord #('oldIndex') > SophiePasteFromImporterRecord #('book' 'importer' 'position' 'marker' 'partialTree') > SophiePromoteTemplateOverridesRecord #('book' 'pageTemplateFrame' 'page' 'frameMap' 'deletedTemplateFrames' 'overrideFrames' 'templateFrameFramesFromOverideFrames' 'frameOverrides' 'frameStyleOverrides' 'frameActionsOverrides' 'oldTemplateFrameFrames' 'oldPageFlowMap' 'oldTemplateFlowMap' 'oldPageTemplate' 'newTemplateFrameFrames' 'newPageFlowMap' 'newPageTemplate' 'allRemovedFrames' 'removedOverrideFrameContents') > SophieRegisterFlowRecord #('spine' 'flowID' 'content' 'contentID' 'flow') > SophieRemoveContentRootRecord #('contentRoot' 'book') > SophieRemoveFlowRecord #('spine' 'flow') > SophieRemoveFrameRecord #('bookModel' 'page' 'frame' 'wasLocalOverride') > SophieRemoveLeafNodeRecord #('book' 'leafNode' 'oldContentIndexPosition') > SophieRemovePagesRecord #('spine' 'indices' 'pages') > SophieReplaceLibraryTemplateRecord #('book' 'template' 'newTemplate') > SophieReplaceTemplateRecord #('book' 'template' 'oldTemplateCopy' 'newTemplate') > SophieResourceUndoRecord #('resources') > SophieResourceDeleteRecord #('player') > SophieResourceImportStreamRecord #('resourceManager' 'mimeType' 'stream') > SophieResourceImportURIRecord #('resourceManager' 'uri') > SophieResourceLinkToURIRecord #() > SophieResourceStoreRecord #('book' 'object' 'metaKey') > SophieSpineStateDeltaRecord #('book' 'spine' 'addedPages' 'removedPages') > SophieSpineStateRecord #('book' 'spine' 'prevState' 'postState') > SophieTimelineUndoRecord #('timelinePlayer') > SophieTimelineUndoAbstractEventsRecord #('events') > SophieTimelineUndoAddEventsRecord #() > SophieTimelineUndoDeleteEventsRecord #() > SophieTimelineUndoAddTimeline #('timeline' 'book') > SophieTimelineUndoDeleteTimeline #() > SophieTimelineUndoEventsMoveRecord #('undoData') > SophieTriggerObjectCleanupRecord #('triggerObject' 'undoInformations') > SophieUpdateLibraryStyleRecord #('book' 'newStyle' 'styleName' 'oldStyle') > UndoRecord #('undoable' 'doMessage' 'undoMessage' 'description') > SophieFrameUndoRecord #('bookModel' 'frame') > SophieLibraryResourceUndoRecord #('bookModel') > SophiePageInvalidationRecord #('bookModel' 'page') > SophieFrameAlignmentUndoRecord #('groupFrame' 'framesAndOldPositions' 'framesAndNewPositions') > SophieTriggerMarkerUndoRecord #('bookModel' 'marker') > UndoRecordWithPostMessage #('postMessage') > UndoRecordGroup #('description' 'subRecords') > SophieFrameGroupUndoRecord #('frameGroup' 'bookModel') > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 13, 2010

Re: [Pharo-project] clone vs shallowCopy

by Schwab,Wilhelm K

I admit I have never fully understood the concern, but Lewis' Art and Science makes reference to flaws in #deepCopy. Not much to go on, but pg. 60 in my copy. It is a good book, so I do not easily dismiss what he says. At around the time I saw that, #postCopy came to my attention - connection??? Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Lukas Renggli Sent: Wednesday, January 13, 2010 2:54 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] clone vs shallowCopy > #clone and #shallowCopy have a difference in their semantics. If the > vm cannot allocate enough space for the new object, #clone raises an > error immediately, while #shallowCopy signals the low space semaphore, > so the image or the user can do something, then retries the copying. Do we really need that? It would be cool to merge #clone and #shallowCopy, and all the different #deepCopy* instances. Also the implementation of #deepCopy might need some cleanup, it seems to be rather complicated for such a trivial task of copying a object graph. Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 13, 2010

Re: [Pharo-project] I cannot believe that Browser is relying on Object>>initialExtent

by Lukas Renggli

And #defaultColor and #inform: and #modelSleep and #modelWakeUp and #modelWakeUpIn: and ... 2010/1/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > argh....... > May be not putting everything in Object would help. > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 13, 2010