On 12/11/14 17:17, Magdalen Berns wrote:
Hi Alejandro,
Great idea! I'm happy to clone that and add some javascript and python
work, if this is useful. From my end, I would be keen to see some C
examples on there as I feel this would be very informative.
Ok. As I mentioned, right now there are more C examples that other
languages examples. So a first task could be port those C examples (and
functionality) to other language. Until they became somewhat mature, I
prefer to maintain it as a private github repository. Anyone can use
github issues and pull request to propose new code, instead of GNOME
bugzilla.
I suspect emphasising good documentation practice for this module will
increase it's usefulness to those wishing to learn from the examples
themselves. Perhaps it is worth taking some time to establish some
sort of "documentation practices" guide for the module so that
developers wishing to add code examples in for each of the relevant
languages concerned, are prompted to mind to that stuff when
submitting new examples?
Ok, but I don't think that something really complex or formal are
needed. Eventually I will write a informal guide. In general, I think
that the more important aspect is keep in mind that those are examples,
not full programs, so they should be small, and probably focused on
specific features/API of the libatspi library.
Regards,
Magdalen
On Wed, Nov 12, 2014 at 3:24 PM, Alejandro Piñeiro
<apinhe...@igalia.com <mailto:apinhe...@igalia.com>> wrote:
Hello,
recently Joanmarie asked me if I had any atspi example written in
javascript, and I started to search my disorganized folder of
custom scripts, and I also found several examples most of them
written in C (libatspi), and one in javascript (libatspi with
gobject introspection).
Right now there aren't any similar thing on any official
repository, so I cleaned them up and uploaded on a private github
repository:
https://github.com/infapi00/atspi-examples
They are basic stuff like list the available accessible
applications, dump the accessibility hierarchy of a given app and
print out the current selected/focused accessible object on each
state change.
The next immediate tasks would be have equivalent examples of the
current C ones written in javascript and python examples (both
using pyatspi2 and gobject introspection). Then we could think on
adding more examples.
Although they need some more cleaning, I think that it would be
worth to eventually move them to a gnome repository. Initially I
was thinking on putting them directly at at-spi2-core repository,
but that would prevent to add non-C examples without complicating
too much the configure. So I think that if they become part of a
gnome repository, it should be also independent of at-spi2
repository. Would be somewhat similar to gnome-shell and
gnome-shell extensions. Opinions?
BR
--
Alejandro Piñeiro (apinhe...@igalia.com <mailto:apinhe...@igalia.com>)
_______________________________________________
gnome-accessibility-devel mailing list
gnome-accessibility-devel@gnome.org
<mailto:gnome-accessibility-devel@gnome.org>
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
--
Alejandro Piñeiro (apinhe...@igalia.com)
_______________________________________________
gnome-accessibility-devel mailing list
gnome-accessibility-devel@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
