AdamB,
cheers for the reply, before attempting to write any rubies myself I'm trying to analyze what I can and can't see using Xcode and Console (in combination)
it appears (to me) that if a ruby or it's loader.rb and subfolder reside in SU Plugin folder they will be initiated on start-up whether required or not and generate error reports if they have a prerequisite for "xxx" which is not available/selected prior to start-up(which, of course it's not)
This type of error does't seem to be generated for rubies that are placed inside their own sub-folder with a non-automatic step in their path i.e. rudy console, or a separate toolbar ruby that has it's own sub-folder that contains a on/off-button for an in-folder loader ruby that opens/closes the desired ruby.
Not even sure I follow that myself, but main lightup ruby (for example) appears to have to a degree of separation (for activation at least) and cannot generate errors and cause conflicts, unless it's actually being used and there's a problem.
What I think I'm after is a way to active/de-active any ruby, from within SU using a single(per ruby) external action.
Do you know if that's even realistic en-mass?
Which Xcode template is appropriate for SU rubies? or is there an importable or custom layout that's preferable?
cheers
john