00:13 <androidusr> Have a quick question about PilBox before deciding whether I should delve deeper into it.  Is it possible to fully access all aspects of the Android Accessibility API from within PilBox?  If I need to extend a class, can I do that from within PilBox, or just implement interfaces?  Can apps that are created in PilBox run in the background?  Can

00:13 <androidusr> they send/receive all different types of accessibility events?  In short, are there any limitations or other disadvantages to building accessibility apps (e.g. for automating other apps) from within the PilBox framework than from using say Kotlin + Android Studio?

00:21 <aw-> androidusr: hi

00:21 <androidusr> hi

00:21 <aw-> i think you'll need to wait for the author to answer those questions, not many others in here have deep knowledge of the PilBox functionality

00:22 <androidusr> Thanks ... I may try on the mailing list too if I don't hear anything back.

00:22 <aw-> my best guess is PilBox doesn't impose any limitations that aren't imposed by Android itself

00:24 <androidusr> Thanks ... that's what I initially suspected.  But I wasn't able to find an example of extending a class, or how to create an app that runs in the background since the docs that are available for PilBox are still pretty sparse at this point.

00:25 <aw-> yes you'd have to look at the sources for existing apps to see how things have been done

00:25 <aw-> or wait until abu[m] / Regenaxer are online

00:27 <aw-> he's here pretty much every day so just wait a few hours for him to wake up ;)

00:27 <androidusr> Will stay logged in ... thanks again.

06:52 <abu[m]> Hi androidusr! Thanks aw-!

06:53 <aw-> hi abu[m]

06:54 <abu[m]> I would say you can access *almost* all aspects. But you cannot write Java methods of course

06:54 <aw-> i think that person left the chat haha

06:54 <abu[m]> oh, grr!

06:55 <aw-> does PilBox provide an function to access all aspects of the android API?

06:55 <abu[m]> IIRC there are *some* quirks of the Java lang which are not supported

06:56 <abu[m]> Not an issue of the Toolbox by itself

06:56 <abu[m]> As he suspected, we can only write interfaces to extend the toolbox

06:56 <abu[m]> Not sure what he meant

06:57 <abu[m]> Overwrite Java methods of existing classes?

06:57 <abu[m]> Or implementing new classes? This is not possible. Instead, implement Lisp classes.

06:59 <abu[m]> Yeah, I see "02:47 androidusr has quit". I should look more closely first! ☺

07:38 <aw-> don't worry, my IRC client doesn't even show user quit messages (by choice)

07:39 <abu[m]> I also switch it off sometimes, as it gets too noisy

07:39 <aw-> it was getting too noisy, but it only hides them for idel users

07:39 <aw-> idle* users

07:39 <abu[m]> Some people like alexshendi enter and quit all the time

12:42 <brandelune> anybody attending emacsconf tomorrow ? Or is it today ?