[Paraview] registry file?

Berk Geveci berk.geveci at kitware.com
Wed Jun 4 15:30:39 EDT 2008


I agree. I will make a note to add this to the wiki.

-berk

On Wed, Jun 4, 2008 at 2:15 PM, John Doe <ufnoise at gmail.com> wrote:
> .config is not the standard for Linux.  That freedesktop standard
> someone mentioned isn't yet a common standard.  I have many more
> hidden files in my home directory than in my .config directory:
>
> I wouldn't object to keeping it in the .config directory, as long as
> it is documented where the registry files are located.
>
> Juan
>
>
> On Wed, Jun 4, 2008 at 12:36 PM, Mike Jackson <imikejackson at gmail.com> wrote:
>> <squeaky wheel gets the oil>
>>  I'll re-chime against that idea.
>> </squeaky wheel gets the oil>
>>
>> If you make this a compile-time option then the support costs go up because
>> you then have to know how ParaView was compiled in order to attempt to help
>> someone.
>>
>> Basically I am voting to change this just on OS X. On windows, the registry
>> will not work and on Linux the .config seems to be the "standard". So we are
>> left with just 2 places to look depending on Operating system.
>>
>> Mike
>>
>> On Jun 4, 2008, at 1:23 PM, John Biddiscombe wrote:
>>
>>>
>>>> I could chime in but it looks like everyone covered the issues :)
>>>>
>>> I'd like to vote in favour of $HOME/.config - one place on all systems is
>>> better (for me) and much easier to edit/wipe than a registry etc...by all
>>> means add QSettings::NativeFormat as an option (compile time?), but I vote
>>> to keep the existing method as default
>>>
>>> JB
>>>
>>
>> _______________________________________________
>> ParaView mailing list
>> ParaView at paraview.org
>> http://www.paraview.org/mailman/listinfo/paraview
>>
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview
>


More information about the ParaView mailing list