Re: Callbacks for Yueliang : Speaking Lua for Screenreaders

[KHMan <keinhong@...>]

Veli-Pekka Tätilä wrote:
> KHMan wrote:
> <heavy snippage>
>> Yueliang is a casual project with no clear goals, so it's in bits
>> and pieces. You can follow what the bits and pieces are by looking
>> at what the test scripts use.
>>
>> test_lparser_mk3.lua in the test directory exercises the
>> lparser_mk3.lua parser, and uses the llex_mk3.lua lexer as well.
>> The parser_log directory shows the result of the message logger
>> calls, basically showing which functions are called during
>> parsing, and it closely follows the original C equivalents.
> [snip snip] If they are locals rather than object fields then ummm I
> reckon I'd need to access the callers namespace then, too. Technically
> overriding log is still an object method but it is also my own code, not
> really extending the parser per se. This introduces a dependencey on the
> parser internals. but at this point in which I'm trying to figure out
> whether attempting to improve Lua code read outs for screen reader users
> like me is worth it in the first place, even that quick n dirty solution
> would probably do fine. In fact I think I'll do just that.

A very brief note. I've just updated Yueliang with simple variable
management code to classify variables into locals, upvalues or
globals. It's around 100 lines of added code only. The release
include sample parser log output also, but note that parts of the
output, such as internal variables in a 'for' loop, may not be
relevant to a screen reader.

HTH,
-- 
Cheers,
Kein-Hong Man (esq.)
Kuala Lumpur, Malaysia