I though it would be appropriate to try'n get some kind of overview of this. At the moment I think the whole toolbox seems a bit confusing and trying to get a hold of what exactly needs to be done seems almost impossible to me, so a bit of dicussion where we end up with a plan of what exactly needs to be done in the nearest future and organizing whom who takes care of what would be a very nice thing to have.
First of all, I really think that a clear way of organizing the script should be set.. I've talked about this plenty of times but I keep coming up with too many cons for each way.
Right now, with the core file, I know that it is easier to update everything when the one procedure only is defined in the core, BUT.. it makes all tools dependent of the core procedures and the way they all works, which makes it hard for us to edit something that could make on tool alot better and faster, without ruining alot of other tools at the same time. I think that this core help me loosing the overview of what needs to be done, as I can't just fix the tools from the first to the last, as everything needs to work together all of the time.
I suggest a new starting point where all tools have all their helper procedures included which makes them totally independent of everything (execpt the Maya core)
This gives us to opportunity to develop the tools easier while we wont have to think of who edited the core last time, and that he maybe fucked something on my procedure. We are also able to optimize the helpers a lot better for each tool and as it develop and some procedures lives happily ever after without ever creating a bug, we can start to think of adding this to a core - provided that it can be used for more then just the one tool - .
Furthermore I would suggest though, that we group some tools, which are much the same, like the draggerContexts and maybe the split and selection tools as well. This would probably end up with something the like the core setup, but just a lot smaller ones instead.
At least this is what I think can help splitting up the work and starting to organize the development, but this way ofcourse has cons as well..
What do you say out there?
And do you have any ideas of what should be done next with this toolbox?
Cheers.
Jakob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been looking for a "Soft Selection" tool similar to 3dsmax and BPT's if you're interested in developing that. Maya's Soft and Prop Mods just don't do it for me. Seems like a pretty good fit for your toolkit.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Henry korol is working on a soft selection like tool at the moment.
Some further suggestion would be to make the menu dynamical so that it checks the module script/plugin path for files and arrange them using some kind of naming convention and then creates to manu accordingly, so that users have the possibility of just downloading the menu set and place their own costum scripts in the scripts dir, change the names to match the namin convention and it will be included in the OMT menu next time Maya opens.
And as suggested above, the toolbox should be made of many seperate items which all works independent, so that a user can download only the tools he/she wants and place them in the OMT dir's and everything will be simple and work :D
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I tried getting through via email, but I guess that didn't work. Anyway I was wondering if you accepted independent tools and such. I have a API library which I'd like to share but don;t know how to do it.
Thanks,
Ben
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I though it would be appropriate to try'n get some kind of overview of this. At the moment I think the whole toolbox seems a bit confusing and trying to get a hold of what exactly needs to be done seems almost impossible to me, so a bit of dicussion where we end up with a plan of what exactly needs to be done in the nearest future and organizing whom who takes care of what would be a very nice thing to have.
First of all, I really think that a clear way of organizing the script should be set.. I've talked about this plenty of times but I keep coming up with too many cons for each way.
Right now, with the core file, I know that it is easier to update everything when the one procedure only is defined in the core, BUT.. it makes all tools dependent of the core procedures and the way they all works, which makes it hard for us to edit something that could make on tool alot better and faster, without ruining alot of other tools at the same time. I think that this core help me loosing the overview of what needs to be done, as I can't just fix the tools from the first to the last, as everything needs to work together all of the time.
I suggest a new starting point where all tools have all their helper procedures included which makes them totally independent of everything (execpt the Maya core)
This gives us to opportunity to develop the tools easier while we wont have to think of who edited the core last time, and that he maybe fucked something on my procedure. We are also able to optimize the helpers a lot better for each tool and as it develop and some procedures lives happily ever after without ever creating a bug, we can start to think of adding this to a core - provided that it can be used for more then just the one tool - .
Furthermore I would suggest though, that we group some tools, which are much the same, like the draggerContexts and maybe the split and selection tools as well. This would probably end up with something the like the core setup, but just a lot smaller ones instead.
At least this is what I think can help splitting up the work and starting to organize the development, but this way ofcourse has cons as well..
What do you say out there?
And do you have any ideas of what should be done next with this toolbox?
Cheers.
Jakob
I've been looking for a "Soft Selection" tool similar to 3dsmax and BPT's if you're interested in developing that. Maya's Soft and Prop Mods just don't do it for me. Seems like a pretty good fit for your toolkit.
Henry korol is working on a soft selection like tool at the moment.
Some further suggestion would be to make the menu dynamical so that it checks the module script/plugin path for files and arrange them using some kind of naming convention and then creates to manu accordingly, so that users have the possibility of just downloading the menu set and place their own costum scripts in the scripts dir, change the names to match the namin convention and it will be included in the OMT menu next time Maya opens.
And as suggested above, the toolbox should be made of many seperate items which all works independent, so that a user can download only the tools he/she wants and place them in the OMT dir's and everything will be simple and work :D
Hi, I tried getting through via email, but I guess that didn't work. Anyway I was wondering if you accepted independent tools and such. I have a API library which I'd like to share but don;t know how to do it.
Thanks,
Ben