> The programming for the interface is pretty trivial really. But who > is going to explain to the users what the tests mean and how they > work and so on. To me that's the big issue. Most of our users would > neither want to learn nor would they.
I think Terry's statement is precisely on-point. Rather than feasting on Tom and his engineers' technical abilities, all should realize that rolling out Declude with self-administered per-user settings has user acceptance and training issues that exacerbate what might originally seem like a straightforward coding/scripting task. There are many excellent engineers who have little coding experience, and even more who have such experience, but wish to leave it in the past. Additionally, as the Declude documentation is not written for end users, any interface meant for a wide base of non-technical users would need its own set of docs--and few are the engineers who are competent/interested in writing for such an audience, as missives from corporate IT departments often bear out. With that said, Declude's shipping management options are clear even before you purchase the product, so any time consumed trying to find Scott's "Easter Egg" of a full GUI was definitely not well spent! Ah well, live and learn. :) -Sandy P.S. Tom, I'd bet posting feature specs for your ideal management interface to the Declude list would help get somebody else moving, perhaps on a contracting basis. To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
