04:02 <z4k4ri4> Can I ask about android PilBox here?

06:35 <abu[m]> Hi z4k4ri4! Yes, sure, PilBox is also covered here.

10:23 <z4k4ri4> OK here's my background I grokk lisp but have no practical experience in it and while I used to code java j2me I've no experience in android programming

10:24 <abu[m]> ok

10:24 <z4k4ri4> So I want to make simple android app proof of concept to:

10:25 <z4k4ri4> 1) read qr code (I can see pilbox has example for it)

10:25 <z4k4ri4> 2) read rfid via nfc API

10:26 <z4k4ri4> 3) send it to another server ideally using client side SSL cert

10:27 <z4k4ri4> On rfid I only need the basic manufactured tag identifier so no need for custom read or write operation

10:27 <abu[m]> OK, so (1) and (3) are easy I think. (2) I haven't tried

10:27 <abu[m]> I thint you need something based on (setq *NfcAdapter (java "android.nfc.NfcAdapter" 'getDefaultAdapter CONTEXT))

10:28 <abu[m]> What does work here is (msg (java *NfcAdapter 'isEnabled) " enabled")

10:29 <z4k4ri4> I'm still reading and understanding both picolisp and nfc example java code

10:31 <abu[m]> I have no idea about the tag identifier

10:31 <z4k4ri4> So here's first question does the pilbox can read nfc? Do I need to custom compile the pilbox myself?

10:31 <abu[m]> Is there an API call?

10:32 <abu[m]> If there is an API in Android, you don't need to rebuild PilBox

10:32 <z4k4ri4> https://www.codexpedia.com/android/android-nfc-read-and-write-example/

10:33 <z4k4ri4> Here's example code I want to "port" to pilbox

10:35 <abu[m]> It will not be possible out of the box to have PilBox respond to intents

10:38 <abu[m]> i.e. we cannot extend AndroidManifest dynamically

10:38 <abu[m]> Only Java calls

10:39 <abu[m]> Some time ago I seem to have tried this: http://pb1n.de/?296e08

10:40 <abu[m]> If I do, I get

10:40 <abu[m]> [LISP:1] java.lang.ClassNotFoundException: android.nfc.NfcAdapter.ReaderCallback / java.lang.ClassNotFoundException: android.nfc.NfcAdapter.ReaderCallback

10:40 <abu[m]> Not sure, I did not investigate any deeper

10:42 <z4k4ri4> So I need to "rebuild" pilbox to add nfc stuff to pilbox manifest then?

10:42 <z4k4ri4> So my code can respond to nfc intent

10:43 <abu[m]> Depends what you need. If you want an IntentFilter, then yes.

10:44 <z4k4ri4> Do I need to? (still trying to grasp android API structure in a weekend :)

10:45 <abu[m]> I think you need the <intent-filter> if you want PilBox to be started externally and receive data

10:46 <abu[m]> If PilBox runs and wants to read NFC, it should be doable the normal way

10:46 <abu[m]> What I don't understand in my example above is why the class is not found

10:47 <z4k4ri4> So just normal should work?

10:47 <abu[m]> Is it because the API is not available on my phone? As I said, I did not investigate further back then (seems it was in 2019)

10:47 <z4k4ri4> No need for custom compile

10:48 <abu[m]> "android.nfc.NfcAdapter" is there, but not "android.nfc.NfcAdapter.ReaderCallback"

10:49 <abu[m]> Maybe I did something wrong

10:51 <abu[m]> You need to study https://developer.android.com/reference/android/nfc/NfcAdapter

10:53 <z4k4ri4> <abu[m]> I thint you need something based on (setq *NfcAdapter (java "android.nfc.NfcAdapter" 'getDefaultAdapter CONTEXT)) <~ thanks abu I think this just enough to get me started the right way

10:54 <abu[m]> I just tried again, and found one point

10:54 <abu[m]> (java T "android.nfc.NfcAdapter.ReaderCallback")

10:54 <abu[m]> should perhaps be

10:54 <abu[m]> (java T "android.nfc.NfcAdapter$ReaderCallback")

10:55 <abu[m]> i.e. the "$" for a local class

10:55 <abu[m]> This is always not clear from the Java references

10:56 <abu[m]> Then I get the next error: java.lang.NoSuchMethodException: enableReaderMode([Ljava.lang.Class;@7160a57)

10:57 <abu[m]> The method enableReaderMode exists, so the args must be wrong

11:04 <abu[m]> Perhaps the last arg, the Bundle. Is it OK to be null?

11:05 <abu[m]> Ah! Found the problem!! ☺

11:06 <abu[m]> The 'null' must be passed as a symbol and thus needs to be quoted

11:06 <abu[m]> http://pb1n.de/?5afef6

16:47 <abu[m]> Next version of PilBox will have 'null' auto-quoted

17:07 <avocadoist> would having standard support on build (no cygwin/etc) for Windows be too much work ? just curiously wondering

17:12 <abu[m]> The main problem is not the build, but the runtime environment. PicoLisp needs POSIX.

17:29 <abu[m]> All non-trivial parts like multiplexed I/O, terminal and process handling, child processes, interprocess communication, file control, sgnals etc. use POSIX-mechanisms

17:30 <abu[m]> PicoLisp is not just a language, it is a full ecosystem