[QUOTE=arvindk.86;11021]PS: QT Designer is awesome![/QUOTE]
QT Designer is installed with Maya 2012 for Windows and Linux. Mac OSX users still need to download and install it separately.
Still feel I have more control with the old code based system though… I like dynamic interfaces. 
[QUOTE=arvindk.86;11021]Here’s the link to the tutorial
Here are the files (mel code, ui file and readme) : [/QUOTE]
Overall good, but…
The deployment feels off target… The description if for the way you deploy scripts when putting them up on Creative Crash for example. But the project goals specified a small team working on quick prototypes and later on in the tutorial you use a network location and it also says “Keep in mind that non programmers will be using this script”. For any team that works towards a network drive or version control software, all deployment should be made using a common script location in either of those systems so that the user doesn’t need to do anything. It should just pop-up the next time they restart Maya in a TA controlled interface (toolbar menu, shelf and/or other system), and have a link to the documentation in the tool. 
Another thing that bothers me a bit is the writing of the .txt file on a network location. I don’t feel that is a good practice as it can create a lot of problems, especially when a team grows and collisions when accessing that file will be more likely. If that type of data should be saved, a proper database would be the better solution, or at least have it make a new file each time based on user name and time stamp to prevent collision issues.
Other options:
Write it in python to remove the need for a few of those small procedures and shorten a lot of the code.
Personally I wouldn’t use a .txt file locally to save data either. I would just setup my own internalVar(s).
Thanks for your input Wolfsong!! I’m working on some changes based on these …
Hey man, I just gave your tutorial a read. For a first tool and tutorial, it seems like you did a good job. I agree with Erik about the writing of a text file, although I can say I’ve done the same thing before. One thing I would say is that as great as writing a tutorial is, the time spent writing it could be furthering your education on a particular subject.(IE: learning more MEL) I’m not sure how long you spent writing it up, but I would guess it took quite a while. I’m not against trying to teach others, but at this point it might be better off focusing on developing your tech art “toolbox.” Plus, if you’re going to release the code, anyone who knows the language will be able to read it, there are plenty of comments in your code.
Overall good job man, I think you said it best when you said, “I now know I would need immense experience to write a manual like that.” It’s good to think about projects after their done, keep up the work. I’ll be watching out for your next project.
Yes i read and really enjoyed posts you have shared here, keep posting nice ideas …