diff options
author | Marcus Fritzsch <marcus_fritzsch@mentor.com> | 2017-09-12 13:40:06 +0200 |
---|---|---|
committer | Marcus Fritzsch <marcus_fritzsch@mentor.com> | 2017-09-14 14:04:51 +0200 |
commit | def0c7482d78db4cf29a407aa329ccbd7bc9ee2d (patch) | |
tree | 491be8b89355d1a6207df95c392fd70d1ae5b5a4 | |
parent | 78571bc2aa3dd5e826262a14eceffcdcf1f7ee50 (diff) |
remove obsolete TODO
Signed-off-by: Marcus Fritzsch <marcus_fritzsch@mentor.com>
-rw-r--r-- | TODO | 14 |
1 files changed, 0 insertions, 14 deletions
@@ -1,14 +0,0 @@ -* WM client lib that implements afb calls to the WM -* Most of the API -X Application structure, whereas controller events should be forwarded to it? - Decorator? Proxy? -X Loose coupling between API calls and the actual handler in the appliation, - perhaps convert the verb's json input into a nlohmann::json and pass it to - some app method which then in turn can return a Result<error, json> kind - of thing. The verb's entry point would then construct a reply accordingly -X Design a sensible and lightweight representation of a Layout inside the WM - Appication. -* Wm Objects (Layers, Screen, Surface, Areas?) Should be handled with IDs, only - Upon making the concrete calls shall the actual objects be resolved. -* Implement an application configuration, possibly in /etc, must contain: - - json configuration names |