etoys-dev June 2010

etoys-dev@lists.squeakfoundation.org

22 participants
110 discussions

etoys-dev meet today at 19:00 GMT on #etoys
by Timothy Falconer 09 Jun '10

09 Jun '10

Hi everyone, As before, we'll be having a software meet on the IRC freenode channel #etoys at 19:00 GMT (3pm ET, 12 PT). You can also attend by clicking "chat" on squeakland.org. It might be helpful to watch the two preview videos here: http://squeakland.org/resources/audioVisual/ Also, have a look at the current Etoys 4 roadmap: http://tracker.squeakland.org/browse/SQ?report=com.atlassian.jira.plugin.sy… Take care, Tim

2 1

text oddity
by kharness＠illinois.edu 09 Jun '10

09 Jun '10

Hi See the attached screen print. I typed the words correctly but when I looked they were backward. Is this a keystroke command? Regards, Kathleen

1 0

Etoys: Compiler-kfr.3.mcz
by commits＠source.squeak.org 08 Jun '10

08 Jun '10

Karl Ramberg uploaded a new version of Compiler to project Etoys: http://source.squeak.org/etoys/Compiler-kfr.3.mcz ==================== Summary ==================== Name: Compiler-kfr.3 Author: kfr Time: 8 June 2010, 10:48:49 pm UUID: d735b799-4fd3-f74b-baec-abca8a9c31bf Ancestors: Compiler-bf.2 Fixes jira bug SQ-710 Removal of variable used in a script caused a walkback =============== Diff against Compiler-bf.2 =============== Item was changed: ----- Method: Decompiler>>decompile:in:method:using: (in category 'public access') ----- decompile: aSelector in: aClass method: aMethod using: aConstructor | block | constructor := aConstructor. method := aMethod. self initSymbols: aClass. "create symbol tables" method isQuick ifTrue: [block := self quickMethod] ifFalse: [stack := OrderedCollection new: method frameSize. caseExits := OrderedCollection new. statements := OrderedCollection new: 20. super method: method pc: method initialPC. "skip primitive error code store if necessary" (method primitive ~= 0 and: [self willStore]) ifTrue: [pc := pc + 2. tempVars := tempVars asOrderedCollection]. block := self blockTo: method endPC + 1. stack isEmpty ifFalse: [self error: 'stack not empty']]. ^constructor + codeMethod: (aSelector ifNil: [method defaultSelector]) - codeMethod: aSelector block: block tempVars: tempVars primitive: method primitive class: aClass!

1 0

Etoys: Multilingual-Richo.12.mcz
by commits＠source.squeak.org 08 Jun '10

08 Jun '10

Ricardo Moran uploaded a new version of Multilingual to project Etoys: http://source.squeak.org/etoys/Multilingual-Richo.12.mcz ==================== Summary ==================== Name: Multilingual-Richo.12 Author: Richo Time: 8 June 2010, 2:01:43 pm UUID: a9b4b3fd-d4ac-8040-b9e3-e87751a18c54 Ancestors: Multilingual-Richo.11 * Fixed an error in TTCFont. It used to throw an error in #displayString:on:from:to:at:kern:baselineY: when ascent wasn't properly initialized. =============== Diff against Multilingual-Richo.11 =============== Item was changed: ----- Method: TTCFont>>glyphInfoOf:into: (in category 'private') ----- glyphInfoOf: aCharacter into: glyphInfoArray "Answer the width of the argument as a character in the receiver." | form | (self hasGlyphOf: aCharacter) ifFalse: [ ^ self fallbackFont glyphInfoOf: aCharacter into: glyphInfoArray. ]. form := self formOf: aCharacter. glyphInfoArray at: 1 put: form; at: 2 put: 0; at: 3 put: form width; + at: 4 put: self ascent "(self ascentOf: aCharacter)"; - at: 4 put: ascent "(self ascentOf: aCharacter)"; at: 5 put: self. ^ glyphInfoArray. !

1 0

Etoys: TrueType-Richo.4.mcz
by commits＠source.squeak.org 08 Jun '10

08 Jun '10

Ricardo Moran uploaded a new version of TrueType to project Etoys: http://source.squeak.org/etoys/TrueType-Richo.4.mcz ==================== Summary ==================== Name: TrueType-Richo.4 Author: Richo Time: 8 June 2010, 1:56:22 pm UUID: faa86417-ca11-f245-b53f-074479205bb2 Ancestors: TrueType-Richo.3 * Added a missing method. I copied it from the squeak image. =============== Diff against TrueType-Richo.3 =============== Item was added: + ----- Method: TTFileDescription>>readGlyphAt: (in category 'glyphs') ----- + readGlyphAt: glyphIndex + | glyph | + self withFileDo:[:fontFile| + glyph := self readGlyphAt: glyphIndex fromFile: fontFile. + self updateGlyphMetrics: glyph fromFile: fontFile. + ]. + ^glyph!

1 0

Re: Touchscreen requirements
by Bert Freudenberg 08 Jun '10

08 Jun '10

On 08.06.2010, at 07:44, John Watlington wrote: > OLPC is looking to add multi-touch to our interface over > the next year --- it is certainly necessary for a tablet. > But "multi-touch" describes a huge range of parameters. > Before taking a first pass at a spec. document, I'd like to > stir up some discussion. Here are the parameters that > I think should be specified. Feel free to comment on them > as well as suggest others! > > Cheers, > wad Thanks for inviting discussion! I recently started testing Etoys on the Apple iPad - not the least to get an idea of what needs to be done to it for an XO tablet. Multi-touch is definitely "cool", e.g. you can move around multiple Etoys objects simultaneously. If you are interested, I can send you a test version (pm me). Etoys uses the Sugar tool bar on all platforms. That works very well, the buttons are large enough even for my fingers. However, many other Etoys UI elements are much too small for touching. They're finicky even on the XO screen, but with a pointer you can at least hit them. That's rather hard with a finger (though the Apple touch screen is amazingly precise). A stylus would be preferable, but then, two-finger gestures are awkward with a stylus. It would help if the tablet had a 4:3 ratio. Ideally 1200x900 pixels just like the XO, but at least preserve the ratio. The iPad has 1024x768 pixels and I made Etoys use a virtual 1200x900 screen hw-scaled to the actual screen size, looks very nice. > ----------------- > 1) Number of simultaneous touches: > The number of simultaneous touches that can be tracked. > For W7, this is two. I believe OLPC is looking for more. IMHO multi-touch is almost essential on a tablet. Two would be enough IMHO, more are nice. What's "W7"? > 2) Behavior when number of simultaneous touches is exceeded: > If the number of simultaneous touches is exceeded, what happens ? > I suggest that the "oldest" touch be forgotten and no longer tracked, > but have seen other behaviors as well. I'd rather keep tracking the first touches and ignore additional ones. Then accidental touches wouldn't interrupt the current interaction. > 3) Palm rejection: > A number of vendors include "palm rejection" algorithms in their > controllers. I'm not sure how I feel about this --- I would prefer to > push this information higher in the stack before discarding it... > > 4) "Sensor size": > This applies to multizone resistive touchscreens, which may be > thought about as a number of small touchscreens, each capable of > a single touch. Two touches cannot be detected in any one zone, > so this affects how close buttons which might be pressed simultaneously > (think piano keys) can be placed to one another. W7 specs 1 in. x1 in. max. > I believe this needs to be closer to 1 cm x 1cm max. I'm imagining to use a two-finger tap to invoke meta operations, like the right touchpad button in Etoys on the XO. For this it would need to detect two kid's fingers form one ... > 5) Resolution: > Do we need to have a touch resolution equal to the screen size ? I have no real experience with this yet, but it needs to be high enough to allow drawing. > 6) Scan rate: > The number of times a second that the touch controller > can identify and report a touch. W7 specifies 50 Hz minimum, > which seems a little high. > > 7) Robustness: > This is usually specified as the number of presses in one spot with a contact > area of either 8mm (finger) or 0.8mm (stylus). Industry standard for resistive > (single or multizone) seems to be around 80K, which is too low for our needs > (we try to reach a 2000 day lifetime). But the one vendor supporting 250K > touches was unusable by a bare finger (needed fingernail or stylus). > > 8) UV resistance: > Since this touchscreen is on top of a sunlight readable display, it will need > to be UV resistant. Our current standard (for the display) is no significant > change (>5%) in optical properties after 4000 hours of full sunlight UV > irradiation. > > 9) Humidity, temperature: > Same as the XO: operation from 0 to 50C, in RH up to 95%. > > Regards, > wad No opinion on these issues, yet ... - Bert -

2 1

Etoys: Etoys-kfr.19.mcz
by commits＠source.squeak.org 07 Jun '10

07 Jun '10

Karl Ramberg uploaded a new version of Etoys to project Etoys: http://source.squeak.org/etoys/Etoys-kfr.19.mcz ==================== Summary ==================== Name: Etoys-kfr.19 Author: kfr Time: 7 June 2010, 9:41:29 pm UUID: c71b911b-9633-1846-808a-9a8ec286834a Ancestors: Etoys-kfr.18 Fix again, wrong merge applied ... =============== Diff against Etoys-kfr.18 ===============

1 0

ALSA Play & Record on X0-1.5
by Derek O'Connell 07 Jun '10

07 Jun '10

Sorry, long post, only read if you are interested in *both* play & record. If you are not bothered about recording then this is probably of no interest. Latest results in effort to get both play & record working on the XO-1.5. This may seem more appropriate to vm-dev and ideally that would be the case but unless Etoys itself is tested then problems peculiar to the performance of one particular image over another might be overlooked (for example Scratch does recording in a much tighter loop so appears to cope with higher sampling rates than Etoys). Diagnosing these types problems is time consuming so I would be grateful if someone else wants to pick it up from this point. Testing done on vanilla XO Etoys image with the attached version of vm-sound-ALSA which contains additional error checking to avoid apparent freeze when the XO suspends then resumes. Playing... - before playing/recording anything... - SoundPlayer class>>initialize, set SamplingRate to 44100 - I don't think it's important but I turn reverb off (via class var) - Open Sound Library and play a sound twice, first time will probably be at double speed, second time should be ok - From then on playback should be ok Recording... - SoundRecorder>>initialise, set SamplingRate to 8092 - Recording not great quality but passable, no clicks (initial click is due to something else) - If "preserveTrash"is enabled then deleted Sound Recorder continues to monitor sound or, worse, continues recording while in the trashcan. This is also true with preserveTrash disabled because of "undo" facility, at least until something else is deleted. This means Etoys can appear to freeze even when no Sound Recorder is visible. - Even for 8092 recording will sometimes hang but unlike for 11025/22050 there is plenty of time to actually get something recorded. - I suspect underlying problem to be buffer overruns, badly handled ALSA errors or paging delays related to the use of flash memory on the XO... or a combination there-of. *Note* that if left long enough things will actually unfreeze. strace results during recording (and capturing a hang) show a stream of select() time-outs and EAGAIN errors on read()'s, eg: 0.000061 select(8, [3 7], [], [3 7], {0, 0}) = 0 (Timeout) 0.000082 read(3, 0x973e858, 4096) = -1 EAGAIN (Resource temporarily unavailable) ...ending in a stream of... 0.008931 --- SIGIO (I/O possible) @ 0 (0) --- 0.000060 rt_sigreturn(0x4c01f15c) = 0 0.010951 --- SIGALRM (Alarm clock) @ 0 (0) --- 0.000056 sigreturn() = ? (mask now []) The full strace in this case is ~10M so email me if you want a copy or reproduce yourself using "strace -s 64 -r -o <a-filename> squeak vm-sound-ALSA etoys.image" (run in /usr/share/etoys). For anyone willing to adopt the problem the only suggestion I have is to wrap recording in the ALSA plugin in threaded-buffering similar to what I have done in vm-sound-pulse. Good luck! -D

1 0

Variables in viewer broken
by Korakurider 06 Jun '10

06 Jun '10

Hello. I noticed that display of "variables" category in viewer broken in the latest dev-image. Here is my result of quick test: + update 2378 that Bert made public without the latest package works. + 2378 and Etoys-Richo.11 works + it breaks after Etoys-kfr.12 was loaded. But I couldn't what's wrong... Could you look into this? /Korakurider

3 6

Etoys: Etoys-kfr.18.mcz
by commits＠source.squeak.org 06 Jun '10

06 Jun '10

Karl Ramberg uploaded a new version of Etoys to project Etoys: http://source.squeak.org/etoys/Etoys-kfr.18.mcz ==================== Summary ==================== Name: Etoys-kfr.18 Author: kfr Time: 6 June 2010, 6:48:55 pm UUID: d472d925-5bd5-2c46-b222-f2b574a19750 Ancestors: Etoys-kfr.17 Try once again to get to changes right. Do not add info to slotInfo, just change it if it's there.... =============== Diff against Etoys-kfr.17 =============== Item was changed: ----- Method: Player>>noteDecimalPlaces:forGetter: (in category 'misc') ----- noteDecimalPlaces: aNumber forGetter: aGetter "Note the given preference of decimal places for the given getter" + | slotInfo | + slotInfo := self slotInfoForGetter: aGetter. + slotInfo ifNotNil:[ slotInfo floatPrecision: (Utilities floatPrecisionForDecimalPlaces: aNumber)]. - | | - "slotInfo _ self slotInfoAt: (Utilities inherentSelectorForGetter: aGetter). - slotInfo floatPrecision: (Utilities floatPrecisionForDecimalPlaces: aNumber)." costume noteDecimalPlaces: aNumber forGetter: aGetter! Item was changed: ----- Method: Player>>setPrecisionFor: (in category 'slots-user') ----- setPrecisionFor: slotName "Set the precision for the given slot name" | aList aMenu reply val aGetter places | aGetter := Utilities getterSelectorFor: slotName. + places := Utilities + decimalPlacesForFloatPrecision: (self defaultFloatPrecisionFor: aGetter). - places := Utilities decimalPlacesForFloatPrecision: (self getPrecisionFor: slotName). aList := #('0' '1' '2' '3' '4' '5' '6' '7' '8' '9' '10'). aMenu := SelectionMenu labels: aList selections: (aList collect: [:m | m asNumber]). reply := aMenu startUpWithCaption: ('How many decimal places? (currently {1})' translated format: {places}). reply ifNotNil: [(self slotInfo includesKey: slotName) ifTrue: ["it's a user slot" (self slotInfoAt: slotName) floatPrecision: (Utilities floatPrecisionForDecimalPlaces: reply). self class allInstancesDo: [:anInst | reply == 0 ifFalse: [((val := anInst instVarNamed: slotName asString) isInteger) ifTrue: [anInst instVarNamed: slotName asString put: val asFloat]]. anInst updateAllViewers]] ifFalse: ["it's specifying a preference for precision on a system-defined numeric slot" self noteDecimalPlaces: reply forGetter: aGetter. self updateAllViewers]]!

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

etoys-dev June 2010