Le 10 mai 06 à 17:57, Yen-Ju Chen a écrit :
I notice there are several system-related patches for
EtoileMenuServer.
I think we will have more and more these stuffs.
Is it possible that we can centralized it in a single library or
bundle ?
Yes, I think that something we should have by relying on defaults.
Just query NSUserDefaults for +standardSystemDefaults, new factory
method which returns a custom class cluster object to handle system
related defaults (this class could be provided through a bundle).
Then when you call objectForKey: @"CPUName", the value is computed on
the fly. Finally the value can be obtained by passing a request to
System Tools Backend, in fact it should be the most common way to
handle -objectForKey: and -setObject: forKey: calls.
For example, if we have an etoile.make somewhere which containing
cflags and libs of most common libraries,
all applications don't need to specify the location of these libraries
depending on the OS.
(I suppose, this isn't strictly related to the first question ?)
Yes, would be better. It's something I'm thinking about anyway
because I have to fix the build system (not supporting single module
compilation at this time).
Same applies to the information EtoileMenuServer are using now.
I know there is a SystemToolBackends.
Maybe we can get it to work.
It works. Just need to write to map its XML schema to our own NSUser/
SystemDefaults keys.
By the way, pehaps it's better to have a simple NSUserDefaults
subclass called NSSystemDefaults.
I have written such basic system defaults support, I'm not sure I can
access this code right now, because iirc it is located on my PC
missing a working power supply for now.
Quentin.
--
Quentin Mathé
[EMAIL PROTECTED]
_______________________________________________
Etoile-discuss mailing list
[email protected]
https://mail.gna.org/listinfo/etoile-discuss
