Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.6
-
Fix Version/s: 1.7.1
-
Component/s: ICE-Components
-
Labels:None
-
Environment:ICEfaces 1.6.
-
Support Case References:
Description
During the component showcase refactoring I had a change to use the panelPositioned component for the first time. Unfortunately the component has some issue that will make the average user pretty unhappy. Here are the issues in no particular order.
Simple/picky Issues
- Documentation is very poor, end user has to make many assumption and read between the lines to figure out how the component works.
- Component only takes list interface as a value. I find this strange as just about every other JSF component that iterates can also take arrays.
Functionality Issues
- positioning a component will not work unless the listener class has been hocked up in a the backing bean. Also the listener uses a customer listener/event object which is not documented. End user has to guess what the signature of the method.
- constraint attribute can take either vertical or horizontal and possibly no value. There is very little documentation around how this attribute would be used for a horizontal and vertical instance of the component.
- the whole component is dragable and as a result text selection is not possible for any contained content.
- specifying a handle attribute breaks the component. No positioning is possible once specified.
- the style attributes hoverClass and overlap appear to be broken as the style do not get applied as specified by the documentation.
- And lastly there is no security attributes for render and disable on user role.
Simple/picky Issues
- Documentation is very poor, end user has to make many assumption and read between the lines to figure out how the component works.
- Component only takes list interface as a value. I find this strange as just about every other JSF component that iterates can also take arrays.
Functionality Issues
- positioning a component will not work unless the listener class has been hocked up in a the backing bean. Also the listener uses a customer listener/event object which is not documented. End user has to guess what the signature of the method.
- constraint attribute can take either vertical or horizontal and possibly no value. There is very little documentation around how this attribute would be used for a horizontal and vertical instance of the component.
- the whole component is dragable and as a result text selection is not possible for any contained content.
- specifying a handle attribute breaks the component. No positioning is possible once specified.
- the style attributes hoverClass and overlap appear to be broken as the style do not get applied as specified by the documentation.
- And lastly there is no security attributes for render and disable on user role.
Activity
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Assignee Priority | P3 | |
Assignee | Adnan Durrani [ adnan.durrani ] |
Adnan Durrani
made changes -
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Adnan Durrani
made changes -
Status | Open [ 1 ] | In Progress [ 3 ] |
Ken Fyten
made changes -
Assignee Priority | P3 | |
Assignee | Adnan Durrani [ adnan.durrani ] |
Michael Thiem
made changes -
Attachment | Test_DragAndDropInTable.war [ 10866 ] |
Michael Thiem
made changes -
Support Case References | https://www.icesoft.ca:4443/supportilla/show_bug.cgi?id=4642 |
Ken Fyten
made changes -
Description |
During the component showcase refactoring I had a change to use the panelPositioned component for the first time. Unfortunately the component has some issue that will make the average user pretty unhappy. Here are the issues in no particular order. Simple/picky Issues - Documentation is very poor, end user has to make many assumption and read between the lines to figure out how the component works. - Component only takes list interface as a value. I find this strange as just about every other JSF component that iterates can also take arrays. Functionality Issues - positioning a component will not work unless the listener class has been hocked up in a the backing bean. Also the listener uses a customer listener/event object which is not documented. End user has to guess what the signature of the method. - constraint attribute can take either vertical or horizontal and possibly no value. There is very little documentation around how this attribute would be used for a horizontal and vertical instance of the component. - the whole component is dragable and as a result text selection is not possible for any contained content. - specifying a handle attribute breaks the component. No positioning is possible once specified. - the style attributes hoverClass and overlap appear to be broken as the style do not get applied as specified by the documentation. - And lastly like many other of Robs component there is no security attributes for render and disable on user role. |
During the component showcase refactoring I had a change to use the panelPositioned component for the first time. Unfortunately the component has some issue that will make the average user pretty unhappy. Here are the issues in no particular order. Simple/picky Issues - Documentation is very poor, end user has to make many assumption and read between the lines to figure out how the component works. - Component only takes list interface as a value. I find this strange as just about every other JSF component that iterates can also take arrays. Functionality Issues - positioning a component will not work unless the listener class has been hocked up in a the backing bean. Also the listener uses a customer listener/event object which is not documented. End user has to guess what the signature of the method. - constraint attribute can take either vertical or horizontal and possibly no value. There is very little documentation around how this attribute would be used for a horizontal and vertical instance of the component. - the whole component is dragable and as a result text selection is not possible for any contained content. - specifying a handle attribute breaks the component. No positioning is possible once specified. - the style attributes hoverClass and overlap appear to be broken as the style do not get applied as specified by the documentation. - And lastly there is no security attributes for render and disable on user role. |
Ken Fyten
made changes -
Fix Version/s | 1.7.1 [ 10122 ] | |
Security | Private [ 10001 ] | |
Assignee | Ken Fyten [ ken.fyten ] |
Patrick Corless
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Ken Fyten [ ken.fyten ] |
Patrick Corless
created issue -
Separate cases has been created for each issue, so please see the relative JIRA.