<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><font face="Andale Mono"><span style="font-size: 12px;">I just had a go at it (for about 5 or 10 minutes). It is of course (i.e. conforms to current trend in LaTeX editors) one of that "all the things in a big window" style editors, with a information section to the left, the editor in the middle, and the output PDF on the right. Small console window under the editor. You can "live update" the PDF.</span></font><div><font face="Andale Mono"><span style="font-size: 12px;"><br></span></font></div><div><font face="Andale Mono"><span style="font-size: 12px;">You can customise which engine you use by default; I use xelatex. However once I did that I found it still compiled the file I had open with pdflatex. After clicking about a bit I found that one of the icons in the information section (the little cog) allowed me to change which engine I was using for the current file, which is apparently remembers.</span></font></div><div><font face="Andale Mono"><span style="font-size: 12px;"><br></span></font></div><div><font face="Andale Mono"><span style="font-size: 12px;">The build started to complain about a file I was \input'ing which could not be converted to UTF-16, However this is not a problem I have encountered with the same files under TeXShop. For the sake of getting things to work I commented out the \input line and continued with my demo.</span></font></div><div><font face="Andale Mono"><span style="font-size: 12px;"><br></span></font></div><div><font face="Andale Mono"><span style="font-size: 12px;">Like most of these programs if you're used to a really powerful editor (e.g. BBedit, Textmate, EMACS, a programmer's IDE) you'll find the editor lacking in many advanced features. It's not even up to TexShop's ability yet. That's why I'v always found it necessary to keep versions of those editors around and available to edit file if I need to do complex search-and-replace based on regex, for example.</span></font></div><div><font face="Andale Mono"><span style="font-size: 12px;"><br></span></font></div><div><font face="Andale Mono"><span style="font-size: 12px;">It has some syntax highlighting which is customisable to some degree. The default syntax highlighting is a little too subtle, everything being various shades of blue, except maths macros, which are red (not being a maths/science person, I always feel a little left out). I tried out the maths macro just to see and it puts only the dollar signs '$' in red, the content between them is left in the default colour.</span></font></div><div><font face="Andale Mono"><span style="font-size: 12px;"><br></span></font></div><div><font face="Andale Mono"><span style="font-size: 12px;">Some more work could be done on the syntax colouring. All arguments in braces {}, including the braces themselves, are coloured the one colour. So if I write this footnote, it looks like this following screen cap (sorry to people with plain-text email viewers):</span></font></div><div><font face="Andale Mono"><span style="font-size: 12px;"><br></span></font></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div style="margin: 0px; "><font face="Andale Mono"><span style="font-size: 12px;"><img id="6b328f82-b3e9-4061-a611-a2b62cf068ae" height="137" width="640" apple-width="yes" apple-height="yes" src="cid:4D604B84-BE6A-4754-A1BD-86F93A14C4D5"></span></font></div></blockquote><div><font face="Andale Mono"><span style="font-size: 12px;"><br></span></font></div><div><font face="Andale Mono"><span style="font-size: 12px;">(I've change the default colour here to green). As you can see, what is hidden from immediate display, is my use of embedded formatting commands inside the \footnote{}, viz, the '\emph{lectisternium}'; it's all just a big block of green. I think a number of solutions ought to be applied to improve this: </span></font></div><div><ul><li><font face="Andale Mono"><span style="font-size: 12px;">embedded, recursive, arguments should be coloured differently (perhaps just getting darker with additional recursion, or cycling through a preset palette selection).</span></font></li><li><span style="font-size: 12px; font-family: 'Andale Mono'; ">commands inside commands ought to be highlighted.</span></li><li><span style="font-size: 12px; font-family: 'Andale Mono'; ">certain common commands like \footnote \emph \textit \textbf \section etc should have </span><span style="font-size: 12px; font-family: 'Andale Mono'; ">separate</span><span style="font-size: 12px; font-family: 'Andale Mono'; "> colour schemes</span><span style="font-size: 12px; font-family: 'Andale Mono'; ">.</span></li><li><span style="font-size: 12px; font-family: 'Andale Mono'; ">the brace colour should be subtly different to the colour of the argument content (eg. slightly darker).</span></li></ul></div><div><span style="font-size: 12px; font-family: 'Andale Mono'; ">By default the editor is set to "hard wrap" which meant my soft-wrapped tex file line ran off the right of the page. There is a global option to change this, which I had to discover, only after looking for, and failing to find, a "view" style option to apply to the current window.</span></div><div><font face="Andale Mono"><span style="font-size: 12px;"><br></span></font></div><div><font face="Andale Mono"><span style="font-size: 12px;">The "live update" is an interesting idea but its execution needs improving. Of course while you're typing the poor thing is just about continuously compiling or trying to compile to PDF. But what happened is that the PDF preview did not jump to the place where I was typing. It did seem to jump around (to the last page in my case) but not exactly to where I had made changes. Which sort of defeats the purpose a little.</span></font></div><div><font face="Andale Mono"><span style="font-size: 12px;"><br></span></font></div><div><font face="Andale Mono"><span style="font-size: 12px;">Well, that's about as much time as I should spend on this, took me longer to write than to demo.<br></span></font><div><font face="Andale Mono"><span style="font-size: 12px;"><br></span></font></div><div><font face="Andale Mono"><span style="font-size: 12px;"><br></span></font></div><div><font face="Andale Mono"><span style="font-size: 12px;"><br></span></font><div apple-content-edited="true"><font face="Andale Mono"><span style="font-size: 12px;">-- <br><a href="mailto:scot.mcphee@gmail.com">scot.mcphee@gmail.com</a><br>http://inlustre.net/<br>http://crazymcphee.net/</span></font></div><br><div><div>On 28/12/2012, at 01:22 , Herbert Schulz <<a href="mailto:herbs@wideopenwest.com">herbs@wideopenwest.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Howdy,<br><br>TeXnicle 2.0, a free (as in beer) front end Editor/Previewer for TeX has been released. You can get it at <<a href="http://www.bobsoft-mac.de/texnicle/texnicle.html">http://www.bobsoft-mac.de/texnicle/texnicle.html</a>>. Anyone interested in testing and reviewing the app? Looks like it might have some nice features.<br><br>Good Luck,<br><br>Herb Schulz<br>(herbs at wideopenwest dot com)<br><br><br><br>----------- Please Consult the Following Before Posting -----------<br>TeX FAQ: <a href="http://www.tex.ac.uk/faq">http://www.tex.ac.uk/faq</a><br>List Reminders and Etiquette: <a href="http://email.esm.psu.edu/mac-tex/">http://email.esm.psu.edu/mac-tex/</a><br>List Archive: <a href="http://tug.org/pipermail/macostex-archives/">http://tug.org/pipermail/macostex-archives/</a><br>TeX on Mac OS X Website: <a href="http://mactex-wiki.tug.org/">http://mactex-wiki.tug.org/</a><br>List Info: <a href="http://email.esm.psu.edu/mailman/listinfo/macosx-tex">http://email.esm.psu.edu/mailman/listinfo/macosx-tex</a><br><br></blockquote></div><br></div></div></body></html>