#fifedev: February Developer Meeting

Meeting started by prock at 16:25:19 UTC (full logs).

Meeting summary

  1. FIFE 0.3.1 release (prock, 16:28:10)
    1. http://www.swig.org/Doc1.3/Python.html#Python_nn30 (vtchill, 16:53:13)
    2. AGREED: Ticket #197 should be moved to the 0.4.0 release as it requires an API change. (prock, 17:00:35)
    3. ACTION: vtchill will put a summary of what we discussed into ticket #197 and move it to the 0.4.0 milestone (prock, 17:01:36)
    4. http://meetbot.debian.net/Manual.html#commands (prock, 17:42:11)
    5. ACTION: CheeseSucker is going to assign himself to Ticket #443 and look into a solution (vtchill, 17:48:46)

  2. 0.4 - FIFEdit (vtchill, 17:59:32)
    1. Proposal to use a more feature rich GUI toolkit for FIFEdit (vtchill, 18:00:58)
    2. http://www.use.com/fifedit_mockup_4a99c0b8433c80012a65 (vtchill, 18:05:32)

  3. 0.4 - Pathfinding (vtchill, 18:36:48)
    1. http://www.ai-blog.net/archives/000152.html (vtchill, 18:42:38)
    2. IDEA: use navigation meshes for pathing support in FIFE (vtchill, 19:06:35)

  4. 0.4 - Map loader/saver in c++ (vtchill, 19:06:51)
    1. ACTION: vtchill will provide interface information for the map loader/saver as soon as it is ready so other work can start for integration of this feature (vtchill, 19:17:14)
    2. ACTION: vtchill and prock will figure out what to do about Ticket #439, it may need to be retargeted since it will involve interface changes (vtchill, 19:22:13)

  5. 0.4 - Triggers (vtchill, 19:23:57)
    1. ACTION: look into the current implementation of triggers and come up with plans to implement more efficient triggers (vtchill, 19:28:48)
    2. IDEA: use a quad tree type approach to limit the number of triggers fired (vtchill, 19:29:08)
    3. AGREED: save topics 0.4 - Manuals and 0.4 - Fog of War for another time (vtchill, 19:34:22)
    4. leaving topics 0.5 and Into the future for another time (vtchill, 19:35:02)


Meeting ended at 19:38:55 UTC (full logs).

Action items

  1. vtchill will put a summary of what we discussed into ticket #197 and move it to the 0.4.0 milestone
  2. CheeseSucker is going to assign himself to Ticket #443 and look into a solution
  3. vtchill will provide interface information for the map loader/saver as soon as it is ready so other work can start for integration of this feature
  4. vtchill and prock will figure out what to do about Ticket #439, it may need to be retargeted since it will involve interface changes
  5. look into the current implementation of triggers and come up with plans to implement more efficient triggers


Action items, by person

  1. CheeseSucker
    1. CheeseSucker is going to assign himself to Ticket #443 and look into a solution
  2. prock
    1. vtchill and prock will figure out what to do about Ticket #439, it may need to be retargeted since it will involve interface changes
  3. vtchill
    1. vtchill will put a summary of what we discussed into ticket #197 and move it to the 0.4.0 milestone
    2. vtchill will provide interface information for the map loader/saver as soon as it is ready so other work can start for integration of this feature
    3. vtchill and prock will figure out what to do about Ticket #439, it may need to be retargeted since it will involve interface changes


People present (lines said)

  1. vtchill (249)
  2. chew-ie (166)
  3. prock (114)
  4. CheeseSucker (36)
  5. barra__out (16)
  6. helios_ (3)
  7. fifer (3)


Generated by MeetBot 0.1.4.