User forums > General (but related to Code::Blocks)

Where to store the configuration of Code::Blocks

<< < (6/7) > >>

AkiraDev:
Hmmm...

Just HOW complicated exactly (= how many hours work) would it be to make a specialization of wxConfigBase to a new wxXMLConfig class?

Were that the case, it would be fairly simple to preserve a lot of Code::Blocks code.

EDIT: OK, I got your point in the last paragraph of your post, nevermind.

rickg22:
I think it would be wiser to keep the current model until all the pros and cons are discussed (this is, _AFTER_ 1.0).

Something very important: If it ain't broke, don't fix it!

The config manager has been the only module that hasn't given us trouble in the past (with the exception, of course, of those cases where HOME=%USERPROFILE%, but I'm sure that can be fixed somehow). I'm happy as it is.

takeshimiya:
Ok, I can suppose then that BEFORE C::B 1.0 we can have the configuration stored in INI files.  :)
And AFTER C::B 1.0 we can do the XML configuration stuff, right?

thomas:
That is a one-line code change, sounds like a good idea.

I will play with it anyway, and if it turns out to be stable before 1.0 and if it finds unanimous acceptance, you can still incorporate it, should not need too many changes really.

sushi_cw:
I don't care if it's INF, XML or whatever, just not the registry. :) Putting everything in %appdata%/codeblocks seems like a perfect idea to me.

Navigation

[0] Message Index

[#] Next page

[*] Previous page