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

[General] Alternative for hard-coding asset file names #106

Open
robertkety opened this issue Feb 27, 2017 · 1 comment
Open

[General] Alternative for hard-coding asset file names #106

robertkety opened this issue Feb 27, 2017 · 1 comment

Comments

@robertkety
Copy link
Contributor

Wanted: An Asset Manager that eliminates our current practice of hard-coding asset file names. Furthermore, I'd appreciate if we didn't resort to a single json file of file names.
Maybe a separate library which generates code against an asset directory using t4 templates?

@persn
Copy link
Contributor

persn commented Feb 27, 2017

The MonoGame Content Pipeline tool supports add-ons, but I'm unsure if we can use that for this purpose. If we could make the pipeline generate a code file, xml, json or whatever with our data it would be neat I think. Either way, anyone researching this issue should probably get familiar with the pipeline tool.

@robertkety robertkety changed the title Alternative for hard-coding asset file names [General] Alternative for hard-coding asset file names Mar 25, 2017
@persn persn added this to the v0.2.0 milestone May 2, 2017
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

2 participants