jon 01/03/19 00:54:07
Modified: xdocs todo.xml
docs todo.html
Log:
removed a bunch of things from the todo list because they are already done
Revision Changes Path
1.12 +0 -75 jakarta-velocity/xdocs/todo.xml
Index: todo.xml
===================================================================
RCS file: /home/cvs/jakarta-velocity/xdocs/todo.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- todo.xml 2001/02/26 06:38:54 1.11
+++ todo.xml 2001/03/19 08:54:02 1.12
@@ -25,16 +25,6 @@
<section name="The List">
<p>
- <strong>Runtime API</strong>
- <br/>
- The Velocity Runtime is the single access point for all
- Velocity's functionality. A standard API for the
- Runtime should be defined so that in the span between
- the 0.5 Milestone release and a 1.0 release, the Runtime
- API changes as little as possible.
- </p>
-
- <p>
<strong>Directive Interface</strong>
<br/>
Right now there is a very thin interface for directives, but
@@ -45,41 +35,6 @@
</p>
<p>
- <strong>Context</strong>
- <br/>
- The Velocity Context class is still fairly primitive. It
- loosely adheres to a Map, but it definitely needs some
- thinking. It works fine now, but it might be good to
- think about: how to load standard tools and how to
- make that process efficient; how to stamp items in
- the context with expiry durations so that items can
- be cached and how this might work.
- </p>
-
- <p>
- <strong>User's Guide</strong>
- <br/>
- This would be a guide for designers who would
- be using the Velocity Template Language (VTL) to
- create templates. The users guide would give
- example usage and a definitive description
- of the VTL syntax. <a href="mailto:[EMAIL PROTECTED]">Jason van Zyl</a>
- has started work on this with John Castura, but any and all
- suggestions are welcome.
- </p>
-
- <p>
- <strong>Developer Guide</strong>
- <br/>
- This would be a guide for developers who would use
- Velocity as a standalone servlet tool, or in conjuction
- with a servlet controller framework like Turbine.
- <a href="mailto:[EMAIL PROTECTED]">Jason van Zyl</a> is
- currently working on this guide, but any and all suggestions
- are welcome.
- </p>
-
- <p>
<strong>Caching</strong>
<br/>
It would be good to have a discussion about how objects
@@ -124,34 +79,6 @@
</p>
<p>
- <strong>Encoding Caching</strong>
- <br/>
- What would this entail? And how could we implement an
- efficient encoding caching mechanism.
- </p>
-
- <p>
- <strong>Plugins</strong>
- <br/>
- It would be good to allow plugins in the form of JAR files
- to be picked up the Velocity Runtime during startup. This
- would be a good way for Velocity developers to share tools
- that could be used in a context. For example there are some
- utilities in Turbine that allow email to be sent from within
- a template. It might be good to package this sort of utility
- in a JAR file so that there are no dependencies in the
- Velocity build for a specific utility.
- </p>
-
- <p>
- <strong>Context Tools</strong>
- <br/>
- What kind of tools might be good to add to Velocity? There
- are several utilties that have been created in Turbine that
- might be good to move over to the Velocity code base.
- </p>
-
- <p>
<strong>Syntax Dumper</strong>
<br/>
Right now there is a primitive syntax dumper in the Velocity
@@ -200,8 +127,6 @@
scripting solutions provide a compiler, performance would still
remain at an acceptable level.
</p>
-
-
</section>
1.20 +0 -66 jakarta-velocity/docs/todo.html
Index: todo.html
===================================================================
RCS file: /home/cvs/jakarta-velocity/docs/todo.html,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- todo.html 2001/03/15 07:10:48 1.19
+++ todo.html 2001/03/19 08:54:05 1.20
@@ -124,15 +124,6 @@
<tr><td>
<blockquote>
<p>
- <strong>Runtime API</strong>
- <br />
- The Velocity Runtime is the single access point for all
- Velocity's functionality. A standard API for the
- Runtime should be defined so that in the span between
- the 0.5 Milestone release and a 1.0 release, the Runtime
- API changes as little as possible.
- </p>
- <p>
<strong>Directive Interface</strong>
<br />
Right now there is a very thin interface for directives, but
@@ -142,38 +133,6 @@
probably makes sense to shield directive creators from JavaCC.
</p>
<p>
- <strong>Context</strong>
- <br />
- The Velocity Context class is still fairly primitive. It
- loosely adheres to a Map, but it definitely needs some
- thinking. It works fine now, but it might be good to
- think about: how to load standard tools and how to
- make that process efficient; how to stamp items in
- the context with expiry durations so that items can
- be cached and how this might work.
- </p>
- <p>
- <strong>User's Guide</strong>
- <br />
- This would be a guide for designers who would
- be using the Velocity Template Language (VTL) to
- create templates. The users guide would give
- example usage and a definitive description
- of the VTL syntax. <a href="mailto:[EMAIL PROTECTED]">Jason van Zyl</a>
- has started work on this with John Castura, but any and all
- suggestions are welcome.
- </p>
- <p>
- <strong>Developer Guide</strong>
- <br />
- This would be a guide for developers who would use
- Velocity as a standalone servlet tool, or in conjuction
- with a servlet controller framework like Turbine.
- <a href="mailto:[EMAIL PROTECTED]">Jason van Zyl</a> is
- currently working on this guide, but any and all suggestions
- are welcome.
- </p>
- <p>
<strong>Caching</strong>
<br />
It would be good to have a discussion about how objects
@@ -213,31 +172,6 @@
to have a configuration of a setup for a common profiler
so that anyone who wanted to do some profiling could do
so in a consistent manner.
- </p>
- <p>
- <strong>Encoding Caching</strong>
- <br />
- What would this entail? And how could we implement an
- efficient encoding caching mechanism.
- </p>
- <p>
- <strong>Plugins</strong>
- <br />
- It would be good to allow plugins in the form of JAR files
- to be picked up the Velocity Runtime during startup. This
- would be a good way for Velocity developers to share tools
- that could be used in a context. For example there are some
- utilities in Turbine that allow email to be sent from within
- a template. It might be good to package this sort of utility
- in a JAR file so that there are no dependencies in the
- Velocity build for a specific utility.
- </p>
- <p>
- <strong>Context Tools</strong>
- <br />
- What kind of tools might be good to add to Velocity? There
- are several utilties that have been created in Turbine that
- might be good to move over to the Velocity code base.
</p>
<p>
<strong>Syntax Dumper</strong>
