On 04/02/2017 04:32 PM, Mathieu Lirzin wrote:
- The solution for handling multi-page manuals using iframe, using
div elements, and adjusting their visibility is implemented and
works great. That is the main contribution of my prototype.
The only change I'd like in this area is a modest extensio
Per Bothner writes:
> On 04/02/2017 02:46 PM, Mathieu Lirzin wrote:
>>
>> Mathieu Lirzin writes:
>>
>>> I have sent a draft of my proposal which can be found here:
>>>
>>> http://mathieu.lirzin.emi.u-bordeaux.fr/gsoc/texinfo.pdf
>>
>> I have updated this draft, and tried to do it according to
On 04/02/2017 02:46 PM, Mathieu Lirzin wrote:
Hello,
Mathieu Lirzin writes:
I have sent a draft of my proposal which can be found here:
http://mathieu.lirzin.emi.u-bordeaux.fr/gsoc/texinfo.pdf
I have updated this draft, and tried to do it according to the very
valuable feedback that has
Hello,
Mathieu Lirzin writes:
> I have sent a draft of my proposal which can be found here:
>
> http://mathieu.lirzin.emi.u-bordeaux.fr/gsoc/texinfo.pdf
I have updated this draft, and tried to do it according to the very
valuable feedback that has been made.
Since there is less than 19 hours
Per Bothner writes:
> On 03/30/2017 03:40 PM, Mathieu Lirzin wrote:
>
>> Per Bothner writes:
>>> While I re-emphasize this is my personal roadmap of how I think texinfo
>>> should
>>> evolve (not everyone agrees ...), I think there is general agreement of the
>>> value of a nice JavaScript-base
On 03/30/2017 03:40 PM, Mathieu Lirzin wrote:
Per Bothner writes:
While I re-emphasize this is my personal roadmap of how I think texinfo should
evolve (not everyone agrees ...), I think there is general agreement of the
value of a nice JavaScript-based UI for texinfo/html documents.
Yes, th
Hello,
Per Bothner writes:
> On 03/29/2017 01:21 PM, Mathieu Lirzin wrote:
>> As suggested by Per, I have re-read his texinfo roadmap in more details.
>
> While I re-emphasize this is my personal roadmap of how I think texinfo should
> evolve (not everyone agrees ...), I think there is general a
On 03/29/2017 01:21 PM, Mathieu Lirzin wrote:
As suggested by Per, I have re-read his texinfo roadmap in more details.
While I re-emphasize this is my personal roadmap of how I think texinfo should
evolve (not everyone agrees ...), I think there is general agreement of the
value of a nice JavaS
Hello,
Gavin Smith writes:
> On 20 March 2017 at 22:37, Per Bothner wrote:
>> 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
On 20 March 2017 at 22:37, Per Bothner wrote:
> 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 inte
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 w
Hello,
I know I am a bit late but after a second thought, I have decided to
candidate for the project "JavaScript for info-style navigation".
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
12 matches
Mail list logo
