Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIFedit support for custom loaders / savers #14

Open
stubb opened this issue Mar 14, 2016 · 2 comments
Open

FIFedit support for custom loaders / savers #14

stubb opened this issue Mar 14, 2016 · 2 comments

Comments

@stubb
Copy link
Member

stubb commented Mar 14, 2016

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

@stubb
Copy link
Member Author

stubb commented Mar 14, 2016

From @vtchill on February 26, 2010 13:50

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.

@stubb
Copy link
Member Author

stubb commented Mar 14, 2016

From @vtchill on February 26, 2010 13:52

this is the beginning of the engine support for custom loaders and savers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant