All customised code is stored in a farcry project ie. the actual application you are writing. farcry_core always remains untouched.
by untouched you mean untouched by joe blow on the street? i assume somebody must be fixing/improving things? cheapest way is to handle the "core admin" rb the same way. i'm not sure over-riding these willy-nilly would be a good idea--a brute for instance, swapping the translations for confirm & cancel could be disastrous.
If RBs were to follow a similar vein we'd be effectively combining the farcry project local RB with the core RB on application initialisation.
i guess users could split off their mutant rb into ones *seperate* from the "core admin" & do whatever they wanted w/them. they'd have to handle the init themselves (maybe by simply appending their rb to the "core admin" rb structures if that were appropriate). all the plumbing is there already so it shouldn't be a big deal.
I'm not sure I see an easy way out of this. Unless we try and rationalise the lables in the RB to provide folk with a generic set they can use in their own apps... and have folks lobby for additions to the core RB.
uh, i thought that's what we did already? all the rb are used in the farcry_core if i recall correctly.
Docs would be great :) Should I publish on the site the doc you sent through for translators?
up to you.
--- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
