Pancake/French Toast/Store: Difference between revisions
< Pancake | French Toast
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
==== As a front-end developer, I need to be able to specifiy sub-sets of information and be notified when these sub-sets change, so that parts of the interface can react to the data that interests them. ==== | ==== As a front-end developer, I need to be able to specifiy sub-sets of information and be notified when these sub-sets change, so that parts of the interface can react to the data that interests them. ==== | ||
''There are a few ways to do this. Event channels is one. Filtering is another. If you think about it, event channels are really a domain | ''There are a few ways to do this. Event channels is one. Filtering is another. If you think about it, event channels are really a domain specific language around querying change notifications. I prefer a filtering approach because predicate functions are more flexible than DSLs. If we still should want an event channel DSL, we could create one on top of predicate functions.'' -[[Gbrander]] | ||
==== As a front-end developer, I need to transform and reformat data coming from the server for display on the client-side. I need this transformed data to be "live". It should be updated when the original data is updated. ==== | ==== As a front-end developer, I need to transform and reformat data coming from the server for display on the client-side. I need this transformed data to be "live". It should be updated when the original data is updated. ==== | ||
Revision as of 17:25, 4 September 2012
User Scenarios
As a front-end developer, I need my program to be "push" notified of updates from the server and other data sources, so that the client can efficiently react to the most up-to-date information.
As a front-end developer, I need to be able to specifiy sub-sets of information and be notified when these sub-sets change, so that parts of the interface can react to the data that interests them.
There are a few ways to do this. Event channels is one. Filtering is another. If you think about it, event channels are really a domain specific language around querying change notifications. I prefer a filtering approach because predicate functions are more flexible than DSLs. If we still should want an event channel DSL, we could create one on top of predicate functions. -Gbrander