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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Use ad hoc classes rather than hashes for context and options.	David A. Madore	2010-04-17	7	-46/+64
\|
*	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	4	-41/+47
\| \| \| \| \| \| \| \| \| \|	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).
*	Use static initializers correctly (I had forgotten the "static" keyword!).	David A. Madore	2010-04-16	2	-8/+2
\|
*	Change dispatching approach: handlers are now part of todoItems.	David A. Madore	2010-04-15	11	-106/+130
\| \| \| \| \| \| \|	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.
*	Instantiate TodoDeque rather than using static variables.	David A. Madore	2010-04-15	4	-24/+30
\| \| \| \|	Unfortunately, processing is now rather significantly slower.
*	Make handlers instances instead of using static methods.	David A. Madore	2010-04-14	6	-85/+67
\|
*	Handle d:xempty attribute, as proof of concept.	David A. Madore	2010-04-13	3	-7/+22
\|
*	Framework for handling attributes.	David A. Madore	2010-04-13	6	-59/+141
\|
*	Create a todo deque class, and use it.	David A. Madore	2010-04-13	3	-6/+72
\|
*	Start writing a todo item handling framework.	David A. Madore	2010-04-13	3	-3/+53
\|
*	Start writing code for a todo stack.	David A. Madore	2010-04-12	2	-0/+26
\|
*	Purge unnecessary import.	David A. Madore	2010-04-12	1	-1/+1
\|
*	Write a semi-decent unparser(=serializer).	David A. Madore	2010-04-12	2	-13/+74
\| \| \| \|	Still a bit rough at the edges, but this basically does what I want.
*	Move ad hoc serializer to an "Unparser" class (ugly and unfinished).	David A. Madore	2010-04-12	2	-47/+92
\|
*	Handle x-daml-magic URL (this should go away eventually, of course).	David A. Madore	2010-04-11	1	-0/+38
\|
*	Implement a toy serializer of my own (just the structure).	David A. Madore	2010-04-11	1	-15/+48
\| \| \| \|	This should go into a separate class, of course.
*	Another attempt at output formatting, this time with serializers. Still sucks.	David A. Madore	2010-04-11	1	-13/+8
\|
*	Alternate version using javax interfaces rather than the W3C DOM Load&Save.	David A. Madore	2010-04-11	1	-19/+25
\| \| \| \| \| \|	I was rather hoping this would pretty-print XHTML as required (e.g., put a space before the final slash on empty tags), but alas, such is not the case.
*	Start a Java version of a daml engine. So far, just the identity transform.	David A. Madore	2010-04-11	2	-0/+204
	Even for something so completely trivial, this was a pain to write, because some stupid XML catalog was distributed with a DOCTYPE referencing a broken URL which could not be replaced by a local file because the catalog engine was bootstrapping; nor did Xerces provide a way, in org.apache.xerces.util.XMLCatalogResolver, to provide a bootstrap resolver: so I had to partially rewrite XMLCatalogResolver.