[Paraview] registry file?

[Mike Jackson]

Ok, I can see that thought process, but users of each OS are used to  
the way _their_ Operating system works. Having their preference file  
located in a "non-standard" location is a "surprise" to the user and  
does not make for a nice user experience. Having said that I do agree  
that if an operating system's preference system can not handle the  
data that is needed to be stored then that needs to be changed, but  
why punish all operating systems for one's failure? As a "normal" OS  
X user that is using ParaView, I would _expect_ my settings to be  
stored in ~/Library/Preferences or _Maybe_ ~/Library/ParaView or  
_possibly_ ~/Library/Application Support but NOT in .config/blah/blah/ 
blah. So the old argument comes up, what is "consistent". Should the  
app adapt to the platform or should the user adapt to the App? I  
would vote for the app to adapt to the platform. The support issues  
would be _less_ because users can help themselves because they _know_  
instinctively where to look for application settings.

I'll leave it alone as there is nothing more I can say or debate.

Everyone have a great day. :-)

Peace.
Mike Jackson


On Jun 4, 2008, at 10:47 AM, Shead, Timothy wrote:

> On 6/4/08 7:17 AM, "Berk Geveci" <berk.geveci at kitware.com> wrote:
>
> The main issue was that the "native" format on Windows (the  
> registry) has
> some really draconian limitations on the sizes and numbers of keys,  
> which
> was causing problems.  Since we were forcing the use of the "ini"  
> format on
> one platform, it seemed to make sense to be consistent on all  
> platforms.
>
>> I can't remember the reason (Clint will probably chime in) but there
>> was one. We started using the native format and then we switched.
>>
>> On Wed, Jun 4, 2008 at 8:46 AM, Mike Jackson  
>> <imikejackson at gmail.com> wrote:
>>> Why are you using "iniFormat" and NOT QSettings::NativeFormat? It  
>>> is VERY
>>> un-natural for OS X users to go looking for .config in their home  
>>> directory.
>>> If you use QSettings::NativeFormat each platform will get their own
>>> "correct" usage. One small change and LOTS of people happy.
>>>
>>> Unless of course there is some odd reason why ParaView can not use
>>> QSettings::NativeFormat and _must_ use QSettings::IniFormat?
>>>
>>> --
>>> Mike Jackson   Senior Research Engineer
>>> Innovative Management & Technology Services
>>>
>>>
>>> On Jun 4, 2008, at 7:02 AM, Utkarsh Ayachit wrote:
>>>
>>>> Take a look at:
>>>> http://doc.trolltech.com/4.3/qsettings.html
>>>>
>>>> We use iniFormat settings files in ParaView.
>>>>
>>>> Utkarsh
>>>>
>>>> John Doe wrote:
>>>>>
>>>>> It appears to be in the .config directory.  Shold I file a bug  
>>>>> report
>>>>> to have it moved to a more obvious location, such as perhaps a
>>>>> .Paraview directory?  When was this standard for configuration  
>>>>> files
>>>>> invented?  I wasted an hour trying to find it.
>>>>> Juan
>>>>> On Tue, Jun 3, 2008 at 10:36 PM, John Doe <ufnoise at gmail.com>  
>>>>> wrote:
>>>>>>
>>>>>> Where do I find the registry file? Every time I start paraview  
>>>>>> it is
>>>>>> always in the same unusable state as before.  Using the "-dr"  
>>>>>> option
>>>>>> makes the problem go away.
>
> --
> Timothy M. Shead
> Scalable Analytics & Visualization (1424)
> Sandia National Laboratories
> 505-284-0139
>
>
>