Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
The only issue is that this doesn't work with any production environment naming conventions. Aka
sh01_v01_aw.ma
would be a good naming convention but this script just makes it sh01_v01_aw_v01.ma if used. So it's practically useless for that. It will work nicely for people who are working on their own though...
So in essence, it needs to be more versatile with recognizing version numbers in file names.
Most cad apps have this feature of the bat. And so does maya too except it saves them under a aseparate folder to hide them away.
But sure this adds some versatility. Personaly i use cvs for the same thing wich is more econmic and safer anway. And you can have 2 concurent edits, and tracjk the infio even tough you dont cluitter yiour drive with many files.
But yeah i can see the vakllue of this tool, for one man operations. I dont oarticulary like when thisng tlike thsi come in installers since that implies something vile ;)
