Squeak-dev June 2001

squeak-dev@lists.squeakfoundation.org

122 participants
362 discussions

Re: Cassowary Demo Question
by Steve Wart 29 Jun '01

29 Jun '01

If you load them up you will see the title is 'How The Mouse Roars' Cheers, Steve Ross Boylan <RossBoylan(a)stanfordalumni.org> wrote: > > I'm also wondering what HTMR stands for in project names on the SuperSwiki.... > > Yours in curiosity.

1 0

Re: [BUG] SyntaxMorph testClass:andMethod:
by Bob Arning 29 Jun '01

29 Jun '01

Steve On Fri, 29 Jun 2001 09:19:08 -0800 Steve Wart <thecows(a)home.com> wrote: >1. The confusing bit is how to resize the scriptor. I read the class >comments on SyntaxMorph and couldn't get past the first step. After >spending about and hour and consulting with someone who was using it >with 3.0 we were able to track down the change and get the command to >work with the earlier version of the method. Since this method is only >used from StringHolder>>openSyntaxView, a hypothesis was put forth that >this change made it easier to drop SyntaxMorphs into books for >interactive demos. >3. The 'nasty' method is testClass:andMethod: -- in the sense that the >original window-based method was pretty short and easy to understand. >The new version of the method has what appear to be UI parameters >hard-coded into it, and it's not clear why the authors made these >changes. The changes were made to make script editors in the Universal tiles environment work correctly. If you change the final few lines #testClass:andMethod: to reas as follows: syn finalAppearanceTweaks. ">>SyntaxMorph setSize: nil andMakeResizable: outer.<<" outer setProperty: #autoFitContents toValue: true. outer openInWorld you will find it a bit friendlier. Cheers, Bob

1 0

Re: Cassowary Demo Question
by Ross Boylan 29 Jun '01

29 Jun '01

I went into the system browser and found the Cassowary-xxx categories; one of them is Cassowary-Demo. Another technique would be to interrupt the demo in the middle of it running (e.g., alt-. on Linux or Win) and look up the stack. The nice thing about smalltalk is that, unless someone is being perverse, you always have the source. On Fri, Jun 29, 2001 at 11:05:54AM -0400, Rosemary Michelle Simpson wrote: > Hi Ross, > > I have a newbie question to ask you triggered by the statement in your > message: > > > less taxing than "read the source code." > > How do you find out what the source is for a demo when all you have is the > executing demo? > > Thanks, > > R. > > >

1 0

Re: Fwd: BankAccount Tutorial
by Bob Arning 29 Jun '01

29 Jun '01

Greg, On Fri, 29 Jun 2001 11:13:51 -0400 (EDT) woods(a)weird.com (Greg A. Woods) wrote: >[ On Friday, June 29, 2001 at 08:52:58 (-0400), Dan Ingalls wrote: ] >> Subject: Re: Fwd: BankAccount Tutorial >> >> 3. This did not find anything I hoped for (users of a new centering >> message), except that it located the wonderfully revealing method, >> convertOldAlignmentsNov2000: varDict using: smartRefStrm >> which makes it quite clear that the old #centering: message has been >> replaced by a new #wrapCentering: message. > >This brings up a question I've had about managing change in message >protocols. > >It's very interesting to see that there are indeed instances of methods >such as the one you refer to above. > >It seems very good to write such methods and use them to convert >everything that happens to be in an image at the time, as well as to >leave them in the system for posterity, but this doesn't do anything for >code that might be written in older images, saved in changesets or >projects, etc. These methods are not there just for posterity. In fact, their primary purpose is to convert old instances that are encountered when loading a project created before the changeover into a more modern image, so they have a definite day-to-day utility. As for converting code, it might be possible to do *something*, but I'm not sure how useful it could be without a great deal of work. Sometimes the protocol change is a simple 1-to-1 replacement, using #foo in all cases instead of #fu, e.g. Other changes may not be so simple -- changes to the semantics of #hResizing: and #vResizing: necessitated a careful examination of each sender to determine whether #shrinkWrap or #spaceFill was the appropriate choice going forward. In an even larger view, these same changes mean that any Morph can do the job once done by AlignmentMorph and do it better. This may affect the design of some morphs such that layer(s) of nested morphs required to accomplish a given layout might be replaced with a single, more capable layer. How to search for these in any helpful way would be hard to implement. Cheers, Bob >Would it be possible to (also) collect such methods into an enhanced >"fileIn" that would be able to at least detect old protocols, if not >actually fix them on the way in?

1 0

Re: BankAccount Tutorial
by Bob Arning 29 Jun '01

29 Jun '01

Optionally, anyone could post an updated version on the public swiki at Ga Tech or on BSS. Cheers, Bob On Fri, 29 Jun 2001 11:15:41 -0400 Doug Way <dway(a)riskmetrics.com> wrote: >"Rev. Aaron" wrote: >> >> Do we all think that perhaps it is time to replace the code on that >> Morphic tutorial to work with 3.0 on the Swiki itself? It seems most >> newbies are using 3.0. > >Yes, I agree that the tutorial should be updated to work with 3.0. The tutorial itself is on squeak.org, not on a Swiki, so not just anyone can update it... perhaps whoever is in charge of squeak.org could update it. Would that be Russell? > >I assume it would just be a matter of pasting in the new code forwarded in Bob's message, plus maybe a note at the top indicating that the tutorial is compatible with 3.0.

1 0

Re: BankAccount Tutorial
by John Hinsley 29 Jun '01

29 Jun '01

Michael Guenter wrote: > > Hi, > > I have been working through the tutorial but when I try to "accept" the > following code, > > historyMorph > |bars m| > bars_history collect: [:v| Morph new extent: 5@v]. > m_AlignmentMorph newRow centering: #bottomRight. > m addAllMorphs: bars. > ^m > > Squeak tells me that "centering:" is an unknown selector. Of course, when I > told it to confirm and then tried to do a "printIt" in the workspace of the > following, I get an error. I believe I know enough about Squeak that I > shouldn't have had to ask it to confirm "centering:", and just because I did > confirm it, doesn't mean that their is an object to communicate with, am I > right? > > Is the tutorial wrong, or is my version of Squeak (3.0) inappropriate, or > have I made some error in copying it? > > Thanks for your time. Basically, the tutorial was written for an earlier version of Squeak, so the old alignment stuff doesn't work properly now. It certainly used to, so, strictly speaking, the tutorial isn't wrong. Someone did post a fix for it, but I can't find it and it looks like it may not have made it back to the tutorial. I'll try and find it tomorrow or you might like to trawl through the archived list at Yahoo. Cheers John -- ****************************************************************************** Marx: "Why do Anarchists only drink herbal tea?" Proudhon: "Because all proper tea is theft." ******************************************************************************

5 5

Re: Philosophical questions about collections
by Diego Gomez Deck 29 Jun '01

29 Jun '01

>Diego, > >On Fri, 29 Jun 2001 09:51:00 -0300 Diego Gomez Deck <DiegoGomezDeck(a)ConsultAr.com> wrote: >>I can't find the correct way to think about #= message for collections... > >You are not alone in this feeling. ;-) > >>For example, Dictionary use Set>>= that ignores keys. >> >>Bag, has not implemented the message. >> >>All the SequenceableCollection family seems to be good (IMHO). >> >>There exists a message that compares the elements of a collection with >>another ignoring the collection species? > >I don't think so, but you could do something like > > collection1 asSet = collection2 asSet >or > collection1 asArray = collection2 asArray > >The fact that these two options could easily produce different results suggests that there may be more than one way to think about collection equality. My inclination would be to write a method that did what I wanted in a particular situation and try to make it clear whether the order of the elements was important or not and whether duplicate elements should affect the result. Other factors, such as the precise way of comparing elements, may also be important. The other 'criteria' could be the way that the keys get compared. Example: d := Dictionary new. d at:1 put:'A'. d at:2 put:'B'. d at:3 put:'C'. {'A'. 'B'. 'C'} isEqualsTo: d > >Cheers, >Bob > Diego Gomez Deck

1 0

Luna/Borg Look for Squeak ?
by Torsten.Bergmann＠phaidros.com 29 Jun '01

29 Jun '01

Does anyone know who did the screenshots of the Luna and Borg look for Squeak at http://minnow.cc.gatech.edu/squeak/1869 ? Really cool! The name "Zurgle" in one of the screenshots reminds me on Jim Bensons WindowFrame Goodie ? Jim, could you tell us something about it ? Thanks Torsten

1 0

Re: Image Morphs
by Tim Olson 29 Jun '01

29 Jun '01

>I've been poking around the systems browser, and I've figured out how to >load a jpeg into an ImageMorph. But, how to I get access to that jpeg, >pixel by pixel (like to built a histogram of the image, for instance), and >write it back to disk? Or is the ImageMorph the wrong way to go about >this? You can get the form using: form := Form fromFileNamed: 'my_image_file.jpg'. This is a 32-bit-per-pixel form, stored as 4 8-bit color components (alpha, red, green, blue). To get the raw pixel bits: pixels := form bits. You can then do a histogram something like: redHist := Bag new. greenHist := Bag new. blueHist := Bag new. bits do: [:pel | redHist add: ((pel bitShift: -16) bitAnd: 255). greenHist add: ((pel bitShift: -8) bitAnd: 255). blueHist add: (pel bitAnd: 255)]. -- tim

1 0

RE: Image Morphs
by Torsten.Bergmann＠phaidros.com 29 Jun '01

29 Jun '01

Have a look at the PixelFilter demo accessible on Bobs Super Swiki (BSS) http://209.143.91.36/super.308 Download it from within you squeak using the orange "find" button at the bottom of your squeak window or install the squeak plugin from www.squeakland.org and open the project inside of your browser. The projects changeset includes the code. Also have a look at the Image processing framework source code. http://209.143.91.36/super.347 (Project Overview) and http://webs.sinectis.com.ar/jmvuletich/ImageProcessing/ImageProcessing.html for the code and samples. Cheers Torsten -----Original Message----- From: Joshua D. Boyd [mailto:jdboyd@cs.millersville.edu] Sent: Freitag, 29. Juni 2001 15:18 To: squeak(a)cs.uiuc.edu Subject: Image Morphs I've been poking around the systems browser, and I've figured out how to load a jpeg into an ImageMorph. But, how to I get access to that jpeg, pixel by pixel (like to built a histogram of the image, for instance), and write it back to disk? Or is the ImageMorph the wrong way to go about this? -- Joshua Boyd

1 0

← Newer
1
2
3
4
5
6
7
8
...
37
Older →

Jump to page: