Hey Nils, Go ahead, fork Stalker and Anima in GitHub (Stalker Pyramid is not on GitHub yet).
I've not written any documentation on installing Anima along with Stalker yet and sadly there are no screen casts, I will try to do it as soon as I've time. What you need to know about Stalker, Stalker Pyramid and Anima is the level of generality of each of them: Stalker (LGPLv2) > Stalker Pyramid (LGPLv2) > Anima (BSD) So, Stalker is the most generalized one, I tried to make it as generic as possible. But, I think with v0.2.5 I had to introduce what I've called the **Task Status Workflow**. It is the workflow of statuses that a task/asset/shot/sequence can have on their life time. This part is not that much open yet. That is, Stalker will force you to follow a scheme, you can read it from http://pythonhosted.org//stalker/generated/stalker.models.task.Task.html#stalker.models.task.Task Also the Ticket statuses are fixed and hard coded, but it is a little bit more open then Tasks (you can define the ticket workflow in config.py as a python dictionary). But I plan to merge the both status workflows of Tasks and Tickets in to something that is managed by a custom class which may be called StatusManager. So Stalker will have a default status manager for Tasks and then one for Tickets but then you can setup your installation to use your own custom StatusManager. Stalker Pyramid is tried to be written as generic as possible again, but I think we have failed on that. It is currently working only with PostgreSQL, even SQLite3 is not supported. And we didn't follow TDD practices at all, cause we were learning how to create a web application let alone how to test it. Also we were not aware how to test javascripts etc. That's way it is full of regressions. And we are very good at adding new buggy code on to it everyday. I plan to do a rewrite on Stalker Pyramid so it will have a good backend somewhere around next year or so. Anima, is fully customized to fit in to the pipeline we are trying to create here in Anima Istanbul (and our pipeline is having its baby steps right now). So it is tailored for our needs, I don't think that it is going to fit 100% to any other studios needs. Anima is licensed under BSD and I think I should convert it to MIT, so you guys can use it as a quick and dirty place to copy and paste the code from, it may help you at least tackle with the problems that I've had (like displaying one cell of a QTreeView as a QButton or displaying/fetching data on demand etc). So again please fork them, and play with them. Best, E.Ozgur Yilmaz eoyilmaz.blogspot.com On Sat, May 10, 2014 at 2:23 PM, Erkan Özgür Yılmaz <[email protected]>wrote: > Hi Chad, > > It is my honor to hear a python experts thoughts on Stalker. Thank you > very much for your compliments, I tried to write it as clean as possible. > > Customizing Stalker is possible by instantiating the SOM classes that you > think that fits to your needs. Also before doing that I am very open to new > ideas to be implemented directly to Stalker it self. > > I'll upload the documentation to readthedocs.org or you can read the > whole API documentation from http://pythonhosted.org/stalker/. > > For Stalker Pyramid, I don't think that it is ready to be announced right > now. Currently, it is shaping according to our daily needs and what me and > my wife is coding in to it is a little bit quick and dirty. We probably > will write it from scratch after the production of the current feature > animation project is completed. But I can upload screen shots of it, you > probably will enjoy the UI, UI is good but the backend is not in good shape. > > Cheers > > E.Ozgur Yilmaz > eoyilmaz.blogspot.com > > > On Sat, May 10, 2014 at 3:31 AM, Chad Dombrova <[email protected]> wrote: > >> Erkan, >> I read through your tutorial and checked out some of the code. This is >> really good stuff. The code is super-clean, well organized, and well >> documented. I also really like the sqlachemy mixin design. Very nice >> work. Anyone out there who is looking to setup a custom production tracker >> should have a look at this, even if just to learn from it. >> >> Your models as a great starting point, but most studios will of course >> want to associate additional data with shots, projects, sequences, etc. >> I'd like to hear how if you support this or plan to support it. >> >> I noticed that the docstrings are all well-formatted for sphinx: do you >> have the full api docs generated somewhere? it would be great to see it on >> https://readthedocs.org/ >> >> It would also be helpful if you had a little sandboxed demo of >> stalker-pyramid running. >> >> Thanks for open sourcing this. >> >> chad. >> >> -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/python_inside_maya/06444F30-DEB0-4385-910C-DDEB5D98B6D1%40gmail.com<https://groups.google.com/d/msgid/python_inside_maya/06444F30-DEB0-4385-910C-DDEB5D98B6D1%40gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAGNmyx5wMmpedbFyBuKZsSfH1fHMvFntVUVXTjfTkfVybhn3OA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
