Add PolicyManager to windowmanager-service for using state transition
Description
Environment
Attachments
- 28 Jun 2018, 06:27 AM
Activity
Yuta Doi July 11, 2018 at 7:59 AM
@Tadao Tanikawa
Thank you for your advice.
I have finished to split the patch into Change 15133 and 15269.
Please see the patches.
Tadao Tanikawa July 10, 2018 at 5:09 AM
I recommend Change 15133 should be split into 2 patches.
Policy Manager I/F and stub plugin (default policy should be empty, means all things are permitted), this is REFERENCE.
ZIPC plugin for EXAMPLE (This plugin should not be REFERENCE)
toshikazu_ohiwa July 2, 2018 at 7:13 PM
The code generated by ZIPC is not unique to that tool nor binary. And they are library made by AGL SDK.
Jan-Simon Moeller June 28, 2018 at 8:09 AM(edited)
I'm not familiar with how the zipc built policy/code is included, so please excuse if my assumptions that lead to my questions below are wrong.
My concerns currently are these:
As zipc is not open source, there is no way for us to modify the rules ourselves. Right ?
If it is a machine specific shared library, will you provide the shared library for all target boards of AGL? Will you update it/recompile as needed ?
IMHO it would be beneficial if we have a minimal/simple built-in (lets say hardcoded) default policy that can 'just work' out-of-the-box. Then we amend/replace it with the zipc generated policy. In that way we get the best of both worlds.
Jan-Simon Moeller June 28, 2018 at 8:02 AM(edited)
Question: the 'zipc' generated shared library is architecture specific ?
Or is it some other intermediate binary format ?
We will add PolicyManager which using state transition.
It is requested optimal window layout by ResourceManager and returns it.
It is shared library and the OEMs can replace it freely.
We are developing the reference now and it has state transition which is created by ZIPC Designer.