-
New Feature
-
Resolution: Fixed
-
Minor
-
None
-
None
All WAM application are called WebAppMgr, which seem to be rather confusing when trying to figure which application is what.
Combined with the fact that the shell is split between multiple applications makes this even weirder.
This task is about finding some ways to determine to represent these applications.
Currently we're using env vars like AFM_ID and a directory path for webapps.
Currently experimenting to see if the following would make much more sense, as in pass these options as arguments to WAM rather than using hidden env variables:
WebAppMgr launcher WebAppMgr hvac WebAppMgr navigation
/cc jdapena
- relates to
-
SPEC-4301 [WAM] Process WAM arguments using some (well known) libraries/methods
- Closed
# | Subject | Branch | Project | Status | CR | V |
---|---|---|---|---|---|---|
27414,4 | wam, chromium, html5-*: improve initial frame, and drop usage of config.xml | master | AGL/meta-agl-demo | Status: MERGED | +2 | +1 |
27420,2 | wam, chromium, html5-*: improve initial frame, and drop usage of config.xml | marlin | AGL/meta-agl-demo | Status: MERGED | +2 | +1 |