[GSOC] about:config utility - Weekly Report #4

classic Classic list List threaded Threaded
3 messages Options
Efe Gürkan YALAMAN Efe Gürkan YALAMAN
Reply | Threaded
Open this post in threaded view
|

[GSOC] about:config utility - Weekly Report #4

Hi,

This week I only did debugging. Configuration management code is a little complicated. I could handle it mostly. Learned a lot about about configuration process now. I know where is the config codes mostly. But I don't know how to use it. Also there was no good internet access this week. I couldn't asked as much information this week.

As I understand:
-configmgr/source stores codes for taking settings from configxmls,
-unotools/source/config stores configmgr, and other cxx files. They handle settings to use on other parts of the code.
-configmgr and configItem are important for using the config files in other files.

I will take save options for the first. There are some questions for this week I will deal:
-What is XNameAccess and why we use it? (It is not quite important I think but I may need it.)
-Why some cxx files have cfgmgr.cxx in includes and others don't? What is the difference of them?
-What "notify" methods do and how this aspects the behavior of program?
-Should I need new cxx files for every single options group? Or how much I need them in case of ?
-Which part of code I should use for my project? (I think I need to look around configmgr.cxx on /unotools)
-How options dialog saves new options? Which part of the code it uses? (I assume it is same file which loades the settings. And probably I should really look into configmgr.cxx)

Best,

--
Efe Gürkan YALAMAN
http://about.me/efegurkan

_______________________________________________
LibreOffice mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/libreoffice
Thorsten Behrens Thorsten Behrens
Reply | Threaded
Open this post in threaded view
|

Re: [GSOC] about:config utility - Weekly Report #4

Hi Efe,

you wrote:
> -configmgr/source stores codes for taking settings from configxmls,
>
yup

> -unotools/source/config stores configmgr, and other cxx files. They handle
> settings to use on other parts of the code.
>
they are basically convenience wrappers, yep

> -configmgr and configItem are important for using the config files in other
> files.
>
not really - as mentioned on irc, using the plain uno api should work
as well

> -What is XNameAccess and why we use it? (It is not quite important I think
> but I may need it.)
> -Why some cxx files have cfgmgr.cxx in includes and others don't? What is
> the difference of them?
> -What "notify" methods do and how this aspects the behavior of program?
> -Should I need new cxx files for every single options group? Or how much I
> need them in case of ?
> -Which part of code I should use for my project? (I think I need to look
> around configmgr.cxx on /unotools)
> -How options dialog saves new options? Which part of the code it uses? (I
> assume it is same file which loades the settings. And probably I should
> really look into configmgr.cxx)
>
I think these are mostly distractions - picking the 'new cxx files for
every option group' question, I think there lies madness; what we'd
want is a generic piece of code that handles ~all current and future
settings. Writing dedicated code for new options is exactly not was is
wanted here.

Sorry for the lag in responding - can we sit down today (irc, hangout,
phone) and hash this out quickly please?

Cheers,

-- Thorsten

_______________________________________________
LibreOffice mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/libreoffice

signature.asc (853 bytes) Download Attachment
sberg sberg
Reply | Threaded
Open this post in threaded view
|

Re: [GSOC] about:config utility - Weekly Report #4

On 07/19/2013 03:45 PM, Thorsten Behrens wrote:

>> -unotools/source/config stores configmgr, and other cxx files. They handle
>> settings to use on other parts of the code.
>>
> they are basically convenience wrappers, yep
>
>> -configmgr and configItem are important for using the config files in other
>> files.
>>
> not really - as mentioned on irc, using the plain uno api should work
> as well

Just for completeness' sake (and I guess it is rather irrelevant here
where you want to use a generic approach anyway), note that there are
C++ helper headers generated into
workdir/*/CustomTarget/officecfg/registry/officecfg/...hxx for all the
officecfg/registry/schema/org/openoffice/...xcs files, allowing for
type-safe access to all the statically-known configuration items.  (One
intent of introducing them was to get rid of any of those wrapper
facilities, cf. EasyHack
<https://bugs.freedesktop.org/show_bug.cgi?id=46037> "Clean up uses of
comphelper/configurationhelper.hxx.")

Stephan
_______________________________________________
LibreOffice mailing list
[hidden email]
http://lists.freedesktop.org/mailman/listinfo/libreoffice