Re: [Embedlets-dev] Re: JAPL part of specification

[Brill P. <bri...@ro...>]

I've attached the javadocs for the current cork-japl library, so you can see
how things are going... and describes the event system you where talking
about.

You will notice that I have several I2C driver already, which where ported
from the old lib... I just finished the OneWireTransportLink and Pipe for
TINI, but it hasn't been debugged yet.

Also, I've only got 3 JAPL interfaces so far Pin, Port, Temperature... and I
have yet to implement those on all the drivers I ported over.

> >Is there a list of Type ID's? Or can I use a JAPL event/action id
instead?
>
> Can you give a bit more information about the idea behind these Type IDs?

This may be something I'm misunderstanding. I've been extram.ly busy with
new work, and have only had a few hours a week to try and get this
integration thing happening.

I started Piccadilly (what I'm calling the Outpost/JAPL combo) by extending
Embedlet... the methods are fairly easy to understand.

What I don't understand is how the embeled talks to the JAPL device.
What is looked like, extending Embedlet is that the embedlet receives events
from the system... now I assumed that I would do something different
depending on the event code.


> >So, I need to know if the event I've received is a polarity, direction
> >or value event.  Also, how would the port be read? I can receive an
> >event telling the port to change its value, but how would the remote
> >app request the value from the embedlet? (it looks to me as If I would
> >have to receive a "get value" event, then generate my own event listing
> >the value.
>
> The architecture document shows Embedlets having direct references to JAPL
> peripherals so sending or obtaining information from a JAPL peripheral
should
> be done by just calling some methods on it.  I think that giving JAPL
> peripherals the ability to receive events seems like it would become messy
> fairly quickly because then the JAPL peripheral would need to accommodate
a
> wide number of client event schemes.

Oh, I'm not saying you have to do it that way ;) I can do all sorts of
things agains the device in the embedlet, but it would be isolated.

For instance... for a starter, I was working on the tini 8 bit port... a
nice easy one to do... Anyway, I can set it to anything I like, but its
meaningless unless connected to  the outside somewhere.

So... what I need to understand is how Outpost would be setting and getting
attributes of a peripheral?

- Brill