Research: Text and Callouts

[ibuild]

I didn't say it was bullet proof. Just that it works. Any work around is just that....a work around.

Everyone reading this thread will see a lot of really good ideas from everyone who has taken the time to contribute. Make no mistake....the sum of the ideas constitutes a MAJOR investment in time and resources by Chief. If we want to create a situation where we have any expectation of getting something good within one development cycle, we (those who use this thing professionally) need to get together and define....SPECIFICALLY....what we want and what's most important. To maximize the chances of getting something done, we also have to make the case that what we want will benefit the entire product line....that it's in Chiefs best interest to make the investment. It's time to distill what's been suggested. If we don't, Jeff(remember Jeff? the developer who started this thread) won't know where to start...Any suggestions on how to quantify/prioritize some of this would be helpful.....