summer-of-code
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

project idea for texinfo project


From: Per Bothner
Subject: project idea for texinfo project
Date: Tue, 16 Feb 2016 14:26:49 -0800
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0

see attachment.
--
        --Per Bothner
address@hidden   http://per.bothner.com/

Texinfo

GNU documentation is based on the texinfo source format (conceptually similar to markdown, but better for documentation). There are tools to convert texinfo into various formats, including pdf, html, and info format. The info format is used for reading the documentation in a terminal emulator (using the info program) or in the emacs editor.

Keyboard-centric UI in _javascript_ for GNU HTML documentation

The info format is very bare-bones (no fonts or images). On the other hand, the info program has a number of conveniences for browsing documentation, and the keyboard-centric user interface is very efficient. We would like to combine the user interface and features of the info program with the rich text and graphics of HTML. Specifically porting most of the functionality of the info program to _javascript_ and CSS that can work in a browser.

Desirable features of the info program that we would like to replicate in _javascript_ include:

The focus of this project is writing logic and event handlers in _javascript_. You may also want to make some tweaks to how the texinfo tools generate HTML so the HTML is cleaner and easier to work with.

Once we have a good basic browser-based documentation reader (hopefully by the mid-term), there are some possible enhancements. One is to generate on-the-fly a navigation bar. For example see the Kawa homepage, which is generated from texinfo, but goes through some extra complex processing. It would be nice if it could be done in _javascript_ and CSS.

Another enhancement is to use the DomTerm web-based terminal emulator. The idea that a modest front-end wrapper would locate the HTML files, and send a request to DomTerm to load the HTML in an iframe of the DomTerm browser window. If the user selects some other manual, the _javascript_ could send a request to the front-end to locate and load the manual.

Contact: address@hidden
Mentors: Per Bothner, Gavin Smith


reply via email to

[Prev in Thread] Current Thread [Next in Thread]