| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This makes it possible to modify the underlying tree without getting
hit by .item(i) returning the wrong next item.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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).
|
|
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.
|