Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is it bad practice/design to nest components inside components using Flex 4? Should I simply be creating components and inserting them into my main application as below, or doesn’t it matter?
<com:MyComp1>
<com:MyComp2>
<com:MyComp3>
<s:Label text="This is a test."/>
</com:MyComp3>
</com:MyComp2>
</com:MyComp1>
If
MyComp1,MyComp2andMyComp3are a containers then it’s the recommended workflow. Custom containers in Flex 4 usually extendSkinnableContainerBaseorGroup. If the given code is used more than once then it’s recommended to refactor it into a custom big component.If they are not designed to contain unknown visual elements then it’s a bad practice. Defining components inline is also known as bad practice in production code.