Resource allocation clarificationBy Chris Williams. Published: 3rd Dec 2004, 17:58:59 | Permalink | Printable
Blushes all roundIt's come to our attention that we've been publishing inaccuracies. It seems back in 2001, this news item from RISCOS Ltd. managed to slip under our news radar and was completely missed by drobe.co.uk: it announces that the RISC OS resource allocation list is to be managed by RISCOS Ltd., and not by Pineapple's Alan Glover.
The resource list maintains a database of numbers and names that applications and other software can officially use. An application developer cannot officially use resources, such as SWI numbers and names, system variables and icon names, with having had them allocated from the list. This prevents applications clashing and otherwise upsetting each other if two developers were to try to use the same resources. For more information on the subject, see RISCOS Ltd.'s announcement.
Now because developers should request resource allocations during the early stages of development, the resource requests are commercially sensitive - as an example, in the past and still to the present day, Castle and RISCOS Ltd. remain rivals as they develop their separate streams of RISC OS (especially in the desktop arena and now moreso as RISC OS gears up for embedded kit). One side may not want the other side to see what kind of developments they're up to. You might find this sort of thing to be ridiculous in a market the size of the RISC OS platform, but competition drives innovation and this is the reality of the situation. Justin Fletcher recently gave a good argument why the list should be kept independent, if you ignore the bits where he, like others, thought that Alan was still maintaining the list independently.
So therefore, we and many others argue, the list should be independently maintained and protected by trusted a third party that has no overall interest in any particular developer: this person has been, for a long time now, Alan Glover. Due to the nature of the allocation process, it can't be automated, and Alan's basically done a good job over the years in maintaining the allocation list.
And so now, it turns out that RISCOS Ltd. now own ("manage") the list, although Alan still, at the end of day, maintains the list for ROL. However, ROL can request the list at any time from Alan. Yes, it's messy, but the announcement in 2001 is before the RISC OS 4/5 split hit the scene. Castle confirmed that Alan still maintains the list for all third parties, although Castle's CTO John Ballance seemed as surprised as us. When we tried to contact Alan today, we learnt that he does still centrally maintain the allocations list.
Anyway, previous drobe.co.uk articles, such as the one about the filetype wiki, which refer to Alan as independently maintaining the list are wrong: RISCOS Ltd. have for some time now managed the list, with Alan maintaining the allocations for them. Let's hope this is clear now.
Resource allocation on riscos.com
Previous: Spellings.net to open e-shop for software
Next: Updates from the Unix Porting Project
DiscussionViewing threaded comments | View comments unthreaded, listed by date | Skip to the end
Please login before posting a comment. Use the form on the right to do so or create a free account.
Search the archives
Today's featured article
Archive magazine reviewed
A media watch special
10 comments, latest by diomus on 27/10/07 12:01PM. Published: 23 Oct 2007
Ian Nichols shows the DIY mouse way
9 comments, latest by diomus on 25/3/05 5:17PM. Published: 17 Mar 2005
News and media:
RISCOS Ltd •
RISC OS Open •
MW Software •
Advantage Six •
CJE Micros •
Liquid Silicon •
Chris Why's Acorn/RISC OS collection •
The Register •
The Inquirer •
Apple Insider •
BBC News •
Sky News •
Google News •