On Aug 8, 2009, at 5:00 PM, Trevor Jacques <tre...@videlicet.com> wrote:
>> 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. Agreed. Mostly. :) the pop up idea puts the burden back on the developers to maintain the data. This I do not like. It can not easily be localized either. What I would like is as you suggest, strong formatting of basic data in short form. The pop up is fine, but the resulting data needs to be community editable. > >> 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. :-/ I agree the wiki needs more work. I myself resist using it and adding to it because it does not seem to be used. If the default doc link in the web admin was /docs? command=something&lang=eng I would be much more inclined to use that to enter what I learn as I use assp. > 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. Correct. And I think should be solved by UI and not verbiage. Check one checkbox, the others grey out so you visually see they are not an option. If you would like to work on this with me please email. I am thinking plain text files each named command-lang.txt which could easily be included in ASSP and read in and seved by the web admin. I think in short time we could bang out English, get a real set of docs to distribute, and then be in a position to look to lighten up the web admin. I have little interest in working on this alone, but would be highly interested if someone else worked with me to help motivate :) -- Scott Iphone says hello. ------------------------------------------------------------------------------ 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
