Cuis on Raspberry Pi

On 12/19/2013 1:39 PM, Casey Ransberger wrote:
Agreed.

> An industrious programmer might bring it back in as an external package.
>
> I think it's fairly certain that we'd like to be the ideal Smalltalk
> to run on small/low-end devices like the Pi, so I do think this merits
> discussion.
>

Please don't. The main reason I removed it was that the implementation
was hacky and needed ugly code at several places. Let me work on a new,
cleaner implementation.

Cheers,
Juan Vuletich

_______________________________________________
Cuis mailing list
[hidden email]
http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org

Hi Nacho,

On 12/20/2013 8:35 AM, nacho wrote:
Please try the version I've just uploaded (#1898). I did a kind of
automatic #fastDrawWindow... that kicks in when Morphic is getting too
slow. It should make the Raspi feel faster.

Please report any problems or comments.

Cheers,
Juan Vuletich

_______________________________________________
Cuis mailing list
[hidden email]
http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org

Juan / Cuisers
I've been playing around with the new image. It much faster, though not as faster as Cuis3.
The procedure I'm always doing with a new image is:
1) in the World (PasteUpMoroh) I'm setting backgroundImage and backgroundImageData, both to nil.

2) Preferences class >> #aaFontsColormapDepth
      I'm using 3.
3) Preferences class >> #initialize
     Preferences slowMachine
(which set as false a number of things like: smartUpdating, checkForSlips, subPixelRederFonts, etc) and also sets the ClassicTheme (if installed).
4) Setting display depth at 16, which works good.

Now finally regarding the changes you made, the feeling definitely snappier. I did some changes (I'm attaching a change set) to avoid the black cast being draw at all. That slows things. I don't know how to do this without affecting Cuis under other environments that can handle this good.

And finally the last thing that I notice that still presents a problem is window resizing, as it's done fully drawing the contents of the window as oposite to Cuis3 in which only the contour was drawn.
Juan, thanks for your support on this. I think it's going to be great to have a very good smalltalk working on the pi. Some might wonder it's just a toy. Well it is, for me (a grown up children) and for children too. But what strategy works best when learning? playing and having fun with a toy?  
I'm starting a blog which is going to be 100% devoted to the Pi and Cuis Smalltalk. Just opened it
pismalltalk.wordpress.com I have some materials already to be uploaded. Will do it in the following days.
My idea there is to achieve a goal: Have a Personal Smalltalk Machine running fast, with everything needed to develop educational, hobbits, scientific, music, (dynabook style) applications. A system that will grow up with the user at USD35.

Thanks for all
Cheers
Nacho
PS: Sorry I've used the change sorter, in now way I'm saying that 1899 has to be added. It's just that I thought it was going to be easy to read the changes.
1899-CuisCore-IgnacioSniechowski-2013Dec21-16h09m-IS.1.cs.st

Hi Nacho,

(inline)
On 12/22/2013 5:13 PM, nacho wrote:
Oh, I've just pushed a commit and overlooked it. Will take a look now.
It will be integrated in the next days.

> And finally the last thing that I notice that still presents a problem is
> window resizing, as it's done fully drawing the contents of the window as
> oposite to Cuis3 in which only the contour was drawn.

Yes, it still needs a bit more of work :)

Great!

> Thanks for all
> Cheers
> Nacho
> PS: Sorry I've used the change sorter, in now way I'm saying that 1899 has
> to be added. It's just that I thought it was going to be easy to read the
> changes.
> 1899-CuisCore-IgnacioSniechowski-2013Dec21-16h09m-IS.1.cs.st
> <http://forum.world.st/file/n4732004/1899-CuisCore-IgnacioSniechowski-2013Dec21-16h09m-IS.1.cs.st>
>

Don't worry at all. In general, folks, any way you can get your stuff to
me is good. Let me worry about the update stream, etc.

> -----
> Nacho
> Smalltalker apprentice.
> Buenos Aires, Argentina.

Cheers,
Juan Vuletich

_______________________________________________
Cuis mailing list
[hidden email]
http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org

The second one is the split between the ram devoted to the GPU and the OS. I found that the best balance is to have 128 MB dedicated to the GPU and the rest to the OS.