[QUOTE=bjorke;8450]Yes. What you really need is to spec-out what you want/need, even before picking the tools & methods (“I need it to be in python because our coders and artists already know some python” can be part of the spec, but it’s a line item among line items)
This is, of course, almost never how production software gets actually made – it tends to evolve according to changes in the environment. But as an ideal, it’s a good ideal.[/QUOTE]
BAM! I strongly agree with you.
I’m no expert myself, as I just graduated from school, but heres what I’ve been thinking.
At this point, I think we are starting to agree on what we are trying to acomplish. From what I’ve gathered so far, it’s seems like most people want to “Build a UI for a small asset management program. This will include things such as creating new assets with the ability to assign them to a user, tags and keywords for sorting/querying, due dates, links to other assets, (concepts of the 3d models to be built) a commenting system, and leave hooks to link DCC programs as well as Version control.”
If we can first agree on what the program is going to do, it will be easy to create a Data Model that further defines what the program can do/can’t do.
Also, at this point I don’t think we need to worry about whether it’s web based or a stand alone program. I understand that will be a major discussion down the road, but either way I believe deciding now is getting ahead of ourselves. Getting the initial design done correctly, would easily allow both to be created. If you haven’t heard of Model/View/Controller, check that page out.
Also, maybe having a group chat or conference would be a good idea. I believe Skype has a nice group conference feature.