I did a fuse filesystem when I was at my previous studio. It wasn't the primary system. Just a mount that offered specific functionality. When you navigated it, it was aware of your user name and could show you a directory of just your assigned shots and then department specific areas under that shot. Then it also included general role ups of locations at the top level. You could go into a location a see just the published data because it referenced the production tracking and asset system. On May 12, 2014 6:42 AM, "Marcus Ottosson" <konstrukt...@gmail.com> wrote:
> Even though I'd consider heading down that route it an incredible > fascinating experience and one I'd follow closely (if you for example where > to blog or otherwise take notes on your journey) I'd stress the potential > failure- and maintenance-rate you would be up against compared to the very > slim winnings you would probably end up with. > > Honestly, who does that and gets away with it? :) What it sounds like you > need is flexibility in directory structure on a per-project level, so that > you can keep your code as-is inbetween your variations. > > I'm all for thinking differently, challenging the status quo and all that, > but don't hurt yourself doing it. :) > > Chad, can you see somehing like fuse work for this purpose? I mean, even > where there are plenty of resources in pipeline and IT? > > On Sunday, May 11, 2014, Chad Dombrova <chad...@gmail.com> wrote: > >> If you're planning on doing all of the work required to implement a >> virtual-folder system, you might consider implementing it using >> fuse<http://fuse.sourceforge.net/>. >> Fuse let's you create a new file system that is run as application run by >> the user. For example, people have used fuse to create file systems that >> mount over FTP and SSH and even git. To the user the new file system looks >> like any other, so files and folders are accessible in any application, >> including finder/explorer. >> >> There are python bindings for fuse here: >> https://github.com/terencehonles/fusepy. >> >> The API will probably have a steep learning curve, but on the other hand, >> you won't have to write any UI code. >> >> 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 python_inside_maya+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/python_inside_maya/CAGq9Q7G8H%2BbohSMwKDTX84wdMhQw5NsEEtg7tTbrqJMK%3DLTMYg%40mail.gmail.com<https://groups.google.com/d/msgid/python_inside_maya/CAGq9Q7G8H%2BbohSMwKDTX84wdMhQw5NsEEtg7tTbrqJMK%3DLTMYg%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > *Marcus Ottosson* > konstrukt...@gmail.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/CAFRtmOCZx%3DUok5sw09OBCpYuOFqmh%3Dyjbu5OLb4bSGXUHjDJGw%40mail.gmail.com<https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOCZx%3DUok5sw09OBCpYuOFqmh%3Dyjbu5OLb4bSGXUHjDJGw%40mail.gmail.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 python_inside_maya+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA0j9AsgP3sgi-aaqc3jfzn_Mnpa37cw43D6_UCeF%3D-PEQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
