Re: LyX 2.3.0 on Windows
On 19/05/2018 5:12 a.m., Richard Kimberly Heck wrote: On 05/18/2018 11:16 AM, Richard Kimberly Heck wrote: On 05/18/2018 04:32 AM, Andrew Parsloe wrote: On 18/05/2018 11:27 a.m., Richard Kimberly Heck wrote: I've fixed the problems reported by people who've tried the new installers. The question is how now to proceed. Note that these are questions for 2.3.0 (and probably 2.3.1, since I will turn my attention to that once this issue is resolved). Larger questions about how to proceed with the Windows installer can be deferred to 2.3.2 if not 2.4.0. It's my hope that we can find someone to take over building the installer, etc, before too long. I'm happy to do it for a bit So, questions. 1) Should we include any form of the 'update MiKTeX' code, with a dialog asking for permission to perform the update, or should we not do so? 2) Should we try to get wider testing of these new packages by advertising the putatively final version on the users' list before doing an official release? I have no strong opinion about (1), though I don't think it would be too difficult to include such a dialog. I gather that the risk is that updating LyX itself could trigger a partial update (due to packages being installed at compilation time) that will break MiKTeX. As Pavel said, the people this might affect seem to be only folks who did some kind of update between October and January, but who knows. The main issue would be getting translations of the message in the dialog. I guess I could write to the relevant folks and ask for quick responses. There's also Google, if all else fails. I suppose another option would be for me to contact the MiKTeX maintainer and see what they think. Regarding (2), I guess I am a bit nervous about these installers, since I have no idea what I'm doing, and we didn't get THAT much feedback from my previous messages. Riki I've run LyX-230-Installer-103.exe. It has installed and from a very first glance, LyX is displaying a couple of complex documents correctly. The only obvious thing at this stage is that the LyX icon (an irregular LyX in large blue type) is missing and a generic windows program icon has taken its place (see attached). I noticed that, but didn't realize what it was. I'll try to figure out what's wrong. By the way, do you know how to figure out where Windows is trying to find the icon? I've presumably changed something unknowingly about where it's being put. Riki I don't know where it hides although I see that the icon is attached to pdfview.exe in LyX 2.3/bin and to Uninstall-LyX.exe. (I notice there is lyx.png and lyx.svg in LyX 2.2/Resources/images but only lyx.png in LyX 2.3/Resources/images.) The windows generic icons are at %SystemRoot%\system32\SHELL32.dll (on right clicking on a shortcut, choosing properties and then Change Icon). Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Re: Error messages with lyx2.3
On Fri, May 18, 2018 at 06:40:00PM +0200, Jean-Marc Lasgouttes wrote:
> Le 16/05/2018 à 20:01, Enrico Forestieri a écrit :
> > On Wed, May 16, 2018 at 01:43:45PM -0400, Richard Kimberly Heck wrote:
> > > I think you are right that it is during metrics. Tracing some things,
> > > RenderGraphic::metrics seems to be responsible for starting the preview,
> > > and it gets called from InsetGraphics::metrics.
> > >
> > > But maybe it is as easy as expanding the cases for which we check in
> > > graphics::Loader::startLoading?
> >
> > I tried this but it doesn't seem to work (see preview3.diff). However,
> > the patch preview2.diff should accomplish the same goal and it seems
> > to work.
> >
>
> preview3.diff looks like the cleanest approach to me. I think it should go
> in.
Unfortunately, it does not work, as already said. It would have been
surprising if it had worked, though, as the added condition is already
catched by "pimpl_->status_ != WaitingToLoad".
Instead, the attached works for me. Anyway, all of this appears to be racy.
--
Enrico
diff --git a/src/graphics/GraphicsLoader.cpp b/src/graphics/GraphicsLoader.cpp
index 683f0925fc..c38761c85b 100644
--- a/src/graphics/GraphicsLoader.cpp
+++ b/src/graphics/GraphicsLoader.cpp
@@ -299,7 +299,8 @@ void Loader::reset(Params const & params) const
void Loader::startLoading() const
{
- if (pimpl_->status_ != WaitingToLoad || !pimpl_->cached_item_)
+ if (pimpl_->status_ != WaitingToLoad || !pimpl_->cached_item_
+ || pimpl_->cached_item_->status() == Converting)
return;
pimpl_->startLoading();
}
Re: LyX 2.3.0 on Windows
On 05/18/2018 11:16 AM, Richard Kimberly Heck wrote: > On 05/18/2018 04:32 AM, Andrew Parsloe wrote: >> On 18/05/2018 11:27 a.m., Richard Kimberly Heck wrote: >>> I've fixed the problems reported by people who've tried the new >>> installers. The question is how now to proceed. Note that these are >>> questions for 2.3.0 (and probably 2.3.1, since I will turn my attention >>> to that once this issue is resolved). Larger questions about how to >>> proceed with the Windows installer can be deferred to 2.3.2 if not >>> 2.4.0. >>> >>> It's my hope that we can find someone to take over building the >>> installer, etc, before too long. I'm happy to do it for a bit >>> >>> So, questions. >>> >>> 1) Should we include any form of the 'update MiKTeX' code, with a dialog >>> asking for permission to perform the update, or should we not do so? >>> >>> 2) Should we try to get wider testing of these new packages by >>> advertising the putatively final version on the users' list before doing >>> an official release? >>> >>> I have no strong opinion about (1), though I don't think it would be too >>> difficult to include such a dialog. I gather that the risk is that >>> updating LyX itself could trigger a partial update (due to packages >>> being installed at compilation time) that will break MiKTeX. As Pavel >>> said, the people this might affect seem to be only folks who did some >>> kind of update between October and January, but who knows. The main >>> issue would be getting translations of the message in the dialog. I >>> guess I could write to the relevant folks and ask for quick responses. >>> There's also Google, if all else fails. I suppose another option would >>> be for me to contact the MiKTeX maintainer and see what they think. >>> >>> Regarding (2), I guess I am a bit nervous about these installers, since >>> I have no idea what I'm doing, and we didn't get THAT much feedback from >>> my previous messages. >>> >>> Riki >> I've run LyX-230-Installer-103.exe. It has installed and from a very >> first glance, LyX is displaying a couple of complex documents >> correctly. The only obvious thing at this stage is that the LyX icon >> (an irregular LyX in large blue type) is missing and a generic windows >> program icon has taken its place (see attached). > I noticed that, but didn't realize what it was. I'll try to figure out > what's wrong. By the way, do you know how to figure out where Windows is trying to find the icon? I've presumably changed something unknowingly about where it's being put. Riki
Re: Windows Installers: TESTING ONLY
Am Donnerstag, den 17.05.2018, 19:14 -0400 schrieb Richard Kimberly Heck: > Is there a concrete proposal to be made here? I.e., that the 'bundle' > installer should install TeXLive? And default to 'medium' (if we can > make it do that)? I can't make a fair judgment, since I really don't know MikTeX, and I also don't know whether TL on Windows works as Win users expect it. However, I think the installer (and to some extend even LyX itself) has been tied much too strong to a specific LaTeX distribution and its needs. Jürgen signature.asc Description: This is a digitally signed message part
Re: Error messages with lyx2.3
Le 16/05/2018 à 20:01, Enrico Forestieri a écrit : On Wed, May 16, 2018 at 01:43:45PM -0400, Richard Kimberly Heck wrote: I think you are right that it is during metrics. Tracing some things, RenderGraphic::metrics seems to be responsible for starting the preview, and it gets called from InsetGraphics::metrics. But maybe it is as easy as expanding the cases for which we check in graphics::Loader::startLoading? I tried this but it doesn't seem to work (see preview3.diff). However, the patch preview2.diff should accomplish the same goal and it seems to work. preview3.diff looks like the cleanest approach to me. I think it should go in. JMarc
Re: Windows Installers: TESTING ONLY
Le 16/05/2018 à 05:33, Richard Kimberly Heck a écrit : PS Certainly one thing I've learned is that installing LyX with MikTeX takes *forever*, and I've got a fast internet connection. It would be nice to know what packages we need to install to compile the User Guide, etc, and just install those, rather than every single package LyX could possibly need. This is not trivial, since some of those are font definitions. I have tried several times to convince Uwe to take a look at the MikTeX API that allows to download packages. This has to be faster than relying on \input hijacking. If it is not then something is seriously broken with MikTeX. JMarc
Re: Windows Installers: TESTING ONLY
On 05/18/2018 07:56 AM, Pavel Sanda wrote: > Richard Kimberly Heck wrote: >> Another possibility is to abandon the bundle installer and tell people >> they need to install a TeX distribution (and here are some links) >> before installing LyX. > Maybe the best option initially is it to keep it as simple as possible. I am > not sure how much rewarding is it for you in the long term to care about > possible issues with LaTeX distribution. Yes, that's more an issue for later. > If someone else joins the party, he can start doing it later (though somewhat > ironically your attempt to make the installers on your own prevents folks > like that to appear. I think ppl usually needs some itch to start new > enterprise and when some sort of installer is already available, well... ;) I thought about that. I'm intending, once this has been released, to raise some questions about how to proceed. E.g., posting a message to lyx-users, and maybe on the website, asking for help. In light of > What could help is some wiki page clearly explaining steps how to create > the current installer, so the initial learning curve is easy and potential > contributor does not need to reinvent the wheel like you did now. ...the time commitment won't be that great, and I'm happy to provide backup and help to figure out whatever issues might arise. We may also need to figure out what to do about the doucmentation and the translations, which Uwe largely handles. I'm not quite sure what his status is at this point. Riki
Re: Windows Dependencies
On 05/18/2018 08:09 AM, Pavel Sanda wrote: > Richard Kimberly Heck wrote: >> I've uploaded the zip file with Uwe's Windows dependencies (Python, etc) >> to here >> >> http://ftp.lyx.org/pub/lyx/devel/win_deps/lyx-windows-deps-msvc2015.zip >> >> Others should be able to build our installers on Windows, and you need >> this stuff to do so. We will need to keep this up to date somehow. >> >> Right now, my question is about licensing. There's a licence statement at >> >> development/Win32/packaging/installer/license.rtf >> >> that gets included in the Windows release, but the zip file itself does >> not seem to contain any sort of license statements. By putting it on our >> website (and by Uwe's putting it where he had it before), we are >> presumably 'redistributing' quite a lot of stuff. > I do not think it's anything new, we used to have earlier versions of this zip > since it's creation by Joost on ftp already; I'm not even sure when/why those > earlier got deleted from there. I deleted the old ones when I uploaded the new ones. LyX can't be compiled with less than MSVC 2105 now, and I don't think we need to archive that sort of stuff in devel/. >> I'm afraid I'm fairly ignorant about such things. Could someone else >> volunteer to have a look at what's included in that zip file and figure >> out what we need to include ourselves in order to be doing things right? > Maybe put link to development/Win32/packaging/installer/license.rtf > into the same directory as if the zip file? Good idea. Riki
Re: LyX 2.3.0 on Windows
On 05/18/2018 04:32 AM, Andrew Parsloe wrote: > On 18/05/2018 11:27 a.m., Richard Kimberly Heck wrote: >> I've fixed the problems reported by people who've tried the new >> installers. The question is how now to proceed. Note that these are >> questions for 2.3.0 (and probably 2.3.1, since I will turn my attention >> to that once this issue is resolved). Larger questions about how to >> proceed with the Windows installer can be deferred to 2.3.2 if not >> 2.4.0. >> >> It's my hope that we can find someone to take over building the >> installer, etc, before too long. I'm happy to do it for a bit >> >> So, questions. >> >> 1) Should we include any form of the 'update MiKTeX' code, with a dialog >> asking for permission to perform the update, or should we not do so? >> >> 2) Should we try to get wider testing of these new packages by >> advertising the putatively final version on the users' list before doing >> an official release? >> >> I have no strong opinion about (1), though I don't think it would be too >> difficult to include such a dialog. I gather that the risk is that >> updating LyX itself could trigger a partial update (due to packages >> being installed at compilation time) that will break MiKTeX. As Pavel >> said, the people this might affect seem to be only folks who did some >> kind of update between October and January, but who knows. The main >> issue would be getting translations of the message in the dialog. I >> guess I could write to the relevant folks and ask for quick responses. >> There's also Google, if all else fails. I suppose another option would >> be for me to contact the MiKTeX maintainer and see what they think. >> >> Regarding (2), I guess I am a bit nervous about these installers, since >> I have no idea what I'm doing, and we didn't get THAT much feedback from >> my previous messages. >> >> Riki > > I've run LyX-230-Installer-103.exe. It has installed and from a very > first glance, LyX is displaying a couple of complex documents > correctly. The only obvious thing at this stage is that the LyX icon > (an irregular LyX in large blue type) is missing and a generic windows > program icon has taken its place (see attached). I noticed that, but didn't realize what it was. I'll try to figure out what's wrong. Riki
Re: Windows Dependencies
Richard Kimberly Heck wrote: > I've uploaded the zip file with Uwe's Windows dependencies (Python, etc) > to here > > http://ftp.lyx.org/pub/lyx/devel/win_deps/lyx-windows-deps-msvc2015.zip > > Others should be able to build our installers on Windows, and you need > this stuff to do so. We will need to keep this up to date somehow. > > Right now, my question is about licensing. There's a licence statement at > > development/Win32/packaging/installer/license.rtf > > that gets included in the Windows release, but the zip file itself does > not seem to contain any sort of license statements. By putting it on our > website (and by Uwe's putting it where he had it before), we are > presumably 'redistributing' quite a lot of stuff. I do not think it's anything new, we used to have earlier versions of this zip since it's creation by Joost on ftp already; I'm not even sure when/why those earlier got deleted from there. > I'm afraid I'm fairly ignorant about such things. Could someone else > volunteer to have a look at what's included in that zip file and figure > out what we need to include ourselves in order to be doing things right? Maybe put link to development/Win32/packaging/installer/license.rtf into the same directory as if the zip file? Pavel
Re: LyX 2.3.0 on Windows
Richard Kimberly Heck wrote: > 1) Should we include any form of the 'update MiKTeX' code, with a dialog > asking for permission to perform the update, or should we not do so? Unless we also do also bundle with MiKTeX it might be better to stay distribution agnostic. But no strong opinion either. > 2) Should we try to get wider testing of these new packages by > advertising the putatively final version on the users' list before doing > an official release? Definitely. Pavel
Re: Windows Installers: TESTING ONLY
Richard Kimberly Heck wrote: > Another possibility is to abandon the bundle installer and tell people > they need to install a TeX distribution (and here are some links) > before installing LyX. Maybe the best option initially is it to keep it as simple as possible. I am not sure how much rewarding is it for you in the long term to care about possible issues with LaTeX distribution. If someone else joins the party, he can start doing it later (though somewhat ironically your attempt to make the installers on your own prevents folks like that to appear. I think ppl usually needs some itch to start new enterprise and when some sort of installer is already available, well... ;) What could help is some wiki page clearly explaining steps how to create the current installer, so the initial learning curve is easy and potential contributor does not need to reinvent the wheel like you did now. Pavel
Re: LyX 2.3.0 on Windows
On 18/05/2018 11:27 a.m., Richard Kimberly Heck wrote: I've fixed the problems reported by people who've tried the new installers. The question is how now to proceed. Note that these are questions for 2.3.0 (and probably 2.3.1, since I will turn my attention to that once this issue is resolved). Larger questions about how to proceed with the Windows installer can be deferred to 2.3.2 if not 2.4.0. It's my hope that we can find someone to take over building the installer, etc, before too long. I'm happy to do it for a bit So, questions. 1) Should we include any form of the 'update MiKTeX' code, with a dialog asking for permission to perform the update, or should we not do so? 2) Should we try to get wider testing of these new packages by advertising the putatively final version on the users' list before doing an official release? I have no strong opinion about (1), though I don't think it would be too difficult to include such a dialog. I gather that the risk is that updating LyX itself could trigger a partial update (due to packages being installed at compilation time) that will break MiKTeX. As Pavel said, the people this might affect seem to be only folks who did some kind of update between October and January, but who knows. The main issue would be getting translations of the message in the dialog. I guess I could write to the relevant folks and ask for quick responses. There's also Google, if all else fails. I suppose another option would be for me to contact the MiKTeX maintainer and see what they think. Regarding (2), I guess I am a bit nervous about these installers, since I have no idea what I'm doing, and we didn't get THAT much feedback from my previous messages. Riki I've run LyX-230-Installer-103.exe. It has installed and from a very first glance, LyX is displaying a couple of complex documents correctly. The only obvious thing at this stage is that the LyX icon (an irregular LyX in large blue type) is missing and a generic windows program icon has taken its place (see attached). Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Link to windows installers
Please ignore my previous message. I see the link that pointed to version 1 now points to version 3. I will install it and try it out. Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Re: LyX 2.3.0 on Windows
On 18/05/2018 11:27 a.m., Richard Kimberly Heck wrote: ... I guess I am a bit nervous about these installers, since I have no idea what I'm doing, and we didn't get THAT much feedback from my previous messages. Riki I'm very happy to try your latest version if you can provide a link. Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
