> The GUI is already burdened with too much data. I have always felt > only the most basic of descriptions should live in it.
Perhaps a consistent, systematic look at what should and should not be included in the GUI notes that are visible would be a good idea. Each set of notes could follow that set of requirements, so that users become familiar with what they can expect from the GUI description/ notes. Follow that with pop-up windows with more information, and one kills two birds with one stone. > Each item could then simply link to the wiki, where users are in > control to provide as much, or as little detail as they desire. Either a reliable link to the wiki or, better yet, a link to another, pop-up window (target="_blank") with the full description, as noted above. :-) FWIW, I've yet to find a single wiki that answered my questions, and very few seem to have a useful structure that leads readers quickly to the information they seek. The wikis are usually motherhood with little relevant detail. :-/ Either way, if a setting is going to significantly affect (positively or negatively) the performance of the software (positively or negatively), as the TLS-Tunnelling setting certainly does, I suspect that the GUI is the right place for that information. T. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
