General Actions:
Log-in
Wiki:
Courses
▼
:
Document Index
»
Space:
HCCF2010
▼
:
Document Index
»
Page:
Footprint
Search
Page Actions:
Export
▼
:
Export as PDF
Export as RTF
Export as HTML
More actions
▼
:
Print preview
View Source
Human-Centered Computing Foundations, Fall 2010
»
Student Projects
»
Footprint
Wiki source code of
Footprint
Last modified by
Zachary Clark
on 2010/12/08 16:50
Content
·
Comments
(1)
·
Attachments
(6)
·
History
·
Information
Hide line numbers
1: This is the Footprint Project Page. If you want to keep up with our work closely, you can follow the codebase as it changes [[on Github>>http://github.com/spyyddir/Footprint]]. 2: 3: 4: Our final report is available [[here>>Final Report (Team Cacti)||title="Final Report for Footprint"]]. 5: 6: 7: = Project Description = 8: 9: Footprint is an application based around the idea that by showing user's their environmental impact based on their travel, those people may change their habits. The project is based heavily around using the Fousquare API to get data around where a user has been, which the app then uses to figure out how far someone has traveled. Our involvement in the project is to help move it forward from its humble beginnings, by working on making the use of the application easier by a user. In its current state it only supports a single user per deployment, and is not friendly in its interface or design. Our goals are to improve this user signup / sign in process, as well as improving the interface. There has also been discussion of adding Google Maps functionality to help map out where a user's checkins occur, but this may be beyond the scope of the class. 10: 11: = Organization / Role Distribution = 12: 13: **Team Leader**: Zac Clark 14: 15: **UI Team**: Thomas Cavalier, Luke Mattingly 16: 17: **Back-end Team**: Jacob Burton, Aaron Stockton 18: 19: = Member Specific Info = 20: 21: ==== Zac Clark ==== 22: 23: Since starting the project I have taken the leadership role and worked on getting the team set up to easily share code and work together. I took the base application code provided by our sponsor and wrote up a series of detailed instructions on how to get it running on each of our machines so we can work on it. This involved minor re-writes to the application as well as adding some new functionality for setting up the database. Then I put the code in version control on Github, with a setup to allow easy collaboration between team members. After that I refactored the codebase to logically separate different pieces on functionality for easier updates. 24: 25: Over the next few weeks I plan on managing the group, keeping everyone on task, and helping out where needed. I have some experience in almost every area this app covers, so I know how to build many of the needed features, at least in abstract. If any other team members get stuck on their task, I can lend a hand getting them in the right direction. I'll also handle keeping the codebase clean, such that changes do not trample each other and co-exist nicely. 26: 27: 28: ==== Thomas Cavalier , Luke Mattingly ==== 29: 30: Since starting the project we have looked into foursquare, set up GitHub on my laptop, forked and cloned to Footprint repository, and set up Footprint to run on our computers. We have also created wireframes for our user interface and sketched out some Footprint logo ideas. 31: 32: Thomas has been working towards: 33: Over the next few weeks I plan continuing my work on the wireframes and help implement some of the UI ideas. Also, I will be helping to finalize the UI by picking a color scheme, general layout, etc. 34: 35: Luke has been working towards: 36: 37: Over the next few weeks I will be looking at 'good design' and how to integrate good HCC into our UI. I will continue working on wireframes, and from there begin to create a solid plan. I will be looking at usability, accessibility, and overall physical appeal. 38: 39: 40: ((( 41: (% style="border-width: 0px 0px 1px; font-family: inherit; font-size: 1.33em; font-style: inherit; font-weight: 400; margin: 20px 0px; outline-width: 0px; padding: 0px; vertical-align: baseline; line-height: 1.2em; border-bottom: 1px solid rgb(204, 204, 204); color: rgb(0, 90, 131); display: block; overflow: hidden;" %) 42: ==== (% style="border-width: 0px; font-family: inherit; font-size: 19px; font-style: inherit; font-weight: inherit; margin: 0px; outline-width: 0px; padding: 0px; vertical-align: baseline; line-height: 1.2em; border-bottom-style: none; display: inline; position: static;" %)Aaron Stockton, Jacob Burton(%%) ==== 43: 44: ((( 45: (% class="Apple-style-span" style="font-size: 14px;" %)Since the start of the project we have set up a GitHub account, forked and cloned the Footprint project, and got a bare bones version running on our computers.(%%)This took us setting up development servers on our home machines so we can get a localhost from our browsers. 46: 47: Currently, Footprint is still a very independent application. We plan on starting by getting it to where Footprint relies more heavily on Foursquare. This will allow us to use Foursquare's login and user ID's. This will make the application much more convenient as it will then only require a user to log in through Foursquare and then they are set. 48: 49: There is a lot of work that needs to be done with code management as well. All of the back-end is shoved into a single file which makes for a confusing flowchart and it will only become more difficult to modify as time goes on. These are the starting points. 50: 51: Over the next few weeks, and after we get the existing code organized, we will venture into more complex development. For instance we will attempt to tie in the google maps API which could potentially allow for one touch updates. This is about as easy as it could get for the users. 52: 53: Of course, as time moves on and we dive further into the project, we will find more stuff that we will want to try out. We will keep everyone updated as to our ideas. 54: 55: = Sketches/Mock Ups = 56: 57: Here are some of the original ideas we had for Footprint 58: 59: [[image:FootprintHomeLayout.jpg||height="200" style="display: block; margin-left: auto; margin-right: auto;" width="300"]] 60: 61: Here are a couple sketches of potential logos. 62: 63: [[image:FootprintHomeLayout2.jpg||height="200" style="vertical-align: middle;" width="300"]] 64: 65: Here are potential UI mockups for the login and main page. These are rough wireframes and sketches and will be improved upon. 66: ))) 67: )))
Course Pages
Home
Roster
Assignments
Schedule and Syllabus
Course Announcement
Lecture Material
Relevant Resources
Questionnaires
Student Projects
Voluntary Contributions
Blog
Tutorials
Recently Modified
MSC Final Project ...
MakeShiftCrew Proj...
Embedding Content
Human-Centered Com...
Assignment12KyleMa...
See More Changes
Recent Comments
Recently Created
WebPreferences
|
RatingStats
|
palen
|
ksiek
|
kena