From: ES <ruby-ml@...>
Date: 2005-06-19T11:24:54+09:00
Subject: Re: [ANN] Frameless RDoc template ('technology preview')

Eric Hodel wrote:
> On 17 Jun 2005, at 20:02, ES wrote:
> 
>> Eric Hodel wrote:
>>
>>> On 17 Jun 2005, at 12:59, ES wrote:
>>>
>>>> == Issues
>>>> - It is all on one page and there is a bit of JavaScript magick   
>>>> involved
>>>>   so the document tends to be large and the initial load is a bit  slow
>>>>   and choppy; however, once the file has loaded, it works very fast.
>>>> - The JavaScript works but is absolutely atrocious.
>>>>
>>> It doesn't work very well with w3m.
>>
>>
>> OK; are the below items specifically what was wrong or it just  generally
>> does not work with w3m (and lynx and others)? I will try to get to  XHTML
>> 1.0 conformance before finalising in any case.
> 
> 
> The document is readable, but not navigable with w3m.  That probably  
> applies to lynx as well.  (I have found newer versions of w3m support  
> some CSS, like display: none.)

I will attempt to get that resolved; it does seem that keyboard-based
navigation works in graphical browsers (links take you to the right
place etc.) right now.

I also achieved XHTML 1.0 Strict and CSS conformance and the main
accessibility validators do not have a problem with the code as
it stands, either.

>>> The menus are just a big blob of text.  How about lists instead?
>>
>>
>> Will do!
>>
>>> JS links aren't clickable:
>>> <li><a href="#M000027" onclick="scroll_to('#M000027');  false">add</ 
>>> a></li> (untested)
>>> instead of shoving JS into the href?
>>> I bet you could do something similar with list_scroll_to, but it   
>>> would require more time than a glance for me to propose something.
>>
>>
>> Check; it is fairly straightforward in both cases.
> 
> 
> I think this will also solve the history problem mentioned by Adam.

Unfortunately not; that problem is more complex than I thought (and
now that I think about it, for good reasons). JavaScript does not
offer any direct ways to manipulate history entries (a Good Thing
in general), which means that any such manipulation that I can
think of would have to be done by reloading the document which
somewhat defeats the purpose. I will go back to the drawing board
with this (ideas/scripts) are of course welcome; for right now, I
will put in [back to top] links.


Thanks!

E

-- 
template<typename duck>
void quack(duck& d) { d.quack(); }