damlengine.git - daml-to-html blog engine (Java)

	Commit message (Collapse)	Author	Age	Files	Lines
*	Rather than an ad hoc "Options" class, use caller todo directly.	David A. Madore	2010-04-19	1	-8/+6
\|
*	Rename TodoContext class to Context. Usually call "ctx" its instances.	David A. Madore	2010-04-18	1	-6/+6
\|
*	Preliminary handler for <daml> element.	David A. Madore	2010-04-18	1	-1/+0
\|
*	Hide the use of NodeList and NamedNodeMap by real Java ArrayList objects.	David A. Madore	2010-04-18	1	-9/+25
\| \| \| \| \|	This makes it possible to modify the underlying tree without getting hit by .item(i) returning the wrong next item.
*	Use ad hoc classes rather than hashes for context and options.	David A. Madore	2010-04-17	1	-11/+11
\|
*	Use ArrayList (supposedly faster because unsynchonized) rather than Vector.	David A. Madore	2010-04-17	1	-3/+3
\|
*	Use factories implemented as nested classes (rather than reflected ↵	David A. Madore	2010-04-17	1	-1/+10
\| \| \| \| \| \| \| \| \| \|	constructors) to store classes to instantiate. Now every subclass of TodoElement or TodoAttr should also come with a nested subclass of TodoElement.Factory or TodoAttr.Factory which just contains a(n instance) method to call its constructor. In essecne, the factory instance is just used as a pointer to the class to create (or its constructor, as in the previous version).
*	Change dispatching approach: handlers are now part of todoItems.	David A. Madore	2010-04-15	1	-0/+49
	Instead of dispatching the todo item in function of the DAML node's local name at todo-handling time, the appropriate todo handler subclass is now instantiated in the todo deque by dispatching the creation of the todo item to the appropriate constructor.