-- blog set up successfully
-- working on client/server communication, observing inconsistency between phones. Same code, different results. We would blame it on gingerbread, but the code doesn't work properly on Derek's droidx either.
-- looking into more primitive tcp/ip approach in case it is a problem with kryonet. Derek will continue to work on it while I research the alternatives.
put about 2 hours in tonight, its getting too late to do good work.
Monday, March 28, 2011
We're having difficulties with the networking communication between devices, specifically discovering the servers from clients.
We have the following three phones:
My Droid X (Phone A)
The Nexus One (Phone B)
Alan's Droid X (Phone C)
Phones A and B can successfully host games. Phone C can discover games. Phone A and B cannot discover games; thus we are unsure if Phone C can host games, but we think it probably can.
We adjusted the timeout period to discoverHosts() to no avail. I'll probably make a post to the usergroup tomorrow to find out if there's any advice available.
The next step is to investigate more basic standardized Java network communication using Socket and other base classes, potentially moving away from Kryonet if we can't get that working.
We have the following three phones:
My Droid X (Phone A)
The Nexus One (Phone B)
Alan's Droid X (Phone C)
Phones A and B can successfully host games. Phone C can discover games. Phone A and B cannot discover games; thus we are unsure if Phone C can host games, but we think it probably can.
We adjusted the timeout period to discoverHosts() to no avail. I'll probably make a post to the usergroup tomorrow to find out if there's any advice available.
The next step is to investigate more basic standardized Java network communication using Socket and other base classes, potentially moving away from Kryonet if we can't get that working.
First Scrum
First time we are meeting to work on this officially to track development.
For the first sprint we plan on using two agile methods: scrum and pair programming. We expect this sprint to last about two weeks. A majority of the work work will happen during this sprint, leaving the last two or three sprints for polishing.
For pair programming, we plan to meet about twice a week and work 2-4 hours a meeting. Each meeting will be logged with a blog post.
Scrums will happen on a near-daily basis. Any independent work that is done will be logged by the individual developers.
What we have in Trivioid so far:
--simple ui
--splash screen and animations
--simple server requests
--a high level overview of our communication protocol
What we plan to accomplish tonight:
--firm up host/client connectivity
--flesh out the communication protocol
Tracking progress:
By now we have established the x-pf. Obviously, we have set up a developer blog to track progress. We have started to log hours of work. Whenever any work is done by a developer, they should post on this blog what they accomplished, how many hours of work, how much productive the time spent was, the working situations (location, time of day, partners, methodologies, etc.), and how they feel (morale).
more to come later tonight
For the first sprint we plan on using two agile methods: scrum and pair programming. We expect this sprint to last about two weeks. A majority of the work work will happen during this sprint, leaving the last two or three sprints for polishing.
For pair programming, we plan to meet about twice a week and work 2-4 hours a meeting. Each meeting will be logged with a blog post.
Scrums will happen on a near-daily basis. Any independent work that is done will be logged by the individual developers.
What we have in Trivioid so far:
--simple ui
--splash screen and animations
--simple server requests
--a high level overview of our communication protocol
What we plan to accomplish tonight:
--firm up host/client connectivity
--flesh out the communication protocol
Tracking progress:
By now we have established the x-pf. Obviously, we have set up a developer blog to track progress. We have started to log hours of work. Whenever any work is done by a developer, they should post on this blog what they accomplished, how many hours of work, how much productive the time spent was, the working situations (location, time of day, partners, methodologies, etc.), and how they feel (morale).
more to come later tonight
Subscribe to:
Comments (Atom)