> it's needed so seldom, that in the few cases where I *could* have > think I ever actually used this feature in w3m - probably because > Well, this is one thing I originally meant to implement but
ELINKS KEYBINDINGS CODE
> My code also has a basic implementation of page marking * a PATRICIA trie implementation (trie.c) * a compiler for the above spec (compiler) * a spec for the system data (inputData.vic) * a bunch of bindable commands (key-commands.c) I've seen a few vi-inspired projects that could do with this functionality, so I've coded it keeping open the idea of sucking most of it into a shared library. Here are the files and patches for the input system. Would be great if you could implement it.ītw, this page collects information about support and use of - leif halvard silli Text based browsers has a certain user base amongst blind users - purpose is to point to a description of an image, so theīlind can understand it better than a short text may do. Pretty uniform support for image maps, and I hope that they couldįor Lynx that they too implement - see Lynx' mailinglist and PS: I have also filed the same bug for Elinks. Perhaps a combination: Offer a hard coded text, in combinatio with the The address of the link as link text, is probably up for debate. Whether netrik should do the same, or if netrik should simply present
Text, in order to replicate how works in Jaws. element provides "Press enter for long description" as the link And hence in the example, the attribute of the In Jaws's case, the hard coded text is "Press enter for longĭescription". However, for such as the well known Jaws, offers a "hard coded" text. One particular detail: For image maps, the link text is provided via Mimic the behavior by using a simple image map.) |1] example has been crafted solely in order to show one may More or less the same way the following image map example works: Thus, practically speaking, I would expect to work in netrik, Map, where the URL inside represents the link of the image I have a concrete proposal for how it should be implemented: The bestĪpproach seems to me to be to implement it as if the image is an image Netrik currently has no support for provides "link to long description (complements alt)".Įxample page: chance that netrik could implement support? Thus prioritizing longdesc support probably makes sense. That's where most feedback came from in the past :-) Regard - however, the code actually implementing the translation would Longdesc would indeed be kinda similar in this I think it should be pretty easy though simply to translate image mapsĪs a list of links. Not a high priority feature - I don't remember ever missing it. Well, there is actually no support for image maps in netrik so far. > netrik currently has no support for Doesn't sound too hard to fix. On Wed, at 03:13:53AM +0200, Leif Halvard Silli wrote: I'd be happy to test, whenever you have something! > Thus prioritizing longdesc support probably makes sense. > Text based browsers has a certain user base amongst blind users But I guess it is also valuable to have similarĬoncepts even if the code is different. > - however, the code actually implementing the translation would > I think it should be pretty easy though simply to translate image maps Lynx, Elinks, Links, w3m and retawq all have it. Then I think netrik is the only text browser without image map support. > not a high priority feature - I don't remember ever missing it. > Well, there is actually no support for image maps in netrik so far. > map, where the URL inside represents the link of the image > approach seems to me to be to implement it as if the image is an image > I have a concrete proposal for how it should be implemented: The best > netrik currently has no support for Hm.
0 kommentar(er)
