Update of /cvsroot/dynapi/dynapi/docs/docs
In directory usw-pr-cvs1:/tmp/cvs-serv26900
Modified Files:
faq.html
Log Message:
updated faq
Index: faq.html
===================================================================
RCS file: /cvsroot/dynapi/dynapi/docs/docs/faq.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -r1.6 -r1.7
*** faq.html 2001/02/09 15:48:31 1.6
--- faq.html 2001/02/13 18:09:28 1.7
***************
*** 11,15 ****
<h1>The official DynAPI2 F.A.Q.</h1>
! <h5>last update: 2001.02.05</h5>
<ul>
--- 11,15 ----
<h1>The official DynAPI2 F.A.Q.</h1>
! <h5>last update: 2001.02.13</h5>
<ul>
***************
*** 42,45 ****
--- 42,46 ----
<li><a href="#3.2">3.2. I tested on browser X, here are the results</a></li>
<li><a href="#3.3">3.3. What about the Mac?</a></li>
+ <li><a href="#3.4">3.4. DOM compliant</a></li>
</ul>
<li><a href="#4">4. How can I contribute</a></li>
***************
*** 47,50 ****
--- 48,52 ----
<li><a href="#4.1">4.1. "Why don't you guys do this, or add that?"</a></li>
<li><a href="#4.2">4.2. This thing isn't working at all</a></li>
+ <li><a href="#4.2.1">4.2.1. Where can I submit bugs?</a></li>
<li><a href="#4.3">4.3. How can I become a developer</a></li>
<li><a href="#4.4">4.4. Using CVS.</a></li>
***************
*** 66,69 ****
--- 68,72 ----
<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>
+ <li><a href="#6.4">6.4. Accessing html elements in layers</a></li>
</ul>
</ul>
***************
*** 130,139 ****
the other developers will help by adding questions and answers to this
f.a.q. I'll make this f.a.q. available at the sourceforge site and my
! own website (<a href="http://www.dynamic-core.net">http://www.dynamic-core.net</a>).
</p>
<h1><a name="1.1.3"></a>1.1.3. Where to get the f.a.q.</a></h1>
<p>The latest f.a.q. can be found on my own website, because it's uploaded
! there first (<a href="http://www.dynamic-core.net">www.dynamic-core.net</a>). But
! it's also available at the urls mentioned in <a href="#2.3">2.3 Other
resources</a></p>
<h1><a name="1.2"></a>1.2. Why upgrade</a></h1>
--- 133,142 ----
the other developers will help by adding questions and answers to this
f.a.q. I'll make this f.a.q. available at the sourceforge site and my
! own website (<a
href="http://www.dynamic-core.net/core/files/faq.dynapi2.html">http://www.dynamic-core.net/core/files/faq.dynapi2.html</a>).
</p>
<h1><a name="1.1.3"></a>1.1.3. Where to get the f.a.q.</a></h1>
<p>The latest f.a.q. can be found on my own website, because it's uploaded
! there first (<a
href="http://www.dynamic-core.net/core/files/faq.dynapi2.html">http://www.dynamic-core.net/core/files/faq.dynapi2.html</a>).
But
! it's also available at the urls mentioned in <a href="#2.3">2.3 Other resources</a>
and should be available in the DynAPI2 distribution as well (although outdated).</p>
<h1><a name="1.2"></a>1.2. Why upgrade</a></h1>
***************
*** 175,181 ****
<h1><a name="1.4"></a>1.4. Differences between DynAPI and Dynacore</a></h1>
! <p>The DynAPI2 (as found at <a
href="http://dynapi.sourceforge.net/">http://dynapi.sourceforge.net</a> is the
official release as started by Dan Steinman and is being continued by a group of
developers (including little me).
! The Dynacore is my personall distribution of the DynAPI2, it's based on DynAPI2 code
and ideas but differs in certain
areas from the official one. These are usually ideas that I wanted to include but
others didn't, and ideas that
others wanted to include and I didn't will be left out of the Dynacore.<br/>
--- 178,184 ----
<h1><a name="1.4"></a>1.4. Differences between DynAPI and Dynacore</a></h1>
! <p>The DynAPI2 (as found at <a
href="http://dynapi.sourceforge.net/">http://dynapi.sourceforge.net</a>) is the
official release as started by Dan Steinman and is being continued by a group of
developers (including little me).
! The Dynacore is my personal distribution of the DynAPI2, it's based on DynAPI2 code
and ideas but differs in certain
areas from the official one. These are usually ideas that I wanted to include but
others didn't, and ideas that
others wanted to include and I didn't will be left out of the Dynacore.<br/>
***************
*** 206,210 ****
to put a deadline on things. The main idea is "it's done when it's done". It's
understood that a previous
release sometimes looks very outdated compared to the latest snapshot, but that's
just how it works. You are ofcourse
! free to use the daily snapshot but as stated at some places it's code which is under
development; meaning that if it works today
it might be broken tomorrow, something which won't happen in the release (if it's
broken tomorrow, it was also broken today :-).</p>
<h1><a name="2.2"></a>2.2. Where can I find support</a></h1>
--- 209,213 ----
to put a deadline on things. The main idea is "it's done when it's done". It's
understood that a previous
release sometimes looks very outdated compared to the latest snapshot, but that's
just how it works. You are ofcourse
! free to use the daily snapshot but as stated at some places in this faq: it's code
which is under development; meaning that if it works today
it might be broken tomorrow, something which won't happen in the release (if it's
broken tomorrow, it was also broken today :-).</p>
<h1><a name="2.2"></a>2.2. Where can I find support</a></h1>
***************
*** 229,232 ****
--- 232,236 ----
<dl><dd>Used for DynAPI2 development. Mostly used by the developers and people
helping out with bug fixes, new functionality, etc..</dd></dl>
</ul>
+ <p>for a full list of DynAPI2 mailinglists visit: <a
+href="http://www.mail-archive.com/index.php3?hunt=dynapi">http://www.mail-archive.com/index.php3?hunt=dynapi</a>
+ this also contains searching facilities to search the mailinglist archives.</p>
<h1><a name="2.3"></a>2.3. Where can I find the documentation</a></h1>
<p>If your used to Dan Steinman's dynduo tutorial your in for a shock because
***************
*** 267,271 ****
<p>The current version of the API is mainly worked on by windows users, so logically
the windows browsers will be supported better then other platforms. Here's the
! list of browsers:<br/></p>
<table border=0 width = 100%>
<tr><td>Internet Explorer 4</td><td>(windows)</td></tr>
--- 271,275 ----
<p>The current version of the API is mainly worked on by windows users, so logically
the windows browsers will be supported better then other platforms. Here's the
! list of browsers:<br></p>
<table border=0 width = 100%>
<tr><td>Internet Explorer 4</td><td>(windows)</td></tr>
***************
*** 276,279 ****
--- 280,284 ----
<tr><td>Mozilla (milestone 16 and higher)</td><td>(windows, linux?)</td></tr>
</table>
+ <p>Note that these browsers might not be fully 100% supported but we're targetting
+these browsers. For a better and more complete compatibility matrix please visit <a
+href="http://www.shireyproductions.com/dynapi/matrix/default.htm">http://www.shireyproductions.com/dynapi/matrix/default.htm</a></p>
<h1><a name="3.1"></a>3.1. When will browser X be supported</a></h1>
<p>Good question, the most important thing to remember is the simple fact that
***************
*** 308,311 ****
--- 313,326 ----
do the debugging them selves.. it's the only way that will work.</p>
+ <h1><a name="3.4">3.4. DOM compliant</a></h1>
+ <p>The DynAPI is being created to be cross-browser compliant. Although the W3C is
+setting standards (DOM1, DOM2), the browsers that comply
+ to these standards might not always work correctly. The problem lies in a few
+factors. The main factor being Javascript, Javascript standards are
+ not part of the W3C's DOM, although there is a Javascript standard, this is
+something not (yet) supported by all browsers. This is also the main problem
+ we have when trying to make DynAPI work crossbrowser. Another problem is that there
+are no real DOM compliant browsers yet. There are ofcourse a few
+ browsers that are being developed to be DOM compliant, but at this time these
+browsers seem to contain small bugs that can screw up the DynAPI code.<br>
+ <Br>
+ The main goal is to get things working correctly under NS6 (seeing as it is the best
+known DOM compliant browser) and from there on it should be possible
+ to support all other DOM compliant browsers.</p>
+
<h1><a name="4"></a>4. How can I contribute</h1>
<p>"I like the project alot, I have been using it for a while and want to help
***************
*** 358,361 ****
--- 373,388 ----
still hasn't fixed your problems, please join the mailinglists at sourceforge (see
<a href="#2.1">2.1</a>)
and post a detailed description of your problem and code.</p>
+
+ <h1><a name="4.2.1">4.2.1. Where can I submit bugs?</a></h1>
+ <p>The best place to submit bugs is at the Sourceforge site <a
+href="http://www.sourceforge.net/projects/dynapi">http://www.sourceforge.net/projects/dynapi</a>
+ in the bugs section,
+ Sourceforge supplies us with a great tool for keeping track of bugs. Alot of people
+post there bugs in the mailinglists, this is great but it also means that with the
+ high-traffic of those lists that bugs might get lost.<br>
+ <br>
+ When submitting your bugs please make sure to specify the bug as clearly as possible
+(with the smallest example code if possible) this way it's alot easier for
+ developers to recreate the situation. Also try to leave your name somewhere (if you
+have a sourceforge user name it will be done automatically) this is easier then
+communicating
+ with "nobody".<br>
+ <br>
+ If for some reason your bug is closed without a fix, this might mean that the bug
+was not reproduceable.. if the bug can't be recreated it's hard to fix and will most
+likely be closed specifying the reason.</p>
+
<h1><a name="4.3"></a>4.3. How can I become a developer</h1>
<p>Currently there's only a short list of developers for the DynAPI2, this doesn't
mean those developers are
***************
*** 363,368 ****
no special rules on who can or can not join the developers list, but I think it all
depends on how much you
can and are contributing to the project. There's a large difference between someone
giving feedback, and someone fixing
! a multiple bugs and adding extra functionality.. so I guess only people doing alot
of development, and showing a "long-term"
! commitment are added to the developers list and given full access to patches/bugs,
etc..
</p>
<h1><a name="4.4"></a>4.4. Using CVS.</a></h1>
--- 390,396 ----
no special rules on who can or can not join the developers list, but I think it all
depends on how much you
can and are contributing to the project. There's a large difference between someone
giving feedback, and someone fixing
! multiple bugs and adding extra functionality.. so I guess only people doing alot of
development, and showing a "long-term"
! commitment are added to the developers list and given full access to patches/bugs,
etc.. But everyone on the developers list is
! part of the DynAPI developers.
</p>
<h1><a name="4.4"></a>4.4. Using CVS.</a></h1>
***************
*** 433,440 ****
<h1><a name="5.2"></a>5.2. Where should I upload my widgets</a></h1>
<p>Good question.. your website? There's no official location availabe yet that
contains a
! widget archive (see <a href='#5.3'>5.3</a> for more info). If there's enough people
offering widgets I might open one on my
! own site somewhere but for now just use your own website and post a message in
! one of the mailinglists (see <a href="#2.1">2.1</a>). If you don't own a website you
could
! get a free one at one of the many free web space providers (geocities, xoom,etc).</p>
<h1><a name="5.3"></a>5.3. Where is widget X</a></h1>
<p>Most of the original DynAPI1 widgets have (or will be) ported to the DynAPI2. If
--- 461,470 ----
<h1><a name="5.2"></a>5.2. Where should I upload my widgets</a></h1>
<p>Good question.. your website? There's no official location availabe yet that
contains a
! widget archive (see <a href='#5.3'>5.3</a> for more info). Also please don't expect
that your widgets are being added
! to the DynAPI2 distribution. DynAPI2 will be supplied with a standard set of widgets
(either the same package or as seperate download
! from the DynAPI2 website). If we would add all widgets to the distribution it would
become bloated and might also scare new users by having
! so much code and not knowing what to do with it. For now just use your own website
and post a message in
! one of the mailinglists (see <a href="#2.1">2.1</a>). If you don't own a website you
could get a free one at one of
! the many free web space providers (geocities, xoom,etc).</p>
<h1><a name="5.3"></a>5.3. Where is widget X</a></h1>
<p>Most of the original DynAPI1 widgets have (or will be) ported to the DynAPI2. If
***************
*** 456,460 ****
<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>
--- 486,490 ----
<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>
***************
*** 463,466 ****
--- 493,502 ----
<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>
+ <li><b>Scrolling problems</b>; browser: any</li>
+ <dl><dd>Not a real bug, but when using DHTML Layers that extend beyond the
+browsers frame borders there are some differences in how browsers handle this. In
+Netscape there will be no scrollbars showing up, yet in IExplorer there will always
+be scrollbars moving. This causes problems any way you want it. If you like the IE
+style you can emulate it with NS by using the following code:
+
+<br><code>document.width=<pixels><br>document.height=<pixels></code><br>This
+resizes the browsers document showing the scrollbars. If, however, you like it the NS
+style (no scrollbars) you can add the keyword <code>scroll=no</code> in the property
+of the <body> tag for IE.</dd></dl>
+ <li><b>Naming inline layers/variables</b>; browser: Internet Explorer</li>
+ <dl><dd>One bug/feature in IE causes problems when creating a variable with
+the same name as an inline layer. It will cause problems in IE, it will not see the
+difference between the inline layer and the variable. Workaround: use another name
+:)</dd></dl>
+
</ul>
<h1><a name="6.1">6.1. Doing advanced things</a></h1>
***************
*** 482,485 ****
--- 518,533 ----
The only way to do this is by using the LoadPanel widget, this provides
functionality for loading URL's into a normal DynLayer. The LoadPanel widget should
be supplied with your DynAPI2 distribution.</p>
+
+ <h1><a name="6.4">6.4. Accessing form elements in layers</a></h1>
+ <p>DynLayers can contain form elements or images, in some cases you'll need to be
+able to retrieve values from these form elements or set the image source. This can be
+done using the <code>.doc</code> property of a layer.
+ This property refers to the layer's document. So to access a form in a layer this is
+basically how to do it:</p>
+ <pre>
+ myLayer.doc.formname.formelement.value
+ </pre>
+ <p>or setting an image's source:</p>
+ <pre>
+ myLayer.doc.images['imagename'].src=newsource
+ </pre>
+ <p>Note that in IE the image array is a global array, so you can't use the name
+"thisimage" in two different layers.</p>
_______________________________________________
Dynapi-CVS mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-cvs
