Re: [g-a-devel] RFC: AtkText simplification

Hi. For Gecko it's much easier if TEXT_BOUNDARY_FOO constants were the same with IAccessible2 constants since it allows to have shared implementation. I should notice however that IAccessible2 says to return no word for TEXT_BOUNDARY_WORD if the given offset is outside a word. It seems it makes the presence of getTextBefore/After methods very helpful.

P.S. it's not fair to deprecate these methods after it seems I understood how to implement them :)

Thank you.

On Sun, Apr 14, 2013 at 4:09 AM, Joanmarie Diggs <jdiggs igalia com> wrote:
Hey all.

As many of us know, AtkText is one thorough interface. :) So thorough,
in fact, that it boggles the minds of those implementing it and sends
many others running to create PangoLayout instances so that they can use
GailTextUtil to do the implementation for them.

So I am here to propose we simplify AtkText and do it *now* i.e. while
we are very early in the GNOME cycle. In particular, I would like to
suggest for your consideration the following two changes:

1. Deprecate atk_text_get_text_{before,after}_offset()

In the first case, clients such as Orca would use (through AT-SPI2)
atk_text_get_text_at_offset(). If the text before or after a given
offset were desired, clients would make a second call having gotten the
needed offset from the first call.

In the second case, clients such as Orca would use (through AT-SPI2) a
brand new set of TEXT_BOUNDARY_FOO boundaries. My guess is that we'd
want it to mimic the behavior of the current START results, but that
will require some investigation to be sure.

In order to facilitate this simplification getting under way, I will
remove Orca's use of atk_text_get_text_{before,after}_offset().

gnome-accessibility-devel mailing list
gnome-accessibility-devel gnome org

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]