Thanks for both of your responses. I'm afraid things have got a bit too busy for me at the moment. I hope to get back to the forum when I have more time.
Quote:
Originally Posted by lensmann
I've only tried this on the Boox E43 where I had a go at writing LaTeX in Droidedit. It wasn't slow as such, but the lag seemed worse than it was because of the slow refresh rate. If you type without looking at the screen very much, it will probably be less evident. That said, I have no idea whether this translates across to large screen ereaders, so please take this under advisement.
|
My impression is that, for such applications at least, it is just the refresh rate. It think this carries over to the larger screen models. This seemed to be the case for Obuntu on the M92 for instance. If you can touch type you shouldn't loose keystrokes, they just don't turn up immediately. This is one reason why I'm rather emphatic on the need for a good keyboard (rather than a bluetooth one). If I can use a good keyboard so that I can focus on my typing, I can keep my typing mistakes down in which case I shouldn't need as much feedback from the screen.
Quote:
Originally Posted by franzli
I tried two different ways of accessing a Linux chroot. The chroot itself is stated by Linux deploy which works as expected.
Initially, I tried my usual setup with the xsdl xserver app. It loads up OK with since patience, but really seems to draw a lot of CPU power (don't quite remember, but I think I had 30-40%load when idle). So that is possible in principle (and would be more flexible for seeing keymaps with setxkbmap and so forth), but doesn't seem lots of fun on a single core CPU.
My alternative is to use the vnc server method in Linux deploy and acres that with the bvnc app. That seemed to be the least resource hogging one among the ones I've tried, I think you get below 10%CPU load when idle (maybe even below 5?)and some reasonably low memory load.
|
Thanks. That's very interesting. You at least sound like you know what you are doing. I recently managed to get a cheap Icarus Excel (sort of crippled M96 I think). After trying lots of distros I seem to have managed to install a distro using Linux Deploy. The RPM based distros ultimately seemed the most successful but I haven't really got much beyond that. I think I was in the process of setting up the VNC server which I don't think I quite finished before having to abandon it. I'll get back to it when I have more time.
Quote:
Originally Posted by franzli
Gedit is rather usable that easy, I think - it's still a tad slow, but more comfortable than with xsdl (where it's also possible but with the high cpu usage battery life should take a plunge). Is poetically use it more often if 1) it was still a bit faster, 2) I'd get around the keyboard mapping issue and 3) I had a larger screen than the 6.8 of the T68+. Given the relatively show scroll speed (partly due to the eink, partly due to simple cpu limitations), it's harder to get an overview of a larger piece of text on such a small screen, since you'll try to not scroll around too much.
|
Yes. I've never tried one of the standard, 6" screen devices. 10" is already a pretty small screen, although it strikes me as very workable if one has an efficient editor. I'd be using emacs. I gather this can create problems not unlike yours on Android because there are very few SSH clients that support Ctrl etc keys.