James>I wasn't envisoning using RO4 Kernel modules *at all*, just using the higher level stuff - and keeping the RO5 Kernel and *its* hardware modules.
If RO4 *higher level* modules (things like the Draw module) *demand* that an RO4 Kernel be present then that's daft isn't it ? Such high level modules should make *no* assumptions about lower level or kernel stuff and should access all OS functionality via SWI's in the normal way. Those SWI's being of course *documented*.
I don't see why to use *Select* you need to dump lower level stuff from RO5 (e.g., the Kernel) in order to use *much* of the Select functionality which appears to be UI enhancements (things that *should not* be accessing lower level stuff at all - except via defined SWI's).
It appears to me that ROL are making their life unnecessarily difficult, they should simply take what *can* be readily ported to RO5 (surely *something* must work, eh?) and make that available as a UI upgrade (a bit like Microsofts' Plus packs on some versions of windows). That way ROL make some money (good) while not fashioning a stick to beat themselves with (as would be the case if they tried to re-write the whole OS or shoehorn RO5 hardware modules onto RO4 Select's kernel.
What's more people would *expect* it not to have full Select functionality - so that would make the task less difficult - yet give RO5 users a UI "spruce up" - a good thing surely ? What do you think ?