squeakland January 2004

squeakland@lists.squeakfoundation.org

23 participants
33 discussions

Re: [Squeakland] Q: Leverage Overlapping Player to Etoys?
by Alan Kay 06 Jan '04

06 Jan '04

Hi Ned -- At 11:13 AM -0800 1/5/04, Ned Konz wrote: >On Monday 05 January 2004 8:25 am, Markus Gaelli wrote: > >> Did we overlook some other way to find out with Etoys which of the UFOS >> have been hit by our shot? > >Well, there's the colorSees: test. > >> If not, should be put it to miscellaneous? > >> Is it a problem that we only >> return one of possible many overlapped players? > >How would you return more than one? > >I've been thinking about making a CollectionPlayer that can apply commands and >slot setters to its members; if we had one of these it could be returned. >However, there's a problem with slot getters, and with the display of such a >collection (what should it look like if it's visible?). It should look like (and be) a Holder. > >> Should I send the changeset? > >Of course, though it may be of more interest to squeak-dev > >> Another question: How do you destroy Players with Etoys? Is there >> something there and hidden? > >You'd have to get rid of all the costumes. > >In the case of players with identical behavior, you'd probably want them to be >siblings, so there isn't the problem with class duplication. The "copy" >pseudo-slot getter gives you one of these. > >> We created the bombs of the UFOS by copying the "mother of all bombs". >> But we also wanted to >> destroy them, if they hit the ground. > >You could do > theBomb doMenuItem: 'delete' This is a good way. The way I do this is to do everything in a Playfield (which is a kind of Holder or vice versa). Then I set up another playfield "PF" to use as temporary trash. So: PF include theBomb PF removeAll When I'm doing stuff that results in lots of "atoms" in a Playfield, I reset by taking everything out of the playfield that I want to save (like the mother of the bomb) PF include bombMother and then do a Playfield removeAll. Cheers, Alan > >-- >Ned Konz >http://bike-nomad.com >GPG key ID: BEEA7EFE --

2 1

Re: [Squeakland] Q: Leverage Overlapping Player to Etoys?
by Markus Gaelli 06 Jan '04

06 Jan '04

Hi Ned, thanks for the quick answer. >> Did we overlook some other way to find out with Etoys which of the >> UFOS >> have been hit by our shot? > > Well, there's the colorSees: test. Ahm, yes, but the idea is to give a link to the specific player where the color was seen... > >> If not, should be put it to miscellaneous? > >> Is it a problem that we only >> return one of possible many overlapped players? > > How would you return more than one? Exactly. I just don't like the fact that my overlappingPlayer tile is kind of suggesting that there is only one player which could be overlapped. > > I've been thinking about making a CollectionPlayer that can apply > commands and > slot setters to its members; if we had one of these it could be > returned. > However, there's a problem with slot getters, and with the display of > such a > collection (what should it look like if it's visible?). I think this approach is worth a try: Go for it... > >> Should I send the changeset? > > Of course, though it may be of more interest to squeak-dev Done. > >> Another question: How do you destroy Players with Etoys? Is there >> something there and hidden? >> > You could do > theBomb doMenuItem: 'delete' Yes, thanks, this one should do the trick... Regards, Markus

1 0

Q: Leverage Overlapping Player to Etoys?
by Markus Gaelli 05 Jan '04

05 Jan '04

Hi, I showed a good friend of mine (a teacher) how to program space invaders completely with Etoys. You can try out the result here: http://www.squeakland.org/project.jsp?http://www.emergent.de/pub/ smalltalk/squeak/projects/petersInvaders.003.pr We used the common "seesColor" trick for the collision-detection, but we found it difficult to determine which UFO was hit by our laser, so I leveraged the existing Smalltalk Method called "Morph >> morphsInFrontOverlapping:" to a tile in miscellaneous called: "overlappingPlayer" in Etoys. Here an exemplifying screenshot: Did we overlook some other way to find out with Etoys which of the UFOS have been hit by our shot? If not, should be put it to miscellaneous? Is it a problem that we only return one of possible many overlapped players? Is there a better name than overlappingPlayer? Should I send the changeset? Another question: How do you destroy Players with Etoys? Is there something there and hidden? We created the bombs of the UFOS by copying the "mother of all bombs". But we also wanted to destroy them, if they hit the ground. I usually end up leveraging this from Smalltalk too, but I have the feeling, that I am not the only one here... I guess, you want to protect the innocent from destroying valuable players by accident, maybe the effect of a "destroy-tile" should be to stop all scripts and just put the player in the trash? Thanks, Markus and Peter

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

squeakland January 2004