Hello,
As you might remember, a while ago I sent an email in which I was
explaining how I wanted to create a schema for the projects at work.
(Hopefully, I used the right word there). Since a lot of those projects are
of the same type and they share not only data but behavior, I decided to
create a class for them.
Initially, I was declaring paths manually as Instance attributes but you
guys told me that I was better off storing that information in a file and
then somehow importing it.
I've put together some code that reads JSON data from a file once the
instance is initialized, and replaces the contents of __dict__ with the
data retrieved from the file (A dictionary).
Code can be seen here:
- https://gist.github.com/davidmartinezanim/0eddcecc4d141c8fa165
Do you think that this would be an acceptable approach to for the 'Project'
classes?
The main reason why 'Project' is still a class is that all projects of this
kind use the same functionality but there are other kinds of projects and I
want them all to be children of a Project type. (Even though that the
example above looks like a base class, it will be a concrete one inheriting
from the base class instead of 'object')
Thanks in advance
--
David Martinez - Technical Animator
Email: david.martinez.a...@gmail.com
Website: http://www.elusiveideas.com
--
You received this message because you are subscribed to the Google Groups
"Python Programming for Autodesk Maya" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to python_inside_maya+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/python_inside_maya/CAMLeNpwdOcRurhmaw6eydz4ySj70tOanrZf1-bTB4KUTN86aRQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
