Hopefully this is more to mithro’s liking
I did my best to at least link to one or two of the products of my work for each day.
This Week
- Monday:
- “Shelled out” the ruleset a little more by adding all create* classes. diff.
- Converted from basic Galaxy type to a class with a bonus integer that indicates the bonus garnered for owning the entire constellation/galaxy. commit.
- Added “Armies” Integer to the Planet class. (Later removed)
- Encounter a Bus Error when launching the server in a certain way - filing a bug report next monday. archives.
- Tuesday:
- A large portion of the day was spent trying to debug the bus error using gdb and ddd.
- Mithro taught me some good methods for asking for help/filing bug reports. instructions. help post.
- Wednesday:
- Added code to ensure all objects are visible. commit.
- Made note of a bug wherein client would not download objects. I later found that the Planet’s Frame was not being packed with enough data.
- Thursday:
- Converted “Armies” Integer to a Resource; Reinserted resource setters/getters and Frame packing code. Client now loads and displays universe properly. commit. results (really low res).
- Attempted to phase out Star Systems with Planets and in its stead implement lone Planets. It turns out there is a bug where lone Planets do not display in the client. Reverted the change.
- Did research and gave names to all stars corresponding to their relative positions in their constellations. names.
- Friday:
Next Week:
- Spread out star positions to make it more clear the boundary between constellations.
- Implement an adjacency matrix to represent connectivity between stars. This will provide a 2D-array to iterate down a row to discover a star’s neighbors.
- File bug reports on both:
- The Bus Error I discovered and,
- Planets not displaying without a star system parent.
- Begin implementing basic turn structure (before individual orders.) I believe this top down approach will more properly acquaint me with OrdersQueues and make it easier to implement the individual orders.
- Investigate the drawing of lines while issuing orders. This would allow adjacency lines to be drawn to make it more clear which territories neighbor the selected territory.
Mithro | 31-May-08 at 5:45 pm | Permalink
I don’t think you necessarily need to divide the things into what I did per day. Otherwise this report is looking quite good.
Might I suggest some more reflection on how you think you went this week. Did you spend enough time on GSoC? What was frustrating? What went better or worse then you expected? The idea of the status report is to put someone into the same frame of mind that you are in.
I had a chat to JLafont about his status report, you have mostly covered them but it could still be useful to read over it too.
Keep up the good work!
jphr | 31-May-08 at 6:48 pm | Permalink
You know, as silly as it is, I never thought to include any reflection. I’ll be sure to include that next week.
As for the days of the week thing: I generally keep a day to day log of major things, which in turn gets reworded and linkified for the report. If you would like me to cut out the days though, I can do that.
adjacency_matrix, among other things - Hammer of Code | 02-Jun-08 at 5:16 pm | Permalink
[...] Weekly Report 3 [...]