Drobe :: The archives
About Drobe | Contact | RSS | Twitter | Webspace | Tech docs | Downloads | BBC Micro

Profile for thesnark

ContactAbout me
Username: thesnark
Realname: Christopher Bazley
About me:
Homepage: http://www.bigfoot.com/~chrisbazley
Comments posted:72 (show all)

All comments

On Five tips for ROL over the next five years:

"To a large extent, isn't this a mute point these days?"

Presumably you mean a moot point rather than a silent one, unless you were deliberately putting a fresh spin on a hackneyed phrase.

moot –adjective 1. open to discussion or debate; debatable; doubtful: a moot point. 2. of little or no practical value or meaning; purely academic. 3. Chiefly Law. not actual; theoretical; hypothetical.

mute –adjective 1. silent; refraining from speech or utterance. 2. not emitting or having sound of any kind. 3. incapable of speech; dumb. 4. (of letters) silent; not pronounced. 5. Law. (of a person who has been arraigned) making no plea or giving an irrelevant response when arraigned, or refusing to stand trial (used chiefly in the phrase to stand mute). 6. Fox Hunting. (of a hound) hunting a line without giving tongue or cry.

 is a RISC OS Userthesnark on 20/5/09 6:03PM
[ Reply | Permalink | Report ]

On Website manager app gains backup-like feature:

I really like SiteMatch - it's just a pity that the redraw is so appallingly slow (even on a StrongARM machine).

 is a RISC OS Userthesnark on 6/1/09 7:11PM
[ Reply | Permalink | Report ]

On Star Fighter 3000 revamp revealed:

Just to set the record straight, the authors were Tim Parry and Andrew Hutchings.

I don't know who is responsible for this latest version.

 is a RISC OS Userthesnark on 31/3/08 8:32PM
[ Reply | Permalink | Report ]

On Star Fighter 3000 revamp revealed:

I can't take any credit for this at all. It looks to me like a port of the 3DO version, which was rewritten from scratch by Fednet in C rather than ARM code.

 is a RISC OS Userthesnark on 29/3/08 8:46PM
[ Reply | Permalink | Report ]

On Click right on with RISC OS:

I'm slightly amazed at the existence of RISC OS users who don't know all of this already. One thing that nobody has mentioned yet is that in RISC OS 5 and 6, you can ADJUST-click on the 'back' tool icon of a window in order to bring it to the front. I find that one really useful! (I think it originated in Director, and I am surprised that Acorn did not think of it themselves.)

 is a RISC OS Userthesnark on 23/3/08 7:59PM
[ Reply | Permalink | Report ]

On RISC OS 5 core source release imminent:

hubersn: "I think it is highly unlikely that both branches of RISC OS will merge. Therefore, I see the RISC OS Open source soon becoming the de facto standard for all RISC OS users"

If you are right then a stupendous amount of time will have been wasted by testers and developers who worked on the other branch.

 is a RISC OS Userthesnark on 21/10/07 1:47AM
[ Reply | Permalink | Report ]

On RISC OS 5 core source release imminent:

I don't want to rain on anyone's parade, but as someone who has contributed to the RISCOS Ltd branch of RISC OS in the past, I have extremely mixed feelings about this release. I doubt that I am the only one.

With some of this software such as Browse, there is no risk of conflict with a parallel RISCOS Ltd version, and I welcome its release wholeheartedly. However, in other cases - such as the Toolbox - there seems a high risk of duplicated effort and version number confusion (lucky users). The worst case scenario is that features will diverge, leading to incompatibilities (just what we need to retain developers). Colin Granville posted to usenet about this several months ago: [link]

I am not interested in reinventing wheels, filing duplicate bug reports, or repeating past discussions. Frankly, I am more likely to become disillusioned with both using RISC OS and developing software for it. Hey, I might even get a life instead! Sadly, there are few people left who are both capable and willing to work on RISC OS, and the last thing that we need is the worsening of the current schism. I fear that is what this latest source code release may precipitate, no matter how well-intentioned.

That is merely my personal point of view. I have no influence over the directors of either RISCOS Ltd or Castle Technology Ltd, nor much interest in their alleged past disputes.

 is a RISC OS Userthesnark on 21/10/07 12:27AM
[ Reply | Permalink | Report ]

On NetSurf halts punter's search for love:

arenaman: not everyone can afford to buy/maintain a second computer system in parallel with RISC OS.

 is a RISC OS Userthesnark on 5/2/07 11:30AM
[ Reply | Permalink | Report ]

On Open source Quake 2 port emerges:

I must confess myself disappointed to see Drobe use the bowdlerisation "Big Freaking Gun". Whilst this weapon is apparently described as "Big, uh, freakin' gun" in the Quake 2 game manual, Tom Hall's original design document for Doom leaves no doubt as to the true meaning of 'BFG': [link]

 is a RISC OS Userthesnark on 16/1/07 1:31AM
[ Reply | Permalink | Report ]

On The best of the Microdigital Mico manual:

In reply to TonyStill:

The review that I wrote for RISC Nation magazine (which is linked to from the Drobe article) does criticise the quality of the manual. I wrote:

"Unfortunately, like Microdigital's publicity literature it reads 'as though written by someone for whom English is not their first language' (the words of my sister). Correctly spelt, but grammatically strange. There is one section entitled 'Help its doesn't go', which didn't exactly instil confidence in me."

However, there are aspects of my review that I would change with the benefit of hindsight: I never received the network card that I had paid for (AFAIK they never produced a working network solution). The sound driver arrived very late and was never completely satisfactory (I had to fiddle with the volume to avoid distortion effects at high amplitude). When I made my blithe assertion that "the game port will save you 40ukp for a joystick interface", I didn't know I would have to write the driver myself. My statement that "the MIDI synthesiser on the sound card will be ideal for games" is also erroneous. I had a strong impression from MicroDigital adverts that the sound capabilities included MIDI synthesis, and MD never disabused me of this. My understanding now is that this referred only to the 'game port' on the sound card (i.e. you need an external MIDI synthesiser, which you can't use at the same time as joysticks).

 is a RISC OS Userthesnark on 7/1/07 5:27PM
[ Reply | Permalink | Report ]

On The best of the Microdigital Mico manual:

Surprisingly, this actually made me laugh - even though I had seen many of these mistakes before, and I was less than amused just after having bought the machine.

I think there are two morals here: Firstly, that a spell checker is not an adequate tool for checking the accuracy of a document. Secondly, that writing computer manuals is a skill that requires not only an excellent grasp of grammar, but also a clear and concise writing style. That is why 'technical author' is a profession in itself. Clearly MicroDigital could not afford to employ one.

Personally, I will never again buy any product from a company that produces written material of poor quality. In the case of MicroDigital, I should have been forewarned by some of their advertisements in Acorn User. This is not because I despise people that can't spell or punctuate correctly (I don't), but because the failure to recognise this as a problem and rectify it is often indicative of some deeper malaise.

Any mistakes in the above posting are - of course - deliberate, and were included for ironic effect.

 is a RISC OS Userthesnark on 6/1/07 5:28PM
[ Reply | Permalink | Report ]

On Developers to discuss new Style Guide:

In reply to nx:

If you really feel that the style guide needs drastically updating then it's a wonder that you use RISC OS in the first place!

Personally I feel that the time would be better spent in ensuring that applications are compliant with the existing Style Guide. I have done a lot of work on several legacy commercial applications with this goal.

With regard to future applications, in my opinion style guide compliance is best fostered by encouraging developers to use the Toolbox. Acorn themselves recognised this. Whilst it is possible to achieve a style guide compliant interface without the Toolbox, it seems to me that most people lack the motivation and/or skill to do this.

I would like to single out NetSurf for praise, as an application that adheres to the standard beautifully without using the Toolbox. In fact I believe that some aspects of its GUI would be difficult to implement in a Toolbox application. However, this required a lot of work by experienced developers (and even then there were initially minor anomalies; e.g. behaviour of the Return key in dialogue boxes).

 is a RISC OS Userthesnark on 22/12/06 5:05PM
[ Reply | Permalink | Report ]

On Could open source RISC OS bring back users?:

I am glad that you highlighted some of the erroneous statements in the article. Although it is often trumpeted as one of RISC OS's deficiencies, it does have memory protection, and this situation is improving all the time (especially in RISC OS 6).

I believe that many users see the supposed lack of memory protection as something upon which all other ills can be blamed. Many other things can go wrong, such as single-tasking programs that have claimed vectors being terminated abruptly and failing to release them. Addressing some of these other problems would be more productive than carping on about memory protection all the time.

 is a RISC OS Userthesnark on 10/12/06 1:14PM
[ Reply | Permalink | Report ]

On Castle directors patch up 'disagreement':

In reply to VirtualAcorn:

On my browser the moderation menu says "Derogatory/Off topic". What you said appeared to me to be derogatory, but I admit that it could just have been a colourful use of language.

 is a RISC OS Userthesnark on 27/11/06 10:33PM
[ Reply | Permalink | Report ]

On Midlands 2006 show photos and news:

I think the best picture caption is the one about "blackjack and hookers" - I laughed out loud. :-D

I also love the set up with the Atom and A9Home - the integration of old and new equipment is ingenious. Why haven't I ever seen an Atom at an Acorn show? Particularly impressive that it is still in working order.

 is a RISC OS Userthesnark on 27/11/06 1:47AM
[ Reply | Permalink | Report ]

On RISC OS 6 Select 4 preview released:

In reply to hEgelia:

If you look at the RISC OS Six Home Page, it says that "it is now based on a completely 26 bit / 32 bit neutral source". This is does not necessarily mean that all future builds will be 32 bit.

The preview is advertised as being for "RiscPC, A7000 and VirtualRPC" users. None of these platforms would benefit from a 32 bit build of the OS (it would just prevent you from running old applications). Therefore I assume that the preview is a 26 bit build.

 is a RISC OS Userthesnark on 25/11/06 1:35PM
[ Reply | Permalink | Report ]

On Drobe writer in nuke protest arrest:

As if more proof was needed of my family's left wing nutcase tendencies, I found this on the BBC News web site: [link]

 is a RISC OS Userthesnark on 24/11/06 3:25PM
[ Reply | Permalink | Report ]

On Drobe writer in nuke protest arrest:

Good for Ian!

This is a subject that I have some interest in, since my sister (yes, that one), grandmother, mother and cousin are all involved in CND. I would not describe them as "left wing nutcases". As for me, I don't have the courage of my convictions, but having been brought up on Doctor Who, I find our government's manufacture and possession of such weapons to be obscene. Hypocrisy seems to be the order of the day in international politics.

In reply to druck: The UK's nuclear deterrent is not truly independent (compare it with France's); our dependence on the US is partly what ties us to their foreign policy. The fact that it is seen to be "one of the few things that keeps us on the top table of international politics" is precisely why the non-proliferation treaty has failed. Other countries that aspire to power and influence know that this is only obtainable by having nuclear weapons. Those countries that never had any intention of fulfilling their commitment to disarm (like us) have only themselves to blame for nuclear proliferation.

 is a RISC OS Userthesnark on 24/11/06 2:59PM
[ Reply | Permalink | Report ]

On October news in brief:

I have the 'Home Computer Minefield' on VHS video at my parents house. The marketing schtick is a bit embarrassing to be honest, and the music is terrible. I suppose I bought it out of curiousity and kept it for historical interest.

Some of the claims are rather dubious; for example that an Acorn computer is just as good for games as other home computers and consoles of that era (illustrated by a child playing Lemmings, if I remember correctly). The technology may have been as good, but the number of titles available wasn't comparable.

The exhortation not to buy a computer unless it is "32 bit RISC" also looks very dated nowadays. Fads in processor design come and go, and this just seems like an attempt to blind consumers with jargon. Perhaps as the result, some of my friends at high school were under the impression that in real terms the performance of an A5000 or Risc PC was the equal of an IBM-compatible clocked twice as fast. (Whereas the actual frame rate of 'Doom' on a 40Mhz Risc PC is similar to a 386).

 is a RISC OS Userthesnark on 2/11/06 7:59PM
[ Reply | Permalink | Report ]

On Not enough room for two mags says Qercus ed:

In reply to steelpillow:

I think you vastly underestimate the amount of time required to achieve anything worthwhile in the field of programming. I have recently spent days (not minutes, which is all it takes to comment on a Drobe article) almost solely on a RISC OS programming project.

 is a RISC OS Userthesnark on 12/10/06 6:44PM
[ Reply | Permalink | Report ]

On Open sourcing RISC OS won't help says ROL:

In reply to bucksboy:

The fact that Paul M hasn't said that Select for Iyonix can't be done (or is not intended) suggests that it may happen. Presumably you wouldn't like him to rule it out just because it is not 100% certain?

 is a RISC OS Userthesnark on 3/9/06 8:49PM
[ Reply | Permalink | Report ]

On Resisting change is short-sighted:

In reply to druck:

AIF headers on transient utilities would indeed be wrong, because the design of these headers does not allow return to the calling environment (only termination via OS_Exit).

Fortunately the header required for transient utilities has a more appropriate format (the first word is a branch instruction rather than branch-with-link).

I was not aware of the 'informal lightweight mechanism' that you mention. Was it ever documented anywhere? What was the point of it if it was not enforced?

 is a RISC OS Userthesnark on 3/7/06 5:12PM
[ Reply | Permalink | Report ]

On Who are RISC OS Open Ltd?:

In reply to Xinoyi and liquid:

Unfortunately the PocketReader and Iyonix are both in London (whereas I'm in Bristol) but I will pass your comments on to Harriet.

 is a RISC OS Userthesnark on 29/6/06 1:08PM
[ Reply | Permalink | Report ]

On Who are RISC OS Open Ltd?:

In reply to Xinoyi:

My sister Harriet and I both spent (or should that be 'wasted') many hours trying to get the Siemens PocketReader device working with Iyonix, to no avail. So I can assure you that grey cells have already been applied.

As far as I can tell, the support module is perfectly compatible with 32-bit RISC OS, it is just inexplicable behaviour from the serial port on the Iyonix or the block drivers for it (written by a third party, I believe).

For more info about the Siemens PocketReader: [link]

 is a RISC OS Userthesnark on 27/6/06 6:34PM
[ Reply | Permalink | Report ]

On TEK 1608 in 32bit rumour:

Potentially good news about TEK. I was wondering only the other day whether it might be possible to do a 32 bit compatible version with the remaining bugs ironed out. I wondered this after it crashed for the second time on the same level!

If the code for TEK were open sourced then I believe this is the kind of project that many RISC OS programmers would enjoy working on. Mainly because it appears to be written in C (unlike SF3000, say) and R.T.S. games are fertile ground for interesting AI algorithms. Of course fixing bugs should be the priority.

However I've just come back from watching England draw with Sweden so maybe I'm still dreaming.

 is a RISC OS Userthesnark on 20/6/06 10:57PM
[ Reply | Permalink | Report ]

On Developers divided over RISC OS 4 code checking:

In reply to druck: The Acorn application note didn't merely recommend the move, it states baldly that "all Absolute files must have valid AIF headers".

From that statement I wouldn't have been surprised if RISC OS 3.7 had included the AIF header checking similar to that which has finally been implemented. That would have saved a lot of non-StrongARM compatible software crashing.

 is a RISC OS Userthesnark on 6/6/06 9:13PM
[ Reply | Permalink | Report ]

On Developers divided over RISC OS 4 code checking:

As Martin Wuerthner says, the opportune moment to enforce checks for 32 bit compatiblity is when the operating system is going to start executing code in 32 bit mode. I don't see why Castle's oversight in this matter should influence what ROL do with their own 32 bit RISC OS.

There are still many executable files out there that are not 32 bit compatible, and in my experience the AIF check is useful in identifying this. It has always been the case that most RISC OS applications use AIF anyway.

I am certain that David's figure of "hundreds of 32 bit applications" is an exaggeration, and "absolutely no warning to developers" is laughable given that they had ten years warning. What is the point in deprecating things at all if - even ten years down the line - there are screams of anguish when they are finally removed?

For the record, Star Fighter 3000 has had a valid AIF header since late 2003 and it works fine on the A9Home. No flies on me! :-)

 is a RISC OS Userthesnark on 5/6/06 8:59AM
[ Reply | Permalink | Report ]

On RiscPC prototype kit in auction:

In retrospect I feel that the Xemplar venture with Apple was the beginning of the end. Basically it was Acorn admitting that they had lost control of what had been their most important market (although that wasn't how it was spun in Acorn User). I wonder how the Acorn Education employees felt about it?

 is a RISC OS Userthesnark on 1/6/06 9:08AM
[ Reply | Permalink | Report ]

On Sir Robin leaves ARM:

I'm probably going to be moderated down for this, but is anyone else thinking of the song in Monty Python and the Holy Grail?

"Brave, brave, brave, brave Sir Robin! When danger reared its ugly head he bravely turned his tail and fled..."

 is a RISC OS Userthesnark on 27/5/06 11:01PM
[ Reply | Permalink | Report ]

On RISC OS 3 caught running on Amiga hardware:

In reply to druck:

It seems unfair to complain about "the length of time its take for a few minor fixes to be completed on the A9Home" when bugs in RISC OS 5 have still not been addressed more than three years after the Iyonix PC was launched.

Also, given that the A9Home's OS is significantly different from other versions of RISC OS (and apparently under active development), there may be more than meets the eye to problems that look like they could be solved by "minor fixes".

 is a RISC OS Userthesnark on 22/05/06 9:58PM
[ Reply | Permalink | Report ]

On Acorn is a legendary brand says new Acorn:

I suppose we shouldn't be surprised at this; the Commodore brand has been sold, used and abused by PC box-shifters, so why not Acorn? I find it difficult to muster the same sense of outrage that others evidently feel, but perhaps that's because I'm more cynical as I grow older.

Consumers may be naive enough to believe there is some link to the innovative Acorn we knew and loved, but those people probably wouldn't care anyway. It seems to me that the moral is not to put your faith blindly in brand names.

 is a RISC OS Userthesnark on 15/5/06 1:21AM
[ Reply | Permalink | Report ]

On A9home on sale from CJE Micros:

In reply to Loris:

I added an AIF header to make StrongED work and it really was very simple (my changes are now with the maintainer). The zero init code is not mandatory, and nor is the compression or relocation code.

.start MOV R0,R0 ; image is not compressed MOV R0,R0 ; image is not self-relocating MOV R0,R0 ; image has no debug/zero init code BL image_entry_point ; program should never return SWI "OS_Exit" ; last ditch exit in case of return EQUD image_entry_point-start ; read-only size (just this header) EQUD len_prg%-(image_entry_point-start) ; read-write size (remainder) EQUD 0 ; debug area size EQUD 0 ; zero initialisation size EQUD 0 ; debug type (no debugging data present) EQUD &8000 ; image base address EQUD 0 ; work space required EQUD 32 ; addressing mode and flags (32 bit compatible) EQUD &0 ; data base address EQUD 0 ; reserved word &38 EQUD 0 ; reserved word &3C MOV R0,R0 ; debug init instruction ; would be start of zero init code but we have none .image_entry_point ... rest of StrongED's source code. (len_prg% is the length of the whole output executable file, including this header)

Obviously this is not ideal because almost all of the code is in the read/write area, which will circumvent any memory protection that may be implemented in future. However a utility to produce AIF headers for legacy Absolute files would be very easy to write.

 is a RISC OS Userthesnark on 09/05/06 8:33PM
[ Reply | Permalink | Report ]

On A9home on sale from CJE Micros:

In reply to druck: As far back as October 1996 Acorn stated that "All Absolute files must have valid AIF headers. Absolute files without AIF headers and untyped files are deprecated." This was in application note 295 "Introduction to StrongARM and Programming Guidelines". Given that developers have had nearly TEN YEARS warning, I have little sympathy for those who did nothing about it!

Standardising on an executable file format that includes a header gives other benefits unrelated to 32 bit compatibility, such as: - Can ensure that enough application memory is allocated. - Can check the file is has not been truncated or extended (i.e. corrupted). - Can protect read-only areas of the image from alteration.

I hope that developers will embrace this as a positive step for the future of RISC OS.

 is a RISC OS Userthesnark on 08/05/06 6:17PM
[ Reply | Permalink | Report ]

On News in brief:

Or if they are clever then they might realise that it is a portmanteau word and therefore need not include the entirety of the original two words that have been blended together.

 is a RISC OS Userthesnark on 22/3/06 5:55PM
[ Reply | Permalink | Report ]

On News in brief:

I'm glad that Drobe picked up the story of the untimely death of Neil Raine.

I happened to notice an article about it in the Bristol edition of free newspaper 'Metro' yesterday. At the time I was on my way to a job interview and when the interviewer asked me how I first became interested in programming I produced the bit I had torn out of the newspaper and explained that he and other programmers from the early 8-bit days of Acorn had been inspirational. After all, I still remembered his name after all these years!

I loved Magic Mushrooms - it provided countless hours of fun for me and later my younger brother. Especially with the inclusion of a level editor the possibilities were almost endless.

There is also a thread about Neil's death on usenet: [link] /comp.sys.acorn.misc/browse _thread/thread/334a6abd7e406524 /535fc9344939aa2

Curious that none of the print media journalists seem to have picked up on the fact that he was a moderately well-known computer programmer. I can't help feeling that if he were a published author in the conventional sense then this would have been mentioned.

 is a RISC OS Userthesnark on 22/3/06 5:32PM
[ Reply | Permalink | Report ]

On BBC Micro ARM7 co-processor available:

The availability of an attractive new co-processor might persuade some people that have BBCs but don't currently use them (I, for one, am never getting rid of mine) to get them out of the attic/garage/cupboard.

 is a RISC OS Userthesnark on 9/3/06 1:40AM
[ Reply | Permalink | Report ]

On News in brief:

Again, I feel compelled point out that the name of my sound configuration application is 'Bazound' and not 'Bazsound'. Curiously, Googling for the latter does turn up my web site - presumably because of the two Drobe pages with that mis-spelling which link to it.

 is a RISC OS Userthesnark on 1/3/06 11:06AM
[ Reply | Permalink | Report ]

On South West 2006 theatre talks:


Unfortunately it is not always practical to provide bug fixes separately from other functionality that may since have been incorporated in a module. In fact the only way to be sure of this is to plan ahead and take a snapshot of the source code of at the time of each public release.

If your business depends on selling software then starting to give it away just because there were bugs in earlier versions (very likely not of your making) would be a recipe for disaster.

If you want one instance of free bug fixes having been provided then look no further than the Toolbox modules, which were bug-ridden at the time of their original release. Yet (almost) the latest versions are freely available to all RISC OS users, including Iyonix owners.

 is a RISC OS Userthesnark on 22/2/06 1:52PM
[ Reply | Permalink | Report ]

On News in brief:

Since EasySockets has been unavailable for many years, and Cretin doesn't come with a copy included, where are you supposed to get it?

I'm not criticising the authors, since the situation is not of their making, but it seems to me that all their potential users have a major problem and not just the ones using 32-bit RISC OS.

 is a RISC OS Userthesnark on 16/1/06 12:54PM
[ Reply | Permalink | Report ]

On Web gallery apps compared:

flypig: Having investigated further it appears that the Style Guide *is* still available - but only in PDF format as part of the Acorn C/C++ development suite. That will be cold comfort to many, since Acorn C/C++ currently costs the princely sum of 199 pounds (I don't know how I ever afforded that - I must have caught it on special offer or something).

How about we petition to get Castle to republish the Style Guide on the web in HTML form? After all I can't imagine anyone sane would pay 199 pounds for one book, and it would show support for software developers.

 is a RISC OS Userthesnark on 10/1/06 8:00PM
[ Reply | Permalink | Report ]

On Web gallery apps compared:

flyingpig: Although the Wimp's 'K' command in icon validation strings allows the old-style action of Return, this is presumably deprecated since it goes against the OS 3 style guide. In WinEd (popular template editor) the default validation string for a writable icon is instead "Pptr_write;Kta". This is also mentioned under 'Hints & tips' in the manual. Similarly, the Toolbox's writablefield gadget doesn't allow the old action of Return.

 is a RISC OS Userthesnark on 10/1/06 4:55PM
[ Reply | Permalink | Report ]

On Web gallery apps compared:

mrtd: Actually 'Enter > Activate' is the spawn of the RISC OS 3 Style Guide, published more than a decade ago. I quote from page 69: "Return - Begin a new line of text in an editor window. In a dialogue box, perform the default action." Also page 49: "The default action should be performed if the user presses Return." To rail against the standard now is pointless.

 is a RISC OS Userthesnark on 10/1/06 1:36PM
[ Reply | Permalink | Report ]

On Web gallery apps compared:

Having read druck's comment I downloaded WebGen2 and took it for a spin. It seems to be a very competent application that works with no fuss, but my goodness aspects of the user interface are a blast from the past!

The savebox has a 2D menu-type cream 'OK' button and a 'close' window tool rather than a 'Cancel' button. Dragging the directory icon uses a rotating dash-box (although I have solid icon drags enabled). In the main window, pressing ENTER moves the caret to the next writable field (should activate the default button). Pop-up menus do not appear aligned with the r.h.s. of the button that spawned them.

Am I one of only a small minority of people bothered by this kind of thing? I wonder whether it would help if the Style Guide were available online.

(DS1 - please don't take my criticisms personally - they aren't intended as such.)

 is a RISC OS Userthesnark on 10/1/06 10:31AM
[ Reply | Permalink | Report ]

On 2006 predictions:

druck: I don't feel your comments are entirely fair. I don't think anyone except for a very few people inside RISCOS Ltd know what the internal structure of the RISC OS 4 kernel is at the present time; e.g. how the source code has been adapted to support different hardware platforms.

The RISC OS 4 kernel has been divested of much baggage that arguably doesn't belong in a kernel; e.g. the OS_Convert SWIs. This is something that I applaud. Does it not count as restructuring?

Dynamic areas are only unsuitable for the 32 bit memory map when there are no sensible limits set on the amount of address space claimed. As far as I can tell, this is not the case for RISC OS 4 (most of the new dynamic areas appear to be limited to 16Mb or less, and there aren't an excessive number of them).

It would be fallacious to suggest that the HAL in RISC OS 5 removes the need for device drivers to be written for new hardware, as some people appear to believe. However the limited abstraction it provides is valuable so I hope eventually the OS 4 kernel will present a similar interface for the benefit of those writing driver modules.

Frankly I don't see how RISC OS 4 for Iyonix could work without providing some kind of implementation of the OS_Hardware SWI.

 is a RISC OS Userthesnark on 6/1/06 7:55PM
[ Reply | Permalink | Report ]

On Christmas tracker music reborn in MP3:

Is it just me, or is the first carols track good and the second one dreadful? Perhaps I was listening to it with a flea in my ear. Bah. Humbug!

 is a RISC OS Userthesnark on 2/12/05 7:15PM
[ Reply | Permalink | Report ]

On Software news:

They aren't particularly explicit images though, are they?

Nor should we be afraid to point out that the RISC OS Pinboard is compatible with the vast majority of Renee Zellweger images, as demonstrated by my (slightly outdated) Bazound screenshot.

 is a RISC OS Userthesnark on 1/11/05 2:04PM
[ Reply | Permalink | Report ]

On Software news:

Okay I know I'm a pedant, but it's actually 'Bazound' not 'Bazsound' (even though the latter may appear to make more sense).

 is a RISC OS Userthesnark on 1/11/05 1:10PM
[ Reply | Permalink | Report ]

On Personalised special offers for non-Select and Adjust users:

The fact that RISC OS 4.39 is available in ROM means that the API is no longer a 'moving target' - that argument is a now a red herring. However there have been changes to 'Select' APIs in the past - for example to usage of Wimp_Extend reason codes. IIRC this was mainly to avoid incompatibility with features implemented by Castle.

 is a RISC OS Userthesnark on 7/10/05 8:56PM
[ Reply | Permalink | Report ]

On Star Fighter upgrade in free for all:

'Wasted' is perhaps a little harsh. The fact is that the game runs fast enough without hardware acceleration and will presumably do so on all future RISC OS machines. Any change to the style of the graphics would require a considerable amount of extra work that would probably be better directed at a new game written in a higher level language.

 is a RISC OS Userthesnark on 4/10/05 11:22PM
[ Reply | Permalink | Report ]

On Star Fighter upgrade in free for all:

What about it? Very few people seem to have downloaded it from what I've seen of the web server logs.

 is a RISC OS Userthesnark on 4/10/05 9:04PM
[ Reply | Permalink | Report ]

On Star Fighter upgrade in free for all:

No - but nor was that the sole contributing factor. :-)

 is a RISC OS Userthesnark on 3/10/05 7:50PM
[ Reply | Permalink | Report ]

On Cocognut freely available finally:

I have never seen or heard of anyone use P2P software for anything other than illegally downloading and sharing music and films. If the recent court ruling does result in a blow to the P2P networks then I don't honestly have much sympathy with the users, who have clearly brought it upon themselves. Most people now seem to think that they have an inalienable right to free content via their internet connection (as if some proportion of the money they pay their ISP actually went to the copyright holders). One girl I spoke to the other day said to me that she needed the internet because she 'does a lot of downloading'. I can only speculate what she downloads, but 10 to 1 it is copyrighted music.

 is a RISC OS Userthesnark on 28/6/05 9:32AM
[ Reply | Permalink | Report ]

On STD defends A5 concept:

In reply to guestx:

I honestly don't understand why you are making such a big deal about some RISC OS applications requiring relocatable modules to handle aspects of the GUI. If, as I assume, you are refering to the Toolbox modules then bear in mind that these have been included in ROM since RISC OS 3.6.

 is a RISC OS Userthesnark on 05/08/04 1:12PM
[ Reply | Permalink | Report ]

Search the archives

Today's featured article

  • It's the Music, Man
    It comes from not-so-far away
     14 comments, latest by cynic on 3/2/05 7:59PM. Published: 18 Aug 2004

  • Random article

  • Bug fixed compiler claim disputed
    Rewind that spin, say developers
     20 comments, latest by hEgelia on 11/5/05 4:30PM. Published: 9 May 2005

  • Useful links

    News and media:

    Top developers:
    RISCOS LtdRISC OS OpenMW SoftwareR-CompAdvantage SixVirtualAcorn

    CJE MicrosAPDLCastlea4X-AmpleLiquid SiliconWebmonster


    RISCOS.org.ukRISCOS.orgRISCOS.infoFilebaseChris Why's Acorn/RISC OS collectionNetSurf

    Non-RISC OS:
    The RegisterThe InquirerApple InsiderBBC NewsSky NewsGoogle Newsxkcddiodesign

    © 1999-2009 The Drobe Team. Some rights reserved, click here for more information
    Powered by MiniDrobeCMS, based on J4U | Statistics
    "We incurred the wrath of Chris Williams, the main journalist at Drobe, who told us to 'Take our filthy spam and shove it where the sun doesn't shine'"
    Page generated in 0.4187 seconds.