On 03/20/2017 02:23 PM, Mathieu Lirzin wrote:
As an extensive Emacs user, I really enjoy reading Info manuals because of the amazing index command and the possibility to search through the whole manual via regexps. I would really be interested in porting those wonderful features to the browser which is I guess the most common way for people to read manuals written in texinfo.
The principal reason that was refraining my proposal, is that I have never written any serious project in Javascript yet. I know its syntax, its object model, and as a Scheme programmer I am familiar with functional programming in general, however I am not fluent with the various Javascript APIs and the common idioms.
I suspect enthusiasm, plus familiarity with texinfo, are likely to be more valuable than expert knowledge of the implementation language and APIs. The JavaScript ecosystem is huge - and I only know the core parts of it myself. But that is is OK - for texinfo we want to stick to basic JavaScript, and avoid fancy frameworks. The main task is getting familiar with the DOM API's. (The basics are clunky but simple.) Having some knowledge of CSS is also important. However, if you're an experienced programmer, and comfortable with searching for documentation and solutions on the web, then you should be fine.
Having said that I am willing to overcome my deficiencies and become more familiar with Javascript. The fact that Per Bothner has already written some parts of the implementation will help me. What do people think?
If you haven't already, I suggest you read: http://per.bothner.com/blog/2017/texinfo-roadmap/ While the "roadmap" opinions are my own (and some may be controversial), a good chunk of the article is more details about the JavaScript browser. -- --Per Bothner [email protected] http://per.bothner.com/
