Depends on the nature of the documentation. I find pdf files to be
garbage as they do not make reading easy f*cking around with
lame zoom and too much scrolling, do not support resizing fonts,
nor do they provide inline linking or reference functionality other
than that which may be provided by the author. They also display
on top of your web unless launched in a separate instance of a window
or inline with a frameset.
PopUps are as a general rule now being blocked and if used at all
the user interface of the web must make it very clear to the user that
PopUps are used to enable the user to over-ride the blocker. Holding
one's finger onm the ctrl key while using documentation is not user
friendly and expecting a user to use menus to temporarily reconfigure
blockers is asking a lot.
Best practice in MCAD training guides suggest using the HTML
target attribute to create a new instance of a window which
I agree is the best methodology depending on most circumstances.
In limited circumstances you might consider a frameset but that is
getting back to a level of complexity that may be counterproductive.
--
<%= Clinton Gallagher
A/E/C Consulting, Web Design, e-Commerce Software Development
Wauwatosa, Milwaukee County, Wisconsin USA
NET csgallagher@ REMOVETHISTEXT metromilwaukee.com
URL
http://www.metromilwaukee.com/clintongallagher/
"Mythran" <ki********@hotmail.com> wrote in message
news:eM**************@TK2MSFTNGP09.phx.gbl...
IMO? pdf's for help :)
Otherwise, we make use of pop-up windows (using window.open and
window.showDialog) to display any and all help windows...
Mythran
"poppy" <an*******@discussions.microsoft.com> wrote in message
news:17*****************************@phx.gbl... I have just completed a web application in asp.net and
have been informed that I must offer some kind of online
help.
Whats the best way to do this ?
