You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: readme.md
+10-6Lines changed: 10 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,23 @@
1
1
#Action!
2
+
`Action!` is a front end sub/pub based framework for event based development. No more passing around dependencies, no more worrying about timing. Events free you to build apps that function they way the real world does: cause and effect.
3
+
4
+
Need data? Ask for it. Need to do something with that data? Listen for when it is sent back to you and do it. Need to watch for the user to do something? Listen for it and react accordingly. `Action!` embraces the asynchronicity that is the world around us to create better front end experiences and code.
5
+
2
6
3
7
##Road Map
4
8
So there are a variety of things that need to be completed for Action! to be ready for primetime. Some of them are basic (getting statemachine working), others are more complex (build tooling for troubleshooting event stacks). I am going to keep them here and make this a living document.
5
9
6
10
###TODOs before RC
11
+
0. make the destroy function silence all events registered by the object it is called on
7
12
0. dependency resolution integration with state machines
8
13
0. Figure out the testing side of event driven FED in Action
9
14
0. Revise the destroy function to make it really do what it needs to
10
15
0. Figure out how views really work... (https://github.com/twitter/hogan.js)
11
-
0. Consider web components
12
16
13
17
###TODOs generally
14
18
0. create a prod branch and a debug branch (prod probably doesn't need the extra weight of the call stack and emitterid stuff)?
15
19
0. update documentation
16
20
0. example app
17
-
0. simplify model set function?
18
21
0. make the error output even prettier! https://developers.google.com/chrome-developer-tools/docs/console-api#consoleerrorobject_object
19
22
20
23
###Done
@@ -25,10 +28,11 @@ So there are a variety of things that need to be completed for Action! to be rea
25
28
0. Clone/ Deep Copy in the set functions
26
29
0. Build out the save function for models
27
30
0. ajax resolution/integration for models
28
-
31
+
0. Consider web components (considered... and moved on for now)
32
+
0. simplify model set function?
29
33
30
34
#### Release Names
31
-
We'll use these guys as release names: http://en.wikipedia.org/wiki/List_of_action_film_actors
35
+
We'll use these folks as release names: http://en.wikipedia.org/wiki/List_of_action_film_actors
32
36
33
37
in order from top left - down the column then on to the next column. If we run out we'll add more names to the list :-)
34
38
@@ -41,5 +45,5 @@ in order from top left - down the column then on to the next column. If we run o
41
45
42
46
###Dependencies
43
47
There are a few dependencies for Action to be a fully useful framework. They are (with the reasons for them):
44
-
0. localForage (If you want to use the local cache. It will automatically cache all of your ajax requests in local storage and pull from them all subsequent times they are requested)
45
-
0. Handlebars (a templating library)
48
+
0. localForage (If you want to use the local cache. It will automatically cache all of your ajax GET requests in local storage and pull from them all subsequent times they are requested)
49
+
0. Handlebars, or compatible (a templating library)
0 commit comments