Is it possible to execute a bash script from the SD card?

[Grimulkan]

I see. Well, the search continues then...

[wallcraft]

Originally Posted by Mackx

Sakura uses vte which is easy to compile for the DR (I used version 0.17.4) with Anjuta.

I just came across evilvte. It is also VTE-based and apparently uses GTK+. Its web page also has a list of other terminal programs that might be worth looking into.

The Smart Q7 Tablet is using evilvte. As a low-power keyboardless tablet, this is quite similar to the DR1000S. It also gets better battery life, but with a smaller LCD screen.

[Mackx]

Originally Posted by wallcraft

I just came across evilvte. It is also VTE-based and apparently uses GTK+. Its web page also has a list of other terminal programs that might be worth looking into.

The Smart Q7 Tablet is using evilvte. As a low-power keyboardless tablet, this is quite similar to the DR1000S. It also gets better battery life, but with a smaller LCD screen.

Thanks for the links. The problems I had were with VTE, not (yet) with Sakura. VTE is a GTK-widget implementing a full functional terminal window, that comes with a simple application using the widget. So all VTE based terminal programs are also gtk-based. There seem to be a lot of terminal programs that are vte based, so porting vte seems to be 'the key'.

The dynamics of the code of VTE is my problem, if someone has a link to an easier implementation of 'terminal code' I could try to add a gtk-widget to it.

[Grimulkan]

Originally Posted by Mackx

Thanks for the links. The problems I had were with VTE, not (yet) with Sakura. [...]

Do xterm, rxvt etc. also use VTE? These are not GTK+, but we already have some familiarity on introducing the proper refresh hooks (in fact, what iRex did for GTK+ is much simpler than what we did with Xournal), if we can get everything else to compile on X.

Also, what was done for the iLiad? I'm sure someone thought of something.

[Mackx]

Originally Posted by Grimulkan

Do xterm, rxvt etc. also use VTE?

They seem to use X directly. I am able to build rxvt but get the message:
"/usr/local/bin/rxvt: line 1: syntax error: "(" unexpected"
when I start the program...
My (porting) knowledge is not good enough to find the cause of this problem. Any ideas?

[ross]

Originally Posted by Mackx

They seem to use X directly. I am able to build rxvt but get the message:
"/usr/local/bin/rxvt: line 1: syntax error: "(" unexpected"
when I start the program...
My (porting) knowledge is not good enough to find the cause of this problem. Any ideas?

That's usually because an executable is compiled for the wrong architecture. 'file' can tell you which arch something was built for:

src/rxvt: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.14, not stripped

I got rxvt-2.7.10 to build with:

source /usr/local/poky/eabi-glibc/arm/environment-setup
./configure --host=arm-poky-linux-gnueabi
make

I didn't try it on emulator/device though. Even with display updates fixed, you'de still need to get the keyboard to pop up somehow (since matchbox-keyboard hooks into GTK to know when to show/hide).

[Mackx]

Originally Posted by ross

That's usually because an executable is compiled for the wrong architecture. 'file' can tell you which arch something was built for:

src/rxvt: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.14, not stripped

I got rxvt-2.7.10 to build with:

source /usr/local/poky/eabi-glibc/arm/environment-setup
./configure --host=arm-poky-linux-gnueabi
make

I didn't try it on emulator/device though. Even with display updates fixed, you'de still need to get the keyboard to pop up somehow (since matchbox-keyboard hooks into GTK to know when to show/hide).

Damn that's the tip I wanted...
It seems that CC is not taken from the environment so it used the local gcc for X86 (I should have payed more attention when it was building). After I modified the Makefile it worked. (autoreconf gave some errors so I did not use it.)
I am using rxvt-2.6.4 so that might explain the different experience you had.

Now for the good news: IT RUNS (on the emulator using Ctrl-Alt-1 to refresh :-). I need to add some refresh patches. I need to check which ones are working on an X-only app. Hope to post the binary and modified code soon.

... and then ofcourse the keyboard ...

[Grimulkan]

Originally Posted by Mackx

[...] Now for the good news: IT RUNS (on the emulator using Ctrl-Alt-1 to refresh :-). I need to add some refresh patches. I need to check which ones are working on an X-only app. Hope to post the binary and modified code soon.

... and then ofcourse the keyboard ...

Sweet BTW, all the refresh hooks we used in Xournal are valid, I've tested them out on the Matchbox Keyboard which is an X-only app. You might want to use one of the fast updates (maybe even the 1bpp one) for just text updates.

I have no idea how to summon the keyboard though.

[Mackx]

Originally Posted by Grimulkan

I have no idea how to summon the keyboard though.

I am also still looking into that...

[Grimulkan]

Originally Posted by Mackx

I am also still looking into that...

You could just call the program, will that bring up the keyboard or create a new instance?

[Mackx]

Let me first start with a warning: DO NOT USE THIS (unless you know what you are doing).

I managed to get some type of terminal working, but it should only be used by experts and people with a lot of patience and willing to do extra actions to get anything to display. I worked long enough on this stuff now and I am not making much progress anymore, so I publish it here.

Some information on the content of the zip file.

Programs\_rxvt contains a port of rxvt and mc.
BUT: there is no keyboard! It can be usefull when installing newly ported programs on the DR to figure out what is wrong (I discovered that the qemu has libncurses installed and the DR, not using rxvt). See the .desktop files in Programs/ for some examples.
Refreshes are REALLY BAD, pressing cursor buttons or right/left middle button sometimes has a positive effect on the refresh. Its use is very limited.
(I might have installed an extra library on my DR to get it working, but I am not sure anymore, please let me know if it does not run. You can first try on the qemu ofcourse.)

Programs/_install contains the ipkg files for libncurses and libvte and some helper files.

Programs/Install contains the .desktop files to install libncurses and libvte. I had a lot of problems installing vte this way, the 'please wait' pop-up would show and not disappear anymore, so I had to reset. So maybe you should install vte using the rxvt-vte.desktop file. I also tried that and that seemed to work better.

When you start vte and start typing with your stylus, you will only see some black squares, pressing enter will give some white-space. If you however use the scrollbar to scoll, you will see some text appearing...

That is it... it might be usefull if porting programs to the DR, for all others: DO NOT USE THIS

If anyone is interested in the changes I made, please let me know, maybe someone want to start from here...