Note though that while this does adhere too the MQTT v3.1 spec. as far as messages are concerned; currently all messages you publish are QoS 0 (lowest level) and all subscriptions are QoS 2 (highest lvl).
But it does work in sending messages back and forth to clients through a broker (which isn't included).
I'm trying to figure out how to get PDE to find my contributed mode - however its not playing nice. I'm guessing I'm doing something wrong, does anyone have a short TODO list when building modes? I've not found a template yet (or any other information on the wiki)... but from browsing ModeContribution.java I've gathered the following hints on what needs to be done so that the PDE finds my modes.
It has to extend Mode (or any subclass thereof)
It has to be placed in the "modes" folder (which is automatically created by PDE)
It has to be placed in a folder, named after it's main class (the one subclassing "mode" I suppose?)
There has to be a "mode" folder within that folder.
I probably missed a dozen "rules" here, but hey, it's a start... anyone care to fill me in?
Hey, I've been browsing the source for the new processing implementation and I can't for the life of me find a way to grab the application context from the PApplet. Does someone know a way to do that?
I need to pause the sketch launch until a certain task has finished, and I'd like to add a feedback to the user in the shape of some sort of progressbar... so I was thinking the built in one might be handy.
This is outside of the actual sketch (a library), so any generic tricks like getApplicationContext() are not available.
What about implementing some sort of generic handler in the PApplet class for tasks like this, is that an option?