The relationship between /usr/bin/scratch and /usr/bin/squeak is
somewhat confused. /usr/bin/scratch has some code to handle VMOPTIONS but it is not actually passed to /usr/bin/squeak. But then if /usr/bin/scratch was passing those to /usr/bin/squeak, that shell script does not handle them. I'd think it might be good to copy the LD_LIBRARY_PATH part of /usr/bin/squeak to /usr/bin/scratch, and the latter does not deal with the former. What do you guys think? On Mon, May 16, 2016 at 10:14 AM, Yoshiki Ohshima <[hidden email]> wrote: > On Mon, May 16, 2016 at 10:06 AM, Yoshiki Ohshima > <[hidden email]> wrote: >> On Mon, May 16, 2016 at 10:04 AM, tim Rowledge <[hidden email]> wrote: >>> Forgive me if I’m being hopelessly naive here, but does this text input mechanism work for other languages too? Would it, for example, be usable as an on-screen keyboard for theRaspberry Pi lcd touchscreen? >> >> It should work for any other languages that ibus or scim can handle. >> Yes, it will be usable with the on-screen keyboard. > > So I wrote about two possible options on changes to /usr/bin/scratch; > I think that the option that uses the XMODIFIERS environment variable, > or some other ways to tell that there is an input method running, is > more suitable for this purpose. > > > -- > -- Yoshiki -- -- Yoshiki |
I have not actually looked at the /usr/bin/scratch script, but I do know
that the use of /usr/bin/squeak (or /usr/local/bin/squeak) is already overloaded depending on what flavor of VM was installed most recently. I suspect that it would be better to have a /usr/bin/scratch script that does exactly what you want it to do, possibly not relying at all on the /usr/bin/squeak script. Tim, when someone installs Scratch on their Pi, does that installation include the VM? Or does it expect a VM to be installed separately? I am assuming that the Scratch installation would include a VM and with the Scratch plugins, and that you would not want other installations of VMs to affect the Scratch application. Is that right? Dave > The relationship between /usr/bin/scratch and /usr/bin/squeak is > somewhat confused. /usr/bin/scratch has some code to handle VMOPTIONS > but it is not actually passed to /usr/bin/squeak. But then if > /usr/bin/scratch was passing those to /usr/bin/squeak, that shell > script does not handle them. I'd think it might be good to copy the > LD_LIBRARY_PATH part of /usr/bin/squeak to /usr/bin/scratch, and the > latter does not deal with the former. > > What do you guys think? > > On Mon, May 16, 2016 at 10:14 AM, Yoshiki Ohshima > <[hidden email]> wrote: >> On Mon, May 16, 2016 at 10:06 AM, Yoshiki Ohshima >> <[hidden email]> wrote: >>> On Mon, May 16, 2016 at 10:04 AM, tim Rowledge <[hidden email]> >>> wrote: >>>> Forgive me if Iâm being hopelessly naive here, but does this text >>>> input mechanism work for other languages too? Would it, for example, >>>> be usable as an on-screen keyboard for theRaspberry Pi lcd >>>> touchscreen? >>> >>> It should work for any other languages that ibus or scim can handle. >>> Yes, it will be usable with the on-screen keyboard. >> >> So I wrote about two possible options on changes to /usr/bin/scratch; >> I think that the option that uses the XMODIFIERS environment variable, >> or some other ways to tell that there is an input method running, is >> more suitable for this purpose. >> >> >> -- >> -- Yoshiki > > > > -- > -- Yoshiki > |
On Mon, May 16, 2016 at 1:23 PM, David T. Lewis <[hidden email]> wrote:
> I have not actually looked at the /usr/bin/scratch script, but I do know > that the use of /usr/bin/squeak (or /usr/local/bin/squeak) is already > overloaded depending on what flavor of VM was installed most recently. I > suspect that it would be better to have a /usr/bin/scratch script that > does exactly what you want it to do, possibly not relying at all on the > /usr/bin/squeak script. > > Tim, when someone installs Scratch on their Pi, does that installation > include the VM? Or does it expect a VM to be installed separately? I am > assuming that the Scratch installation would include a VM and with the > Scratch plugins, and that you would not want other installations of VMs to > affect the Scratch application. Is that right? The "nuscratch" package comes with the following files (besides some other files). The thing is that the package seems to have dependency on the scratch package, which in turn has dependency on squeak-vm. Note that both /usr/bin/squeak and /usr/bin/scratch are replaced with the ones that come in the nuscratch package and old ones are renamed to /usr/bin/squeak.old and /usr/bin/scratch.old. Yes, I think it is good that the nuscratch package only replaces /usr/bin/scratch, and not depend on the squeak-vm package. nuscratch: /usr/bin/scratch nuscratch: /usr/bin/squeak nuscratch: /usr/lib/squeak/5.0-3663/LocalePlugin nuscratch: /usr/lib/squeak/5.0-3663/Squeak3D nuscratch: /usr/lib/squeak/5.0-3663/SqueakFFIPrims nuscratch: /usr/lib/squeak/5.0-3663/SqueakSSL nuscratch: /usr/lib/squeak/5.0-3663/UUIDPlugin nuscratch: /usr/lib/squeak/5.0-3663/UnicodePlugin nuscratch: /usr/lib/squeak/5.0-3663/UnixOSProcessPlugin nuscratch: /usr/lib/squeak/5.0-3663/WeDoPlugin nuscratch: /usr/lib/squeak/5.0-3663/XDisplayControlPlugin nuscratch: /usr/lib/squeak/5.0-3663/squeak nuscratch: /usr/lib/squeak/5.0-3663/vm-display-X11 nuscratch: /usr/lib/squeak/5.0-3663/vm-display-null nuscratch: /usr/lib/squeak/5.0-3663/vm-sound-ALSA nuscratch: /usr/lib/squeak/5.0-3663/vm-sound-OSS nuscratch: /usr/lib/squeak/5.0-3663/vm-sound-null nuscratch: /usr/share/scratch/NuScratch02052016.image ... -- -- Yoshiki |
My suggested change to /usr/bin/scratch would look like attached diff.
Basically, it brings in the part to figure out the right LD_LIBRARY_PATH based on the VM's architecture, add a way to specify the display vm module, add a way to specify display module options, and finally figures out the need for -compositioninput based on the XMODIFIERS environment variable. On Mon, May 16, 2016 at 3:28 PM, Yoshiki Ohshima <[hidden email]> wrote: > On Mon, May 16, 2016 at 1:23 PM, David T. Lewis <[hidden email]> wrote: >> I have not actually looked at the /usr/bin/scratch script, but I do know >> that the use of /usr/bin/squeak (or /usr/local/bin/squeak) is already >> overloaded depending on what flavor of VM was installed most recently. I >> suspect that it would be better to have a /usr/bin/scratch script that >> does exactly what you want it to do, possibly not relying at all on the >> /usr/bin/squeak script. >> >> Tim, when someone installs Scratch on their Pi, does that installation >> include the VM? Or does it expect a VM to be installed separately? I am >> assuming that the Scratch installation would include a VM and with the >> Scratch plugins, and that you would not want other installations of VMs to >> affect the Scratch application. Is that right? > > The "nuscratch" package comes with the following files (besides some > other files). The thing is that the package seems to have dependency > on the scratch package, which in turn has dependency on squeak-vm. > Note that both /usr/bin/squeak and /usr/bin/scratch are replaced with > the ones that come in the nuscratch package and old ones are renamed > to /usr/bin/squeak.old and /usr/bin/scratch.old. > > Yes, I think it is good that the nuscratch package only replaces > /usr/bin/scratch, and not depend on the squeak-vm package. > > nuscratch: /usr/bin/scratch > nuscratch: /usr/bin/squeak > nuscratch: /usr/lib/squeak/5.0-3663/LocalePlugin > nuscratch: /usr/lib/squeak/5.0-3663/Squeak3D > nuscratch: /usr/lib/squeak/5.0-3663/SqueakFFIPrims > nuscratch: /usr/lib/squeak/5.0-3663/SqueakSSL > nuscratch: /usr/lib/squeak/5.0-3663/UUIDPlugin > nuscratch: /usr/lib/squeak/5.0-3663/UnicodePlugin > nuscratch: /usr/lib/squeak/5.0-3663/UnixOSProcessPlugin > nuscratch: /usr/lib/squeak/5.0-3663/WeDoPlugin > nuscratch: /usr/lib/squeak/5.0-3663/XDisplayControlPlugin > nuscratch: /usr/lib/squeak/5.0-3663/squeak > nuscratch: /usr/lib/squeak/5.0-3663/vm-display-X11 > nuscratch: /usr/lib/squeak/5.0-3663/vm-display-null > nuscratch: /usr/lib/squeak/5.0-3663/vm-sound-ALSA > nuscratch: /usr/lib/squeak/5.0-3663/vm-sound-OSS > nuscratch: /usr/lib/squeak/5.0-3663/vm-sound-null > nuscratch: /usr/share/scratch/NuScratch02052016.image > ... > > > > -- > -- Yoshiki -- -- Yoshiki scratch.diff (5K) Download Attachment |
In reply to this post by Yoshiki Ohshima-3
NuScratch is not at all properly packaged so far as I’m aware. I simply zip up all the relevant files and dump them on the Pi people, they install them in the Raspbian releases and there you are. So, no dependencies on packages, no users installing it, no complications of multiple VMs. It’s all there ready to run as soon as you boot.
As for the two shell scripts… they’re hacked up versions of the mess I inherited. In my view the /usr/bin/scratch script should gather up all the scratch specific settings, variable, paths and pass them onto the /usr/bin/squeak script which should run the appropriate vm under the appropriate settings with the given image and possible extra options. If someone has a better way to do it I’m very happy to learn. There are no faffing arounds with working out cpu architecture etc since we just don’t care about anyone not smart enough to run on a Pi :-) And if anyone is worrying about licenses etc (I know they’re out there; just like Zombies in the movies, they’re *always out there*) please don’t ask me. Not my issue; my views on license stuff are well scatted across the net and are probably not safe for the faint of heart. Email the Raspberry Pi Foundation and talk to them. Oh, and Yoshiki, you have an out of date version. Fetch a new copy of Raspbian... tim -- tim Rowledge; [hidden email]; http://www.rowledge.org/tim Four wheels move the body. Two wheels move the soul |
On Mon, May 16, 2016 at 4:55 PM, tim Rowledge <[hidden email]> wrote:
> NuScratch is not at all properly packaged so far as I’m aware. I simply zip up all the relevant files and dump them on the Pi people, they install them in the Raspbian releases and there you are. So, no dependencies on packages, no users installing it, no complications of multiple VMs. It’s all there ready to run as soon as you boot. > > As for the two shell scripts… they’re hacked up versions of the mess I inherited. In my view the /usr/bin/scratch script should gather up all the scratch specific settings, variable, paths and pass them onto the /usr/bin/squeak script which should run the appropriate vm under the appropriate settings with the given image and possible extra options. If someone has a better way to do it I’m very happy to learn. > > There are no faffing arounds with working out cpu architecture etc since we just don’t care about anyone not smart enough to run on a Pi :-) And if anyone is worrying about licenses etc (I know they’re out there; just like Zombies in the movies, they’re *always out there*) please don’t ask me. Not my issue; my views on license stuff are well scatted across the net and are probably not safe for the faint of heart. Email the Raspberry Pi Foundation and talk to them. > > Oh, and Yoshiki, you have an out of date version. Fetch a new copy of Raspbian... Oh, shoot. Are you talking about "May-10" version? I am just now trying apt-get dist-upgrade but would it update /usr/bin/scratch? In any case, at least the patch attached to my last email captures the change that is needed and get rid of the need to call /usr/bin/squeak. So adapting this should not be hard. -- -- Yoshiki |
> On 16-05-2016, at 5:01 PM, Yoshiki Ohshima <[hidden email]> wrote: > > Oh, shoot. Are you talking about "May-10" version? I am just now > trying apt-get dist-upgrade but would it update /usr/bin/scratch? Yup. upgrade etc *ought* to work but I too often read of problems, so I just fetch a full release and so on. I guess you might try specifically updating nuscratch (can you do that? I dunno, probably too logical for unix), though you ought to get the pigpio libraries/daemon as well or the gpio server will not work. > > In any case, at least the patch attached to my last email captures the > change that is needed and get rid of the need to call /usr/bin/squeak. > So adapting this should not be hard. > > > > -- > -- Yoshiki > > tim -- tim Rowledge; [hidden email]; http://www.rowledge.org/tim "Both.." said Pooh, as the guillotine came down |
Okay. I think dist-upgrade did it and here is a new patch that is
against the latest /usr/bin/scratch: On Mon, May 16, 2016 at 5:07 PM, tim Rowledge <[hidden email]> wrote: > >> On 16-05-2016, at 5:01 PM, Yoshiki Ohshima <[hidden email]> wrote: >> >> Oh, shoot. Are you talking about "May-10" version? I am just now >> trying apt-get dist-upgrade but would it update /usr/bin/scratch? > > Yup. upgrade etc *ought* to work but I too often read of problems, so I just fetch a full release and so on. I guess you might try specifically updating nuscratch (can you do that? I dunno, probably too logical for unix), though you ought to get the pigpio libraries/daemon as well or the gpio server will not work. > >> >> In any case, at least the patch attached to my last email captures the >> change that is needed and get rid of the need to call /usr/bin/squeak. >> So adapting this should not be hard. >> >> >> >> -- >> -- Yoshiki >> >> > > > tim > -- > tim Rowledge; [hidden email]; http://www.rowledge.org/tim > "Both.." said Pooh, as the guillotine came down > > > -- -- Yoshiki scratch.diff (6K) Download Attachment |
In reply to this post by Yoshiki Ohshima-3
> On 16.05.2016, at 19:06, Yoshiki Ohshima <[hidden email]> wrote: > > On Mon, May 16, 2016 at 10:04 AM, tim Rowledge <[hidden email]> wrote: >> Forgive me if I’m being hopelessly naive here, but does this text input mechanism work for other languages too? Would it, for example, be usable as an on-screen keyboard for theRaspberry Pi lcd touchscreen? > > It should work for any other languages that ibus or scim can handle. > Yes, it will be usable with the on-screen keyboard. Would it be feasible to make the VM primitives generic? That is, do not call it “ImmX11Plugin” but e.g. “KeyboardPlugin” and the “focus” primitive would be called whenever a text field is focused, and the image would pass the cursor position as arguments (plus possibly the text field bounds). Then we could implement the same primitives in e.g. the iOS or Android VMs to support the on-screen keyboard. - Bert - smime.p7s (5K) Download Attachment |
On Tue, May 17, 2016 at 7:29 AM, Bert Freudenberg <[hidden email]> wrote:
> >> On 16.05.2016, at 19:06, Yoshiki Ohshima <[hidden email]> wrote: >> >> On Mon, May 16, 2016 at 10:04 AM, tim Rowledge <[hidden email]> wrote: >>> Forgive me if I’m being hopelessly naive here, but does this text input mechanism work for other languages too? Would it, for example, be usable as an on-screen keyboard for theRaspberry Pi lcd touchscreen? >> >> It should work for any other languages that ibus or scim can handle. >> Yes, it will be usable with the on-screen keyboard. > > Would it be feasible to make the VM primitives generic? That is, do not call it “ImmX11Plugin” but e.g. “KeyboardPlugin” and the “focus” primitive would be called whenever a text field is focused, and the image would pass the cursor position as arguments (plus possibly the text field bounds). > > Then we could implement the same primitives in e.g. the iOS or Android VMs to support the on-screen keyboard. I think it's feasible in theory. Originally, we had separated primitives for different platforms and the dispatch was done in the image. But standard primitive sounds reasonable. On the practice side, The current ImmX11Plugin somehow got some Unix Locale features, which must have been added by for some reasons; it is is a bit overloaded and may require to disentangle them. -- -- Yoshiki |
In reply to this post by Yoshiki Ohshima-3
On Mon, May 16, 2016 at 9:30 AM, Yoshiki Ohshima
<[hidden email]> wrote: > At Sun, 15 May 2016 22:27:13 -0400, > David T. Lewis wrote: > >> - Yoshiki, we should give credit to Mr Hachisuka for his contribution. Can >> you please give his full name for the commit notice? I assume the patch >> is MIT licensed. > > I'll ask him about the license. Mr. Hachisuka stated that it is fine to use the MIT license for that code. -- -- Yoshiki |
On Tue, May 17, 2016 at 06:29:59PM -0700, Yoshiki Ohshima wrote:
> On Mon, May 16, 2016 at 9:30 AM, Yoshiki Ohshima > <[hidden email]> wrote: > > At Sun, 15 May 2016 22:27:13 -0400, > > David T. Lewis wrote: > > > >> - Yoshiki, we should give credit to Mr Hachisuka for his contribution. Can > >> you please give his full name for the commit notice? I assume the patch > >> is MIT licensed. > > > > I'll ask him about the license. > > Mr. Hachisuka stated that it is fine to use the MIT license for that code. Yoshiki, Thank you for confirming this. Dave |
In reply to this post by Yoshiki Ohshima-3
On Mon, May 16, 2016 at 09:30:02AM -0700, Yoshiki Ohshima wrote:
> At Sun, 15 May 2016 22:27:13 -0400, > David T. Lewis wrote: > > > - Test the VM. Tim, I need help on this. I do not currently have a working > > Cog build environment (Unbuntu/autotools/gcc version issues). Can you > > apply the patch from Yoshiki's email and see if your resulting Cog VM > > continues to work for you as expected on Pi with Scratch? > > And more testing would be nice. > The attached sqUnixX11.c should get the HostWindowPlugin functions working on Cog/Spur. If that is confirmed, I will commit to SVN oscog branch and then we can follow up with the ImmX11 updates. When you get a chance, can you please compile a VM with the attached sqUnixX11.c and let me know if the following works on Squeak trunk and Raspberry Pi: saveExtent := Display width @ Display height. DisplayScreen hostWindowExtent: 500@100. (Delay forSeconds: 4) wait. DisplayScreen hostWindowExtent: saveExtent. Thanks, Dave sqUnixX11.c.gz (64K) Download Attachment |
In reply to this post by Yoshiki Ohshima-3
I really must apologize, I see that I attached the wrong file to my
original post. Attached here is the oscog version that needs testing. I am looking to confirm that the resulting Cog or Spur VM performs the HostWindowPlugin function to resize the display window: saveExtent := Display width @ Display height. DisplayScreen hostWindowExtent: 500@100. (Delay forSeconds: 4) wait. DisplayScreen hostWindowExtent: saveExtent. If someone can confirm this, I would be grateful. (Yes I know, we need to get GitHub and Travis CI going for the VM so that people will not need to ask silly questions like this). Thanks, Dave On Wed, May 18, 2016 at 10:44:08PM -0400, David T. Lewis wrote: > On Mon, May 16, 2016 at 09:30:02AM -0700, Yoshiki Ohshima wrote: > > At Sun, 15 May 2016 22:27:13 -0400, > > David T. Lewis wrote: > > > > > > - Test the VM. Tim, I need help on this. I do not currently have a working > > > Cog build environment (Unbuntu/autotools/gcc version issues). Can you > > > apply the patch from Yoshiki's email and see if your resulting Cog VM > > > continues to work for you as expected on Pi with Scratch? > > > > And more testing would be nice. > > > > Tim, > > The attached sqUnixX11.c should get the HostWindowPlugin functions > working on Cog/Spur. If that is confirmed, I will commit to SVN oscog > branch and then we can follow up with the ImmX11 updates. > > When you get a chance, can you please compile a VM with the attached > sqUnixX11.c and let me know if the following works on Squeak trunk > and Raspberry Pi: > > saveExtent := Display width @ Display height. > DisplayScreen hostWindowExtent: 500@100. > (Delay forSeconds: 4) wait. > DisplayScreen hostWindowExtent: saveExtent. > > Thanks, > Dave > sqUnixX11.c.gz (76K) Download Attachment |
Hi, Dave,
Thank you for taking care of this! This sqUnixX11.c does display things on Raspberry Pi for me. On Thu, May 19, 2016 at 6:12 PM, David T. Lewis <[hidden email]> wrote: > I really must apologize, I see that I attached the wrong file to my > original post. Attached here is the oscog version that needs testing. > > I am looking to confirm that the resulting Cog or Spur VM performs the > HostWindowPlugin function to resize the display window: > > saveExtent := Display width @ Display height. > DisplayScreen hostWindowExtent: 500@100. > (Delay forSeconds: 4) wait. > DisplayScreen hostWindowExtent: saveExtent. > > If someone can confirm this, I would be grateful. > > (Yes I know, we need to get GitHub and Travis CI going for the VM so that > people will not need to ask silly questions like this). > > Thanks, > Dave > > > On Wed, May 18, 2016 at 10:44:08PM -0400, David T. Lewis wrote: >> On Mon, May 16, 2016 at 09:30:02AM -0700, Yoshiki Ohshima wrote: >> > At Sun, 15 May 2016 22:27:13 -0400, >> > David T. Lewis wrote: >> > > >> > > - Test the VM. Tim, I need help on this. I do not currently have a working >> > > Cog build environment (Unbuntu/autotools/gcc version issues). Can you >> > > apply the patch from Yoshiki's email and see if your resulting Cog VM >> > > continues to work for you as expected on Pi with Scratch? >> > >> > And more testing would be nice. >> > >> >> Tim, >> >> The attached sqUnixX11.c should get the HostWindowPlugin functions >> working on Cog/Spur. If that is confirmed, I will commit to SVN oscog >> branch and then we can follow up with the ImmX11 updates. >> >> When you get a chance, can you please compile a VM with the attached >> sqUnixX11.c and let me know if the following works on Squeak trunk >> and Raspberry Pi: >> >> saveExtent := Display width @ Display height. >> DisplayScreen hostWindowExtent: 500@100. >> (Delay forSeconds: 4) wait. >> DisplayScreen hostWindowExtent: saveExtent. >> >> Thanks, >> Dave >> > > > > > -- -- Yoshiki |
Thank you Yoshiki, I will commit the update to the oscog branch tonight
when I get home. The next thing to try is your Imm patch for sqUnixX11.c Dave > Hi, Dave, > > Thank you for taking care of this! This sqUnixX11.c does display > things on Raspberry Pi for me. > > On Thu, May 19, 2016 at 6:12 PM, David T. Lewis <[hidden email]> > wrote: >> I really must apologize, I see that I attached the wrong file to my >> original post. Attached here is the oscog version that needs testing. >> >> I am looking to confirm that the resulting Cog or Spur VM performs the >> HostWindowPlugin function to resize the display window: >> >> saveExtent := Display width @ Display height. >> DisplayScreen hostWindowExtent: 500@100. >> (Delay forSeconds: 4) wait. >> DisplayScreen hostWindowExtent: saveExtent. >> >> If someone can confirm this, I would be grateful. >> >> (Yes I know, we need to get GitHub and Travis CI going for the VM so >> that >> people will not need to ask silly questions like this). >> >> Thanks, >> Dave >> >> >> On Wed, May 18, 2016 at 10:44:08PM -0400, David T. Lewis wrote: >>> On Mon, May 16, 2016 at 09:30:02AM -0700, Yoshiki Ohshima wrote: >>> > At Sun, 15 May 2016 22:27:13 -0400, >>> > David T. Lewis wrote: >>> > > >>> > > - Test the VM. Tim, I need help on this. I do not currently have a >>> working >>> > > Cog build environment (Unbuntu/autotools/gcc version issues). >>> Can you >>> > > apply the patch from Yoshiki's email and see if your resulting >>> Cog VM >>> > > continues to work for you as expected on Pi with Scratch? >>> > >>> > And more testing would be nice. >>> > >>> >>> Tim, >>> >>> The attached sqUnixX11.c should get the HostWindowPlugin functions >>> working on Cog/Spur. If that is confirmed, I will commit to SVN oscog >>> branch and then we can follow up with the ImmX11 updates. >>> >>> When you get a chance, can you please compile a VM with the attached >>> sqUnixX11.c and let me know if the following works on Squeak trunk >>> and Raspberry Pi: >>> >>> saveExtent := Display width @ Display height. >>> DisplayScreen hostWindowExtent: 500@100. >>> (Delay forSeconds: 4) wait. >>> DisplayScreen hostWindowExtent: saveExtent. >>> >>> Thanks, >>> Dave >>> >> >> >> >> >> > > > > -- > -- Yoshiki > |
Thank you!
On Fri, May 20, 2016 at 1:52 PM, David T. Lewis <[hidden email]> wrote: > Thank you Yoshiki, I will commit the update to the oscog branch tonight > when I get home. > > The next thing to try is your Imm patch for sqUnixX11.c > > Dave > >> Hi, Dave, >> >> Thank you for taking care of this! This sqUnixX11.c does display >> things on Raspberry Pi for me. >> >> On Thu, May 19, 2016 at 6:12 PM, David T. Lewis <[hidden email]> >> wrote: >>> I really must apologize, I see that I attached the wrong file to my >>> original post. Attached here is the oscog version that needs testing. >>> >>> I am looking to confirm that the resulting Cog or Spur VM performs the >>> HostWindowPlugin function to resize the display window: >>> >>> saveExtent := Display width @ Display height. >>> DisplayScreen hostWindowExtent: 500@100. >>> (Delay forSeconds: 4) wait. >>> DisplayScreen hostWindowExtent: saveExtent. >>> >>> If someone can confirm this, I would be grateful. >>> >>> (Yes I know, we need to get GitHub and Travis CI going for the VM so >>> that >>> people will not need to ask silly questions like this). >>> >>> Thanks, >>> Dave >>> >>> >>> On Wed, May 18, 2016 at 10:44:08PM -0400, David T. Lewis wrote: >>>> On Mon, May 16, 2016 at 09:30:02AM -0700, Yoshiki Ohshima wrote: >>>> > At Sun, 15 May 2016 22:27:13 -0400, >>>> > David T. Lewis wrote: >>>> > > >>>> > > - Test the VM. Tim, I need help on this. I do not currently have a >>>> working >>>> > > Cog build environment (Unbuntu/autotools/gcc version issues). >>>> Can you >>>> > > apply the patch from Yoshiki's email and see if your resulting >>>> Cog VM >>>> > > continues to work for you as expected on Pi with Scratch? >>>> > >>>> > And more testing would be nice. >>>> > >>>> >>>> Tim, >>>> >>>> The attached sqUnixX11.c should get the HostWindowPlugin functions >>>> working on Cog/Spur. If that is confirmed, I will commit to SVN oscog >>>> branch and then we can follow up with the ImmX11 updates. >>>> >>>> When you get a chance, can you please compile a VM with the attached >>>> sqUnixX11.c and let me know if the following works on Squeak trunk >>>> and Raspberry Pi: >>>> >>>> saveExtent := Display width @ Display height. >>>> DisplayScreen hostWindowExtent: 500@100. >>>> (Delay forSeconds: 4) wait. >>>> DisplayScreen hostWindowExtent: saveExtent. >>>> >>>> Thanks, >>>> Dave >>>> >>> >>> >>> >>> >>> >> >> >> >> -- >> -- Yoshiki >> > > > -- -- Yoshiki |
In reply to this post by David T. Lewis
> On 20-05-2016, at 1:52 PM, David T. Lewis <[hidden email]> wrote: > > Thank you Yoshiki, I will commit the update to the oscog branch tonight > when I get home. > > The next thing to try is your Imm patch for sqUnixX11.c I will get around to trying this out on my Pi’s, honest. Stuck in floating point emulation/simulation right now, after the ‘fun’ of fixing serial port + scratchboard code. tim -- tim Rowledge; [hidden email]; http://www.rowledge.org/tim Oxymorons: Almost exactly |
On Fri, May 20, 2016 at 04:10:28PM -0700, tim Rowledge wrote:
> > > On 20-05-2016, at 1:52 PM, David T. Lewis <[hidden email]> wrote: > > > > Thank you Yoshiki, I will commit the update to the oscog branch tonight > > when I get home. > > > > The next thing to try is your Imm patch for sqUnixX11.c > > I will get around to trying this out on my Pi???s, honest. Stuck in floating point emulation/simulation right now, after the ???fun??? of fixing serial port + scratchboard code. > I just committed the update to make HostWindowPlugin work for resizing the main window on Cog/Spur. If something breaks in the VM builds, blame me. Dave |
In reply to this post by David T. Lewis
On Sun, May 15, 2016 at 10:27:13PM -0400, David T. Lewis wrote:
> > If I understand correctly, here is what we need to do: > > 1) Apply the changes of Mr Hachisuka to the VM. > - The diff is in the earlier email from Yoshiki: > http://lists.squeakfoundation.org/pipermail/squeak-dev/2016-May/189599.html > http://www2.asu.ac.jp/hachi/v3/scratch14ime.html > - Test updated VM to make sure the changes do not cause problems. Make sure > it works without problems for Squeak trunk and for Scratch. > - Apply the update in SVN for both oscog and trunk. I can help here. > - Test the VM. Tim, I need help on this. I do not currently have a working > Cog build environment (Unbuntu/autotools/gcc version issues). Can you > apply the patch from Yoshiki's email and see if your resulting Cog VM > continues to work for you as expected on Pi with Scratch? > - Yoshiki, we should give credit to Mr Hachisuka for his contribution. Can > you please give his full name for the commit notice? I assume the patch > is MIT licensed. > Hi Yoshiki, I think that I now understand the VM changes for sqUnixX11.c, and I have applied the changes of Mr Hachisuka and committed them to the SVN trunk for interpreter VM. If these changes are correct, then I will also make a patch and commit them to the oscog branch for Cog/Spur VMs. I arranged the code such that the multibyte recordPendingKeys() logic is used if and only if the -compositioninput option is set on the command line or the equivalent SQUEAK_COMPOSITIONINPUT environment variable is set. I believe that this is the intended usage, but please let me know if I did not understand. If you are able to compile an interpreter VM (http://wiki.squeak.org/squeak/6354), then please let me know if these changes work as you expect. If you cannot easily make an interpreter VM, then I can commit the changes to the Cog/Spur branch, but I would prefer to test them first if possible. I also found that many of the module command line options are not being passed correctly from the VM to the modules. The -compositionsinput option was one of these, so I fixed it in this update (and I will check if for Cog/Spur when we apply the patch there). But there are others that do not work, so if you find other VM options for multilingual support that do not work as expected, this may be the reason. Dave |
Free forum by Nabble | Edit this page |