Re: Why all the different string types?

Guy,

By now I have made up my mind and I am altering the code to use std::
string as we speak. That will eliminate needless implememntations of 
string functionality all other again at the price of writing some 
utility functions to make the std::string actually usefull ;)

Having that we can see what to do next. 

> Instead of having individual getters and setters for 
> each preference, there could be a single SetBoolean, 
> SetInteger and SetString; 

Current persistency implementation is not too bad actually. If we are 
going to use the "named" settings storage we will loose type safety. 
It is also quire error-prone as you are just one typo away from not 
getting what you want. It's also hard to track the changes in the 
names etc... 

But the most troublesome is that current implementation is deeply 
entrenched and works well with the code we have. It would be a huge 
task to change that now, not to mention that we need to migrate data 
from the old to the new storage format so we would have two systems 
operational. 

The idea of making settings more "local" so that MDI can be better 
supported is probably more realistic. 

Best Regards,
Jerzy







 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/cvsgui-dev/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/