[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#426581: meshlab - anyone still working on this



On Tue, Feb 26, 2008 at 8:01 PM, Ian Jackson
<ian@davenant.greenend.org.uk> wrote:
> Paolo Cignoni writes ("Re: Bug#426581: meshlab - anyone still working on this"):
>
> > So adding a compile option disabling the default home phoning is
>  > probably the best idea.
>
>  That would certainly suffice.
>
Ok, i'll do it in the next days.


>
>  >  At least can I ask for enabling at the first run?
>  > Or even this is evil? :)
>
>  I think that would be fine from an ethical point of view.
>
>  But in Debian we already have established mechanisms for the
>  configuration of software, and it would be good to be able to use
>  those.
>
>  So rather than writing code in meshlab to put up a dialogue, I would
>  suggest code in meshlab to read a configuration file or two.  The
>  Debian maintainers would arrange for these files to contain the right
>  answers, according to the questions asked of the system administrator
>  and/or user.

We use QT with QSettings mechanism for saving config files in a portable way
(i would like to avoid to put any OS specific code inside meshlab)

The mechanism i am going to implement is the following
An asking dialog popup at first run.
The result of the dialog will be saved in a persistent place using qsettings.
If this value is already set No dialog will never popup (so an
installer can set these values before first run)

Hopefully this should suffice :)

P.


Reply to: