embedlets-developer

[Embedlets-dev] Re: Adapter

[Andrzej J. T. <an...@ch...>]

> The description for the org.embedlet.Adapter class currently reads as follows:
> 
> 'The Adapter class is the base class for all Embedlets'
> I think that 'Embedlets' here should be 'Adapters'.  

The newer source file in CVS has been corrected already (I posted about that 
a week ago).

> Also, could a more
> detailed description of what an Adapter is be added here?

Be my guest! ;-)

Once we figure out what an Adapter looks like, the docs will be updated.

Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com

Re: [Embedlets-dev] Re: Adapter

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

I've begun going through the Embedlet/Outpost/Outhouse source and have a
question (and more to come).

Is the timer service you have set up emulating a hardware timer, or is it a
service in general? (I think a "service in general" would be useful).

- Brill Pappin

[Embedlets-dev] code conventions request

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

Just a "convention" request.

It would be helpful if everyone explicitly specified their imports rather
than use the ".*" global import... it makes it much harder to find out where
something came from when tracing/reading the code...

the code-base is still fairly small, so it's not impossible to find things,
however it will soon become a major pain.

- Brill Pappin

Re: [Embedlets-dev] code conventions request

[Ted K. <tk...@ya...>]

Brill stated:

> It would be helpful if everyone explicitly specified their imports rather
> than use the ".*" global import... it makes it much harder to find out where
> something came from when tracing/reading the code...

I would second this if it is feasible.


Ted

__________________________________________________
Do you Yahoo!?
Yahoo! Web Hosting - establish your business online
http://webhosting.yahoo.com