Dear Michael,
You wrote:
> I think we should replace config, cfg, m_cfg, configq4, etc. with
> settings instead, so help make it clear that this is QSettings
> and not KConfig.
I like 'settings' that is much clearer and also allows me to leave the
arguments in the function definition/declaration (temporary).
You are spot on about how KConfig ands QSettings work--there is no need to pass
them as arguments now.
I'm happy to take that on, or if your looking for a task, Michael, we could
work in tandem on this.
I was hoping for the gravy part of renaming to 'settings' cleaning up the
function body code and matching .startGroup /.endGroup--since that was what
spawned this talk and I've already done some prep work for that part of the
task. I was hoping you could take on the argument modifications and the fall
out from that. That is if you want to take on the task. I'm happy to keep it
all to myself.
I want to get these issues clarified first before proceeding further. I know
Emanuel had already tried to off-load (not meant in a bad way) this matching
thing. So I don't see a conflict there.
Emanuel's input would be nice. But I'd like to get to coding while its hot on
my plate and I have time to do it right.
Sincerely,
Julie S.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
