etoys-dev December 2012

etoys-dev@lists.squeakfoundation.org

12 participants
31 discussions

Champaign Unit 4 Pilot of Etoys in the middle schools
by Kathleen Harness 30 Dec '12

30 Dec '12

Hi, I have attached an article published in the News Gazette today. Please share with others who will be interested in this pilot. There are some excellent quotes from students and their teachers. Regards and Happy New Year, Kathleen

1 0

Re: [etoys-dev] [etoys-notify] [JIRA] Created: (SQ-1144) When exiting Etoys, you should be asked if you want to save your work
by David Corking 24 Dec '12

24 Dec '12

Kathleen wrote : >> I agree with Bert, "explicit saving is the better trade off". This is a great feature request, though Bert's and Kathleen's conclusion seems right to me. We should bear in mind that unless we implement Steve's request, Etoys defies the Sugar UI guidelines (IMHO.) http://wiki.sugarlabs.org/go/Human_Interface_Guidelines/The_Laptop_Experien… Eventually, it would be nice for learners if Sugar and Etoys 'keep' behaviours were harmonized. One possibility might be to treat each project as a separate Activity, though I won't post that as a feature request, as I haven't thought it through, and I suspect it invites large challenges both for engineering and for usability. David

1 0

Re: [etoys-dev] [etoys-notify] [JIRA] Created: (SQ-1144) When exiting Etoys, you should be asked if you want to save your work
by K. K. Subramaniam 24 Dec '12

24 Dec '12

On Saturday 22 Dec 2012 1:21:17 AM Stephen Thomas wrote: > When exiting Etoys, you should be asked if you want to save your work Is this step really necessary? I realize it is very frustrating when someone presses the exit button and loses hours of work, but that is better handled by disabling Exit button until changes are either saved or rolled back. Why have an active Exit button when it is unsafe? Regards .. Subbu

3 2

STIC 2013: Call for Participation
by James Robertson 21 Dec '12

21 Dec '12

Your Chance to Participate: STIC 2013 30th Anniversary of Smalltalk Conference STIC is a forum where Smalltalk professionals, researchers, and enthusiasts can meet and share ideas and experiences. We are currently accepting proposals for talks involving Smalltalk technology and other areas of innovation in the software industry. We’re looking forward to an excellent conference, and need your participation to maintain the high technical level of the conference! We are also looking for academic papers for the “Smalltalk Directions” part of the conference. If you plan to submit a paper, please follow the same directions listed below for presentations. Such papers should address possible future directions for Smalltalk and/or Smalltalk inspired dynamic languages. The conference will take place at the Wigwam Resort in Phoenix, Arizona between June 9 - June 12, 2013. Presentations will have 45 minutes time slots including discussion. They may be in the form of: History of Smalltalk - It’s the 30th Anniversary of the language - we would love to see presentations on this topic Technical Presentations Experience Reports Technology Demonstrations Panel Discussions Workshops Describe Your Idea to Us! Proposals should be submitted by email to Sts_Speakers(a)stic.st and should include the following information: Name Contact Information Type of Presentation Brief Abstract Short Biography for the Presenter(s) Any Date/Time Constraints Any Other Information You Think We Should Know If you cannot discuss the internal application you are working on due to corporate restrictions, perhaps you can discuss the application’s component usage or development process. We also plan to reserve time for short presentations, in the form of Lightning Talks and short technology demonstrations - but these will be available for sign-up at the conference rather than as advance proposals. These talks will be limited to a 5-8 minute time window, so if you intend to volunteer for one at the conference, be prepared for that! Submissions should be received by February 15, 2013, and should be submitted either in PDF or Word (Microsoft) format. Note that submissions with incomplete information may be rejected – particularly if bio or abstract information is missing. Presenters will qualify for a significantly discounted registration - if your talk is accepted, we’ll have full details on the specifics. For updates and announcements about the conference, please visit us on the web at http://www.stic.st James Robertson http://www.jarober.com jarober(a)gmail.com

1 0

Re: [etoys-dev] Etoys Reference Manual Vol. II
by Edward Mokurai Cherlin 18 Dec '12

18 Dec '12

On Sun, December 16, 2012 3:54 am, Rita Freudenberg wrote: > Hi Ed, > > I'm sorry there was no answer yet. I had hoped for someone to acknowledge my suggestion sooner, and say that it would take a while to evaluate. Thank you for doing so now. > No comments mean no one had the time to > comment right now. I hope to find the time during christmas break. But I > don't want you to assume all your suggestions are agreed upon. That said, > you made certain good points and these will definitely be considered. OK. That's in line with what I expected. > I agree with Steve, feel free to go on with Volume II. Right, then. I will set up Vol. II and move the Squeak materials out of the Volume I draft. I will wait to hear whether splitting the tiles chapter is considered to be a good idea, and everything else concerning Vol. I. > Greetings, > Rita > > Von meinem iPhone gesendet Gibt es Etoys für das iPhone? > Am 16.12.2012 um 01:59 schrieb Edward Mokurai Cherlin > <mokurai(a)sugarlabs.org>: > >> I haven't seen any comments. Without objection, I will proceed. >> >> On Wed, Dec 12, 2012 at 11:45 AM, Edward Mokurai Cherlin >> <mokurai(a)sugarlabs.org> wrote: >>> I have been thinking about Rita's suggestion to split the Etoys >>> Reference Manual material into two volumes. This is how I see the >>> split. Comments, please. >>> >>> Etoys Reference Manual >>> outline >>> >>> Vol. I >>> >>> Etoys Programming >>> >>> Introduction >>> Getting Started >>> User Interface >>> Basic Objects >>> More Objects >>> Common Tiles (everything common to Morphs) >>> Less Common Tiles (every other category) >>> Etoys Scripting >>> Tile types and components (move from Common Tiles) >>> Variable data types >>> Custom events >>> Script editor >>> Running and stepping scripts >>> Ticking >>> Gold Box >>> Menu >>> Event-based programming >>> Parallel programming (include Copies and Siblings) >>> Glossary >>> Further Reading >>> Etoys by Example >>> Kedama manual >>> Waveplace tutorials >>> etc. >>> Credits >>> >>> Vol. II >>> >>> Etoys Internals >>> >>> Introduction >>> This is not a manual of Squeak or Smalltalk >>> From Etoys into Squeak: How and Why >>> Squeak and Smalltalk: the irreducible minimum >>> Object structure >>> Objects >>> Classes and Metaclasses >>> Methods and Selectors >>> Variable types >>> Smalltalk syntax >>> Accessing Squeak from Etoys >>> Translating scripts to text >>> Squeak objects on Etoys menus >>> Etoys/Squeak Development Environment >>> Players and Costumes >>> Introspection and Development Tools >>> Accessing Etoys Objects in Squeak >>> Implementation of Etoys >>> Squeak definitions of Morphs and other Etoys objects >>> The Object Catalog >>> Viewer Category Definitions >>> Squeak definitions of Etoys Scripting Tiles >>> Etoys Preferences >>> Etoys Friendly Off >>> Known Errors >>> Mime Types >>> Glossary >>> Further Reading >>> Squeak by Example >>> Gnu Smalltalk Manual >>> etc. >>> Credits -- Edward Mokurai (默雷/निशब्दगर्ज/نشبدگرج) Cherlin Silent Thunder is my name, and Children are my nation. The Cosmos is my dwelling place, the Truth my destination. http://wiki.sugarlabs.org/go/Replacing_Textbooks

5 4

Etoys Reference Manual Vol. II
by Edward Mokurai Cherlin 16 Dec '12

16 Dec '12

I have been thinking about Rita's suggestion to split the Etoys Reference Manual material into two volumes. This is how I see the split. Comments, please. Etoys Reference Manual outline Vol. I Etoys Programming Introduction Getting Started User Interface Basic Objects More Objects Common Tiles (everything common to Morphs) Less Common Tiles (every other category) Etoys Scripting Tile types and components (move from Common Tiles) Variable data types Custom events Script editor Running and stepping scripts Ticking Gold Box Menu Event-based programming Parallel programming (include Copies and Siblings) Glossary Further Reading Etoys by Example Kedama manual Waveplace tutorials etc. Credits Vol. II Etoys Internals Introduction This is not a manual of Squeak or Smalltalk From Etoys into Squeak: How and Why Squeak and Smalltalk: the irreducible minimum Object structure Objects Classes and Metaclasses Methods and Selectors Variable types Smalltalk syntax Accessing Squeak from Etoys Translating scripts to text Squeak objects on Etoys menus Etoys/Squeak Development Environment Players and Costumes Introspection and Development Tools Accessing Etoys Objects in Squeak Implementation of Etoys Squeak definitions of Morphs and other Etoys objects The Object Catalog Viewer Category Definitions Squeak definitions of Etoys Scripting Tiles Etoys Preferences Etoys Friendly Off Known Errors Mime Types Glossary Further Reading Squeak by Example Gnu Smalltalk Manual etc. Credits -- Edward Mokurai (默雷/निशब्दगर्ज/نشبدگرج) Cherlin Silent Thunder is my name, and Children are my nation. The Cosmos is my dwelling place, the Truth my destination. http://wiki.sugarlabs.org/go/Replacing_Textbooks

2 2

Etoys: Tools-kfr.15.mcz
by commits＠source.squeak.org 15 Dec '12

15 Dec '12

Karl Ramberg uploaded a new version of Tools to project Etoys: http://source.squeak.org/etoys/Tools-kfr.15.mcz ==================== Summary ==================== Name: Tools-kfr.15 Author: kfr Time: 15 December 2012, 2:10:31 am UUID: 7590fc64-07a8-9246-a833-920b979b5234 Ancestors: Tools-kfr.14 Use unique name in code string for PhraseTile for other players than self. =============== Diff against Tools-kfr.14 =============== Item was changed: ----- Method: MethodHolder>>acceptDroppingMorph:event:inMorph: (in category 'drag and drop') ----- acceptDroppingMorph: dropee event: evt inMorph: targetMorph "Return the dropee to its old position, and add a reference to it at the cursor point." + | referenceName selfUniqueName dropeeUniqueName | + selfUniqueName := (self dependents first )owner playerScripted uniqueNameForReference. - | externalName | (dropee isTileLike) ifTrue:[dropee isTileMorph + ifFalse:[ referenceName := dropee codeString unparenthetically. + dropeeUniqueName := dropee associatedPlayer uniqueNameForReference. + (dropeeUniqueName = selfUniqueName) + ifFalse:[referenceName := referenceName copyReplaceAll: 'self' with: dropeeUniqueName .]] + ifTrue:[referenceName := dropee actualObject uniqueNameForReference]] + ifFalse:[referenceName := dropee assuredPlayer uniqueNameForReference]. + targetMorph correctSelectionWithString: referenceName. - ifFalse:[ externalName := dropee codeString unparenthetically] - ifTrue:[externalName := dropee actualObject uniqueNameForReference]] - ifFalse:[externalName := dropee assuredPlayer uniqueNameForReference]. - targetMorph correctSelectionWithString: externalName. dropee rejectDropMorphEvent: evt. ^ true "success" !

1 0

Re: [etoys-dev] Etoys: Tools-kfr.14.mcz
by Steve Thomas 14 Dec '12

14 Dec '12

On Fri, Dec 14, 2012 at 4:06 AM, karl ramberg <karlramberg(a)gmail.com> wrote: > > > On Fri, Dec 14, 2012 at 6:14 AM, Steve Thomas <sthomas1(a)gosargon.com>wrote: > >> Karl, >> >> Thanks, so just to ensure my understanding, this is basically allows me >> to drop a "tile representing an object" into a textual script and the >> referencenName (as opposed to the externalName, which is what the user sees >> when you get the halo) is inserted for use in the textual script. This is >> needed because the externalName is not necessarily unique and can't be >> referenced directly by just using that name in a script. >> >> So this is good and useful. >> > > Textual scripts are way more useful by this addition :-) > > You can drop any morph or "tile representing an object" and it should > insert it's unique reference name. > > You can also drop any PhraseTile and it should expand to it's code string. > Just tried it, way cool. > (I does not handle correct identification of phrases from other players > yet, so all phrases expand to 'self ...' etc. ( I'll look at this issue. It > should not be hard to implent) > That would be nice too. Thanks.

1 0

Re: [etoys-dev] Etoys: Tools-kfr.14.mcz
by Bert Freudenberg 14 Dec '12

14 Dec '12

On 2012-12-13, at 07:59, commits(a)source.squeak.org wrote: > Karl Ramberg uploaded a new version of Tools to project Etoys: > http://source.squeak.org/etoys/Tools-kfr.14.mcz > > ==================== Summary ==================== > > Name: Tools-kfr.14 > Author: kfr > Time: 13 December 2012, 8:59:15 am > UUID: ca9017f6-5c84-284c-a508-fbabbe39c1dd > Ancestors: Tools-kfr.13 > > A little better conversion of tiles to code > > =============== Diff against Tools-kfr.13 =============== > > Item was changed: > ----- Method: MethodHolder>>acceptDroppingMorph:event:inMorph: (in category 'drag and drop') ----- > acceptDroppingMorph: dropee event: evt inMorph: targetMorph > "Return the dropee to its old position, and add a reference to it at the cursor point." > | externalName | > (dropee isTileLike) > ifTrue:[dropee isTileMorph > + ifFalse:[ externalName := dropee codeString unparenthetically] > - ifFalse:[^dropee rejectDropMorphEvent: evt. ] > ifTrue:[externalName := dropee actualObject uniqueNameForReference]] > ifFalse:[externalName := dropee assuredPlayer uniqueNameForReference]. > targetMorph correctSelectionWithString: externalName. > dropee rejectDropMorphEvent: evt. > ^ true "success" > ! It's a bit misleading that you call the temp var "externalName" because the #externalName message returns the user-visible name of a player, not the unique name for reference. They are sometimes the same, but sometimes not. "referenceName" would be better. - Bert -

3 4

Etoys: Tools-kfr.14.mcz
by commits＠source.squeak.org 13 Dec '12

13 Dec '12

Karl Ramberg uploaded a new version of Tools to project Etoys: http://source.squeak.org/etoys/Tools-kfr.14.mcz ==================== Summary ==================== Name: Tools-kfr.14 Author: kfr Time: 13 December 2012, 8:59:15 am UUID: ca9017f6-5c84-284c-a508-fbabbe39c1dd Ancestors: Tools-kfr.13 A little better conversion of tiles to code =============== Diff against Tools-kfr.13 =============== Item was changed: ----- Method: MethodHolder>>acceptDroppingMorph:event:inMorph: (in category 'drag and drop') ----- acceptDroppingMorph: dropee event: evt inMorph: targetMorph "Return the dropee to its old position, and add a reference to it at the cursor point." | externalName | (dropee isTileLike) ifTrue:[dropee isTileMorph + ifFalse:[ externalName := dropee codeString unparenthetically] - ifFalse:[^dropee rejectDropMorphEvent: evt. ] ifTrue:[externalName := dropee actualObject uniqueNameForReference]] ifFalse:[externalName := dropee assuredPlayer uniqueNameForReference]. targetMorph correctSelectionWithString: externalName. dropee rejectDropMorphEvent: evt. ^ true "success" !

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

etoys-dev December 2012