|author||Matthieu Morel <email@example.com>||Fri Jun 15 09:57:59 2012 +0200|
|committer||Matthieu Morel <firstname.lastname@example.org>||Fri Jun 15 09:57:59 2012 +0200|
bugfixes for the twitter example (thanks Daniel!) - schedule only 1 timer activity - fix hashtag identification - cleanup build files
The goal of this project is to incorporate feedback from various users and create a prototype with a cleaner, simpler API. The base classes are the foundation on top of which higher level layers and tools can be built. For example, one could write a domain specific language to create the application graph. Look at this as the foundation and not as the end product.
Here is a list of ideas:
Please post feedback and suggestions in the s4 forum.
The repo is here:
In this version:
Note that when we create a PE in App, we are really creating a prototype of the PE. The actual PE instances get created every time a node receives an event that is dispatched to a specific PE prototype. The first PE has Map that holds the instances by a specific key. PE instances are clones which means that we don't call the constructor. Instead we provide an init method. Also, the instance variables are cloned. This means that references are also copied. If you wanted to have a List per PE instance, you would have to create it in the init method. This design pattern, makes thing very simple and efficient but has the downside that programmers have to understand how instances are created via clone.
For now we identify PEs using a composite string produced by KeyFinder. We must also pass the raw data types used to create the composite key. Need to think how to do this with type safety in mind.