ICEmobile
  1. ICEmobile
  2. MOBI-218

ContentPane component

          Details

          • Type: New Feature New Feature
          • Status: Closed
          • Priority: Major 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

            creation of a contentPane component to satisfy Patricks' requirement of panelStack but also be able to reuse this as server-side implementation for future layout components.
            For Patrick's requirements, see his comments here
            http://wiki.icesoft.com/display/mobile/LayoutContainer

              Issue Links

              depends on

              New Feature - A new feature of the product, which has yet to be developed. ICE-8115 ACE generator support custom TagHandler

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                12 older comments
                Hide
                Permalink
                Mark Collette added a comment -

                You can just call getBoolean(ctx) on client and facelet, since they're boolean properties now.

                Show
                Mark Collette added a comment - You can just call getBoolean(ctx) on client and facelet, since they're boolean properties now.
                Hide
                Permalink
                Mark Collette added a comment -

                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.

                Show
                Mark Collette added a comment - 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.
                Hide
                Permalink
                Judy Guglielmin added a comment -

                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).

                Show
                Judy Guglielmin added a comment - 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).
                Hide
                Permalink
                Mark Collette added a comment -

                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.

                Show
                Mark Collette added a comment - 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.
                Hide
                Permalink
                Judy Guglielmin added a comment -

                this component was completed for 1.1 Beta release. Any further work should be done on new jira

                Show
                Judy Guglielmin added a comment - this component was completed for 1.1 Beta release. Any further work should be done on new jira

                  People

                  • Assignee:
                    Mark Collette
                    Reporter:
                    Judy Guglielmin
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: