Update of /cvsroot/dynapi/dynapi/docs/docs
In directory usw-pr-cvs1:/tmp/cvs-serv25899
Modified Files:
faq.html
Log Message:
updated the faq as on my website.
Index: faq.html
===================================================================
RCS file: /cvsroot/dynapi/dynapi/docs/docs/faq.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -C2 -r1.5 -r1.6
*** faq.html 2001/01/21 12:24:58 1.5
--- faq.html 2001/02/09 15:48:31 1.6
***************
*** 11,15 ****
<h1>The official DynAPI2 F.A.Q.</h1>
! <h5>last update: 2001.01.20</h5>
<ul>
--- 11,15 ----
<h1>The official DynAPI2 F.A.Q.</h1>
! <h5>last update: 2001.02.05</h5>
<ul>
***************
*** 61,68 ****
</ul>
! <li><a href="#6">6. Doing advanced things</a></li>
<ul>
! <li><a href="#6.1">6.1. Limited Javascript knowledge</a></li>
! <li><a href="#6.2">6.2. Load external content into layers</a></li>
</ul>
</ul>
--- 61,69 ----
</ul>
! <li><a href="#6">6. Known bugs</a></li>
<ul>
! <li><a href="#6.1">6.1. Doing advanced things</a></li>
! <li><a href="#6.2">6.2. Limited Javascript knowledge</a></li>
! <li><a href="#6.3">6.3. Load external content into layers</a></li>
</ul>
</ul>
***************
*** 444,448 ****
visit <a href='http://www.richardinfo.com'>www.richardinfo.com</a>.
</p>
! <h1><a name="6">6. Doing advanced things</a></h1>
<p>After reading the tutorials and looking at the examples you might be able to do
the most basic stuff, but
if you want more there's not much documentation available yet. The examples and
widgets should provide you with
--- 445,468 ----
visit <a href='http://www.richardinfo.com'>www.richardinfo.com</a>.
</p>
! <h1><a name="6">6. Known bugs</a></h1>
! <p>As with any piece of software the DynAPI also contains bugs, some of these bugs
will eventually be fixed but some other
! bugs are more browser-problems and hard to fix using DynAPI code. Here's a list of
the bugs and if possible a work-around.</p>
! <ul>
! <li><b>Netscape4.04</b>;</li>
! <dl><dd>This browser has some problems with parsing Javascript. Some things
can be fixed by adding <code>return true/false</code> lines into functions, but
problems may still exist. Advise: upgrade to a newer Netscape version</dd></dl>
! <li><b>Resizing browser</b>; browser:Netscape 4.x</li>
! <dl><dd>Occurs in Netscape browsers, layers will not be correctly re-rendered.
This is a Netscape bug and the DynAPI code will try to work-around it.. this does NOT
happen on all NS4 browsers, and problems might differ (noticed this on different
machines).</dd></dl>
! <li><b>offsetWidth/offsetHeight</b>; browser:Netscape 6+</li>
! <dl><dd>There are some problems with getting these values from layers. We're
still working on solutions for this. A possible work around is using a setTimeout() of
0 which seems to do the trick (as reported).</dd></dl>
! <li><b>Hourglass syndrome</b>; browser: Internet Explorer</li>
! <dl><dd>This bug shows an hourglass (sometimes blinking) while your page has
already completed loading. The problem is most likely that you've used a bgImage on
one of the layers, and that layer is being moved,resized,or otherwise changed. IE will
try to reload the background image everytime this layers appearance changes. Work
around would be to either use a <code>setHTML('<img src="..."'>)</code> call or
minimize the amount of changes</dd></dl>
! <li><b>Images on layers in another frame</b>; browser: Netscape 4.x</li>
! <dl><dd>When creating a layer in another frame, and then trying to set an
image in it Netscape will either render it completely wrong (colored-lines) or render
the image in the wrong frame (i.e. the frame the DynAPI code is in, and not the target
frame). There's no work-around for this available, and is a browser-bug</dd></dl>
! <li><b>Form components always ontop</b>; browser: any</li>
! <dl><dd>I don't consider this a real bug, but there are alot of question about
this. This is just the way browsers handle form-elements. They will ALWAYS place it on
top of your layers. The only workaround would be to place the elements in one layer,
and hide that one when other layers need to be on top..Can't be fixed.</dd></dl>
! <li><b>Memory leaks</b>; browser: any</li>
! <dl><dd>At this point we're not yet sure if we can fix this, but using DHTML
will cause your browser to use icreasing amounts of memory. This might eventually
cause your browser to crash. This problem seems to be bigger for Internet Explorer
users then Netscape users, but happens in both browsers.</dd></dl>
! </ul>
! <h1><a name="6.1">6.1. Doing advanced things</a></h1>
<p>After reading the tutorials and looking at the examples you might be able to do
the most basic stuff, but
if you want more there's not much documentation available yet. The examples and
widgets should provide you with
***************
*** 450,454 ****
for the Dynacore is available which is for maybe 10% different from the official
DynAPI, and this will be converted into a DynAPI2 reference
somewhere in the future (hopefully NEAR)</p>
! <h1><a name="6.1">6.1. Limited Javascript knowledge</a></h1>
<p>"I want to use the DynAPI but have limited (or no) Javascript knowledge"<Br/>
<br/>
--- 470,474 ----
for the Dynacore is available which is for maybe 10% different from the official
DynAPI, and this will be converted into a DynAPI2 reference
somewhere in the future (hopefully NEAR)</p>
! <h1><a name="6.2">6.2. Limited Javascript knowledge</a></h1>
<p>"I want to use the DynAPI but have limited (or no) Javascript knowledge"<Br/>
<br/>
***************
*** 457,461 ****
change in the future, making it possible to do WYSIWYG development.</p>
! <h1><a name="6.2">6.2. Load external content into layers</a></h1>
<p>"How can I load external pages into dynlayers". <Br/>
<Br/>
--- 477,481 ----
change in the future, making it possible to do WYSIWYG development.</p>
! <h1><a name="6.3">6.3. Load external content into layers</a></h1>
<p>"How can I load external pages into dynlayers". <Br/>
<Br/>
_______________________________________________
Dynapi-CVS mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-cvs
