Annotation of wpdocumenter/www/index.html, revision 1.8

1.1       david       1: 
                      2: <!-- ***************** INFO/NEWS *************** -->
                      3: <div id="infoTabs">
                      4: <div class="infoTab" id="whats-new">
                      5: <h5 class="infoHeader">What's New</h5>
                      6: <ul>
1.8     ! bennyhof    7: <li>The first somewhat usable version is here ready to download!  If you install it, let me know what you think.</li>
1.1       david       8: <li>More news item goes here</li>
                      9: <li><a href="http://mozdev.org/">mozdev.org</a></li>
                     10: </ul>
                     11: </div>
                     12: 
                     13: <div class="infoTab" id="other-stuff">
                     14: <h5 class="infoHeader">Other Stuff</h5>
                     15: <ul>
                     16: <li>stuff goes here</li>
                     17: <li>more stuff goes here</li>
                     18: </ul>
                     19: </div>
                     20: 
                     21: <!-- alternative image/table base tab works better in NS4 -->
                     22: <!--
                     23: <div class="infoTab" id="whats-new-image">
                     24: <h5 class="infoHeader"><img src="http://www.mozdev.org/sharedimages/whatsnew_top.gif" width="154" alt="What's New"></h5>
                     25: <div class="infoItems">
1.5       bennyhof   26: <div>No news yet, but give me time, I&rsquo;ll have some soon!</div>
1.1       david      27: <div>More news item goes here</div>
                     28: <div><a href="http://mozdev.org/">mozdev.org</a></div>
                     29: </div>
                     30: </div>
                     31: -->
                     32: </div>
                     33: <!-- ***************** INFO/NEWS *************** -->
                     34: 
                     35: <!-- MAIN CONTENT -->
1.2       bennyhof   36: 
1.8     ! bennyhof   37: <p><b>What is WP Documenter?</b></p>
1.3       bennyhof   38: 
1.8     ! bennyhof   39: <p>WP Documenter stands for Web Page Documentor.  It is for web site developers and testers, but should be good as a learning tool for anyone wanting to easily see underlying CSS and javascript, and other HTML settings.  
        !            40: This extension will display in an easy to read table format to current exact status of a web page, including any data already entered in forms by the user.</p>
1.3       bennyhof   41: 
1.8     ! bennyhof   42: <p>The idea for this came about that when a tester finds a problem with a web page, often it is difficult to pass along to the developers exactly what the problem was.  
1.3       bennyhof   43: Quite often the developer needs to know the date, time, hidden fields, data entered, and more.
                     44: And often the tester has no idea what all that information was.
1.8     ! bennyhof   45: This can be used to store every piece of pertinent information on a web page into a formatted document that can be printed or stored.
        !            46: With it, all necessary data can be passed back to the developer, making his job easier.</p>
        !            47: 
        !            48: <p>Of course, it can be used by developers as well.  You can use it to quickly see what styles are in use from any style page, view all data settings, and more.</p>
1.3       bennyhof   49: 
1.8     ! bennyhof   50: <p>This is a work in progress, and any ideas on how to make it work better will be appreciated.  
1.3       bennyhof   51: As will any help in coding this monster, as I am very new to this.</p>
                     52: 
1.8     ! bennyhof   53: <hr width="90%"/>
        !            54: 
        !            55: <p><b>Background</b></p>
        !            56: <p>This extension began as a little project to learn how to do macros with Firebird to fill in forms automatically.  (I found that there were extensions built to do that already.)
        !            57: But, from that idea, I have learned how to read, and then display web page data.  Then I saw how to format the data so only the important information (from a web page developer&rsquo;s perspective) was displayed in an easy to read format.   
        !            58: After that I decided why not learn how to add this functionality to the Firebird menu, and after that, build an interface so that the procedure could be customized.
        !            59: This lead to me learning how to work with XML &amp; XUL (quite the learning experience).
        !            60: Well this has grown and grown, so the next logical step is to make this available to all users.</p>
1.3       bennyhof   61: 
1.8     ! bennyhof   62: <p>For the moment, you can check out the screenshots page.  I will be posting a few images there to give you an idea of how it works.</P>
1.4       bennyhof   63: 
                     64: <p>Thanks,
                     65: <br/>
                     66: Scott Bennyhoff</p>
1.7       bennyhof   67: <hr width="85%"/>
                     68: 
                     69: <p><strong>Note:</strong> If you want to add an area for user feedback to any of your pages, take a look at the <a href="notes.html">notes.html</a>
                     70: template.</p>
1.2       bennyhof   71: 

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>