Menu
▾
▴
gnuplot-beta
|
From: Daniel J S. <dan...@ie...> - 2015-01-01 05:10:21
|
I've placed a patch for wxT HelpBook and Qt-Assistant on SourceForge: https://sourceforge.net/p/gnuplot/patches/704 which should give anyone interested something to do on New Year's Day. There are also a couple screenshots of the two help book windows after the gnuplot.htb file and the gnuplot.qch and gnuplot.qhc files are made and installed. Dan -------- Original Message -------- Subject: Re: Last call for issues affecting release of gnuplot 5.0 Date: Mon, 29 Dec 2014 14:48:04 -0600 From: Daniel J Sebald <dan...@ie...> To: sf...@us... CC: gnu...@li... On 12/29/2014 02:31 PM, sfeam wrote: > And why would you want to view it in anything other than your > normal preferred browser? The Help Book/Qt-Assistant format is much faster than a typical browser, it's a little better packaged in a way, and it doesn't require a browser be running. What I've done, in the case that the gnuplot.htb (Help Book) or gnuplot.qhc (Qt-Assistant help collection) is allow for the normal HTML code to be viewed in a wxWidgets or Qt window. Both of those frameworks support HTML code natively. So again, no browser is needed to use the HTML help for those two terminals. |
|
From: Daniel J S. <dan...@ie...> - 2015-01-01 05:21:21
|
[Sorry, that should have been patch #707 in the last post, i.e.,] I've placed a patch for wxT HelpBook and Qt-Assistant on SourceForge: https://sourceforge.net/p/gnuplot/patches/707 which should give anyone interested something to do on New Year's Day. There are also a couple screenshots of the two help book windows after the gnuplot.htb file and the gnuplot.qch and gnuplot.qhc files are made and installed. Dan > -------- Original Message -------- > Subject: Re: Last call for issues affecting release of gnuplot 5.0 > Date: Mon, 29 Dec 2014 14:48:04 -0600 > From: Daniel J Sebald<dan...@ie...> > To: sf...@us... > CC: gnu...@li... > > On 12/29/2014 02:31 PM, sfeam wrote: >> And why would you want to view it in anything other than your >> normal preferred browser? > > The Help Book/Qt-Assistant format is much faster than a typical browser, > it's a little better packaged in a way, and it doesn't require a browser > be running. > > What I've done, in the case that the gnuplot.htb (Help Book) or > gnuplot.qhc (Qt-Assistant help collection) is allow for the normal HTML > code to be viewed in a wxWidgets or Qt window. Both of those frameworks > support HTML code natively. So again, no browser is needed to use the > HTML help for those two terminals. |
|
From: Mojca M. <moj...@gm...> - 2015-01-02 11:07:28
|
On Thu, Jan 1, 2015 at 6:21 AM, Daniel J Sebald wrote: > [Sorry, that should have been patch #707 in the last post, i.e.,] > > I've placed a patch for wxT HelpBook and Qt-Assistant on SourceForge: > > https://sourceforge.net/p/gnuplot/patches/707 > > which should give anyone interested something to do on New Year's Day. > > There are also a couple screenshots of the two help book windows after > the gnuplot.htb file and the gnuplot.qch and gnuplot.qhc files are made > and installed. Thank you very much. This is an excellent addition (that I have been waiting for for a long time already and also tried to implement myself, but gave up too soon) and I would be extremely happy if it could end up in 5.0. (I would suggest releasing RC4 with this addition though since packagers are expected to modify their build flows slightly and some totally unexpected problems might arise there.) The "next level" would be to allow users to configure "help foo" to automatically open the help book, but that doesn't need to be done now. I have problems with an out-of-source build of help files for Qt, but wxt help works very nicely. One tiny problem: when I ran help in wxt for the first time, the dialogue window appeared. During that time the console was completely unresponsive. But maybe that's the expected behaviour anyway. Mojca |
|
From: Daniel J S. <dan...@ie...> - 2015-01-02 19:03:36
|
On 01/02/2015 05:07 AM, Mojca Miklavec wrote: > On Thu, Jan 1, 2015 at 6:21 AM, Daniel J Sebald wrote: >> [Sorry, that should have been patch #707 in the last post, i.e.,] >> >> I've placed a patch for wxT HelpBook and Qt-Assistant on SourceForge: >> >> https://sourceforge.net/p/gnuplot/patches/707 >> >> which should give anyone interested something to do on New Year's Day. >> >> There are also a couple screenshots of the two help book windows after >> the gnuplot.htb file and the gnuplot.qch and gnuplot.qhc files are made >> and installed. > > Thank you very much. This is an excellent addition (that I have been > waiting for for a long time already and also tried to implement > myself, but gave up too soon) and I would be extremely happy if it > could end up in 5.0. > > (I would suggest releasing RC4 with this addition though since > packagers are expected to modify their build flows slightly and some > totally unexpected problems might arise there.) > > The "next level" would be to allow users to configure "help foo" to > automatically open the help book, but that doesn't need to be done > now. I knew that would eventually be a request. :-) The concept doesn't appear to violate any gnuplot terminal philosophy, I guess. It would just be issuing a "help xyz" to the terminal. I think this is possible to do in Qt's case (wxT I don't know about). The commands that could be sent to Qt-Assistant are here: http://doc.qt.io/qt-5/assistant-custom-help-viewer.html#using-qt-assistant-remotely So, that part is easy. The tricky part is that there needs to be some type of lookup file, of sorts, that translates "xyz" to whatever its reference is in the documentation, e.g., "loc432.html". Where that should be done, I'm not sure (inside gnuplot core or inside qt terminal). > I have problems with an out-of-source build of help files for Qt, but > wxt help works very nicely. I sent a separate note on your Qt problem. SQL library file missing would be my guess, but we'll wait to see if anyone else has the same issue and knows an easy solution. > One tiny problem: when I ran help in wxt for the first time, the > dialogue window appeared. During that time the console was completely > unresponsive. But maybe that's the expected behaviour anyway. No, that's not expected. I'm wondering if there is some type of strange bug in the wxT terminal that manifests in different ways on different systems. I've noted some strange behavior (wxT terminals are always persistent, once in a while crashes on exit), which still exists in the 5.1 development version. Dan |
|
From: Ethan A M. <sf...@us...> - 2015-01-02 19:44:23
|
On Friday, 02 January, 2015 13:03:12 Daniel J Sebald wrote: > On 01/02/2015 05:07 AM, Mojca Miklavec wrote: > > > One tiny problem: when I ran help in wxt for the first time, the > > dialogue window appeared. During that time the console was completely > > unresponsive. But maybe that's the expected behaviour anyway. > No, that's not expected. I'm wondering if there is some type of strange > bug in the wxT terminal that manifests in different ways on different > systems. Could it be because wxWidgets on OSX is single-threaded? > I've noted some strange behavior (wxT terminals are always > persistent, once in a while crashes on exit), which still exists in the > 5.1 development version. It would really help if you could capture a backtrace of such a crash. And what do you mean "always persistent"? Are you saying that even if you run without the persist mode the plot window still never exits? Or do you just mean that the toolbar widget always defaults to "persist". If the latter, perhaps there's a corruption in ~/.gnuplot-wxt content? Ethan |
|
From: Daniel J S. <dan...@ie...> - 2015-01-02 20:20:18
|
On 01/02/2015 01:42 PM, Ethan A Merritt wrote: > On Friday, 02 January, 2015 13:03:12 Daniel J Sebald wrote: > >> On 01/02/2015 05:07 AM, Mojca Miklavec wrote: > >> > >> > One tiny problem: when I ran help in wxt for the first time, the > >> > dialogue window appeared. During that time the console was completely > >> > unresponsive. But maybe that's the expected behaviour anyway. > >> No, that's not expected. I'm wondering if there is some type of strange > >> bug in the wxT terminal that manifests in different ways on different > >> systems. > > Could it be because wxWidgets on OSX is single-threaded? Good point. The dialog box should be modal though...let me think about that one. >> I've noted some strange behavior (wxT terminals are always > >> persistent, once in a while crashes on exit), which still exists in the > >> 5.1 development version. > > It would really help if you could capture a backtrace of such > > a crash. I'll try, but it is random and the usual info seems to somewhere other than the terminal window. > And what do you mean "always persistent"? > > Are you saying that even if you run without the persist mode > > the plot window still never exits? Yes. > Or do you just mean that the toolbar widget always defaults > > to "persist". If the latter, perhaps there's a corruption in > > ~/.gnuplot-wxt content? Oh man, operator error! I didn't even know such a setting existed in the wxt terminal. Well, guess I'm OK with the existence of such a setting in the terminal window, except for the fact that there seems to be a logical conundrum to it with regard to a command-line persist setting. That is, right now if one launches with: gnuplot -persist and then looks at the wxT terminal settings, the "Don't quit until all windows are closed (persist)" is not checked. Shouldn't that be checked if "persist" actually is active? But if that box were forced to be checked, it would mean that the next time gnuplot is launched wxT would be persistent regardless of the presence of "-persist". Furthermore, if launching in "-persist" mode, opening the settings window of wxT and checking and then unchecking "Don't quit until all windows are closed (persist)" takes the terminal out of persist mode, obviating the "-persist" argument. If the terminal is to have control of this (why it should, I'm not sure), then maybe there really should be a third "setting", or non-setting, i.e., make the checkbox non-checkable or grayed out or something similar. That is, launching with "-persist" might make it so that the checkbox in the wxT terminal settings is gray and can't be altered. Dan > > Ethan > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > > > > _______________________________________________ > gnuplot-beta mailing list > gnu...@li... > Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-beta -- Dan Sebald email: daniel(DOT)sebald(AT)ieee(DOT)org URL: http://www(DOT)dansebald(DOT)com |
