Elements - a Scratch-like Smalltalk

Hi Squeakers,

I have created an experimental Squeak-Smalltalk GUI which lets you program much like you would in Scratch, i.e. by snapping blocks together. You can also browse through (and change) the Scratch Source Code by using these block-like syntax elements:

   http://www.chirp.scratchr.org/blog/?p=24.

Any feedback is most welcome. Also, if anybody would like to join up in pursuing this idea, let me know!

-Jens

On 05.03.2009, at 11:20, Jens Moenig wrote:


That's awesome! Wow :)

- Bert -

PS: (also reminds me how snappy Morphic used to be ...)

Jens :

I downloading all as I currently seeing if some common ground between
Scratch and Squeak is posible thanks to Klaus idea and Jerome help.

> PS: (also reminds me how snappy Morphic used to be ...)
Still MorphicWrappers run in actual Squeak   and we have Maui and Morphic
3.0.

Squeak is not dead at all and we could have fun and do money with Aida,
Seaside, and many more

Edgar

On Thu, 05 Mar 2009 11:20:01 +0100, Jens Moenig wrote:

Impressive! awesome !

/Klaus

> Also, if anybody would like to join up in
> pursuing this idea, let me know!
>
> -Jens

--
"If at first, the idea is not absurd, then there is no hope for it".  
Albert Einstein

2009/3/5 Klaus D. Witzel <[hidden email]>:
Yeah, and just 3Mb image size.. :)



--
Best regards,
Igor Stasenko AKA sig.

Hi Edgar,

now, why would anybody consider Squeak or Morphic to be "dead" were it not for Squeakers themselves vehemently denying this

Edgar J. De Cleene wrote

Squeak is not dead at all and we could have fun and do money with Aida,
Seaside, and many more

On 3/5/09 9:35 AM, "Jens Moenig" <[hidden email]> wrote:

> Hi Edgar,
>
> now, why would anybody consider Squeak or Morphic to be "dead" were it not
> for Squeakers themselves vehemently denying this :-)

People like you do Smalltalk and others only JusTalk.
Who don't like Morph should use another Smalltalk

Again ,Great Work !!

I seeing the image at work, its very nice and I trying to port to FunSqueak
, actual build on top of my SqueakLightII

Code fileIn in nicely , for have all working I seeing the many changes for
Slider and ScrollBar from 2.x era of Scratch to current 3.10 base.

All #labelFont I replace for
labelFont
    ^StrikeFont familyName: 'ComicSansMS' size: 12 emphasized: 1

No Verdana in  base Squeak 3.10

Edgar

It's wonderful that you're trying to port this to FunSqueak, Edgar! The actual changeset is very small (only about 140 Kb), and I did not merge it with the base changes, so that this kind of porting could be undertaken. The elements themselves should be font-independent, so you can just specify a different label font for each element. I'm not sure about sliders and scroll bars, though (I only know those used by Scratch and basically copied John's code for the ScrollFrames).

-Jens

Edgar J. De Cleene wrote

I seeing the image at work, its very nice and I trying to port to FunSqueak
, actual build on top of my SqueakLightII

Code fileIn in nicely , for have all working I seeing the many changes for
Slider and ScrollBar from 2.x era of Scratch to current 3.10 base.

All #labelFont I replace for
labelFont
    ^StrikeFont familyName: 'ComicSansMS' size: 12 emphasized: 1

No Verdana in  base Squeak 3.10

On 3/5/09 10:09 AM, "Jens Moenig" <[hidden email]> wrote:

> It's wonderful that you're trying to port this to FunSqueak, Edgar! The
> actual changeset is very small (only about 140 Kb), and I did not merge it
> with the base changes, so that this kind of porting could be undertaken. The
> elements themselves should be font-independent, so you can just specify a
> different label font for each element. I'm not sure about sliders and scroll
> bars, though (I only know those used by Scratch and basically copied John's
> code for the ScrollFrames).
>
> -Jens

I need do some adjust before have it running.

I see if any of tricks I do before works for ScrollBar, need go out now but
continue this afternoon.

If I have success send you a .mcz sou you could have a SqueakSource project.
Maybe some of MorphicTeam  guys like Jerome or Juan could join later and
give some valuable advice.

You could contact me in Skype as edgardec later if you wish.
And continue the great job..

Edgar

Jens Moenig wrote:

> Any feedback is most welcome. Also, if anybody would like to join up in
> pursuing this idea, let me know!

It would be nice if the "show result..." option in the menu would return
an object tile which you could then use in any way that you wanted,
including throwing it away (which is what I imagine now happens when you
click on "ok").

One thing that would be easy to do is to allow any object to become a
tile which then could be included in the code. The result could be
compiled into bytecodes with no problems, even in the cases when it
couldn't be expressed as Squeak text. So this change would result in a
small incompatibility, which might be contrary to your goals.

-- Jecel

Hi Jecel, representing a "show result" as new object tile is an excellent suggestion! I had been considering something like this but couldn't come up with a (quick and consistent) paradigm. Currently the element tiles themselves don't actually store any values, let alone bytecode. They're just place-holders for ... words, really. Similar to (or rather the exact same as) text typed into a workspace or browser scripting pane, they don't ever point to "live" objects, like Etoys-tiles or Scratch reporter blocks do. Therefore I'm not so sure if allowing any object to become an "object element" really would be easy or even feasible. But I'll definitely keep on thinking hard about this, and am open to any ideas.

Jecel Assumpcao Jr wrote

It would be nice if the "show result..." option in the menu would return
an object tile which you could then use in any way that you wanted,
including throwing it away (which is what I imagine now happens when you
click on "ok").

One thing that would be easy to do is to allow any object to become a
tile which then could be included in the code. The result could be
compiled into bytecodes with no problems, even in the cases when it
couldn't be expressed as Squeak text. So this change would result in a
small incompatibility, which might be contrary to your goals.

-- Jecel