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.
-
Hide
- Test_DragAndDropInTable.war
- 5.84 MB
- Michael Thiem
-
- META-INF/manifest.mf 0.0 kB
- WEB-INF/classes/test/TableBean.class 3 kB
- WEB-INF/classes/test/TableBean_OLD.class 2 kB
- WEB-INF/classes/test/Task.class 1.0 kB
- WEB-INF/classes/test/User.class 4 kB
- WEB-INF/faces-config.xml 0.5 kB
- WEB-INF/html_basic.tld 244 kB
- WEB-INF/jsf_core.tld 25 kB
- WEB-INF/lib/backport-util-concurrent.jar 319 kB
- WEB-INF/lib/commons-beanutils.jar 100 kB
- WEB-INF/lib/commons-collections.jar 164 kB
- WEB-INF/lib/commons-digester.jar 96 kB
- WEB-INF/lib/commons-fileupload.jar 52 kB
- WEB-INF/lib/commons-logging.jar 27 kB
- WEB-INF/lib/el-api.jar 24 kB
- WEB-INF/lib/el-ri.jar 97 kB
- WEB-INF/lib/icefaces-comps.jar 1.51 MB
- WEB-INF/lib/icefaces-facelets.jar 593 kB
- WEB-INF/lib/icefaces.jar 770 kB
- WEB-INF/lib/jsf-api.jar 324 kB
- WEB-INF/lib/jsf-impl.jar 602 kB
- WEB-INF/lib/jstl.jar 17 kB
- WEB-INF/.../krysalis-jCharts-1.0.0-alpha-1.jar 151 kB
- WEB-INF/lib/standard.jar 343 kB
- WEB-INF/lib/xercesImpl.jar 1.15 MB
- WEB-INF/lib/xml-apis.jar 190 kB
- WEB-INF/web.xml 3 kB
- css/custom.css 0.4 kB
- index.jsp 0.2 kB
- main.jspx 6 kB
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
- 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.
http://jira.icefaces.org/browse/ICE-3019
Show
Adnan Durrani
added a comment -
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.
http://jira.icefaces.org/browse/ICE-3019
- 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.
http://jira.icefaces.org/browse/ICE-3020
Show
Adnan Durrani
added a comment -
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.
http://jira.icefaces.org/browse/ICE-3020
-There is no security attributes for render and disable on user role.
http://jira.icefaces.org/browse/ICE-3022
Show
Adnan Durrani
added a comment - -There is no security attributes for render and disable on user role.
http://jira.icefaces.org/browse/ICE-3022
- The whole component is dragable and as a result text selection is not possible for any contained content.
This behaviour has been extended from the "scriptaculous" library, it can not be changed.
Show
Adnan Durrani
added a comment -
The whole component is dragable and as a result text selection is not possible for any contained content.
This behaviour has been extended from the "scriptaculous" library, it can not be changed.
- The style attributes hoverClass and overlap appear to be broken as the style do not get applied as specified by the documentation.
http://jira.icefaces.org/browse/ICE-3026
Show
Adnan Durrani
added a comment -
The style attributes hoverClass and overlap appear to be broken as the style do not get applied as specified by the documentation.
http://jira.icefaces.org/browse/ICE-3026
- Documentation is very poor, end user has to make many assumption and read between the lines to figure out how the component works.
http://jira.icefaces.org/browse/ICE-3056
Show
Adnan Durrani
added a comment -
Documentation is very poor, end user has to make many assumption and read between the lines to figure out how the component works.
http://jira.icefaces.org/browse/ICE-3056
specifying a handle attribute breaks the component. No positioning is possible once specified.
http://jira.icefaces.org/browse/ICE-3060
Show
Adnan Durrani
added a comment - specifying a handle attribute breaks the component. No positioning is possible once specified.
http://jira.icefaces.org/browse/ICE-3060
Separate cases has been created for each issue, so please see the relative JIRA.
Show
Adnan Durrani
added a comment - Separate cases has been created for each issue, so please see the relative JIRA.
It seems that setting the handle attribute only breaks the component when using IE. Positioning is still possible on Firefox.