Hi, Ben. You have a number of interesting requests. I'd like to share a
few tips about getting your suggestions accepted. You can submit your
suggestions directly to MLO support. This works best for obvious
mistakes, bugs, and awkward interfaces that the developers have
obviously struggled with.
If you are proposing something that will make existing customers
happier, or (even better) attract new customers, you may need to prove
that (a lot of) customers or prospective customers really like your
idea. One way to do that is on
mlo.uservoice.com - the problem with this
is that it has been around for a few years and some old ideas have run
up some pretty big vote tallies so it can be hard for a new idea to make
a splash.
Another way to show that an idea is popular is to post it here and see
is a lot of people say "me too". Two hints for this: First, pick your
one best idea and make the best case you can for it. Leave the rest of
your idea for later. When you send a bunch of ideas in a single email it
tends to be a less productive discussion. Second suggestion: start by
researching whether the thing you are trying to do is already supported.
Check the documentation, and if its unclear or you cant figure it out,
write to this forum with a question, is there a way to whatever. If the
answer is "no" then its time to suggest an enhancement.
It looks to me as though several parts of your suggestion are
recommending functionality that we already have. The accumulating
resource idea feels new, but the basic "part x arrived in the mail"
scenario is handled well by a "wait for part x to arrive" task with
other tasks set to be dependent on this task. Also, I tried out the
subproject progress bars and it seems to me that the current version
works exactly as you requested. If you need a step-by-step walkthrough
on how to use it, write back and say so.
Good luck and I'm l;ooking forward to seeing your next set of suggestions.
-Dwight