Isn't this a little bit back-to-front?
What about first drawing up a list of requirements (maybe "must haves"
and "would be nices")? This then gives you some criteria by which
to assess things which are already around.
If nothing already fits the bill, adjust the criteria or start working
out how to make something that does meet the requirements.
Until you define the requirements all this arguing about Inventor and
stuff is pointless, since we're probably not even talking about the same
-- Chris Hand, Senior Lecturer | Dept of Computing Science, e-mail: firstname.lastname@example.org | De Montfort University, The Gateway WWW: http://www.cms.dmu.ac.uk/~cph/ | LEICESTER, UK LE1 9BH talk: email@example.com "In Cyberspace nobody knows you're bald"