[squeak-dev] [ANN] UziScript first pre-release!
richi.moran at gmail.com
Mon Jan 28 13:56:50 UTC 2019
Thanks for your interest. And thank you Tim for your questions. I'll try to
answer them below.
On Thu, Jan 24, 2019 at 12:06 AM tim Rowledge <tim at rowledge.org> wrote:
> The only question I have so far is why think of using blockly for the
> display of what is basically Scratch? We have a pretty good Scratch in
> Squeak already, there for the customising. It's faster, too.
Blockly was just the easiest choice given the design decision of building
the GUI as a website. We wanted to separate the GUI from the server mostly
because of flexibility.
Imagine a classroom with a laptop for each children but only a handful of
robots. You could have just one computer (or a few) with the UziScript's
server installed and all the children programming the robots from their own
laptops without having to install anything.
Or maybe imagine a robot kit that comes preinstalled with the UziScript's
server and all you need to do is point your browser to the correct url.
Nothing to install, nothing to configure, just open the browser and start
I think that is valuable. Of course, Blockly is just an example. Anyone
could write their own GUI in the language of their choice and interact with
UziScript using the REST api.
On Sat, Jan 26, 2019 at 1:53 AM tim Rowledge <tim at rowledge.org> wrote:
> OK, some quick comments after actually downloading and quickly taking a
> look on my iMac -
> It won't "just run" on Mac OS 10.13.6 High Sierra - it doesn't even offer
> to have me temporarily side-step the security settings, which is something
> I haven't seen before.
Oh yes, I know. We don't have a Mac to test so we weren't expecting it to
work. I should've specified that in the release.
> So I downloaded the plain 5.2 64bit all-in-one to get a Mac 64bit VM
> (which by the way whines about not being able to write to the changes file
> on startup because of a permissions problem; this before it even gets to
> Marcel's nice 'Welcome to Squeak ' initial config tool) to get a Mac 64bit
> VM .
> Opening the Uzi package to drill down to the actual image and dropping the
> image on the fresh 64bit all-in-one opened the Uzi image ok.
You can also install all the packages in your own image if you like. I made
a script that installs everything:
All you need to do is clone the git repository (and recursively clone the
submodules) and then run the script. If the SerialPort works on Mac I don't
see any reason why this wouldn't work.
> First question - where are the comments, folks? I understand not yet
> having done a round of adding comments all over the place but even the
> class examples have no helpful comments to offer good places to start
> trying things. Could save a good bit of time if you add some. Pretty please.
Yes, that's a very good point. I'm not used to writing comments but I
definitely should improve the documentation.
> Next - why a 64 bit image? Right now that means no Raspberry Pi; yes,
> we're working on it but it's going to be a while. Is there some important
> reason, or is it just that this is what you've been working on? A lot of
> people use Pi with Arduino/ESP8266 and this could be a big user base for
No, there is no need for 64 bits. It's just the image I had at the moment.
And yes, Raspberry Pi would be *very* useful (especially for the robot kit
I was talking above) but we haven't even started testing on one yet.
> Third - why 'uzi' ? That has some not so pleasant connotations.
Oh, that was just a joke that stuck due to lack of a better name. Naming
things is really hard. If there is a consensus that it's offensive or
something we can change it.
Again, thank you very much for taking the time to test and write these
questions. We really appreciate it. I'll try to improve the documentation
and maybe start thinking on a better name that doesn't relate to violence.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev