Re: [GnomeMeeting-devel-list] Reorganizing gconf keys, please comment
- From: Miguel Rodríguez <Miguel Rodriguez det uvigo es>
- To: gnomemeeting-devel-list gnome org
- Subject: Re: [GnomeMeeting-devel-list] Reorganizing gconf keys, please comment
- Date: Wed, 15 Oct 2003 09:35:33 +0200
I have mixed feelings about this. On the one hand the current structure
is a mess and could get some cleaning. But cleaning it means one of
this:
1) losing stored preferences for a lot of people
2) being unable to sharestored preferences between different
gnomemeeting versions[1]
3) doing a lot of complicated code to avoid 1), or 2). (So, mess the
code so that you have a beautiful structure).
I'm not sure if it's worth the pain, but it is now or never (before we
reach 1.0).
[1] This happens if you have your HOME in a NFS server but different
gnomemeeting versions installed in different computers.
El mar, 14-10-2003 a las 23:38, Damien Sandras escribió:
> Hi all,
>
> I think that it becomes imperative to reorganize the gconf key
> structure. It is a lot of work, unfortunately, and doesn't bring any new
> to the GUI, but it can potentially break everything.
>
> However, I think that it is required because the current structure is
> too big.
>
> Please open gconf-editor ;)
>
>
> I think I will reorganize things this way :
>
> * protocols->h323->gatekeeper->registering_method
> ->alias
> ->password
>
> ->gatekeeper_host
> ->gatekeeper_id
> ->advanced ->enable_h245_tunneling
>
> ->enable_fast_start
>
> ->user_input_capabilities
> ->ldap->usual keys
> * general->UI->auto_clear_text_chat + the current show_ keys
> ->personal_data
> ->history
> ->video_display
> * audio->devices
> ->codecs
>
> * video->devices
> ->codecs
>
> * nat->ports
> ->ip_translation->enable_ip_translation
> ->enable_ip_checking
> ->public_ip
>
> Any comments about this structure?
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]