International text input on X11

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
127 messages Options
1234 ... 7
Reply | Threaded
Open this post in threaded view
|

International text input on X11

Yoshiki Ohshima-3
Hello,

As some people aware, we have a problem with Japanese text input into
Squeak on X11, especially with NuScratch.

I've been punting to work on this but now Manabu Sugiura volunteered
and I decided to just do what it takes to help him.

I wrote some code to support Japanese text input works on X11 when
OLPC XO time, but things diverged since then.  My understanding is
that porting the code from that branch into the later branch(es), most
notably the VM that NuScratch uses; But I am pretty sure there are
more differences I am not aware of.  Please let us know if there are
some foreseeable issues.  And please consider incorporating patches
Manabu (and I) will produce when it is ready.

Thanks!

--
-- Yoshiki

Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Eliot Miranda-2
Hi Yoshiki,

> On May 5, 2016, at 8:49 AM, Yoshiki Ohshima <[hidden email]> wrote:
>
> Hello,
>
> As some people aware, we have a problem with Japanese text input into
> Squeak on X11, especially with NuScratch.
>
> I've been punting to work on this but now Manabu Sugiura volunteered
> and I decided to just do what it takes to help him.
>
> I wrote some code to support Japanese text input works on X11 when
> OLPC XO time, but things diverged since then.  My understanding is
> that porting the code from that branch into the later branch(es), most
> notably the VM that NuScratch uses; But I am pretty sure there are
> more differences I am not aware of.

Are you targeting the interpreter trunk or the cig JIT branch?

>  Please let us know if there are
> some foreseeable issues.  And please consider incorporating patches
> Manabu (and I) will produce when it is ready.

We are about to move the Cig branch from svn on squeakvm.org to git on github.  But I'm very happy to integrate patches into the svn tree before we've finished the move.  Let me know if I can help in any way.  Thanks for this!

> Thanks!
>
> --
> -- Yoshiki

_,,,^..^,,,_ (phone)
Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Yoshiki Ohshima-3
On Thu, May 5, 2016 at 9:51 AM, Eliot Miranda <[hidden email]> wrote:

> Hi Yoshiki,
>
>> On May 5, 2016, at 8:49 AM, Yoshiki Ohshima <[hidden email]> wrote:
>>
>> Hello,
>>
>> As some people aware, we have a problem with Japanese text input into
>> Squeak on X11, especially with NuScratch.
>>
>> I've been punting to work on this but now Manabu Sugiura volunteered
>> and I decided to just do what it takes to help him.
>>
>> I wrote some code to support Japanese text input works on X11 when
>> OLPC XO time, but things diverged since then.  My understanding is
>> that porting the code from that branch into the later branch(es), most
>> notably the VM that NuScratch uses; But I am pretty sure there are
>> more differences I am not aware of.
>
> Are you targeting the interpreter trunk or the cig JIT branch?

It actually is not clear yet which branches are the right one for
current Scratch on raspi and also future proof.  Perhaps doing for
multiple branches is necessary?  (What are the relationship of those?)

>>  Please let us know if there are
>> some foreseeable issues.  And please consider incorporating patches
>> Manabu (and I) will produce when it is ready.
>
> We are about to move the Cig branch from svn on squeakvm.org to git on github.  But I'm very happy to integrate patches into the svn tree before we've finished the move.  Let me know if I can help in any way.  Thanks for this!

Thank you!

--
-- Yoshiki

Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

timrowledge

> On 05-05-2016, at 10:36 AM, Yoshiki Ohshima <[hidden email]> wrote:
>
> It actually is not clear yet which branches are the right one for
> current Scratch on raspi and also future proof.  Perhaps doing for
> multiple branches is necessary?  (What are the relationship of those?)

Oh, it’s absolutely clear for the Pi; Cog/Spur. The ancient original MIT image and an elderly interpreter are kept around for emergency use but will not be updated.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: FR: Flip Record



Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

David T. Lewis
>
>> On 05-05-2016, at 10:36 AM, Yoshiki Ohshima <[hidden email]>
>> wrote:
>>
>> It actually is not clear yet which branches are the right one for
>> current Scratch on raspi and also future proof.  Perhaps doing for
>> multiple branches is necessary?  (What are the relationship of those?)
>
> Oh, it’s absolutely clear for the Pi; Cog/Spur. The ancient original MIT
> image and an elderly interpreter are kept around for emergency use but
> will not be updated.
>

We might need to harvest some older patches out of trunk and get them
applied in our oscog branch.

Whatever it is that needs to be done, we'll all be happy to help :-)

Dave



Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Yoshiki Ohshima-3
In reply to this post by timrowledge
On Thu, May 5, 2016 at 11:11 AM, tim Rowledge <[hidden email]> wrote:
>
>> On 05-05-2016, at 10:36 AM, Yoshiki Ohshima <[hidden email]> wrote:
>>
>> It actually is not clear yet which branches are the right one for
>> current Scratch on raspi and also future proof.  Perhaps doing for
>> multiple branches is necessary?  (What are the relationship of those?)
>
> Oh, it’s absolutely clear for the Pi; Cog/Spur. The ancient original MIT image and an elderly interpreter are kept around for emergency use but will not be updated.

Okay!

By any chance, can you tell me how you test things? for Raspberry Pi?


--
-- Yoshiki

Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

timrowledge

> On 05-05-2016, at 1:02 PM, Yoshiki Ohshima <[hidden email]> wrote:
>
> On Thu, May 5, 2016 at 11:11 AM, tim Rowledge <[hidden email]> wrote:
>>
>>> On 05-05-2016, at 10:36 AM, Yoshiki Ohshima <[hidden email]> wrote:
>>>
>>> It actually is not clear yet which branches are the right one for
>>> current Scratch on raspi and also future proof.  Perhaps doing for
>>> multiple branches is necessary?  (What are the relationship of those?)
>>
>> Oh, it’s absolutely clear for the Pi; Cog/Spur. The ancient original MIT image and an elderly interpreter are kept around for emergency use but will not be updated.
>
> Okay!
>
> By any chance, can you tell me how you test things? for Raspberry Pi?

For Japanese input? I don’t, because I can’t and wouldn’t have the faintest idea if it were correct anyway. I leave it to Kazuhiro Abee to let me know when he notices something wrong.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
A clear conscience is usually the sign of a bad memory.



Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Eliot Miranda-2
In reply to this post by Yoshiki Ohshima-3
Hi Yoshiki,

> On May 5, 2016, at 1:02 PM, Yoshiki Ohshima <[hidden email]> wrote:
>
>> On Thu, May 5, 2016 at 11:11 AM, tim Rowledge <[hidden email]> wrote:
>>
>>> On 05-05-2016, at 10:36 AM, Yoshiki Ohshima <[hidden email]> wrote:
>>>
>>> It actually is not clear yet which branches are the right one for
>>> current Scratch on raspi and also future proof.  Perhaps doing for
>>> multiple branches is necessary?  (What are the relationship of those?)
>>
>> Oh, it’s absolutely clear for the Pi; Cog/Spur. The ancient original MIT image and an elderly interpreter are kept around for emergency use but will not be updated.
>
> Okay!
>
> By any chance, can you tell me how you test things? for Raspberry Pi?

A Pi is cheap enough that one can simply buy one.  The new 64-bit one runs 32-bit binaries and is significantly faster than a pi2.  As far as testing, one can either connect a display via hdmi and a mouse & keyboard via usb, or use VNC.  There's a guide to setup of raspbian and of the VNC server on raspberrypi.org.

HTH

> --
> -- Yoshiki

_,,,^..^,,,_ (phone)
Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Yoshiki Ohshima-3
In reply to this post by timrowledge
On Thu, May 5, 2016 at 1:43 PM, tim Rowledge <[hidden email]> wrote:

>
>> On 05-05-2016, at 1:02 PM, Yoshiki Ohshima <[hidden email]> wrote:
>>
>> On Thu, May 5, 2016 at 11:11 AM, tim Rowledge <[hidden email]> wrote:
>>>
>>>> On 05-05-2016, at 10:36 AM, Yoshiki Ohshima <[hidden email]> wrote:
>>>>
>>>> It actually is not clear yet which branches are the right one for
>>>> current Scratch on raspi and also future proof.  Perhaps doing for
>>>> multiple branches is necessary?  (What are the relationship of those?)
>>>
>>> Oh, it’s absolutely clear for the Pi; Cog/Spur. The ancient original MIT image and an elderly interpreter are kept around for emergency use but will not be updated.
>>
>> Okay!
>>
>> By any chance, can you tell me how you test things? for Raspberry Pi?
>
> For Japanese input? I don’t, because I can’t and wouldn’t have the faintest idea if it were correct anyway. I leave it to Kazuhiro Abee to let me know when he notices something wrong.

Ah, no.  I meant to ask how you test your things.  Is there a dev
image of some sort you are using (presumably .changes is there), and
compiling VM and transferring it to a Pi, etc.

(I have done my own little share of compiling and testing things on
Pi, which in the end involved compling C with some asm code on Pi on
an SSH terminal and run it.  But I am just curious how you've been
doing it.)


--
-- Yoshiki

Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Yoshiki Ohshima-3
In reply to this post by Eliot Miranda-2
On Thu, May 5, 2016 at 2:06 PM, Eliot Miranda <[hidden email]> wrote:

> Hi Yoshiki,
>
>> On May 5, 2016, at 1:02 PM, Yoshiki Ohshima <[hidden email]> wrote:
>>
>>> On Thu, May 5, 2016 at 11:11 AM, tim Rowledge <[hidden email]> wrote:
>>>
>>>> On 05-05-2016, at 10:36 AM, Yoshiki Ohshima <[hidden email]> wrote:
>>>>
>>>> It actually is not clear yet which branches are the right one for
>>>> current Scratch on raspi and also future proof.  Perhaps doing for
>>>> multiple branches is necessary?  (What are the relationship of those?)
>>>
>>> Oh, it’s absolutely clear for the Pi; Cog/Spur. The ancient original MIT image and an elderly interpreter are kept around for emergency use but will not be updated.
>>
>> Okay!
>>
>> By any chance, can you tell me how you test things? for Raspberry Pi?
>
> A Pi is cheap enough that one can simply buy one.  The new 64-bit one runs 32-bit binaries and is significantly faster than a pi2.  As far as testing, one can either connect a display via hdmi and a mouse & keyboard via usb, or use VNC.  There's a guide to setup of raspbian and of the VNC server on raspberrypi.org.

Sorry for posing a vague question...  I do have a couple of Pis (Pi
and Pi2, but not Pi3), and have done some graphics stuff in C over
SSH.  So I invoke my program from a shell running emacs on an SSH
session and things appear on a display connected to a Pi.  But I have
not tried VNC there.  I haven't done any real Squeak stuff on Pi and
for Pi; if running Squeak on Pi and interacting with it over VNC is
reasonably fast, I'd go with that path.  But this one involves some C
programs and if people does some cross compiling more on a host
computer, that is also an interesting option.


--
-- Yoshiki

Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Eliot Miranda-2
In reply to this post by Yoshiki Ohshima-3
Hi Yoshiki,



_,,,^..^,,,_ (phone)
On May 5, 2016, at 2:10 PM, Yoshiki Ohshima <[hidden email]> wrote:

On Thu, May 5, 2016 at 1:43 PM, tim Rowledge <[hidden email]> wrote:

On 05-05-2016, at 1:02 PM, Yoshiki Ohshima <[hidden email]> wrote:

On Thu, May 5, 2016 at 11:11 AM, tim Rowledge <[hidden email]> wrote:

On 05-05-2016, at 10:36 AM, Yoshiki Ohshima <[hidden email]> wrote:

It actually is not clear yet which branches are the right one for
current Scratch on raspi and also future proof.  Perhaps doing for
multiple branches is necessary?  (What are the relationship of those?)

Oh, it’s absolutely clear for the Pi; Cog/Spur. The ancient original MIT image and an elderly interpreter are kept around for emergency use but will not be updated.

Okay!

By any chance, can you tell me how you test things? for Raspberry Pi?

For Japanese input? I don’t, because I can’t and wouldn’t have the faintest idea if it were correct anyway. I leave it to Kazuhiro Abee to let me know when he notices something wrong.

Ah, no.  I meant to ask how you test your things.  Is there a dev
image of some sort you are using (presumably .changes is there), and
compiling VM and transferring it to a Pi, etc.

(I have done my own little share of compiling and testing things on
Pi, which in the end involved compling C with some asm code on Pi on
an SSH terminal and run it.  But I am just curious how you've been
doing it.)

You'll find an updated squeak 5.0 trunk image on squeak.org/downloads, up-to-date VMs at http://www.mirandabanda.org/files/Cog/VM/ and instructions on building your own VM at http://www.mirandabanda.org/cogblog/compiling-the-vm/



--
-- Yoshiki



Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Eliot Miranda-2
In reply to this post by Yoshiki Ohshima-3
Hi Yoshiki,


> On May 5, 2016, at 2:34 PM, Yoshiki Ohshima <[hidden email]> wrote:
>
>> On Thu, May 5, 2016 at 2:06 PM, Eliot Miranda <[hidden email]> wrote:
>> Hi Yoshiki,
>>
>>>> On May 5, 2016, at 1:02 PM, Yoshiki Ohshima <[hidden email]> wrote:
>>>>
>>>>> On Thu, May 5, 2016 at 11:11 AM, tim Rowledge <[hidden email]> wrote:
>>>>>
>>>>> On 05-05-2016, at 10:36 AM, Yoshiki Ohshima <[hidden email]> wrote:
>>>>>
>>>>> It actually is not clear yet which branches are the right one for
>>>>> current Scratch on raspi and also future proof.  Perhaps doing for
>>>>> multiple branches is necessary?  (What are the relationship of those?)
>>>>
>>>> Oh, it’s absolutely clear for the Pi; Cog/Spur. The ancient original MIT image and an elderly interpreter are kept around for emergency use but will not be updated.
>>>
>>> Okay!
>>>
>>> By any chance, can you tell me how you test things? for Raspberry Pi?
>>
>> A Pi is cheap enough that one can simply buy one.  The new 64-bit one runs 32-bit binaries and is significantly faster than a pi2.  As far as testing, one can either connect a display via hdmi and a mouse & keyboard via usb, or use VNC.  There's a guide to setup of raspbian and of the VNC server on raspberrypi.org.
>
> Sorry for posing a vague question...  I do have a couple of Pis (Pi
> and Pi2, but not Pi3), and have done some graphics stuff in C over
> SSH.  So I invoke my program from a shell running emacs on an SSH
> session and things appear on a display connected to a Pi.  But I have
> not tried VNC there.  I haven't done any real Squeak stuff on Pi and
> for Pi; if running Squeak on Pi and interacting with it over VNC is
> reasonably fast, I'd go with that path.  But this one involves some C
> programs and if people does some cross compiling more on a host
> computer, that is also an interesting option.

VNC feels pretty fast.  IIRC there was some issue about running X11 apps directly.  I'm not sure I could find a package.  Anyway, Tim and u have been using VNC and it feels fine.

>
>
> --
> -- Yoshiki
>

Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

timrowledge
In reply to this post by Yoshiki Ohshima-3

> On 05-05-2016, at 2:34 PM, Yoshiki Ohshima <[hidden email]> wrote:
>
> Sorry for posing a vague question...  I do have a couple of Pis (Pi
> and Pi2, but not Pi3), and have done some graphics stuff in C over
> SSH.  So I invoke my program from a shell running emacs on an SSH
> session and things appear on a display connected to a Pi.  But I have
> not tried VNC there.  I haven't done any real Squeak stuff on Pi and
> for Pi; if running Squeak on Pi and interacting with it over VNC is
> reasonably fast, I'd go with that path.  But this one involves some C
> programs and if people does some cross compiling more on a host
> computer, that is also an interesting option.

Ah, I see.

When the first Pi came out and I started on improving Scratch, things were sufficiently slow in Scratch that I did much of my work on my iMac and just test-ran the system on the Pi. Compiling the VM etc has always been on the Pi, since
a) it’s fast enough to be no problem even on a Pi B
b) I’m not about to start messing around setting up a cross-compiling system. Gcc is enough of a nuisance as it is without that extra layer of madness.

The first improvements to Scratch were to make its image run on a more recent VM, which didn’t take a lot and on the circa 2012 interpreter it was ok to do some Squeak work on the Pi. Morphic was still a bit painful in a development image. That combination sufficed to get Scratch running around 4-8X faster as measured by an assortment of example projects; it wasn’t difficult to find and fix a rather large collection of poor code.

After that I moved all the source to a modern image (4.4? 4.5?) and rewrote almost everything to use layout properly, events, etc etc. That meant we could jump to a stack vm as well - and then the Pi 2 arrived. A Pi 2 running Squeak 4.5 on a stack vm is a decent development machine and by that stage I was doing all my work on the Pi. Then Eliot & I got the Cog vm working as well, and Squeak 5/Cog/spur on a Pi 2 is pretty damn fast.

I got my first Pi 3 last august, just as we got Cog going, which is why the PICs had to be rewritten - it turned out the the first version had a curious bug that didn’t cause a fatal error on a ‘real’ ARM v7 but does on an ARM v8 running v7 emulation. A production Pi 3 with cog/spur/5 benchmarks at around 100 dorado, 10% or so of my i7 3GHz iMac  (using the shootout bmarks) and 280m bc/sec & 12m sends/s. Running my  latest Scratch version you can run power hungry projects like PacMan around twice as fast as the original Scratch on my 2011 era macbook, which I suspect is around twice as fast as one fro m’07 when Scratch was initially released.

So, don’t waste time on cross-compiling or treating a Pi as some sort of arduino/toy; it’s a real computer.  I see that kind of assumption everywhere; people asking what IDE to use to make programs for a Pi and how to download it and make it run. Argh! It’s a quad-core 1.2GHz unix supercomputer!

I recommend installing
sudo apt-get install netatalk libnss-mdns xrdp i2c-tools
then for dev work
sudo apt-get install  libX11-dev uuid-dev libcairo2-dev libpango1.0-dev autoconf libasound2-dev libssl-dev
then save some space
sudo apt-get remove wolfram-engine

set up nfs
On Pi-
`sudo aptitude install nfs-common portmap` (in jessie, no need to install)
On the current version of Raspbian, rpcbind (part of the portmap package) does not start by default. . To enable it manually, so we can mount our directory immediately:
sudo service rpcbind start
sudo update-rc.d rpcbind enable
mkdir /home/pi/DizietFS <- obviously change to suit
sudo mount -t nfs 192.168.1.65:/Users/tim /home/pi/DizietFS <- obviously, your ip & path


Now, to make it permanent, you need to edit /etc/fstab to make the directory mount at boot. I added a line to the end of /etc/fstab:

`192.168.1.65:/Users/tim /home/pi/DizietFS nfs rsize=8192,wsize=8192,timeo=14,intr,noauto,x-systemd.automount 0 0`

On iMac-
in a terminal
`sudo nano /etc/exports` (which won’t normally exist until you save it)
and add the line
`/Users/tim -mapall=tim -alldirs -network 192.168.1.0 -mask 255.255.255.0`
`sudo nfsd restart`
should restart the daemon.

After all that, reboot the Pi and DizietFS ought to be visible and accessible.

On windows -
no idea. Don’t do windows.

Make the LXDE GUI less irritating

edit .xsessionrc (creating if required)
add
xsetroot  -cursor_name left_ptr&

chmod a+x .xsessionrc
reboot to get proper cursor in X instead of a big ugly X

Use an rdp client on your mac/windows machine - I use the msoft one on my iMac and it’s fine. If you expect to use xrdp most of the time, use raspi-config to set the Pi to boot to command line rather than desktop.

Pi 3 has wifi & bt built in. Sound output is via a typically lousy ( and lossy) headphone socket or the hdmi, or add a nice HAT. Sound input is only via usb sound dongle or HAT.


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Never do card tricks for the group you play poker with.



Reply | Threaded
Open this post in threaded view
|

Why everyone should develop on a Pi at least sometimes (was: Re: [squeak-dev] International text input on X11)

timrowledge
In reply to this post by Eliot Miranda-2
A classic problem we have is that people devise UI stuff and other widgetry on a fast computer. Because, of course they do, why not? The issue is then using that stuff on more mundane machines - or even embedded devices. Whereupon we discover to our horror that not having a 750THz intel 256bit gigacore with 42Pb of RAM means that our nice clever button takes 45 years to handle a mouse click.

So to combat this, it really would be smart for everyone doing development to at least occasionally run on a less frenetic machine such as a Pi. A Pi (especially a 3) is fast enough to be pretty nice for running current Squeak, even with Shout operational. But it is slow enough to show up places where your algorithm really isn’t doing a good job, or where your UI doohickey is really spending a terrible number of cycles to animate that cute little effect.

For extra effect, run on a non-cog vm too. That might be too much masochism for everyday development but it will *really* show you were performance is being wasted.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: CPM: Change Programmer's Mind



Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Yoshiki Ohshima-3
In reply to this post by timrowledge
Great.  Thanks.

I'll give it a try... I might not do NFS but seems good.  So the VM
would be the one I would produce by checking out the svn repository on
squeakvm.org, go to the branches/Cog directory and compile?  Is there
a dev image you use?

On Thu, May 5, 2016 at 3:33 PM, tim Rowledge <[hidden email]> wrote:

>
>> On 05-05-2016, at 2:34 PM, Yoshiki Ohshima <[hidden email]> wrote:
>>
>> Sorry for posing a vague question...  I do have a couple of Pis (Pi
>> and Pi2, but not Pi3), and have done some graphics stuff in C over
>> SSH.  So I invoke my program from a shell running emacs on an SSH
>> session and things appear on a display connected to a Pi.  But I have
>> not tried VNC there.  I haven't done any real Squeak stuff on Pi and
>> for Pi; if running Squeak on Pi and interacting with it over VNC is
>> reasonably fast, I'd go with that path.  But this one involves some C
>> programs and if people does some cross compiling more on a host
>> computer, that is also an interesting option.
>
> Ah, I see.
>
> When the first Pi came out and I started on improving Scratch, things were sufficiently slow in Scratch that I did much of my work on my iMac and just test-ran the system on the Pi. Compiling the VM etc has always been on the Pi, since
> a) it’s fast enough to be no problem even on a Pi B
> b) I’m not about to start messing around setting up a cross-compiling system. Gcc is enough of a nuisance as it is without that extra layer of madness.
>
> The first improvements to Scratch were to make its image run on a more recent VM, which didn’t take a lot and on the circa 2012 interpreter it was ok to do some Squeak work on the Pi. Morphic was still a bit painful in a development image. That combination sufficed to get Scratch running around 4-8X faster as measured by an assortment of example projects; it wasn’t difficult to find and fix a rather large collection of poor code.
>
> After that I moved all the source to a modern image (4.4? 4.5?) and rewrote almost everything to use layout properly, events, etc etc. That meant we could jump to a stack vm as well - and then the Pi 2 arrived. A Pi 2 running Squeak 4.5 on a stack vm is a decent development machine and by that stage I was doing all my work on the Pi. Then Eliot & I got the Cog vm working as well, and Squeak 5/Cog/spur on a Pi 2 is pretty damn fast.
>
> I got my first Pi 3 last august, just as we got Cog going, which is why the PICs had to be rewritten - it turned out the the first version had a curious bug that didn’t cause a fatal error on a ‘real’ ARM v7 but does on an ARM v8 running v7 emulation. A production Pi 3 with cog/spur/5 benchmarks at around 100 dorado, 10% or so of my i7 3GHz iMac  (using the shootout bmarks) and 280m bc/sec & 12m sends/s. Running my  latest Scratch version you can run power hungry projects like PacMan around twice as fast as the original Scratch on my 2011 era macbook, which I suspect is around twice as fast as one fro m’07 when Scratch was initially released.
>
> So, don’t waste time on cross-compiling or treating a Pi as some sort of arduino/toy; it’s a real computer.  I see that kind of assumption everywhere; people asking what IDE to use to make programs for a Pi and how to download it and make it run. Argh! It’s a quad-core 1.2GHz unix supercomputer!
>
> I recommend installing
> sudo apt-get install netatalk libnss-mdns xrdp i2c-tools
> then for dev work
> sudo apt-get install  libX11-dev uuid-dev libcairo2-dev libpango1.0-dev autoconf libasound2-dev libssl-dev
> then save some space
> sudo apt-get remove wolfram-engine
>
> set up nfs
> On Pi-
> `sudo aptitude install nfs-common portmap` (in jessie, no need to install)
> On the current version of Raspbian, rpcbind (part of the portmap package) does not start by default. . To enable it manually, so we can mount our directory immediately:
> sudo service rpcbind start
> sudo update-rc.d rpcbind enable
> mkdir /home/pi/DizietFS <- obviously change to suit
> sudo mount -t nfs 192.168.1.65:/Users/tim /home/pi/DizietFS <- obviously, your ip & path
>
>
> Now, to make it permanent, you need to edit /etc/fstab to make the directory mount at boot. I added a line to the end of /etc/fstab:
>
> `192.168.1.65:/Users/tim /home/pi/DizietFS nfs rsize=8192,wsize=8192,timeo=14,intr,noauto,x-systemd.automount 0 0`
>
> On iMac-
> in a terminal
> `sudo nano /etc/exports` (which won’t normally exist until you save it)
> and add the line
> `/Users/tim -mapall=tim -alldirs -network 192.168.1.0 -mask 255.255.255.0`
> `sudo nfsd restart`
> should restart the daemon.
>
> After all that, reboot the Pi and DizietFS ought to be visible and accessible.
>
> On windows -
> no idea. Don’t do windows.
>
> Make the LXDE GUI less irritating
>
> edit .xsessionrc (creating if required)
> add
> xsetroot  -cursor_name left_ptr&
>
> chmod a+x .xsessionrc
> reboot to get proper cursor in X instead of a big ugly X
>
> Use an rdp client on your mac/windows machine - I use the msoft one on my iMac and it’s fine. If you expect to use xrdp most of the time, use raspi-config to set the Pi to boot to command line rather than desktop.
>
> Pi 3 has wifi & bt built in. Sound output is via a typically lousy ( and lossy) headphone socket or the hdmi, or add a nice HAT. Sound input is only via usb sound dongle or HAT.
>
>
> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> Never do card tricks for the group you play poker with.
>
>
>



--
-- Yoshiki

Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

David T. Lewis
On Thu, May 05, 2016 at 04:01:29PM -0700, Yoshiki Ohshima wrote:
> Great.  Thanks.
>
> I'll give it a try... I might not do NFS but seems good.  So the VM
> would be the one I would produce by checking out the svn repository on
> squeakvm.org, go to the branches/Cog directory and compile?  Is there
> a dev image you use?
>

To check out the entire repository for Cog/Spur:

  $ svn co http://squeakvm.org/svn/squeak/branches/Cog

There is an ./images directory that contains development images, and
a README to explain. There are also ./build.* directories for building
various configurations.

Dave


Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

timrowledge
In reply to this post by Yoshiki Ohshima-3

> On 05-05-2016, at 4:01 PM, Yoshiki Ohshima <[hidden email]> wrote:
>
> Great.  Thanks.
>
> I'll give it a try... I might not do NFS but seems good.  So the VM
> would be the one I would produce by checking out the svn repository on
> squeakvm.org, go to the branches/Cog directory and compile?  Is there
> a dev image you use?

Just grab the Squeak 5.0 all-in-one bundle. It has a cog/spur vm ready to go on the Pi. And the image, of course. Just update it as usual. If you want the latest vm, then yes, you can build it in the normal manner as described in the Eliot’s readme. I’d guess that one could get from opening a fresh Pi box to running Sq5 on a new built vm in less than an hour, including all the apt-get and compile time etc. I did most of it a few weeks ago without problem just before a demo.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
To define recursion, we must first define recursion.



Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Yoshiki Ohshima-3
In reply to this post by David T. Lewis
On Thu, May 5, 2016 at 4:34 PM, David T. Lewis <[hidden email]> wrote:
> There is an ./images directory that contains development images, and
> a README to explain. There are also ./build.* directories for building
> various configurations.

Thanks!

First, I can run Squeak-5.0-All-in-One.zip.  on Pi.

I managed to compile squeak.cog.spur VM on ARM (raspberry pi).
However, when I tried to open the image in the All in One, it creates
a window but inside of it is just blank and does not do any
interaction.  I downloaded
http://www.mirandabanda.org/files/Cog/VM/VM.r3692/cogspurlinuxhtARM-16.18.3692.tgz
and tried it, but it has the same problem.

I looked into the chain of shell scripts and tried a command line like:

env LD_LIBRARY_PATH=/home/pi/tmp/cogspurlinuxhtARM/lib/squeak/5.0-3692:/lib/arm-linux-gnueabihf:/lib:/usr/lib/arm-linux-gnueabihf:/usr/lib
/home/pi/tmp/cogspurlinuxhtARM/lib/squeak/5.0-3692/squeak
~/Squeak5.0-15113.image

but no avail.

Does anybody know why the all in one vm and image works but the VM I
downloaded from Eliot's site (nor the one I compiled)?

--
-- Yoshiki

Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Eliot Miranda-2
Hi Yoshiki,

    it's probably just the absence of a sources file.  I don't include it in the VMs on my site to save space.  Simply link the sources into the lib dir in the directory tree, or include the sources in the directory containing the image.

On Fri, May 6, 2016 at 3:53 PM, Yoshiki Ohshima <[hidden email]> wrote:
On Thu, May 5, 2016 at 4:34 PM, David T. Lewis <[hidden email]> wrote:
> There is an ./images directory that contains development images, and
> a README to explain. There are also ./build.* directories for building
> various configurations.

Thanks!

First, I can run Squeak-5.0-All-in-One.zip.  on Pi.

I managed to compile squeak.cog.spur VM on ARM (raspberry pi).
However, when I tried to open the image in the All in One, it creates
a window but inside of it is just blank and does not do any
interaction.  I downloaded
http://www.mirandabanda.org/files/Cog/VM/VM.r3692/cogspurlinuxhtARM-16.18.3692.tgz
and tried it, but it has the same problem.

I looked into the chain of shell scripts and tried a command line like:

env LD_LIBRARY_PATH=/home/pi/tmp/cogspurlinuxhtARM/lib/squeak/5.0-3692:/lib/arm-linux-gnueabihf:/lib:/usr/lib/arm-linux-gnueabihf:/usr/lib
/home/pi/tmp/cogspurlinuxhtARM/lib/squeak/5.0-3692/squeak
~/Squeak5.0-15113.image

but no avail.

Does anybody know why the all in one vm and image works but the VM I
downloaded from Eliot's site (nor the one I compiled)?

--
-- Yoshiki




--
_,,,^..^,,,_
best, Eliot


Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Eliot Miranda-2


On Fri, May 6, 2016 at 4:21 PM, Eliot Miranda <[hidden email]> wrote:
Hi Yoshiki,

    it's probably just the absence of a sources file.  I don't include it in the VMs on my site to save space.  Simply link the sources into the lib dir in the directory tree, or include the sources in the directory containing the image.

Oops, it needs to go I'm the same directory as the VM, so e.g. add
    cogspurlinux/lib/squeak/4.5-3692/ ]SqueakV50.sources


On Fri, May 6, 2016 at 3:53 PM, Yoshiki Ohshima <[hidden email]> wrote:
On Thu, May 5, 2016 at 4:34 PM, David T. Lewis <[hidden email]> wrote:
> There is an ./images directory that contains development images, and
> a README to explain. There are also ./build.* directories for building
> various configurations.

Thanks!

First, I can run Squeak-5.0-All-in-One.zip.  on Pi.

I managed to compile squeak.cog.spur VM on ARM (raspberry pi).
However, when I tried to open the image in the All in One, it creates
a window but inside of it is just blank and does not do any
interaction.  I downloaded
http://www.mirandabanda.org/files/Cog/VM/VM.r3692/cogspurlinuxhtARM-16.18.3692.tgz
and tried it, but it has the same problem.

I looked into the chain of shell scripts and tried a command line like:

env LD_LIBRARY_PATH=/home/pi/tmp/cogspurlinuxhtARM/lib/squeak/5.0-3692:/lib/arm-linux-gnueabihf:/lib:/usr/lib/arm-linux-gnueabihf:/usr/lib
/home/pi/tmp/cogspurlinuxhtARM/lib/squeak/5.0-3692/squeak
~/Squeak5.0-15113.image

but no avail.

Does anybody know why the all in one vm and image works but the VM I
downloaded from Eliot's site (nor the one I compiled)?

--
-- Yoshiki




--
_,,,^..^,,,_
best, Eliot



--
_,,,^..^,,,_
best, Eliot


1234 ... 7