New Dedicated hardware For RO64 - speculations

I tend to refer to the feature as autobol***, and I seem to have taught the iPhone auto-* to offer that as the prime candidate :)

“Typing” on the tiny screen of an iPhone is so horrible that autocomplete is actually useful, but whenever I possibly can I use a proper keyboard, amd somce O tpicj tu[e [rettu fast wotjpit ;pplomg at tje leunpard ,pst pf tje to,e. ot cp,es pit ;ole tjos/ – bah, on the RiscPC I used to have a keyboard driver I wrote that knew when I was doing that, and would fix it without me even noticing. (Go on, challenge for you, what exactly happened? Deliberately, on this occasion…)

Your right hand is one key space to the right. I wrote a Tcl script to decipher your message.

“and since i touch type pretty fast without looking at the keyboard most of the time, it comes out like this.”

set map {
 n b  7 6  u y  j h  
 m n  8 7  i u  k j  
 , m  9 8  o i  l k  
 . ,  0 9  p o  ; l  
 / .  - 0  [ p  ' ;  
}
set msg {amd somce O tpicj tu[e [rettu fast wotjpit ;pplomg at tje leunpard ,pst pf tje to,e. ot cp,es pit ;ole tjos/}
puts [string map $map [string tolower $msg]]

Go on, challenge for you, what exactly happened?

Patrick got it, your right hand was off-by-one. I didn’t read his message but I was working on decoding it in my head as it was a simple “keyboard partly shifted” cypher.

and would fix it without me even noticing.

I look between the keyboard and the screen when I type, so errors are picked up and corrected pretty quickly.

When you see errors from me, and it is entire words that are wrong, this is probably because I’m swiping words on my phone and it picks a different word than the one I wanted and, well, given the small screen size (and bugs in Chrome ¹), things to slip through.

“Typing” on the tiny screen of an iPhone is so horrible

Typing on any phone/tablet is horrible. There’s no give to the screen, so you’re repeatedly banging your fingers on a solid surface.
Swipe-to-type is the only sensible way of doing it. Does Apple support that yet?

[my last foray with Apple was iOS7 which didn’t, and not only that but it was too braindead/obstreperous to change the keyboard text between upper and lower case depending on the status of the shift].

¹ Zoom in on a page to see the text you’re entering more clearly and redraw goes to hell. Yet more quality code from Google…

I think my point is with a 64-bit RIC OS conversion written in pure C for 1; Future compability, ease of maintenance, and 2; Adding functionality updates that weren’t around in 1999 like support for BlueTooth and other current industry standards and multicore CPUs.

I look between the keyboard and the screen when I type,

I often type with my eyes shut. Rarely look at the keyboard, except for function or cursor keys.

Typing on any phone/tablet is horrible.

I don’t doubt it, but I don’t do it much. I’ve only recently got an iPhone…my previous phone, a hand-me-down from my publisher, nominally a smart phone but I never discovered how to do anything with it other than making phone calls or sending or receiving texts, didn’t (as far as I ever discovered) do predictive text. It was even horribler to type on than the iPhone.

And Patrick is of course correct. I forget now exactly how my keyboard driver worked – but it doesn’t work on the Pi – neither the original ones nor the current ones, none of my keyboard drivers do 8~(

I think my point is with a 64-bit RIC OS conversion written in pure C

If written in C, the number of bits, and indeed the architecture of the host system, ought to be largely irrelevant.
If it isn’t, you’re doing it wrong.

written in pure C

Meanwhile, the world outside is looking towards languages that try to protect programmers from themselves.

like support for BlueTooth and other current industry standards

Much of the USB code and networking is written in already C, brought over from afar. If you really want Bluetooth, find somebody willing to do it and pay them for their time. You don’t need a brand new OS for that.

Of course, there is the obvious paradox – if it isn’t getting done with the existing system, what makes you think it’ll get done in the midst of a ground-up rewrite?

I think my point is with a 64-bit RIC OS

Hush child, grown-ups are speaking.

Aw, come on, let’s not be mean…

Sveinung, you seem to have missed my question that I posted on page 6 of this thread, I’m really genuinely interested to know what you use RISC OS for, and what your experience with it is like. You say it’s the most productive system for you which surprises me, so I’m interested to know more about your computing history and why RISC OS means so much to you.

Swipe-to-type is the only sensible way of doing it. Does Apple support that yet?

Yep.

Aw, come on, let’s not be mean…

We’ve exhausted that option a long, long time ago I think.