Hi MS and Jim, It is nice that you try to use it. The immediate goal for me when starting the project was to code faster and having to remember less when coding. Code completion (even though it is sorrowful simple) in nescdt helps some. Syntax highlighting is a must so that is done. The next step is maybe to get some sort of code navigation going so if you press F3 then you go to the definition of a certain variable. Another place where I found myself spending (ie. wasting) some time was trying to remember if a file was a module or a configuration. So I implemented an outline that uses the same symbols as nesdoc to show what type a file is before you open it. Small things, but still it saves some time.
Other plugins are probably more comprehensive and requires perhaps more maintenance. This UI centric plugin does not tinker with the build process (yet:-)), so that is why you did not get so much success there. My reason for this is to lower the barrier of entry for those who like to invoke make from a shell as they do today, but just want an Eclipse based editor for nesC. However, I think an easy way to do something useful is to invoke make from within nescdt and hook into the output produced by the build process. It would be possible to read the line number that causes trouble I think and provide a few of the features that make Eclipse a really nice Java IDE. My best guess is that it would take up to two years more before this plugin is fully developed. Best, Rasmus PS: Jim: thanks for the picture (http://www.enlightenedcode.net/temp/eclipse_screen_capture.JPG). Good documentation of what you meant. It (nescdt) will at *most* do what you see here: http://docs.tinyos.net/index.php/NESCDT-_An_editor_for_nesC_in_Eclipse and the target things are not done. Michael Schippling wrote: > I tried the dcg.ethz.ch version sometime ago with less than stellar > results. I don't remember the details but I think I got basically > nothing... > > I also tried this one: http://sourceforge.net/projects/tinydt/ > and again, my memory is it sort-of worked exactly once, then > stopped and no amount of reinstalling had any effect. > > As I said, I'm not good at following instructions so I probably > missed some important detail. But I have tried both of the above > a couple times thinking that might be the problem... > > I believe Ramus said that the nescdt plugin just does code highlighting > and completion now. At least he said it doesn't do any config parsing > to make it easy to navigate TOS code. So I suppose the build options > are there to make it tantalizing enough that someone might implement > them... > > MS > > > Jim Fell wrote: >> Hello Ramus, >> >> Nescdt was the first TinyOS plug-in I tried. After linking in " >> C:\Program Files\UCB\cygwin\opt\tinyos-2.x\tos" to my project, I added a >> new file, main.c: >> >> void main(void) >> { >> _NOP(); >> } >> >> However, the Create and Build options under Project -> Make Target are >> greyed out >> (http://www.enlightenedcode.net/temp/eclipse_screen_capture.JPG), and if >> I click the Make Target button in the Make Targets pane on the right, >> nothing happens. It's as if there is a path error in linking the nescdt >> plug-in with the installed tinyos on cygwin. >> >> I'm also working on installing the TinyOS Plug-in for Eclipse from DCG >> (http://dcg.ethz.ch/projects/tos_ide/). Is anyone familiar with this >> plug-in? >> >> -Jim >> >> >> Date: Wed, 30 Jul 2008 21:28:07 +0200 >> From: Rasmus Ulslev Pedersen <[EMAIL PROTECTED]> >> Subject: [Tinyos-help] TinyOS and Eclipse >> To: [email protected] >> Message-ID: <[EMAIL PROTECTED]> >> Content-Type: text/plain; charset=windows-1252; format=flowed >> >> Hi Jim and MS, >> >> There is perhaps a way to do it: An editor (Eclipse plugin) project >> for nesC was started some weeks ago. It was committed to contrib a few >> days ago, and it is not tested so much yet... >> But if you go to the contrib index; >> http://tinyos.cvs.sourceforge.net/*checkout*/tinyos/tinyos-2.x-contrib/c >> ontrib.html >> and look for "nescdt" in the "Tools" column; and then follow the links >> you will find the page in the TinyOS wiki that describes how to use >> (and extend (or fix >> bugs)) the editor (or go directly to the home page >> http://docs.tinyos.net/index.php/NESCDT-_An_editor_for_nesC_in_Eclipse). >> >> Good luck, Rasmus >> >> PS: Perhaps drop me a note if you have time to give nescdt a try? >> >>> I have been unsuccessful in repeated attempts to make either >>> of the Eclipse TOS plugins work, perhaps due to my inability >>> to follow instructions...if anyone has been successful I'd >>> love to hear about it. >> >>> However I do use Eclipse with TOS as a big search engine. >>> I create an Eclipse Project at the top of the tinyos tree >>> and make some sub-search components (I forget what they are >>> called, but under Search-File you can select areas to search). >>> Unfortunately Eclipse will only allow you to have one Project >>> in any directory tree. I haven't found a way to make sub- >>> projects for individual apps because TOS seems to insist on >>> having it's devel tree tightly integrated. >>> MS >>> >>> >>> >> Jim Fell wrote: >>>> / Hello. I?m hoping to develop with TinyOS using Eclipse on a Windows >> XP />/> platform. In installed the recommended MSP430 RPMs from this >> page: >> />/> />/> />>/ />>/ >> http://www.tinyos.net/tinyos-2.x/doc/html/install-tinyos.html >> />>/ />>/ />>/ />>/ Now, in Eclipse I?m unsure as to which directory >> I should link my />>/ Eclipse TinyOS project to for a proper build. >> I currently have it />>/ linked to here: >> />>/ />>/ />>/ />>/ C:\Program Files\UCB\cygwin\opt\msp430 >> />>/ />>/ />/> />/> Is this correct, or is there a better folder? >> />/> />/> />>/ />/> Thanks, >> />/> />/> />>/ />/> *Jim Fell* _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
