Apps name in new HMI 2017 must become dynamic

Description

The CES version of the new HMI FW used for CES request to have fixed name for Apps and requires the name of all Apps to be hardcoded in the code.

That can do for a demo at CES but is not viable.

 

  • Apps name should come from the Manifest

  • Apps should be possible to be added at installation time in the home screen
    (hierachie and position display mata data must be created)

Environment

The CES version of the new HMI FW used for CES request to have fixed name for Apps and requires the name of all Apps to be hardcoded in the code. That can do for a demo at CES but is not viable.   * Apps name should come from the Manifest * Apps should be possible to be added at installation time in the home screen (hierachie and position display mata data must be created)

Activity

Walt Miner 
March 20, 2018 at 1:40 PM

Current eel release status - new application installation works ok except graphical icon is not displayed correctly. Everything else now works ok. 

Jose Bollo 
November 21, 2017 at 8:35 AM

understood. You are 100% right. Please excuse me for being confused because I'm working on an other file that has X-AFM-Icon:

https://gerrit.automotivelinux.org/gerrit/gitweb?p=src/app-framework-main.git;a=blob;f=conf/afm-unit.conf.in;h=07ee8a0c363cfeadc212e41f2b20aa2029c881d7;hb=63236151d5e87d83e3e388f302cdb531dd91811a

But the current discussion is challenging the model. Can I continue to use the unit file to put important data in or not?

  • If yes, I have to put json structured values in unit files. It is possible and simple.

  • If no, I have to restore an older algorithm that read the config file of the widget with two issues: [a] because a widget is able to install several applications, data of the given application has to be recomputed, and, its is more coding and I'm already busy.

Advises and ideas welcome! I'll work on this week to implement the "if yes" option in my current development branch and try to propose a solution for during the week.

Tasuku Suzuki 
November 21, 2017 at 12:33 AM
(edited)

This is  where I have seen in homescreen-2017

https://gerrit.automotivelinux.org/gerrit/gitweb?p=staging/homescreen-2017.git;a=blob;f=homescreen/src/applicationmodel.cpp;h=f01df06502eed08f79b8fee0f349fe5b2409b422;hb=HEAD#l55

The returned json contains author, author-email, description, height, id, name, shortname, version and width. I need icon(s) for homescreen.

 

This may be related to the file below doesn't contain icon.

https://gerrit.automotivelinux.org/gerrit/gitweb?p=src/app-framework-main.git;a=blob;f=conf/afm-unit.conf.in;h=237f8ce00473beecd99aab93c527b12ac086d25f;hb=HEAD

Jose Bollo 
November 20, 2017 at 1:05 PM

The icon element can be repeated and can include attributes for width and heigth (see TR below). So the specification is missing the information that you point out: state, intented position. The size could be used to distinguish the position because smaller is probably better for the bar.

TR for widget config file: https://www.w3.org/TR/widgets/

XML generally emphasis the use of xml namespace. And that is the recommended procedure for proprietary extensions. So if the namespace XMLNS is prefixed agl: we could add to icons the attribute "agl:scope" with space separated items like in:

agl:scope="inactive"

or

agl:scope="active toolbar"

Up to you

Tadao Tanikawa 
November 20, 2017 at 12:25 PM
(edited)

I have one additional question about config.xml.

Currently, config.xml has only one entry for icon,

<icon src="icon.svg"/>

But HomeScreen requires 2 type of icons for each app, icons for active and for inactive which switch each other when touch and release.

And more, for short cut on top bar, it requires another icon image for each apps.

E.g. for Media Player, Active/Inactive icon for top bar and Active/Inactive icon for main area are required by HomeScreen.

How to define them ?

 

Fixed

Details

Assignee

Reporter

Fix versions

Labels

Contract ID

Components

Priority

Created November 14, 2017 at 1:51 AM
Updated October 22, 2018 at 10:23 AM
Resolved March 20, 2018 at 1:41 PM