blob: 59a664fffc68a724bf2a2d02b0b0e4ac16ed4760 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
* Now
- (x) Hydrate existing elements instead of re-creating
- (x) `load-cssx` functions
- (x) `get-variable`
- (x) `update-variable`
- (x) Use css units for `delay` function
- (x) Specify node type - `button(id)` or `button#id`
- (x) attributes
- (x) `--cssx-text` (and maybe `--cssx-html`?)
- (x) dom tests
- (x) `attr` function
- (x) `set-attr` should allow specifying id?
- (x) `set-attr` + remove attribute?
- (x) `pair` parsing
- (x) `selector` parsing
- (x) `map` data structure
- (x) component system (with variables. `instance(button#my-btn)`)
- (x) More complex selector support for cssx-children
- (x) `add-element` & `remove-element`
- (x) conditionals
- (x) on update
- ( ) children of instance must also be instantiated
- ( ) access child from an instance (update checkbox)
- ( ) access instance from child (delete task)
- ( ) filter for on update on specific properties
- ( ) eval
- ( ) update property on child on update of parent
- ( ) functions/lazy properties?
- ( ) string concatenation
- ( ) `request` error handling
- ( ) keyboard events
- ( ) Code cleanup
* Later
- ( ) `add-class` & `remove-class` should use self if id is not specified?
- ( ) Evaluate `calc`
- ( ) access an instance of component
- ( ) Additional events
- ( ) Improve error messages
* Maybe
- ( ) `list` & `tuple` data structures?
- ( ) server-side css? Why the fuck not!?
|
