Fixed resource path dependencies issue that caused PARPG to crash on start. * PARPG should now run without issue (system installation not tested). * Utilized FIFE's VFS module to remove path dependencies from most PARPG modules. * The new parpg.vfs module is a singleton with a single global variable, VFS, which is a reference to the global VFS instance. Although a singleton is not ideal it should be replaced once PARPG's core code is refactored. * The parpg.vfs singleton is initialized in the parpg.applicaiton.PARPGApplication class with the absolute path to the data directory via the parpg.settings module and corresponding configuration file. * A new DataPath entry was added to the default system configuration file template under the [parpg] section to support the new parpg.vfs module. * Updated the parpg-assets subrepo to revision 3 to fix some dialog file format issues (for details see commit message for parpg-assets). * Fixed a few bugs in the parpg.dialogueparsers.YAMLDialogueParser class related to exception handling.

--- a/gui/dialoguegui.py	Tue May 31 02:46:20 2011 -0700
+++ b/gui/dialoguegui.py	Mon Jun 06 15:56:14 2011 -1000
@@ -18,6 +18,7 @@
 from fife.extensions import pychan
 from fife.extensions.pychan import widgets
 
+from parpg import vfs
 from parpg.dialogueprocessor import DialogueProcessor
 
 logger = logging.getLogger('dialoguegui')
@@ -29,7 +30,8 @@
     def __init__(self, controller, npc, quest_engine, player_character):
         self.active = False
         self.controller = controller
-        self.dialogue_gui = pychan.loadXML("gui/dialogue.xml")
+        xml_file = vfs.VFS.open('gui/dialogue.xml')
+        self.dialogue_gui = pychan.loadXML(xml_file)
         self.npc = npc
         # TODO Technomage 2010-11-10: the QuestEngine should probably be
         #     a singleton-like object, which would avoid all of this instance