On Thu, 31 Mar 2005 14:12:15 -0800, Neilh10 <[EMAIL PROTECTED]> wrote: > #-----Original Message----- > #From: David Gay [mailto:[EMAIL PROTECTED] > #Sent: Wednesday, March 30, 2005 8:58 AM > #To: [email protected] > #Subject: Re: [Tinyos-users] path level testing tools > # > # > #On Tue, 29 Mar 2005 15:33:43 -0800, Neil Hancock > #<[EMAIL PROTECTED]> wrote: > #> I really like the ability to be able to see in app.c how the > #components are > #> linked together. I would think that as nesC is more widely used, a tool > #> would evolve that could show the call graph. > # > #Note that nesdoc ('make docs') gives you the wiring graph. > > Yes thanks, I realized that after I wrote it. Since then I've been using > 'make docs' a lot to figure out how some new components connect - and I > still have more confidence in looking at app.c for final determinations of > how it works. > For instance the component Graph of the application only shows the "Call > Graph" and not the "Event Graph" that I can figure out.
It shows the wiring of interfaces, with an arrow from "uses" to "provides". This matches the command direction and is the opposite of the event direction. David Gay _______________________________________________ Tinyos-users mailing list [email protected] http://mail.Millennium.Berkeley.EDU/mailman/listinfo/tinyos-users
