ResEdit missing from binary download

I couldn’t find the ResEdit application in the binary-two.zip download. Is it there? Or am I just looking in the wrong location.

Yes, same problem here. I can’t find it.

I’m no expert C programmer, but I am good at designing simple and clean GUIs and am keen to improve the look and feel of RO as much as possible, as I feel a lot of stuff is mis-aligned and disjointed at present. How do I go about submitting my changes?

If there are any coders who would like to work in tandem in improving some apps then please get in touch with me at nytrex2001 @ yahoo . co. uk

cheers nx

Alan B: I’m told the current version doesn’t actually build. It’s on our to-do list.

Alan R: you’ll find template, message and resources files in the “Resources” subdirectory of each source component, and often in further subdirectories depending upon language or other build variant. They get gathered together to go in ResourceFS (as part of the Messages module) during the ROM build process. If you fancy fixing them, you can submit them to the same address as code submissions, that is code@riscosopen.org.

Ben, thanks for the head up. I’ll have a look later.

Also, how would one go about adding some sprites to the main wimp pool? ie radiooff, radioon, optoff opton.

I would like to add a few new sprites as standard so I can use them across multiple applications.

Thanks

The Sprites files in RiscOS/Sources/Desktop/Wimp/Resources are the ones that get built into the Wimp’s ROM sprite pool. Since this takes up a substantial chunk of a ROM image, adding new sprites to it has been deprecated for some time (apart from the fact that if you write applications that rely on new ROM sprites, they won’t work on old OS versions). You may have noticed that on the Iyonix, the ROM sprites are 4-bpp, and a larger range of sprites, all in 8-bpp, are loaded from disc during the boot process; this is due to ROM size constraints. The disc version of the sprites are not yet under CVS control TTBOMK.

If you’re interested in producing alternative themes, it’s worth pointing out two mechanisms that may be useful. One is the UserIF build environment variable, set in your Env file (which corresponds to the Environment menu from !Builder) which controls which subdirectory of Wimp/Resources/<locale> is built into the ROM. There have been many of these – the embedded ones had to be withheld from release, but you’ll see that the published sources include Morris (RISC OS 3.71), Ursula (RISC OS 4.00), RO400 (RISC OS 4.02) and Iyonix (RISC OS 5) UserIF subdirectories. The other mechanism is the Wimp$IconTheme system variable which is used by the Wimp (for *IconSprites) and the Toolbox (for Toolbox sprites files), and is intended to allow applications to ship with alternative icon sets to fit in with the system theme. This hasn’t been widely publicised and consequently hasn’t been much used, but it’s there in the sources for all to see now. There’s no convention yet as to how it’s used. Historic filename length limitations might favour short strings, maybe even single characters, but there’s also an argument for using the same namespace as the UserIF variable. May I invite discussion from the floor?

Remember that any new sprites in the Wimp sprite pool still need to be reserved using the usual allocate addresses at riscos.com or iyonix.com.

Thanks for your lengthy and informative response. Very interesting (and useful to know).

I am interested in updating OS with some new sprites so that we can start to include some more conventional user interface controls such as dropdown boxes and the alike. I firmly believe that the Style Guide should be updated to reflect the needs of the users. Things have moved on a long way since Acorn wrote the Style guides.

I am not looking to replace the objects we already have – merely to expand the range. And then at some point in the future perhaps using these new controls where applicable in the OS and apps.

I will request some sprite names so I can start moving this forward. I love GUIs and I love designing them. And with RO - there is so much scope for improvement. But I need to start small.

Alan B: I’m told the current version doesn’t actually build. It’s on our to-do list.

Builds okay here with Norcroft CC 5.54 [04 Apr 2003]

Go to RiscOS.Sources.Apps.Toolbox.ResEd run !Mk and it will be placed in RiscOS.Sources.Apps.Toolbox.ResEd.Export

Yes. There is some magic in the !Mk file which means that you can’t build it using !Builder (which can only do the stuff which is directly in the Makefile). I’m saying this from what I’ve been told as I’ve not sat down and looked at it yet… Should be easy to fix when I have a moment.

It appears that the applications for creating Windows, Menus and Misc in the CSE subdirectory haven’t had there !RunImages built.

This was an issue when we first put stuff out. I’m sure it was fixed a few weeks ago. Try downloading the pre-built binaries from our site and let me know if you’re still missing those !RunImage files.

All the !RumImages are included now. I had missed the fact that another drop of the binaries had been done after the one that added the !RunImage for ResEdit itself.

OK. For minor releases and updates, I won’t be trumpeting any press releases or anything so just take a look at our downloads pages every now and then. Maybe I’ll put an article in the forums at the same time (if I remember).