International text input on X11

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

Re: International text input on X11

timrowledge

> On 06-05-2016, at 4:27 PM, Eliot Miranda <[hidden email]> wrote:
>
>     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
>

Not on any of my Pi’s it doesn’t; I normally run with the sources in the same directory as the image while developing - and of course , a deployed Scratch image doesn’t need them at all. I’m fairly sure the sources ought to be able to live in the local dir, the image dir, the vm dir and obviously somewhere there will be a place to specify any other location you like.

Another possibility is Yoshiki has an old version of Raspbian; old kernel from early last year (?) wouldn’t let us futz wit the timer thread priority without pain. It’s been a while since that was fixed but if you have an old Raspbian… except that ought to prevent the all-in-one system running. But this is unix, which is carefully designed to drive one to the edge of madness, so maybe you just had the wrong kind of egg for your breakfast last time there was a blue moon.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Asking whether machines can think is like asking whether submarines can swim.



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
oh, ok.  I'll give it a try.

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

>
>
> 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
>
>
>



--
-- Yoshiki

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 Fri, May 6, 2016 at 5:58 PM, tim Rowledge <[hidden email]> wrote:
>
> Another possibility is Yoshiki has an old version of Raspbian; old kernel from early last year (?) wouldn’t let us futz wit the timer thread priority without pain. It’s been a while since that was fixed but if you have an old Raspbian… except that ought to prevent the all-in-one system running. But this is unix, which is carefully designed to drive one to the edge of madness, so maybe you just had the wrong kind of egg for your breakfast last time there was a blue moon.

That sounds plausible.  I did "apt-get update" to get some packages
loadable but did not go on to update the entire system. I'll try that.



--
-- Yoshiki

Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Yoshiki Ohshima-3
The VM still does not display anything in the white window after I did
apt-get dist-upgrade, and copy the .sources file to the same directly.
(But I did not have an egg this morning).  I'll try some display
options.  But also, it appears that the source code for the Cog seems
to have the part I wrote for the composition input.  The goal may be
nearer than I originally thought.

On Fri, May 6, 2016 at 6:23 PM, Yoshiki Ohshima <[hidden email]> wrote:

> On Fri, May 6, 2016 at 5:58 PM, tim Rowledge <[hidden email]> wrote:
>>
>> Another possibility is Yoshiki has an old version of Raspbian; old kernel from early last year (?) wouldn’t let us futz wit the timer thread priority without pain. It’s been a while since that was fixed but if you have an old Raspbian… except that ought to prevent the all-in-one system running. But this is unix, which is carefully designed to drive one to the edge of madness, so maybe you just had the wrong kind of egg for your breakfast last time there was a blue moon.
>
> That sounds plausible.  I did "apt-get update" to get some packages
> loadable but did not go on to update the entire system. I'll try that.
>
>
>
> --
> -- Yoshiki



--
-- Yoshiki

Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

timrowledge

> On 09-05-2016, at 10:35 AM, Yoshiki Ohshima <[hidden email]> wrote:
>
> The VM still does not display anything in the white window after I did
> apt-get dist-upgrade, and copy the .sources file to the same directly.
> (But I did not have an egg this morning).  I'll try some display
> options.  But also, it appears that the source code for the Cog seems
> to have the part I wrote for the composition input.  The goal may be
> nearer than I originally thought.

That’s really disturbing. I mean, no egg for breakfast?

No, seriously, there’s no way you ought to be getting strange display problems. So far I’ve never had them on dozens of Pi’s over dozens of release mixes of Raspbian and VM and image. And even many actual displays both real and virtual.

My suggestion for any serious Raspbian update is do  fresh load fro mPi central. I’ve read many people’s problem with inconsistent results of dist-upgrade and update and mixed up apt-gets and so on. Quicker to download/burn/reboot.

Aaand…. of course; built the new vm with hostwindowplugin included to respond to Levente and what do I get? blank white screen. Sigh.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
USER ERROR: replace user and press any key to continue.



Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Yoshiki Ohshima-3
On Mon, May 9, 2016 at 10:43 AM, tim Rowledge <[hidden email]> wrote:

>
>> On 09-05-2016, at 10:35 AM, Yoshiki Ohshima <[hidden email]> wrote:
>>
>> The VM still does not display anything in the white window after I did
>> apt-get dist-upgrade, and copy the .sources file to the same directly.
>> (But I did not have an egg this morning).  I'll try some display
>> options.  But also, it appears that the source code for the Cog seems
>> to have the part I wrote for the composition input.  The goal may be
>> nearer than I originally thought.
>
> Aaand…. of course; built the new vm with hostwindowplugin included to respond to Levente and what do I get? blank white screen. Sigh.

Oh, so you do get blank white screen?  So, I guess I'd checkout an
older revision of the svn repo just for now. What would a good
revision to go back to?


--
-- Yoshiki

Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

timrowledge

> On 09-05-2016, at 10:47 AM, Yoshiki Ohshima <[hidden email]> wrote:
> Oh, so you do get blank white screen?  So, I guess I'd checkout an
> older revision of the svn repo just for now. What would a good
> revision to go back to?

The last one I have built for Pi and running ok is 3663 and it just went bad in 3692. So I guess we start binary dividing...


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
"How many Motie Mediators does it take to chage a lightbulb?”
"Are you insane? Only Crazy Eddie would want to change *anything*!"




Reply | Threaded
Open this post in threaded view
|

Borked unix displaying in vm3692 (wasRe: [squeak-dev] International text input on X11)

timrowledge
An svn diff -r 3663:3692 in platforms/unix shows only some (to me) innocuous changes in vm/aio.c

More unixy expertise required to say if that has anything to do with it.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: BA: Branch Approximate



Reply | Threaded
Open this post in threaded view
|

Re: Borked unix displaying in vm3692 (wasRe: [squeak-dev] International text input on X11)

timrowledge

> On 09-05-2016, at 11:05 AM, tim Rowledge <[hidden email]> wrote:
>
> An svn diff -r 3663:3692 in platforms/unix shows only some (to me) innocuous changes in vm/aio.c
>
> More unixy expertise required to say if that has anything to do with it.

Building with the older version makes no difference for me. Let’s try an older tree.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
42.7 percent of all statistics are made up on the spot.



Reply | Threaded
Open this post in threaded view
|

Re: Borked unix displaying in vm3692 (wasRe: [squeak-dev] International text input on X11)

timrowledge

> On 09-05-2016, at 11:16 AM, tim Rowledge <[hidden email]> wrote:
>
>
>> On 09-05-2016, at 11:05 AM, tim Rowledge <[hidden email]> wrote:
>>
>> An svn diff -r 3663:3692 in platforms/unix shows only some (to me) innocuous changes in vm/aio.c
>>
>> More unixy expertise required to say if that has anything to do with it.
>
> Building with the older version makes no difference for me. Let’s try an older tree.

3680 fails, let’s try 3670


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Death to all fanatics!



Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Yoshiki Ohshima-3
In reply to this post by timrowledge
I confirm that r3663 does work on my Pi2 for Squeak5.0-15113.image.
I'll try to make some progress from there for now.

On Mon, May 9, 2016 at 10:54 AM, tim Rowledge <[hidden email]> wrote:

>
>> On 09-05-2016, at 10:47 AM, Yoshiki Ohshima <[hidden email]> wrote:
>> Oh, so you do get blank white screen?  So, I guess I'd checkout an
>> older revision of the svn repo just for now. What would a good
>> revision to go back to?
>
> The last one I have built for Pi and running ok is 3663 and it just went bad in 3692. So I guess we start binary dividing...
>
>
> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> "How many Motie Mediators does it take to chage a lightbulb?”
> "Are you insane? Only Crazy Eddie would want to change *anything*!"
>
>
>
>



--
-- Yoshiki

Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

timrowledge

> On 09-05-2016, at 11:37 AM, Yoshiki Ohshima <[hidden email]> wrote:
>
> I confirm that r3663 does work on my Pi2 for Squeak5.0-15113.image.
> I'll try to make some progress from there for now.

3680 fails, 3670 work; 3675 fail; 3673 won’t build

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
When all else fails, let a = 7.  If that doesn't help, then read the manual.



Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

timrowledge

> On 09-05-2016, at 11:40 AM, tim Rowledge <[hidden email]> wrote:
>
>
>> On 09-05-2016, at 11:37 AM, Yoshiki Ohshima <[hidden email]> wrote:
>>
>> I confirm that r3663 does work on my Pi2 for Squeak5.0-15113.image.
>> I'll try to make some progress from there for now.
>
> 3680 fails, 3670 work; 3675 fail; 3673 won’t build

3672 fails.
At this rate my Pi will wear out its SD card by the end of the day…

3671 works.




tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
A conclusion is the place where you got tired of thinking.



Reply | Threaded
Open this post in threaded view
|

Re: Borked unix displaying in vm3692 (wasRe: [squeak-dev] International text input on X11)

timrowledge
In reply to this post by timrowledge

> On 09-05-2016, at 11:24 AM, tim Rowledge <[hidden email]> wrote:
>
>
>> On 09-05-2016, at 11:16 AM, tim Rowledge <[hidden email]> wrote:
>>
>>
>>> On 09-05-2016, at 11:05 AM, tim Rowledge <[hidden email]> wrote:
>>>
>>> An svn diff -r 3663:3692 in platforms/unix shows only some (to me) innocuous changes in vm/aio.c
>>>
>>> More unixy expertise required to say if that has anything to do with it.
>>
>> Building with the older version makes no difference for me. Let’s try an older tree.
>
> 3680 fails, let’s try 3670

Per the X11 input thread for those not paying attention to everything, 3671 is the last one I can get a display displaying on a Pi.


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Klingon Code Warrior:- 6) "Our competitors are without honor!"



Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Yoshiki Ohshima-3
In reply to this post by Yoshiki Ohshima-3
On Mon, May 9, 2016 at 10:35 AM, Yoshiki Ohshima
<[hidden email]> wrote:
> The VM still does not display anything in the white window after I did
> apt-get dist-upgrade, and copy the .sources file to the same directly.
> (But I did not have an egg this morning).  I'll try some display
> options.  But also, it appears that the source code for the Cog seems
> to have the part I wrote for the composition input.  The goal may be
> nearer than I originally thought.

It may not as closer than I thought, however.  The world evolved to
use ibus; we'd need to add some more stuff, such as DBus...  I'll
report more tomorrow.

--
-- Yoshiki

Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Stephan Eggermont-3
In reply to this post by timrowledge
On 09-05-16 20:52, tim Rowledge wrote:
> At this rate my Pi will wear out its SD card by the end of the day…
Does a Pi3 have enough memory to build on a  ram disk?

Stephan



Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

John Pfersich-2
The pi3 has 1 gb of memory, it'd have to be a small disk. Never tried it.

> On May 9, 2016, at 21:34, Stephan Eggermont <[hidden email]> wrote:
>
>> On 09-05-16 20:52, tim Rowledge wrote:
>> At this rate my Pi will wear out its SD card by the end of the day…
> Does a Pi3 have enough memory to build on a  ram disk?
>
> Stephan
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Bert Freudenberg
In reply to this post by Yoshiki Ohshima-3
On 10.05.2016, at 02:23, Yoshiki Ohshima <[hidden email]> wrote:

>
> On Mon, May 9, 2016 at 10:35 AM, Yoshiki Ohshima
> <[hidden email]> wrote:
>> The VM still does not display anything in the white window after I did
>> apt-get dist-upgrade, and copy the .sources file to the same directly.
>> (But I did not have an egg this morning).  I'll try some display
>> options.  But also, it appears that the source code for the Cog seems
>> to have the part I wrote for the composition input.  The goal may be
>> nearer than I originally thought.
>
> It may not as closer than I thought, however.  The world evolved to
> use ibus; we'd need to add some more stuff, such as DBus...  I'll
> report more tomorrow.
Doesn’t ibus generate “old” X events, too? The README suggests this should work:

        XMODIFIERS="@im=ibus" squeak

... which we could put in the startup script.

- Bert -






smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Yoshiki Ohshima-3
On Tue, May 10, 2016 at 7:37 AM, Bert Freudenberg <[hidden email]> wrote:

> On 10.05.2016, at 02:23, Yoshiki Ohshima <[hidden email]> wrote:
>>
>> On Mon, May 9, 2016 at 10:35 AM, Yoshiki Ohshima
>> <[hidden email]> wrote:
>>> The VM still does not display anything in the white window after I did
>>> apt-get dist-upgrade, and copy the .sources file to the same directly.
>>> (But I did not have an egg this morning).  I'll try some display
>>> options.  But also, it appears that the source code for the Cog seems
>>> to have the part I wrote for the composition input.  The goal may be
>>> nearer than I originally thought.
>>
>> It may not as closer than I thought, however.  The world evolved to
>> use ibus; we'd need to add some more stuff, such as DBus...  I'll
>> report more tomorrow.
>
> Doesn’t ibus generate “old” X events, too? The README suggests this should work:
>
>         XMODIFIERS="@im=ibus" squeak
>
> ... which we could put in the startup script.

This does not quite work.  And also Abe-san says that I'd better make
it work with scim first so I am taking that path now.

BTW, I have a long standing question of the development process.  I
create a VM by doing ./mvm, which creates display drivers and VM in
one way or another, and installs them to products directory somewhere
upthere.  I have trouble seeing my changes to code gets reflected
sometimes.  (Say, I change a printf message somehwere in sqUnixX11.c,
run mvm and invoke the squeak shell script in
products/cogspurlinuxhtARM/ but it seems to pick up a different binary
from somewhere else.

What do people do to make the debug cycle go faster on Linux?

--
-- Yoshiki

Reply | Threaded
Open this post in threaded view
|

Re: International text input on X11

Eliot Miranda-2
Hi Yoshiki,

> On May 11, 2016, at 11:52 AM, Yoshiki Ohshima <[hidden email]> wrote:
>
>> On Tue, May 10, 2016 at 7:37 AM, Bert Freudenberg <[hidden email]> wrote:
>>> On 10.05.2016, at 02:23, Yoshiki Ohshima <[hidden email]> wrote:
>>>
>>> On Mon, May 9, 2016 at 10:35 AM, Yoshiki Ohshima
>>> <[hidden email]> wrote:
>>>> The VM still does not display anything in the white window after I did
>>>> apt-get dist-upgrade, and copy the .sources file to the same directly.
>>>> (But I did not have an egg this morning).  I'll try some display
>>>> options.  But also, it appears that the source code for the Cog seems
>>>> to have the part I wrote for the composition input.  The goal may be
>>>> nearer than I originally thought.
>>>
>>> It may not as closer than I thought, however.  The world evolved to
>>> use ibus; we'd need to add some more stuff, such as DBus...  I'll
>>> report more tomorrow.
>>
>> Doesn’t ibus generate “old” X events, too? The README suggests this should work:
>>
>>        XMODIFIERS="@im=ibus" squeak
>>
>> ... which we could put in the startup script.
>
> This does not quite work.  And also Abe-san says that I'd better make
> it work with scim first so I am taking that path now.
>
> BTW, I have a long standing question of the development process.  I
> create a VM by doing ./mvm, which creates display drivers and VM in
> one way or another, and installs them to products directory somewhere
> upthere.  I have trouble seeing my changes to code gets reflected
> sometimes.  (Say, I change a printf message somehwere in sqUnixX11.c,
> run mvm and invoke the squeak shell script in
> products/cogspurlinuxhtARM/ but it seems to pick up a different binary
> from somewhere else.

It shouldn't.  That's where the resulting binary gets installed (or a debug build in products/debug/cogspurlinuxhtARM etc).

>
> What do people do to make the debug cycle go faster on Linux?

That's what I've been using, and I find it unsatisfactory too.  I don't like the automake system and want to replace the whole thing with Gnu make makefiles (as is used in the win32 and MacOS builds) which would result in more sharing between the production, assert and debug builds plus accurate dependency information for reliable compilation, and the possibility of making a valid cogspurlinuxhtARM directory tree in the build directory and hence (again as I do in the win32 and MacOS builds) running the executable in the build directory instead of from products.

> -- Yoshiki

_,,,^..^,,,_ (phone)
12345 ... 7