Displaying the whole t2t file?

18 views
Skip to first unread message

Eric F.

unread,
Apr 15, 2012, 4:38:48 PM4/15/12
to Nested
Hello,

I've just discovered Nested which is an exciting project! I wished I
had such an interface for the textallion :)

I was wondering if it is possible to display the complete t2t document
instead of parts of it? (within headings). The left pane could be only
to quickly access the headings.

Carlos Jenkins

unread,
Apr 16, 2012, 12:48:01 AM4/16/12
to nested...@googlegroups.com
Hi,

Textallion is a great project, I took many ideas from it. I would love to adapt all textallion custom filters so 
users can write with it extended set of macros if they want. Also, I saw the HTML generated, it uses ideas 
from the web Better Web Readability Project, I've in the roadmap the creation of a Theme for Nested based on this too.
 
I was wondering if it is possible to display the complete t2t document
instead of parts of it? (within headings). The left pane could be only
to quickly access the headings.
The way it is intented is to split the content, in a divide and conquer philosophy. This behavior is
in the core of Nested and in the way it process the document, so no, it can't. The tree contains the sections
of the document, you can move drag and drop, make child or sibling of any node (and in the future copy and 
paste a whole section of the tree), quickly change the whole structure of the document, considering the sections 
as nodes enables that. All this properties would be lost if the tree pane is just a dynamic index of the document. 
Also, the tree should need to remember the line of the header it points, but any line you add to the document 
modifies this, so a constant reconstruction of the index will be needed, one could be on any insert of a newline 
or paste, which will be really hard for large documents, or an on demand by the user. In any case, this is out of 
the scope and philosophy of Nested.

Thanks for trying the Software. I recommend you to use the development version, it as a lot of new features not yet
published: LaTeX log parser dialog, spell checking, custom LaTeX title and others.

If you're interested in programming this behavior for Textallion you can use the function body_to_sections() in nested_gui.py
and modify it to count the line number. Then, you can use modules.latex.log.viewer.py to see how is implemented this
exact behavior : viewer.py stores in the tree the line of an error or warning, both for the source document and in the log,
when the user clicks the error on the tree both textviews jumps and highlight the line where the error occurred.

Kind regards

--
Carlos Jenkins
http://carlos.jenkins.co.cr/
Reply all
Reply to author
Forward
0 new messages