[Tinyos Core WG] 2.0.2 release plans

[Vlado Handziski]

On 7/10/07, David Gay <dgay42 at gmail.com> wrote:
>
> On 7/10/07, Vlado Handziski <handzisk at tkn.tu-berlin.de> wrote:
> > Do we have any policy again mixing of platform-dependent and
> > platform-independent applications in the top /apps dir? This would be
> the
> > only platform specific app in the top dir apart from the TOSSIM apps.
> the
> > /apps/tests is currently a mixed bag.
>
> I'm happy to have it live elsewhere, but note that:
> -  it's only platform dependent because of sensor requirements, i.e.,
> with an appropriate sensor board it could run elsewhere.
> - I'm not sure how we should organise platform/sensorboard
> dependencies - platform or sensorboard dependent directories don't
> seem to really cut it either


I understand, it is just that when the name of the application does not
suggest otherwise, people tend to expect that it works on "their" platform
also :)

Note btw that in 1.x we attempted to specify in Makefiles which
> platforms were supported (check PLATFORMS= lines, IIRC) - that's
> another one of making it more explicit that an app is not supported
> everywhere.


I think this is much better then failing on #ifdef in the code.

> On another note. One of the things I hated most in TinyOS 1.x were the
> > platform #ifdefs. We managed to keep the T2 code pretty clear  until
> now,
> > but with this app,
>
> Well for AntiTheft, the #if's are for getting access to the
> LowPowerListening interface. If we specify a place/name for that to
> live, we can remove them...
>
> > platform dependent code in separate components, with clear interfaces
> > between them and the platform-independent logic.
>
> Maybe we can setup a convention of providing platform-named
> directories in apps to support this? (the Makefile can say PFLAGS +=
> -I%p to support that)
>
> i.e., AntiTheft/Nodes/mica2 would contain a LowPowerListeningC
> component with the appropriate wiring to LowPowerListening? (not for
> 2.0.2, though)
>

This is a good idea. It will give the users a pattern that is easy to
understand. And as Phil said, for 2.1 we should try to address the
underlying reasons.

Vlado
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.millennium.berkeley.edu/pipermail/tinyos-2.0wg/attachments/20070710/2c5337b5/attachment.html