mcudich / templatekit Goto Github PK

To the extent that it meets App Store guidelines, templates should allow for simple conditional and looping logic (like Mustache does).

Support mutating property and state values over time, or via a gesture. Proper animation support would allow specifying things like transitions, keyframes, and so on. These need to be settable both via declarative and imperative syntax.

There currently is no way to hide a component (a la display: none in CSS). Hiding a component should remove it completely from layout calculations, but have it remain in the UI tree.

Add a basic List component that supports simple use cases where a TableView might be used. Such a component would receive a delegate and data source as properties and would manage updating itself as needed.

Sometimes templates in XMLTemplateService cache aren't found. This perhaps is due to some sort of thread safety issue with this cache.

Add an out-of-the-box element type for UIScrollView that maps to a container node.

Right now, it blindly reloads data any time it sees that item keys have changed. Instead, the table component should diff the item keys to understand the minimum set of operations it needs to perform to reload rows.

Inserting a section doesn't cause the table view to re-query the data source after endUpdates.

And perhaps consider using cubic bezier functions to represent them (see WebKit's UnitBezier.h)

Right now you can only animate a single animatable, but not chain them or compose them in any way. Add some sort of AnimatableGroup object or something that would allow for this.

EXC_BAD_ACCESS is hit when resuming a data task. This is rare, but it happens.

Right now, there's no way to specify a given set of styles that should be applied to a component when that component's state changes. This has to do with the fact that styles are passed as properties, and an internal state change is insulated within a component. This means that state may change, and the parent component, where the styles are defined, may not know about it.

Add an out-of-the-box element type for UISwitch and other basic elements.

Right now they always execute immediately.

There seems to be an issue with XMLElement being leaked when parsing an XML document.

Using the standard CSS transition property. The component rendering this template would need to get access to whatever Animatables are constructed from the CSS property declarations so that it could animate them appropriately.

updated my fork to swift 4
https://github.com/davidseek/TemplateKit
if anyone s'interested

Attempt to use the Apple protocol-buffer implementation.