I may be about to say something that is not the case, but to me it's a depressing task to contemplate write a substantial application for any platform from scratch. It much easier to get going if you've got the essence of an idea in the form of a piece of working code that can be experimented with and developed.
Personally, I keep running into old but very good RISC OS software that does not run on up to date versions of RISC OS. The reasons for it not running are probably, in some cases, trivial. Many software authors have moved on, died or simply lost interest or motivation. Often, a perfectly aimiable original author no longer has the source code because the machine they wrote the software on was dumped/sold or they've lost the source when a Hard Drive crashed etc, etc. Without the source code it's close to impossible to do anything to rescue such software. It's particularly frustrating - hence my admittedly terse earlier post - when entire regions of functionality are lost. It's not just the programs in themselves, it's the potential they carried to be picked up by someone fresh and developed further.
My point was that software authors ought to have an awareness of the need to future proof their efforts as much as possible along such lines. I didn't expect anyone to find this controversial as it's the whole phisosophy behind open source which I hope, ultimately, is direction RISC OS will drift in, although if a few folk make a living out of it along the way, that's fine by me.
Flicker was written because I was given permission by Bob Seago to play around with what I thought was an inspiringly clever set of routines. It's coded with programming notes throughtout so that anyone interested can see how it does what it does. This includes things like responding to a double click on an application's file type, setting up simple wimp menus, setting up a wimp volume control, and grouped radio icons, quite aside from all of the sprite handling routines. So anyone wanting any piece of it can grab that part of it to recycle and reuse.
Andre Timmerman gave permission for it to use his TimPlayer sound module. So if you want to know how to add sound to your app in a way that works on Iyonix, Risc os 4 & 6, and Virtual Acorn, the gist of it is there - although there is still an "input focus" issue that needs to be coded up.
My particular frustration today revolves around trying to find something with which to write (using RISC OS) the "Tracker" files that Flicker plays as a soundtrack. Correct me if I'm wrong, but is there now a single tracker music making program that works on all modern versions of RISC OS ? Is there a tracker music making program that works on *any* modern version of RISC OS ?
There seem to be around eight old tracker music making programs - non with source. There is nothing upon which to build. It's depressing.