You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FIFedit should allow users to define their own loader/saver duo. E.g. Unknown Horizons is using a combination of sqlite db and filesystem to store their maps. Therefore there is an sqlite loader / saver.
One possible implementation would be, that those loaders / savers describe which format they are written for, and FIFedit chooses them automaticly from the plugin directory due to the selected file extension.
Another way would be to write a profile system which would allow content designers to specify how FIFedit should behave (and which plugins are loaded on startup - as well on how panels are arranged etc.)
I think this is really a whole engine feature and not just an editor feature. Ideally we want the engine to be able to support custom loaders as well that way the client developer can write the loader once and have the engine and all tools use it.
From @prock-fife on January 28, 2010 20:4
This issue was reported by chewie
FIFedit should allow users to define their own loader/saver duo. E.g. Unknown Horizons is using a combination of sqlite db and filesystem to store their maps. Therefore there is an sqlite loader / saver.
One possible implementation would be, that those loaders / savers describe which format they are written for, and FIFedit chooses them automaticly from the plugin directory due to the selected file extension.
Another way would be to write a profile system which would allow content designers to specify how FIFedit should behave (and which plugins are loaded on startup - as well on how panels are arranged etc.)
Copied from original issue: fifengine/fifengine#439
The text was updated successfully, but these errors were encountered: