On Sun, May 1, 2011 at 10:49 PM, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote: > Le 30/04/11 15:38, Richard Heck a écrit : >>> >>> Would it be difficult to automate this? I was thinking that the best >>> solution to the problem, from a LyX point of view, was to provide---in >>> addition to the current message---a button that would download most >>> recent lyx2lyx from SVN or trac and place it to the appropriate >>> location in the profile folder. >>> >> Yes, though it seems kind of dangerous to download python scripts from >> the web and then offer to run them. > > IMO the problem is more what happens when someone hits this button with LyX > version 2.0 and current version is 4.1. Are we sure we have kept the same > interface to lyx2lyx? Are we going to be bound by that forever? > Not necessarily. By some estimates 3.0 is in about 10 years time, so 4.1 should be in the realm of the intangible long-term future. :)
However, even if the lyx2lyx interface changes in the medium-term future, this doesn't mean that having a 'Download' button would necessarily cause problems. What I mean is that we will be controlling the file being downloaded---a recent, signed lyx2lyx script through SSL. If significant changes occur and 2.0 is no longer compatible with lyx3lyx or lyx4lyx, we could spot this from the web query and simply provide an explanatory pop-up message that the two are incompatible and urge the user to upgrade LyX, instead of the (normal) confirmation message that lyx2lyx was successfully downloaded and installed in user's profile dir. > It looks like a complicated solution for a not so frequent problem. Another > solution would be an online (web based) LyX conversion script. > The solution would indeed complicate things from our side, but it could save inexperienced users---and experienced users collaborating with inexperienced ones---a lot of trouble. Cheers Liviu
