This whole asset management part sounds like a general pipeline approach, with svn as data storage and perhaps database ( ->properties ).

Doing that would properly would make many people, including myself, quite happy as this is one major backbone of any pipeline.

Not being too familiar with Maya is probably won't be too much of a problem as you can boil the system down to actually know about maya in the end, by plugging it into your framework.

Thus whenever one says asset management, I do not see maya in the first place, but files and how they are organized. This is useful for many other applications as well, that could play together with your asset management system.

Perhaps I am over-generalizing making things more complicated than they actually are, and its absolutely fine to start 'sane' and focus on one application at first to gain first experiences with asset management.

Lets see how it goes for you - in my head it looks like a large project requiring a good foundation.

Zac Shenker wrote:
At this stage the main focus is to provide a solution for the end users, but in saying that where possible I am building Python Classes that provide alot of useful functionality so it certainly could be useful for developers as well.

Personally I have quite alot of experience with Python and SVN but am new to programming for Maya.

I would like to ultimately include features that improve the pipeline and workflow processes, such as:
Going through the Maya scene files and discover file textures that are no longer being used.
Provide Version Control over all assests in the project
Easy to use management of revisions and file locks
Easy to use support for branching.
Possibly some basic support for automated merging and conflict resolution.

Regards,
Zac

On Mon, Dec 29, 2008 at 9:33 PM, Sebastian Thiel <[email protected]> wrote:
Who will be your target audience ? Will it be programmers that want to use your integration in their environments,  or will it be users that just need nice user interfaces ?

Can you target both ?

>From my perspective,  pysvn already did the job for me. It does not come with any user interfaces, but for pipeline work, these can be very very simple.

Something I had to improve though is the pysvn client to be a little easier to use when trying to check-out or update files in a deep directory structure which does not yet exist locally. If your project, in addition to that, would provide a nice modular user interface, it could workout well.


Hradec wrote:
Sounds really intersting man... I have being thinking about the potential of using svn in maya for a sort of asset management system for quite some time, which is a concept that your project could be used for I think...

I would be really interested in discuss more about the subject, and maybe even contribute to your project...

congrats for the effort and initiative...

-H


On Mon, Dec 29, 2008 at 1:01 AM, Zac Shenker <[email protected]> wrote:
Hi Farsheed,

Thanks for the comments. This project is still very much a work in progress, it still has a number of hardcoded variables and is missing a reasonable amount of the interface integration.

If there is any one out there interested in this project I would be happy to discuss design and goals of the project a bit further before coding much further.

Regards,
Zac


On Mon, Dec 29, 2008 at 5:16 AM, Farsheed Ashouri <[email protected]> wrote:
Nice work, Thank you.
Sincerely,
Farsheed.

















--~--~---------~--~----~------------~-------~--~----~
Yours,
Maya-Python Club Team.
-~----------~----~----~----~------~----~------~--~---

Reply via email to