gatlin/Alm

Issues

• The `class` attribute in VDOM elements should be an array

  #19 opened 9 years ago by gatlin
  1

• Tests? Of any kind whatsoever?

  #6 opened 7 years ago by gatlin
  2

• Add those el helpers I keep manually recreating into Alm

  #20 opened 7 years ago by gatlin
  0

• Allow eventRoot and domRoot to be unspecified until start is called

  #24 opened 8 years ago by gatlin
  0

• Signals should memoize results

  #7 opened 8 years ago by gatlin
  0

• Pull-based signals

  #9 opened 8 years ago by gatlin
  1

• Tasks

  #12 opened 8 years ago by gatlin
  0

• `Signal.recv` should optionally take an array of functions

  #16 opened 8 years ago by gatlin
  0

• "Controller" wrapper around `App` for common design pattern

  #17 opened 8 years ago by gatlin
  0

• Include DOM helpers in some backward-compatible place

  #21 opened 8 years ago by gatlin
  0

• Prune unused event listeners before application start

  #18 opened 9 years ago by gatlin
  0

• Rename `runtime.utils` to `runtime.scope`

  #14 opened 9 years ago by gatlin
  0

• Apps with no Virtual DOM / GUI should be allowed

  #15 opened 9 years ago by gatlin
  0

• App event and DOM scopes shouldn't necessarily be the same

  #13 opened 9 years ago by gatlin
  0

• Do something about loeb.js

  #4 opened 9 years ago by gatlin
  0

• Packaging to satisfy js nerds

  #3 opened 9 years ago by gatlin
  0

• Less naive DOM diffing algorithm

  #5 opened 9 years ago by gatlin
  1

• vdom mailboxes

  #11 opened 9 years ago by gatlin
  0

• 'load' should be a default event

  #10 opened 9 years ago by gatlin
  0

• Remove Signal IDs

  #8 opened 9 years ago by gatlin
  0

• Virtual DOM is recreated from scratch on each view update

  #1 opened 9 years ago by gatlin
  2

• Virtual DOM should allow direct communication with nodes via mailboxes

  #2 opened 9 years ago by gatlin
  1