Skip to main content

Tweak Tutorial

Andreas posted a BankAccount and ATM tutorial. This nicely demonstrates some of the basic Tweak concepts such as fields, events, triggers, and handlers, as well as introducing UI aspects like players, costumes, updating etc.

Comments

Anonymous said…
Thanks for the tutorial. I noticed one problem however, In the balance method of BankAccount bewareOf: should be something like beAwareOf:. To 'beware of' means to 'be careful', 'be wary', 'be on guard' because of expected danger. To 'be aware of' means to 'be cognizant of', to 'know about'.
Vanessa said…
"To be on guard" is actually the meaning we intended - if someone wants to react to changes in this field, he needs to look for the event specified. It's like a flag or sign that signals "danger ahead, this has changed, please act accordingly, proceed with caution". We pondered various anntoations but settled on this.

However, neither of us is a native speaker, so we may well get convinced otherwise if you have a really good suggestion (beAwareOf: feels a bit awkward, too).
Anonymous said…
I agree beAwareOf: is awkward but I thought "be aware of this event" was what you actually meant.

Telling an object to beware of a normal event doesn't make sense to me. The update of a field value is not an abnormal or unexpected or dangerous event. Perhaps you mean beware because there's a danger you will overlook implementing a handler for this event that you probably really want to handle. But thats really a warning to the programmer rather than a message to the object.

How about beReadyFor: or respondTo: or watchFor: or takeActionOn: or the more prosaic but typical registerEvent:.

Don't know if you'll like any of these. In my opinion there all better than the implications of danger in bewareOf:. From what I've read, both you and Andreas express yourselves in English very well but you might want to solicit more input from other native speakers on this. I'm American by the way.

Cheers
Anonymous said…
Sorry, my second paragraph shows I didn't read your explanation carefully enough. That paragraph could be worded a bit differently but in general I object to telling an object that there is 'danger ahead' and that it should 'proceed with caution' because of a normal event.
Vanessa said…
I've taken the discussion to the mailing list.

Popular posts from this blog

Frontend-only Multi-Player. Unlimited Bandwidth. Or: What is Croquet.io, really?

A multi-player web app needs a backend, right? What if I told you, it doesn’t? Read on for how Croquet gets rid of servers. No, really . Instantaneous Shared Experiences  is how we describe Croquet on our website. And while that excellently describes What Croquet does, as Croquet's Chief Architect, I wanted to share a bit about How we do that. So I wrote a Twitter thread . Here it is in blog form, slightly extended. Click the animation above if it does not play automatically Croquet lets you build completely client-side multi-user web apps. Read that again. Client-side. Multi-user. No I’m not kidding. I built it, I know it works. 😁  Croquet apps run completely client-side: can be hosted as a static web site no server-side code needed no networking code needed  Croquet is literally virtualizing the server: Instead of running code on a server (or in a serverless function) we run it as a virtual machine (VM) on each client.  Croquet carefully controls the inputs to these identi

Deconstructing Floats: frexp() and ldexp() in JavaScript

While working on my  SqueakJS VM, it became necessary to deconstruct floating point numbers into their mantissa and exponent parts, and assembling them again. Peeking into the C sources of the regular VM, I saw they use the  frexp ()   and ldexp () functions found in the standard C math library. Unfortunately, JavaScript does not provide these two functions. But surely there must have been someone who needed these before me, right? Sure enough, a Google search came up with a few implementations. However, an hour later I was convinced none of them actually are fully equivalent to the C functions. They were imprecise, that is, deconstructing a float using frexp() and reconstructing it with ldexp() did not result in the original value. But that is the basic use case: for all float values, if [ mantissa , exponent ] = frexp (value) then value = ldexp ( mantissa , exponent ) even if the value is subnormal . None of the implementations (even the complex ones) really worked. I

Emulating the latest stable OLPC XO software

Even with XO laptops readily available now there are quite a lot of reasons why one would want to emulate it on another machine. One being to hook up a projector. Unfortunately there are quite a number of hoops (*) one has to jump through to make it work. Anyway, I made a virtual machine that allows me to emulate the XO in VMWare on my Mac, running Sugar in the XO's native 1200x900 resolution, scaled down to a nice physical size in a window on my regular screen (fullscreen works, too). Sound works (even Tam Tam), Browse works (so networking is good), and after setting a working Jabber server I do see other XOs in the neighborhood view (Chat worked fine). Camera and mic are half working (Measure crashes, Record shows blank picture, but reportedly does record video), and a "Sugar restart" does not actually restart Sugar, but apart from that it seems fully functional, and much nicer than the emulations I had used to date. Click to see actual screenshots (calibrated to m