Dear Jonathan,<div><br></div><div>Your wish is my command :)</div><div><br></div><div>I have modified the configuration to meet the layout you outlined (I think).</div><div><br></div><div>I am looking for a simple string perhaps</div>
<div><br></div><div> ./ .dah../.dah../index.html?\para&nasalatex</div><div><br></div><div>Which would for example search the Nasa Latex (off line) information for the tag \para</div><div><br></div><div> ./ .dah../.dah../index.html?font&ukfaq</div>
<div><br></div><div>Well you can guess TUG UK's Faq (offline) for the word font</div><div><br></div><div>case will not matter, everything - will be treated as lowercase.</div><div><br></div><div>So perhaps initially these search bases:</div>
<div><br></div><div>&ukfaq</div><div>&ctantopics</div><div>&nasalatex</div><div>&texworksToc</div><div>&texworksIndex</div><div><br></div><div>So ..</div><div><br></div><div>index.html - would start in the TexWorks TOC html help</div>
<div>index.html?\para - would start in the Nasa Latex looking for \para command</div><div>index.html?color - would start in the UK-FAQ looking for color</div><div>index.html?colo&ctantopics - would start in the ctan topics looking for colo </div>
<div> (would find colour and color)</div><div>index.html?&ctantopics - no search word just an ampersand would start a search base</div><div><br>
</div><div>would all be valid.</div><div><br></div><div>I'll treat worked on packages in a similar way.</div><div><br></div><div>Trying to make the whole thing easily extensible by anyone.</div><div><br></div><div>How does that sound?</div>
<div><br></div><div>Once open, the User can click through the different bases with their latest search term being applied.</div><div><br></div><div>Ctan is my current mission, putting the offline references in place. Looking good so far, managed to get rsync the needed files and got Graham's python to work locally, and render the individual xml to html and a solid monolithic xml</div>
<div><br></div><div>Feel to try and respect the fact that Ctan rely on sales of their catalogue .pdf to keep things going, so will design to try and not impinge on that.</div><div><br></div><div>Paul</div><div><br><div class="gmail_quote">
2009/10/9 Jonathan Kew <span dir="ltr"><<a href="mailto:jfkthame@googlemail.com">jfkthame@googlemail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On 8 Oct 2009, at 12:32, Paul A Norman wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Dear TexWorks developers - Users,<br>
<br>
I have been able to intergrate the processes on the help files I have been working on so that there is a combined interface. This gives intergrated access and searching to Nasa LaTeX Caoomand and Environments help, Uk Faq, Ctan package information, and Alain's TeXWorks html help.<br>
<br>
I am debugging and working at speeding things up as much as possible<br>
<br>
On the Nasa help, I am starting to work through with Helmut Kopka and Patrick W. Daly's Guide to LateX 4th edition verifying things against the points you raised about the documentations age Jonathan.<br>
<br>
I would like to next focus on some packages that could do with integrated help. I am considering looking at graphicx, hyperref, color issues, and flowfram.<br>
<br>
Johnathan, I would like to ask please, could there be a dedicated directory name under the TeXWorks binary that I could safely use please for any one who wants to add what I am doing to their TeXWorks work flow?<br>
</blockquote>
<br></div></div>
Hi Paul,<br>
<br>
This looks like becoming a really great collection of resources!<br>
<br>
What I'd like to do in a while, once things are reasonably stable, is to bundle at least some of this with the package that's distributed, and have it available via the Help menu. I'm not sure how your "combined interface" will fit with this -- it's certainly nice to have an integrated lookup across all the documents, but at the same time, I think it's probably nice to have browsable starting-points for each of the resources.<br>
<br>
If you create a new folder within the texworks-help directory, and (optionally) language-coded subdirectories within that, texworks will look for a file "index.html" in there. If it finds one, a menu item will automatically be added to the Help menu to launch this with your default browser. The menu item will be the subdirectory name, or you can provide a one-line text file "tw-help-title.txt" to override it. So this already lets you experiment with new Help resources.<br>
<br>
The next step will be to (a) add support for a similar texworks-help subdirectory within the TW library folder (along with the config files, dictionaries, etc) so that you can add "personal" resources separately from those distributed with the package; and (b) make it easy to do a direct lookup of a selected word/command/etc from within texworks, by passing it via the URL that is sent to the browser. I think this should be easy to do if I provide access to the texworks "openUrl" handler from QtScript.<br>
<br>
If I have time at the weekend, perhaps I can look into this and get an experimental build posted for you to try....<br><font color="#888888">
<br>
JK<br>
<br>
</font></blockquote></div><br></div>