Details
-
Type:
Improvement
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-1.3.1.GA_P05
-
Fix Version/s: EE-1.3.1.GA_P07
-
Component/s: None
-
Labels:None
-
Environment:Any
-
Assignee Priority:P1
-
Support Case References:Support Case 14210:- https://icesoft.my.salesforce.com/5000g00001mfHPh
Description
The mobi:contentMenuItem has an 'icon' attribute that allows specifying the name of a FontAwesome icon to display it next to the label. This feature is very limited because it can only be used for the simplest case of FontAwesome icons. It doesn't allow stacking, specifying different icon sizes, arbitrary styling or normal characters. This improvement is to add the capability to specify a complex icon configuration.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description | The mobi:contentStackMenu has an 'icon' attribute that allows specifying the name of a FontAwesome icon to display it next to the label. This feature is very limited because it can only be used for the simplest case of FontAwesome icons. It doesn't allow stacking, specifying different icon sizes and inverting colours. This improvement is to add the capability to specify a complex icon combination. | The mobi:contentStackMenu has an 'icon' attribute that allows specifying the name of a FontAwesome icon to display it next to the label. This feature is very limited because it can only be used for the simplest case of FontAwesome icons. It doesn't allow stacking, specifying different icon sizes, arbitrary styling or normal characters. This improvement is to add the capability to specify a complex icon configuration. |
| Support Case References | Support Case 14210:- https://icesoft.my.salesforce.com/5000g00001mfHPh |
| Fix Version/s | EE-1.3.1.GA_P06 [ 13117 ] |
| Assignee | Ken Fyten [ ken.fyten ] | Arturo Zambrano [ artzambrano ] |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Summary | mobi:contentStackMenu, add support for complex FontAwesome icon combinations | mobi:contentMenuItem, add support for complex FontAwesome icon combinations |
| Description | The mobi:contentStackMenu has an 'icon' attribute that allows specifying the name of a FontAwesome icon to display it next to the label. This feature is very limited because it can only be used for the simplest case of FontAwesome icons. It doesn't allow stacking, specifying different icon sizes, arbitrary styling or normal characters. This improvement is to add the capability to specify a complex icon configuration. | The mobi:contentMenuItem has an 'icon' attribute that allows specifying the name of a FontAwesome icon to display it next to the label. This feature is very limited because it can only be used for the simplest case of FontAwesome icons. It doesn't allow stacking, specifying different icon sizes, arbitrary styling or normal characters. This improvement is to add the capability to specify a complex icon configuration. |
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #51961 | Thu Sep 28 13:39:33 MDT 2017 | art.zambrano | |
| Files Changed | ||||
MODIFY
/icemobile/trunk/icemobile/jsf/components/component/src/org/icefaces/mobi/component/contentmenuitem/ContentMenuItemRenderer.java
MODIFY
/icemobile/trunk/icemobile/jsf/components/component/src/org/icefaces/mobi/component/contentmenuitem/ContentMenuItemMeta.java
|
| Fix Version/s | EE-1.3.1.GA_P07 [ 13122 ] | |
| Fix Version/s | EE-1.3.1.GA_P06 [ 13117 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Resolved [ 5 ] | Reopened [ 4 ] |
| Assignee Priority | P1 [ 10010 ] |
| Attachment | screenshot icon facet.png [ 22676 ] |
| Status | Reopened [ 4 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |

What the component renders with the 'icon' attribute is just the following markup (assuming that icon="envelope"):
If we want to render a bigger envelope icon that has a red circle in the middle, which in turns contains a number 9 (e.g. the number of e-mails), then the following markup is required.
So, for this improvement, an attribute that allows to specify arbitrary HTML markup would be the most appropriate solution. Simply using the body of the component to specify this markup is also an appropriate solution.