Incorporate “ResFind” functionality into OS
6 posts, 5 voices
Andrew Hodgkinson (6)
465 posts
|
This topic has been imported from the old forum. Due to its use of fixed format text, you may need to make your browser view wider in order to see posts with the correct layout. |
Adam (47)
40 posts
|
ResFind is a small utility which interogates the OS to determine what territory it is in, then sets a path system variable pointing to the appropriate resources for an app to use. E.g. an app lays out its structure like this: !AppName Resources UK France Germany Etc. Messages files, templates, help files etc are placed in one of the territory directories. If the app finds itself in, say, Germany, the system variable (e.g. AppNameRes$Path) is set up to include “!AppName.Resources” (for territory independent resources) and “!AppName.Resources.Germany”. This means that script files and the actual program only ever need to refer to one location (AppNameRes:). Adam http://www.gag.de/software/ResFind/ |
Steve Revill (20)
1361 posts
|
Adam (47) wrote: > ResFind is a small utility which interogates the OS to determine what > territory it is in, then sets a path system variable pointing to the > appropriate resources for an app to use. Although that could be something that the BootCommands module (or similar) could provide, there are lots of other things which do the same job - e.g. LocaleRes on the 7th software site. I'd be happy to donate LocaleRes to the shared source project so that it could live in !Boot.Library and then all apps could use it if they so wished. Or the ResFind author could do the same. An alternative would be to ensure that a system variable is set to the current locale (e.g. Sys$Locale "UK"). This could be implemented as a code variable and kept up to date by the Territory module. Applications would just have to create a path like: Set MyApp$Path <myapp>.Resources.<sys>.,<myapp>.Resources.UK. Either way, it's a nice easy one for the wish list! :) |
|
Andrew Hodgkinson (6)
465 posts
|
Steve Revill (20) wrote: > Either way, it's a nice easy one for the wish list! :) Agreed. We should start following these in the bug (feature) tracker really; a summary and link to the relevant forum thread should be good enough. I'm not sure what sort of procedure we should follow here. If every feature request goes in, there'd just be this huge mess of random features with no indication of popularity; but we obviously can't have (say) someone at ROOL nodding wisely and only entering features that they deem worthy ;-) Maybe we dump things into the bug tracker anyway and see how long those feature requests hang around before someone (anyone) gets around to an implementation. If something has been there for "some length of time" (6 months? 12? 24?) perhaps it's showing a need for a forum thread to ask whether or not to close the ticket with "won't fix" or leave it open. Anyone have any other ideas? |
Weiss Niklaus (109)
2 posts
|
Steve Revill (20) wrote: > > An alternative would be to ensure that a system variable is set to the > current locale (e.g. Sys$Locale "UK"). This could be implemented as a > code variable and kept up to date by the Territory module. Applications > would just have to create a path like: > > Set MyApp$Path > <myapp>.Resources.<sys>.,<myapp>.Resources.UK. > > Either way, it's a nice easy one for the wish list! :) My desktop calculator "TransCalc" and my multi-tasking debugger "DeskDebug" even contain their own tools to find the suitable resources for the active territory. My tools even know, that the territory 35 (Switzerland) can use the same resources as territory 7 (Germany), because in a big part of Switzerland the German language is used. However, the French and Italian languages are important too here, and they would even need other keyboard layouts. There should be a standard, how to find the suitable resources for a territory, similar as it already exists for the toolbox. |
Julian Zimmerle (136)
29 posts
|
I am German but live in New Zealand. One thing I really like about MacOS X is that I can set the interface language to German, but things like the decimal point and currency system to the way they are used in NZ. My step-dad is English and lives in Germany. Similar situation there. He uses RISC OS on a daily basis. Luckily Detlef Thielsch created a territory module a few years ago, wich only provided the basic settings for Germany, without the interface translations. But it would be really much better, if one could simply set each localisation option individually, like on most other OS. |
