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

determine and explain boundaries between various systems #54

Open
glyph opened this issue Jun 12, 2014 · 0 comments
Open

determine and explain boundaries between various systems #54

glyph opened this issue Jun 12, 2014 · 0 comments

Comments

@glyph
Copy link
Member

glyph commented Jun 12, 2014

Right now, lots of stuff is dumped into imaginary.objects and imaginary.actions, with random additional packages such as imaginary.garments and imaginary.creation.

Current thinking is that the Imaginary core ought to be extremely small: imaginary.idea, Thing, most of what is in imaginary.language, and so on. However, that core will definitely not be useful without a series of extension packages.

We should be factoring out separate systems - garments being the most readily separable one, but combat would be a good one to follow up with. It may be interesting to completely separate these out into different distutils distributions to force the issue of how 3rd party developers will extend Imaginary both for authors and for players of their own games, although it may also make sense to package these along with Imaginary in its namespace.

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

No branches or pull requests

1 participant