PageRenderTime 14ms CodeModel.GetById 9ms app.highlight 1ms RepoModel.GetById 1ms app.codeStats 0ms

/todo/stuff_I_could_use_now.todo

http://zoop.googlecode.com/
Unknown | 45 lines | 45 code | 0 blank | 0 comment | 0 complexity | 00c416058d1ab4415591099b49eb706c MD5 | raw file
 1-	form validation
 2-	smarty replacement
 3	-	lists
 4		-	http://www.webresourcesdepot.com/19-promising-php-template-engines/
 5		-	http://www.sitepoint.com/forums/showthread.php?threadid=123769
 6		-	http://fabien.potencier.org/article/34/templating-engines-in-php
 7	-	individual engines
 8		-	H2O http://github.com/speedmax/h2o-php there are some interesting concepts here
 9		-	twig: http://www.twig-project.org/
10	-	pure php caches
11		-	http://www.optimalworks.net/blog/2007/software/free-download/tacs-php-template
12	-	write your own
13	-	also see gui.todo
14	-	make it configurable so users can choose what they want
15	-	also look into other radical non-template type replacements
16		-	client side systems that just spit out static html/css and get their dynamic data through json and then put it in on the client side
17		-	systems that have static html that is manipulated outside the markup with css like selectors
18			-	http://tobiasz123.wordpress.com/2009/03/01/querytemplates-development-progress/ (I don't like this one very well but I think the concept could be done well)
19			-	http://querypath.org/
20		-	yaml based system that is just html but readable
21		-	php object based systes that use object and method calls to construct the markup
22	-	things that we need
23		-	complex expression evaluation in the template
24		-	good variable scoping
25		-	the ability to handle ordering issues
26			-	logical execution order and display order are not the same
27				-	for instance a display element below uses logic to calculate a value above
28				-	or you want to set the title of a page inside an include and then use it in the outer tempalte, possibly above where the include actually occured
29			-	see the concept of inheritance as implemented here http://github.com/speedmax/h2o-php
30		-	good control of output filtering on a per variable / per function basis
31			-	default to filtering
32			-	let you easily disable the filter for specific instnances or at the template level
33		-	easy debugging - making sure that line numbers in the compiled php match up with the template line numbers (nice to have)
34		-	whitespace control (nice to have)
35		-	php css extensions (exotic)
36			-	http://wiki.github.com/anthonyshort/csscaffold
37		-	translation integration (exotic)
38-	better authorization tools
39-	improved graphic module
40-	better charting / graphing module
41-	good logging framework
42-	good stuff for dynamically generating static files
43	-	proper caching
44	-	posibility of combining many files into one
45	-	optimize of content: minimize js, remove whitespace, etc