<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Am 16.10.2010 10:33, schrieb Bruno Voisin:
<blockquote cite="mid:DDA17CF5-5033-4F53-BF43-DF65E29DF54B@me.com"
type="cite"><br>
<pre wrap="">Project management is appropriate when you are writing a long, structured document, like a PhD thesis, a multi-author paper, or a scientific report. This implies more-or-less the user has prior experience with TeX.
On the other hand, project management just adds unnecessary burden and complexity when you are writing a one-shot document, like a letter, an invitation to a party, etc., and may be seen as an entry barrier for the novice.
</pre>
</blockquote>
I think the whole discussion about when you require project
management and not and and for which document types or not is just
the wrong approach. Think the other way round: If many poeple
require project management for tex documents you can include or
exclude them as users for tw. Therefore I consider project
management as a must have, and under no curcumstances optional for a
tex editor. Personally I use projects for any documents. And my
templates are widely used, also very successful for by beginners and
they are split into many documents and thus require project
management.<br>
<br>
<blockquote cite="mid:DDA17CF5-5033-4F53-BF43-DF65E29DF54B@me.com"
type="cite">
<pre wrap="">So, regarding TeXworks, I'd suggest that project management, if any, remains unobtrusive and does not imply modifications of the current user interface.
</pre>
</blockquote>
While I would basically agree with this, it is so vague that <span
id="result_box" class="short_text" lang="en"><span
style="background-color: rgb(230, 236, 249); color: rgb(0, 0,
0);" title=""></span></span>it does not help creating an ui.<br>
<br>
Personally I find QtCreator as a good ui which includes project
management elements.<br>
<br>
However you will always find that the ui includes more visual
complex elements once you have a complex project.<br>
And it is not only a matter of visual projections of the project but
also of finding files, switching between files and making sure that
the user knows what he is currently working with.<br>
But once you have selected the document you want to work with, there
is no reason to not hide the project ui elements.<br>
<br>
Currently all Interfaces I know of present the structure-list only
on the side. If one displays the document side by side with the pdf
then this list becomes to small in width.<br>
(I have seen this with texmakerx which I use currently) I would
therefore propose the make the interface as wide as the tw
mainwindow. More space also allows a better ui.<br>
This should then include a list of open project, file lists,
structure lists, ...<br>
For editing a document (and thus not displaying the whole project
ui) I could envision only a single line on top of the document
showing a list of open files, a breadcrump view, <br>
a jump to structure (sec, fig, tab), all similar to how QtCreator
presents it.<br>
<br>
Matthias<br>
</body>
</html>