- Pharo-dev - lists.pharo.org

[Pharo-project] About nextPut:
by StÃ©phane Ducasse Oct. 18, 2008

Oct. 18, 2008

Hi damien I was looking at the following code Sequenceable>>flatCollect: aBlock "Evaluate aBlock for each of the receiver's elements and answer the list of all resulting values flatten one level. Assumes that aBlock returns some kind of collection for each element. Equivalent to the lisp's mapcan" "original written by a. Kuhn and released under MIT" | stream | self isEmpty ifTrue: [^self copy ]. stream := (self species new: self size) writeStream. self do: [ :each | stream nextPutAll: (aBlock value: each) ]. ^stream contents and if we send the message to a set we get a problem because WriteStream>>nextPut: anObject "Primitive. Insert the argument at the next position in the Stream represented by the receiver. Fail if the collection of this stream is not an Array or a String. Fail if the stream is positioned at its end, or if the position is out of bounds in the collection. Fail if the argument is not of the right type for the collection. Optional. See Object documentation whatIsAPrimitive." <primitive: 66> ((collection class == ByteString) and: [ anObject isCharacter and:[anObject isOctetCharacter not]]) ifTrue: [ collection := (WideString from: collection). ^self nextPut: anObject. ]. position >= writeLimit ifTrue: [^ self pastEndPut: anObject] ifFalse: [position := position + 1. ^collection at: position put: anObject] so the solution is to specialize flatCollect: on Set flatCollect: aBlock "Evaluate aBlock for each of the receiver's elements and answer the union of all resulting values. Assumes that aBlock returns some kind of collection for each element." | set | self isEmpty ifTrue: [^self copy]. set := Set new. self do: [ :each | set addAll: (aBlock value: each) ]. ^set Now I was wondering if there is way to avoid that. Stef

2 3

[Pharo-project] Cannot browse senders of #binary
by nicolas cellier Oct. 18, 2008

Oct. 18, 2008

Browse senders of #binary and... MessageSet >> #methodDisplayStringForClass:selector: -> ByteString doesNotUnderstand: #packageName This change seems recent.

2 4

[Pharo-project] New pharo dev
by Damien Cassou Oct. 18, 2008

Oct. 18, 2008

New pharo-dev available at http://code.google.com/p/pharo/wiki/Downloads?tm=2. It only contains the package you want (http://code.google.com/p/pharo/wiki/Packages) -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

3 2

[Pharo-project] etoy update on the pipe
by StÃ©phane Ducasse Oct. 17, 2008

Oct. 17, 2008

I will give a try to apply the fixes I did in the train today. Removed HaloMorph>>addScriptHandle: HaloMorph>>addViewHandle: Morph class>>additionsToViewerCategoryPenUse Morph class>>additionsToViewerCategoryObservation Morph class>>additionsToViewerCategoryMiscellaneous Morph class>>additionsToViewerCategoryMotion Morph>>isEtoyReadout Morph>>isaViewer Morph>>isTurtleRow Morph>>accumlatePlayersInto: aCollection andSelectorsInto: selectorsCollection Morph>>addStackItemsTo: Morph>>wrapWithAStack Morph>>abstractAModel Morph>>moveWithPenDownBy: Morph>>getPenColor Morph>>penUpWhile: Morph>>choosePenColor: Morph>>getPenDown Morph>>allMorphsWithPlayersDo: Morph>>appearsToBeSameCostumeAs: Morph>>addPlayerItemsTo: Morph>>containsCard: Morph>>getIndexInOwner Morph>>getPenSize Morph>>presentCardAndStackMenu Morph>>showBackgroundObjects Morph>>explainDesignations Morph>>insertCard Morph>>showForegroundObjects Morph>>goToNextCardInStack Morph>>goToPreviousCardInStack Morph>>showForegroundObjects Morph>>selectorsForViewer Morph>>selectorsForViewerIn: Morph>>showPlayerMenu Morph>>becomeSharedBackgroundField Morph>>slotSpecifications Morph>>putOnForeground Morph>>putOnBackground Morph>>makeHoldSeparateDataForEachInstance Morph>>stopHolingSeparateDataForEachInstance Morph>>viewMorphDirectly Morph>>x Morph>>x: Morph>>y Morph>>y: Morph>>x:y: Morph>>wrap Morph>>fenceEnabled Object>>isUniversalTiles Object>>isPlayerLike PasteUpMorph>>notePenDown: penDown forPlayer: player at: location PasteUpMorph>>updateTrailsForm PasteUpMorph>>drawPenTrailFor: aMorph from: oldPoint to: targetPoint PasteUpMorph>>addStackMenuItems:hand: PasteUpMorph>>presentCardAndStackMenu PasteUpMorph>>liftAllPens PasteUpMorph>>lowerAllPens PasteUpMorph>>linesForAllPens PasteUpMorph>>linesAndArrowsForAllPens PasteUpMorph>>dotsForAllPens PasteUpMorph>>addPenTrailsMenuItemsTo: PasteUpMorph>>arrowsForAllPens PasteUpMorph>>trailStyleForAllPens: PasteUpMorph>>printVocabularySummary PasteUpMorph>>clearTurtleTrails PasteUpMorph>>fenceEnabled PasteUpMorph>>fenceEnabled: PasteUpMorph>>toggleFenceEnabled PasteUpMorph>>fenceEnabledString PasteUpMorph>> PasteUpMorph>> PasteUpMorph>>browseAllScriptsTextually PasteUpMorph>>abandonCostumeHistory Pen>>arrowHeadFrom: prevPt to: newPt forPlayer: aPlayer PluggableTextMorphWithModel>>newTextContents: PluggableTextMorph>>selectionAsTiles PluggableTextMorph>>tileForIt Preferences>>fenceEnabled Quadrangle class>>exampleInViewer TextMorph>>setAllButFirstCharacter: TextMorph>>insertContentsOf: ScrollableField>>insertContentsOf: TransformationB2Morph ParagraphEditor>>selectionAsTiles TheWorldMainDockingBar>>clearTurtleTrails TheWorldMainDockingBar>>eToyVocabularySummary TheWorldMainDockingBar>>hideAllViewers TheWorldMainDockingBar>>hideAllViewersIn: TheWorldMainDockingBar>>showAllViewers TheWorldMainDockingBar>>clearTurtleTrails

2 1

[Pharo-project] One click feature list request/question
by Bill Schwab Oct. 17, 2008

Oct. 17, 2008

Hello all, Please feel free to say "that's going in the wrong direction," but it might be nice to have FFI, or at least the plugins, lurking in the one-click file structure. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029

7 8

[Pharo-project] [ANN] new 10095 prebuild image
by Torsten Bergmann Oct. 17, 2008

Oct. 17, 2008

Marcus wrote: >one-click will come soon, too. Will this be based on the newest VM sources so we can close issue 231? (I typically use the full screen mode to forget about the boring OS ;) Bill wrote: >might be nice to have FFI, or at least the plugins would at least vote for the plugins. FFI itself could be loaded if required. Thx Torsten -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/wasistshortview.php?mc=sv_ext_mf@gmx

5 5

[Pharo-project] copy dependent packages
by StÃ©phane Ducasse Oct. 16, 2008

Oct. 16, 2008

Hi guys did one of you implement copy which pay attention to copy also the dependent packages to a given repository? Because it would be really cool to have that. Stef

2 1

Oct. 16, 2008

Hi gary I removed Morph>>y following your changes but now when I open a class with a comment I get an error. Because splitterMorph uses y. I will put back the old methods. Stef

1 0

Oct. 16, 2008

hi all After spending a couple of hours redoing I imagine the same process as Gary and reading all the code I can tell you that people wanting Etoy to load back in any squeak versions do not know what they were talking about. seriously! I'm amazed by the amount of abstractions that could have been put elsewhere. Now if we try to learn from that here is my take on it: I think that what was missing is a kind of layering system so that etoy developers could enhance Morph (since I imagine that they wanted that any objects in the system could be scriptable, react as a card.....) but layer it and remove cleanly. May be a kind of classboxes system is what they should have implemented so that when you were in etoy you could get all the stuff but when when you are out of the etoy project you would get a nice little morphic. Stef

1 0

Oct. 16, 2008

hi guys I would like to get some support from the tools to help us curiving out etoys. Here is the scenario: when I see a method I would like to see a color or symbol which tell me how many sender kinds were calling this method either statically or dynamically. I would like to put etoy classes in red and see the colors propagating in the system. So we could get a kind of coloring schema. We could do the same with letters then we could have some single colored methods or mix Alex/Damien do you want to help because this could be fun? Then when i see how I work I always do a kind of yoyo between senders and implementers it would be really interesting to log the senders and implementers so that we could trace back the sequence and understand also how the remove happen and the frequency of the removal. Stef

1 0