It has been a while since last post, so here are a few updates. While going for a wander reading about the new GWT release, I discovered another project by the Google Code team called [http://code.google.com/docreader docreader]. It looks like it could be a nice way to offer a better structured view of the wiki pages, so I have created a new issue for this task and started to make a table of contents page. You can see the current result here. Next step will be to also create an Index page ... and maybe bug the team about the ugly double titled start page.
Hopefully, it will also soon be time for a minor version release of the 1.x branch with the accumulated bug fixes. I hope to get this done first thing when I will get back to working on Re-Mote. I will also have to finish the work on the compile host for the DIKU Testbed, which currently works only for smaller projects.
Man Pages and 2.0 Preparation
I finally finished the man pages for the scripts and programs in MCI. Together with the improved installation instructions for the mote host it should now be a little easier to figure out how to setup this part of the testbed.
Anyway, it has all been pushed it to the remote-mci-1.x branch, which I also finally merged back into my trunk. I haven't decided whether it is worth creating a 1.x branch for SVN; time will tell. However, Rosta mentioned during our talk today that some fixes from his side might be expected in the future and I have some things I would like to fix myself to make 1.x more robust.
In other news, preparation for 2.0 will start to take place and today's chat was a step in that direction. We discussed what the focus should be, and went into detail with a few of the bigger task ahead, such as the administrator interface. To help with this preparation, I made some changes to the wiki to introduce a better framework for the enhancement proposals inspired by TinyOS' TEPs and Python's PEPs. The REP structure is still very informal and simple, since it is still not clear to what extent this will be used. Some work remains to convert the old design documents to the new structure.
Anyway, it has all been pushed it to the remote-mci-1.x branch, which I also finally merged back into my trunk. I haven't decided whether it is worth creating a 1.x branch for SVN; time will tell. However, Rosta mentioned during our talk today that some fixes from his side might be expected in the future and I have some things I would like to fix myself to make 1.x more robust.
In other news, preparation for 2.0 will start to take place and today's chat was a step in that direction. We discussed what the focus should be, and went into detail with a few of the bigger task ahead, such as the administrator interface. To help with this preparation, I made some changes to the wiki to introduce a better framework for the enhancement proposals inspired by TinyOS' TEPs and Python's PEPs. The REP structure is still very informal and simple, since it is still not clear to what extent this will be used. Some work remains to convert the old design documents to the new structure.
User Manual with Screenshots and 1.x Branch
Wow, it is nice to see that the announcement of the 1.0 release on wsnblog.com inspired a lot of people to visit the project page and have a closer look. This is all really encouraging so today I have made some screenshots to try to exemplify what Re-Mote has to offer from the users' point of view. Most of the screenshots have also been integrated into the user manual, which now presents itself much more visually appealing.
I would also like to announce the creation of a new branch for remote-mci-1.x, which already have one embarrassing fix of a typo in the code for setting up the baud rate for the dig528-2 platform. It slipped through because the dig528-2 UDEV rule had the same typo, making it all work perfectly until the rule file was fixed right before the release. Although the fix was easy, it raises the question if it would not be better to also make platform specific UDEV scripts responsible for specifying the baud rate. Something to consider for the upcoming planing of the next release ...
I would also like to announce the creation of a new branch for remote-mci-1.x, which already have one embarrassing fix of a typo in the code for setting up the baud rate for the dig528-2 platform. It slipped through because the dig528-2 UDEV rule had the same typo, making it all work perfectly until the rule file was fixed right before the release. Although the fix was easy, it raises the question if it would not be better to also make platform specific UDEV scripts responsible for specifying the baud rate. Something to consider for the upcoming planing of the next release ...
Re-Mote Testbed Framework v1.0
With the dust settling after some last minute hectic renaming and reorganization taking place it is time to celebrate. Finally it's here: version 1.0 has been released and is ready to be deployed at a testbed near you!
This release is the first featuring code development in collaboration between DIKU and CIT. It brings many enhancements mainly to the mote control infrastructure, which has been made more portable and configurable and updated to use UDEV for mote device discovery. The major contribution of this release is the support for MicaZ and Tmote Sky in addition to the original DIG528-2 platform.
While most of the effort has gone into the darker sides of the testbed framework, users of the Re-Mote Control Client will find that upgrading from the preview builds will bring a few nice enhancements, such as improved support for the different mote platforms.
This release is the first featuring code development in collaboration between DIKU and CIT. It brings many enhancements mainly to the mote control infrastructure, which has been made more portable and configurable and updated to use UDEV for mote device discovery. The major contribution of this release is the support for MicaZ and Tmote Sky in addition to the original DIG528-2 platform.
While most of the effort has gone into the darker sides of the testbed framework, users of the Re-Mote Control Client will find that upgrading from the preview builds will bring a few nice enhancements, such as improved support for the different mote platforms.
Javadocs Online and a Hope of Are-ee-pe
Just a minor update to announce that javadocs for the remote-ws and remote-gui components are now available online. The web service documentation is so far the most polished one, and should serve as a good introduction to some of the client server interaction.
Also, I have started a wiki page with some enhance proposals for the next major milestone. Right now it is just a simple "scratch" page with loose ideas, but hopefully it will evolve into a useful resource for planning the future development and collaboration. Expect REPs (Re-Mote Enhancement Proposals) to land in the future!
Also, I have started a wiki page with some enhance proposals for the next major milestone. Right now it is just a simple "scratch" page with loose ideas, but hopefully it will evolve into a useful resource for planning the future development and collaboration. Expect REPs (Re-Mote Enhancement Proposals) to land in the future!
Re-Boot Testbed
A lot of things have happened in the last week. In preparation for the upcoming release, all the repositories have been tagged as version "1.0pre0", however no archives have been uploaded to the project download area. Some minor cleanups have also managed to sneak in. Other project updates include closing of some more issues related to Milestone1.0.
In other news, installation of the DIKU Testbed server is almost complete and a small test setup is already up and running in my office with PXE booting mote hosts. I probably won't have time to make the first test deployment before Thursday or Friday, however, with the hardest parts of the reinstall out of the way the rest should be over quickly. I hope to get time to write down a walk-through or howto covering the basics of what I did either here in the blog or at the project wiki.
Related to the reinstall, I made an effort to try and strip down the webapps/axis directory from axis-1.0. The idea is of course to be able to provide an easily deployable web application archive (.war file) complete with web service descriptors and associated jar files, as well as a simple administrator interface and dependency validation similar to that offered by the example axis web application. It is still a work in progress in terms of integration, but I feel it is a good start.
In other news, installation of the DIKU Testbed server is almost complete and a small test setup is already up and running in my office with PXE booting mote hosts. I probably won't have time to make the first test deployment before Thursday or Friday, however, with the hardest parts of the reinstall out of the way the rest should be over quickly. I hope to get time to write down a walk-through or howto covering the basics of what I did either here in the blog or at the project wiki.
Related to the reinstall, I made an effort to try and strip down the webapps/axis directory from axis-1.0. The idea is of course to be able to provide an easily deployable web application archive (.war file) complete with web service descriptors and associated jar files, as well as a simple administrator interface and dependency validation similar to that offered by the example axis web application. It is still a work in progress in terms of integration, but I feel it is a good start.
Reinstallation Count-down
The last few days have been a bit slow with no real progress on the testbed. I've spoken with Janus, the engineer at DIKU, about how we should proceed and he has provided the missing hardware pieces for what will become testbed.diku.dk. With that out of the way, I hope to begin setting up a small test environment in my office by the end of the week. It will be good to have the system running again; not being able to properly test is not very inspiring.
While wasting my time on the great internet the other night I again stumbled upon Google Web Toolkit. It looks good, quite easy to use, and has a nice framework for testing with both command line support and plugins for both NetBeans and Eclipse. I think it will fit all the needs of the admin interface and help to keep as much as possible of the high-level server code in one language. Though I still need to read more about how the server-side part of the toolkit works, the dream of a future web service module with easy installation and a nice admin interface lives on. It will also be fun to see if the database part can be merged into the web service module so that site specific costumization "plugins" defining new web services will be possible.
[ BTW, I played with Yahoo pipes yesterday and created the "Recent Changes" RSS feed displayed in the right column. It aggregates commit activity from the four DIKU git repositories on repo.or.cz. ]
While wasting my time on the great internet the other night I again stumbled upon Google Web Toolkit. It looks good, quite easy to use, and has a nice framework for testing with both command line support and plugins for both NetBeans and Eclipse. I think it will fit all the needs of the admin interface and help to keep as much as possible of the high-level server code in one language. Though I still need to read more about how the server-side part of the toolkit works, the dream of a future web service module with easy installation and a nice admin interface lives on. It will also be fun to see if the database part can be merged into the web service module so that site specific costumization "plugins" defining new web services will be possible.
[ BTW, I played with Yahoo pipes yesterday and created the "Recent Changes" RSS feed displayed in the right column. It aggregates commit activity from the four DIKU git repositories on repo.or.cz. ]
Subscribe to:
Posts (Atom)