Saturday, December 5, 2009

The GreenDepot project

The deadline for this project was always at the back of my mind during the time our group worked on it. I have to say that I honestly had a tremendously fun time working on GreenDepot version 2.0. Unlike working on version 1.0, there was no overhead in creating the structure of our web application. Once the initial functions set up, we started throwing ideas around and figuring out how improve our application. Granted, the project was probably the worst application in our class at the version 1.0 phase. I feel that we made great progress and feel really proud of our work.

It started on the second week of November. Our groups were chosen and I was partnered up with Nate and Edwin. We had some trouble getting together to meet because of our varying schedule. Night was the only time we could meet and talk, so we talked over google chat. And for a time that sufficed, but now that I look back I think the few times we met up outside of class were really valuable. Those times allowed us to talk and make sure we were on the same page with each other.

GreenDepot is a web application that uses wicket as the basis. Wicket allows programmers to just use html a markup language and java. The application is geared toward displaying data in a meaningful manner, using WattDepot as the source for all the data. WattDepot is a open source software project that allows developers to get simulated data from the Oahu power grid. This software was the foundation for GreenDepot. Without it, we wouldn't have anything to work with. Using this data we displayed it in two ways.

First there is the StopLight page. This page shows you a meter with green, yellow and red, and acts as a sort of stoplight. It will generate data using WattDepot and based on our thresholds for what is a low carbon emission time and what is high, we indicate green for a good time and red for a bad time for using eletricity. We also provide suggested hours on the side which indicate data from yesterday which hours were best.

Secondly there is the GridInfo page. It serves as a chart that will display the 24 hours data from the date you chose as input. Right now, we have a start date input and an end date input. This way you can set the time as long as you like to get an idea of the carbon emission, whether it be for a day or ten days. This was implemented in a much easier way using google charts. I've really come to love all the software tools google offers. I never knew that google had invested so much into developing so much software for users everywhere. There is a lot to look at when you click that "more" tab in their front page.

More recently, I've added a contact page for information pertaining to our project and also changed the layout of the page. It has a smoother look and I think it doesn't look as junkie as it used to. Before the page had too much stuff that distracted the user. Now it can focus the user to the results of the page and what we have to say.

This project had some bumps, but I've tried to work on it daily and the software ICU has shown that the development side has been healthy.


This project was really hard. Wicket was hard to learn and I struggled at first. But I learned a lot. What amazed me was the amount of time I spent on this. I was really excited for this project. It really drew my attention and I think it shows that I could do this as a profession. Writing software and creating applications has a great appeal for me and I would love to continue doing it.

No comments:

Post a Comment