When I’m at the computer, a great deal of my writing activity happens not precisely in a word processor (such as MS Word, or LibreOffice Writer), but on a text editor, preparing source code for a document typesetting and preparation system known as LaTeX (Wikipedia entry). This system is easy, powerful and beautiful, allowing me to prepare professional-looking documents with a minimum of effort, way less than with a regular word processor. This advantage is achieved by separating presentation from content; once you got your presentation parameters sorted out, all you have to do is write text. It is also batch-processed: you write text with some markup code in an editor, then you feed the text to a LaTeX processor, which in turn produces readable output (my system produces camera-ready PDF files). An additional advantage of LaTeX —though I have not explored that fully— is that it is cross-platform; LaTeX systems are available for almost any computer system imaginable, since LaTeX is Free Software.
You can write LaTeX in any text editor, because the processor requires a plain text file as input. In Windows, Notepad would be adequate, and any barebones text editor would suffice in any platform. (Or you could use a gorilla such as MS Word or any other word processor, as long as you save your files as plain text, but that would be overkill.) There are document processors that act as a LaTeX frontend and that could be used more or less like “LaTeX graphical word processors”, such as LyX or GNU TeXmacs. They are great, capable tools, but they are also limited; if you want the full power and flexibility of LaTeX, the best approach is to code your document in LaTeX itself. (And besides that, LaTeX is not that difficult. It is actually quite simple to learn.)
The best way to typeset text –to code– in LaTeX is by using a dedicated LaTeX development environment: A special text editor that, in a way that is analogous to IDEs (integrated development environment), provides specialized access to tools, reusable code components, and such. For casual uses it may be too much; but when you’re really into LaTeX typesetting, it could be a lifesaver.
As a Linux desktop user, my graphical environment is KDE, and it has been so almost since the day I began using Linux. For the uninitated, let me explain that KDE is a graphical desktop for Unix-like systems built on top of the Qt graphical library. KDE is great and it is so friendly and powerful that it almost feels like an extension of my brain, staying out of my way and letting me getting my work done. The current stable version is KDE 4.14.1, from the great KDE 4.x series, based on the Qt 4.x graphical library:
KDE folks are now readying a completely new environment based on the Qt 5.x graphical library, which could be loosely known as “KDE 5”. This denomination is inaccurate; in fact KDE released so far Plasma 5.0.x and Frameworks 5.2.x, and the whole world of KDE applications are being ported to Frameworks 5.x as of now. Thanks to the work of Eric Hameleers, one of the Slackware Crew members, I now have the latest and greatest of KDE 5 on my computer: Plasma 5.0.2 and Frameworks 5.2.0. So far, it is behaving itself quite well:
The writing is on the wall, then; the applications I use on my workflow should be in the process of porting to KDE 5 or I risk being cornered with an obsolete version of both desktop and applications. As of now, however, and despite being totally usable, KDE 5 is in a very early stage of development to be useful. In order to make it my default desktop I need at the very least to be able to migrate my PIM workflow, which is highly dependent on KDE4’s aKonadi and there’s no clear upgrade path to KDE 5 yet. So, for me it’s KDE 4.14.1 for the time being.
In this regard, if you think that LaTeX is important in my workflow, you are correct. I code LaTeX with a great KDE application known as Kile (KDE’s Integrated LaTeX Environment). At version 2.1.3, it is a stable, mature and powerful application, perfectly suitable for any major LaTeX editorial project.
Founded by Pascal Brachet in the early KDE 3.x days, maintainership passed over to Jeroen Wijnhout, and then to a team headed by Michel Ludwig. They have all done a great job; and it shows. I wrote several mission-critical texts with it, including my lawyer’s thesis, my Th.M. major research paper, and several published works. Over the time, it proved itself an invaluable asset for my workflow. But there’s a problem.
KDE 5.x is already on the horizon, and Kile does not have an upgrade path to it. Version 2.1.3, while powerful and stable, was released on 2012 and there is no sign of active development on its SourceForge page. It is reasonable then to assume that Kile development was, for all practical purposes, abandoned. Now, for KDE 4.x this statu quo would be fine, since the current version works great and it’s rock-solid. But I had to find somethinhg that would work well with KDE 5 in order to be ready for the future.
I researched alternatives. One was Texmaker, which is developed by Kile’s founder, Pascal Brachet. Version 4.1 was released last August and it is clearly in active development. It is a Qt-only application, cross-platform, and it compiles under Qt5. However, it feels like a very early and limited Kile:
Don’t jump to conclusions, though. Texmaker is a great application, very powerful and well-designed. But it does not adjust itself well to my workflow. So, I had to look for an alternative. After some searching, I found what it seems a good option, Texstudio:
Developed by Benito van der Zander, Jan Sundermeyer, Daniel Braun and Tim Hoffmann, TeXstudio began as a series of patches to Texmaker, with the hope of integrating them upstream; however, it soon became apparent that it would not be possible. So they forked Texmaker, applied their improvements, and began development of a wholly different application. TeXstudio has a strong resemblance to Kile, and it could be made even more similar by applying customizations (such as keyboard shortcuts and menu items). Even better: like Texmaker, it is both cross-platform and could be compiled under Qt 5.x by passing a simple compilation parameter to the build system, so it’s future proof and could be used under KDE 5.x. I began to use it and I find it pleasant to use and a great drop-in replacement to Kile.
Thus, one major roadblock to KDE 5 was sorted out. I may not be able to use Kile, but I can certainly use TeXstudio.
Update – Sep 29: Jure Repinc replied in a comment that Kile is being actively developed after all, and there is also a porting effort to Frameworks 5. Great!