Uwe Stöhr wrote:
The problem is that you always did your own thing with the installer. I
have never had a chance to contribute or discuss with you before you do
a change.
I always ask the developers for comments when I add new features (other
than NSIS code optimization and things like that).
What I want to try is to make this a team project with multiple
maintainers. That is, to have a single code base we can both work on.
The problems you mentioned regarding PDF viewing have been solved
Good to hear, but I've reported this to you several times before and you
didn't believe me that this was a real problem. Am I nevertheless
allowed to use your fixed PDF-update method also for my installer as
workaround wit the problems on Vista?
I've never seen anyone who has reproduced any issue with notebook
standby due checking for file modifications. I actually think this
information is retrieved from the system cache without the hard drive
having to spin up. But nevertheless I have changed the method because
you requested it.
Of course you're free to use the PDF viewing for your installer as well
to solve the problems you're having with Vista. It will also solve the
file locking problems of your current implementation.
Actually I think it would be very good if we would use the same
additional applications. Maybe you can use my launcher as well, it
captures the debug output while LyX is running and shows that in case of
a crash, which in my opinion is a nice feature.
and the installer now also runs the configure script during
installation, so MiKTeX won't have to install its packages when LyX is
started for the first time.
But then MiKTeX will install the packages and this is the intention -
the user should have a full featured LaTeX system.
Yes, that's what I mean.
A number of nice new features, such as automatic conversion of
metafiles, have also been added.
This is not installer specific, or have I misread the SVN commits?
A virtual Postscript printer and a conversion application are installed
to do the conversion, so the installer does need to handle this. This
has been discussed on the devel list recently.
Joost
