The idea of "chrome" is that these are components that do not count as
regular children and have special locations within the component. The
TitleBar and ControlBar are considered chrome because if you ask for the
children of the Panel, they are not listed and if you have so many
children in the Panel that it requires scrolling, these items do not
scroll. You can consider the fixed scrollbars in the SWF version to be
chrome pieces too.
Let's say you wanted to have a special type of title bar that did have
images and other buttons. If your component implements IChrome, then you
could add it to a container that knew how to handle chrome:
<ChromedContainer>
<MyTitleBar Š left="0" top="0" right="0" height="40"/>
<button or label or input etc etc not chrome />
</ChromedContainer>
Where your MyTitleBar.mxml might be:
<Group implements="IChrome">
<beads>
<HorizontalFlexLayout />
<beads>
<Images or Buttons or Labels />
</Group>
Then the ChromedContainer would place the MyTitleBar at the top of the
container outside of the content area. But you could also do this as:
<Group>
<beads>
<BasicLayout />
</beads>
<MyTitleBar top="0" left="0" right="0" height="40" />
<Container top="40" left="0" right="0" bottom="0">
<beads>
<ScrollingViewport />
</beads>
<Images or Buttons or Labels />
</Container>
</Group>
This would accomplish the same thing. The problem with "chrome" is that
you could put the chrome into the middle of the container and then I'm not
sure how the layout algorithm would handle that.
‹peter
On 3/9/17, 11:16 AM, "PKumar" <prashaku...@gmail.com> wrote:
>ChromeContainer should be fine. We should be able to modify the panel
>title
>bar style as header corlor , border etc.
>
>Can Panel title bar contain other controls as image , button , check box?
>
>
>On 09-Mar-2017 9:37 PM, "piotrz [via Apache Flex Development]" <
>ml-node+s2333347n60286...@n4.nabble.com> wrote:
>
>Hi Peter,
>
>Let's say that you reconstructed Panel using new Group container - How can
>we use there Chrome ?
>
>I would go with ChromedContainer.
>
>Piotr
>Apache Flex PMC
>piotrzarzyck...@gmail.com
>
>
>------------------------------
>If you reply to this email, your message will be added to the discussion
>below:
>http://apache-flex-development.2333347.n4.nabble.com/FlexJS-Panel-
>tp60285p60286.html
>To start a new topic under Apache Flex Development, email
>ml-node+s2333347n1...@n4.nabble.com
>To unsubscribe from Apache Flex Development, click here
><http://apache-flex-development.2333347.n4.nabble.com/template/NamlServlet
>.jtp?macro=unsubscribe_by_code&node=1&code=cHJhc2hha3VtYXJAZ21haWwuY29tfDF
>8LTU0MTcyMzE2NA==>
>.
>NAML
><http://apache-flex-development.2333347.n4.nabble.com/template/NamlServlet
>.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.
>naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-na
>bble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabb
>le%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21
>nabble%3Aemail.naml>
>
>
>
>
>--
>View this message in context:
>http://apache-flex-development.2333347.n4.nabble.com/FlexJS-Panel-tp60285p
>60287.html
>Sent from the Apache Flex Development mailing list archive at Nabble.com.
