[Smax-commit] SF.net SVN: smax: [14] trunk/smaxproto/htdocs/index.html
Status: Alpha
Brought to you by:
dbrosius
Menu
▾
▴
[Smax-commit] SF.net SVN: smax: [14] trunk/smaxproto/htdocs/index.html
|
From: <dbr...@us...> - 2008-01-17 06:54:35
|
Revision: 14
http://smax.svn.sourceforge.net/smax/?rev=14&view=rev
Author: dbrosius
Date: 2008-01-16 22:51:32 -0800 (Wed, 16 Jan 2008)
Log Message:
-----------
add in the blend and links to other pages
Modified Paths:
--------------
trunk/smaxproto/htdocs/index.html
Modified: trunk/smaxproto/htdocs/index.html
===================================================================
--- trunk/smaxproto/htdocs/index.html 2008-01-17 06:47:23 UTC (rev 13)
+++ trunk/smaxproto/htdocs/index.html 2008-01-17 06:51:32 UTC (rev 14)
@@ -2,27 +2,36 @@
<head>
<title>SMAXProto - Simple Mutated API for XML Prototype</title>
</head>
- <body>
- <h1>SMAXProto</h1>
- <p>Thanks for your interested in SMAXProto.</p>
- <p>After using SAX parsing for just few times, it becomes clear that often the
- custom parser you write is only interested in a subset, and often a small subset,
- of the entire document. Often, much of the content handler is determining where
- you are in the tree, and ignore stuff you don't want. This project builds a
- prototype that attempts to simplify filtering out what you don't want to handle,
- thus simplifying the handler, and improving performance.</p>
- <p><b>THIS IS A PROTOTYPE</b></p>
- <p>A prototype should</p>
- <ul>
- <li>Be fun to do</li>
- <li>Be quickly implemented</li>
- <li>Do a decent job of showing the api</li>
- <li>Show relative performance issues</li>
- <li>Let you learn something new</li>
- <li>Be so ridiculously implemented, that no one is tempted to build a real product with it</li>
- </ul>
- <p>Hopefully this prototype fulfills all of these tasks</p>
- <p>SMAX follows the basic flavor of SAX. There are 3 key differences (at this point).<p>
+ <body background>
+ <div style="position:absolute;top:0;left:0;width:256;height:65535;z-index:1;background-image:url(blend.jpg);">
+ </div>
+ <div style="position:absolute;top:20;left:20;z-index:2;">
+ <h1>SMAXProto</h1>
+ <hr/>
+ <a href="http://www.sourceforge.net/projects/smax">Project Page</a>
+ <img src="vbar.gif" height="12"/>
+ <a href="javadoc/index.html">JavaDoc</a>
+ <hr/>
+
+ <p>Thanks for your interested in SMAXProto.</p>
+ <p>After using SAX parsing for just few times, it becomes clear that often the
+ custom parser you write is only interested in a subset, and often a small subset,
+ of the entire document. Often, much of the content handler is determining where
+ you are in the tree, and ignore stuff you don't want. This project builds a
+ prototype that attempts to simplify filtering out what you don't want to handle,
+ thus simplifying the handler, and improving performance.</p>
+ <p><b>THIS IS A PROTOTYPE</b></p>
+ <p>A prototype should</p>
+ <ul>
+ <li>Be fun to do</li>
+ <li>Be quickly implemented</li>
+ <li>Do a decent job of showing the api</li>
+ <li>Show relative performance issues</li>
+ <li>Let you learn something new</li>
+ <li>Be so ridiculously implemented, that no one is tempted to build a real product with it</li>
+ </ul>
+ <p>Hopefully this prototype fulfills all of these tasks</p>
+ <p>SMAX follows the basic flavor of SAX. There are 3 key differences (at this point).<p>
<ol>
<li>startDocument and startElement return an enum value of type NextParserAction<br/>
Enum Values are:
@@ -41,5 +50,6 @@
<li>startElement doesn't provide attributes</li>
<li>SMAX's ContentHandler provides an attributes method to implement to get attributes</li>
</ol>
+ </div>
</body>
</html>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
