[Templates-cvs] cvs commit: Template2/docsrc/src/Release TODO.tt2
cvs@template-toolkit.org
cvs@template-toolkit.org
cvs 06/05/25 08:22:38
Modified: docsrc/src/Release TODO.tt2
Log:
Applied Paul Seamon's CHOMP patch
Revision Changes Path
1.19 +8 -68 Template2/docsrc/src/Release/TODO.tt2
Index: TODO.tt2
===================================================================
RCS file: /template-toolkit/Template2/docsrc/src/Release/TODO.tt2,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- TODO.tt2 2006/02/01 15:03:12 1.18
+++ TODO.tt2 2006/05/25 08:22:37 1.19
@@ -12,7 +12,7 @@
# Andy Wardley <abw@wardley.org>
#
#------------------------------------------------------------------------
-# $Id: TODO.tt2,v 1.18 2006/02/01 15:03:12 abw Exp $
+# $Id: TODO.tt2,v 1.19 2006/05/25 08:22:37 abw Exp $
#========================================================================
#------------------------------------------------------------------------
@@ -113,14 +113,6 @@
#------------------------------------------------------------------------
-# Stash
-#------------------------------------------------------------------------
-
-* Have stash, etc., add current template name/line when reporting errors.
- (may be tricky under the current implementation)
-
-
-#------------------------------------------------------------------------
# Parser
#------------------------------------------------------------------------
@@ -139,64 +131,6 @@
# foo <- this gets printed
%]
-* Allow { and } as block delimiters, replacing for the ugly ';' and
- big, chunky [% END %] approach.
-
- e.g. something like:
-
- [% FOREACH a = [ 1 2 3 ] %]
- [% IF b == a %]
- [% INCLUDE foo %]
- [% ELSE %]
- [% INCLUDE bar %]
- [% END %]
- [% END %]
-
- could be written as:
-
- [% FOREACH a = [ 1 2 3 ] {
- IF b == a {
- INCLUDE foo
- }
- ELSE {
- INCLUDE bar
- }
- }
- %]
-
-* Ability to set different parser options for BLOCK definitions, etc.
-
- [% BLOCK header
- eval_perl = 0
- pre_chomp = 1
- %]
- ...
- [% END %]
-
- Anonymous BLOCK can then be used to set a parser scope
-
- [% BLOCK trim=1 %]
- ...
- [% END %]
-
- [% BLOCK trim=0 %]
- ...
- [% END %]
-
- And/or set different tag styles, etc.
-
- [% BLOCK tags='star' %]
- [* INCLUDE this_is_a_directive *]
- [% INCLUDE this_is_not %]
- [* END *]
-
- [% INCLUDE back_to_normal %]
-
- This is likely to be a TT3 feature and I've already got the basic
- parser for this up and running. It might get back-pactched into
- version 2, otherwise you might have to wait for the first alpha
- release of verion 3.
-
* Craig Barratt reports the following:
I looked at Parse.yp to see how hard it would be to push FILTER
@@ -296,7 +230,8 @@
* The Template::Plugin DBI iterator first/last() methods don't behave
the same as list first/last(). Randal also reports that get_all()
- doesn't work as it should - may be a conflict in code/docs?
+ doesn't work as it should - may be a conflict in code/docs? Again,
+ this is a problem to solve in TT3.
* PLUGINS could accept a reference to an object which is used as a
singleton factory for a plugin. (NOTE: 2.01 includes PLUGIN_FACTORY
@@ -364,6 +299,11 @@
#------------------------------------------------------------------------
# Splash!
#------------------------------------------------------------------------
+
+The Splash! library will be extracted into a separate distribution at
+some point (probably when TT3 is released, possibly before). At that
+point it will deprecated (read: not supported by me any more) in favour
+of something better.
The current implementation is a fairly ugly hack to get something up
and running that's good enough to use. It's mainly template driven