Port PARPG codebase to FIFE 0.3.0 import scheme

[barra_parpg]

The FIFE developers recently updated their engine and switched to a more standard-compliant Python module import scheme. Therefore FIFE-based games need to adjust their codebase if they want to use the newer FIFE SVN revisions or the latest official FIFE 0.3.0 package.

Announcement with notes about the import scheme change and build system changes:  http://fifengine.de/2010/01/12/the-build_system_rework-branch-has-been-merged-intro-trunk/

Import scheme instructions at the FIFE wiki:  http://wiki.fifengine.de/Importing_Python_Module

[barra_parpg]

Chewie from Zero-Projekt played around with the code and managed to port PARPG to FIFE 0.3.0. Unfortunately he can't provide a DIFF right now but he has uploaded a patched snapshot of PARPG rev. 466:  http://ul.to/82hrn4

Somebody would have to turn this into a diff, check the patch and apply if it works fine.

[eliedebrauwer]

the ul.to link isn't responding here.

i just updated my FIFE svn repo and parpg repo, did a FIFE rebuild and a parpg ./run.py and it ... well just worked ... am i missing something obvious here ?

[barra_parpg]

Attached patch to fix FIFE 0.3.0 support.

Thanks to chewie for figuring out the details and to pirum for turning this into a working diff!

[barra_parpg]

(In [482]) Ticket #246. Patch by pirum:

• Fixed map_editor local loaders directory not found problem
• We're currently relying on a hardcoded folder structure: the map editor directory gets pulled from FIFE's SVN repo via SVN externals; you need to have a checkout of parpg/trunk/tools to run the editor
• closes #246