Meeting:2009/04/04

From FIFE development wiki
Jump to: navigation, search

This article contains a list of topics for as well as the results of the March/April developer IRC meeting.

List of topics

Revisit map code

Document, refactor and also document the map code. Rationale: I think at the moment no one understands the code under model/ in its entirety. That needs to be taken care of before it gets unmaintainable.

phoku 22:29, 16 March 2009 (UTC)

Localisation?

With unicode support rearing its beautiful head, I'd like to get some input on what kind of features the clients aka zero,uh and parpg actually need.

phoku 22:29, 16 March 2009 (UTC)

Editor

Discuss next steps of editor development; Decisions about current proposals to create a roadmap for the editor. --chewie 12:47, 20 March 2009 (UTC)

Forums

Should we declutter the forums by creating new (sub)boards, removing unused boards (e.g. rio de hola feedback)? --chewie 12:47, 20 March 2009 (UTC)

Wiki/Trac Reality Check

The documentation on the wiki and also the tickets in Trac need a reality check. Any volunteers? Ideas?

phoku 17:49, 24 March 2009 (UTC)

Results

Localisation?

Text in Pychan XML files is not parsed by standard pygettext. Zero approach is distribute the text via code anyway. UH is undecided, but in case they want a gettext parser for text in GUI XML, christoph_debian might try and write one.

Editor

Cheesesucker is busy working on a rewrite and progressing fast. The only real requested feature the ability for a custom map loader/saver by UH.

There are some problems with nameclashes, as Cameras are declared in the map files.

Forums

  • The *Rio de Hola feedback* board will get removed.
  • Ask barra for permissions, and give out moderator rights to the active FIFE devs.
  • No new sub-boards for now.

Trac Tickets

Create a *Deleted* Milestone and move tickets there rigorously (e.g. ambiguous, content/, may or may not apply to reality ). In a month or two, we delete those for which no one offers a reason 'for real'. Chewie volunteered to prepare the cleanup.

Wiki

The next meeting day will also be *spring-cleaning* as at the moment no one is really motivated to work on the wiki. There are some grey areas (e.g. the Ntework Demo, which should be removed or brought up to date). The general layout is mostly misleading, and some parts may simply be out of sync with reality.


Map code

Some features are broken ATM. Documentation is sparse. Pathfinding is too basic. Needs a plan. phoku volunteered to cleanup/document a bit and come up with a plan.