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

["Paolo Cignoni" <cignoni@gmail.com>]

Dear all,

we are going to release the v1.1.1 of meshlab
and i have arranged the source with hopefully all the issues that you
have raised.

Before releasing officially , could you check that the following sources are ok?

http://vcg.isti.cnr.it/~cignoni/meshlab_20080308.tgz

If someone does not want the automatic checking for new releases of
the software
(e.g. the feature that would imply phoning home)
it is sufficient to define the symbol __DISABLE_AUTO_STATS__ during
the compilation

the automatic checkForUpdates call is guarded in the following way:

#if not defined(__DISABLE_AUTO_STATS__)
		checkForUpdates(false);
#endif		

Let me know for any compilation problem or other issues. I will try to
patch them.

Cheers
P.




On Wed, Feb 27, 2008 at 3:15 AM, Ian Jackson
<ian@davenant.greenend.org.uk> wrote:
> Paolo Cignoni writes ("Re: Bug#426581: meshlab - anyone still working on this"):
>
> > We use QT with QSettings mechanism for saving config files in a portable way
>
>  Can these files be written other than by Qt ?  Our configuration
>  management systems often need to write to configuration in situations
>  where the application in question is not available.  Often there will
>  not be a graphical display and sometimes not even a user to interact
>  with (eg, preloading for automated operating system installs).
>
>
>  > (i would like to avoid to put any OS specific code inside meshlab)
>
>  I understand that view.
>
>  If you make a hook that we can use to control the behaviour, we can
>  happily add any necessary Debian-specific code to our version.
>
>
>  > 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)
>
>  I think this isn't the right answer for Debian.  We wouldn't want it
>  popping up its own dialogues.  But it sounds like it would provide a
>  place for us to plumb in our own configuration.  So if you do it that
>  way then that's fine by us but we will adjust the configuration
>  arrangements a bit for our users.  I hope that's OK with you.
>
>  The beauty of Free Software is that we can all have the version we
>  want.
>
>  Regards,
>  Ian.
>