Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.1 Beta
-
Component/s: None
-
Labels:None
-
Environment:jsf 2 icefaces 3 icemobile
Description
For Patrick's requirements, see his comments here
http://wiki.icesoft.com/display/mobile/LayoutContainer
Issue Links
- depends on
-
ICE-8115
ACE generator support custom TagHandler
-
- Closed
-
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
You can just call getBoolean(ctx) on client and facelet, since they're boolean properties now.
I was thinking that maybe ContentPaneMeta should be changed to make the @Property annotations for cache and facelet to have an Implementation of Implementation.EXISTS_IN_SUPERCLASS so that no getter or setter will be made in the component itself, since the component properties aren't used and the tag attributes are used directly, instead.
the client attribute is used in the Renderer. If you have facelet="false", then client makes a difference on whether the children are rendered or not --if client="true", they are always rendered on client, if client="false" then, the children are only rendered when the pane is selected.
I can see doing this with the facelet attribute though as the Renderer doesn't care about this one at all. I can put that in if you like (since I am working on it now).
Ok then we should let it generate all the code for isClient() and setClient(), but then override the methods in ContentPane so make them not use the clientId and not try to set or get it per row. Just copy and paste the generated methods in, and strip out the row related stuff.
this component was completed for 1.1 Beta release. Any further work should be done on new jira
scrollable attribute is on this component (for now) and may be removed if deemed unecessary, however in order for the inner panel to be scrollable, may require some styling on this component so left it in for now.
Also, for now it extends UIPanel, but may be changed to UIComponent if no requirement to be a panel.
just has a div for the "mobi-panel-stack" base class, but Patrick can decide if he wants that there as he may want to do his styling outside of this component.