-
Notifications
You must be signed in to change notification settings - Fork 534
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
component inside another component ? #26
Comments
Yes, by all means. Components are not defined in terms of DOM nodes, rather you attach an instance of a Component to one or more DOM nodes after it is defined. There is nothing to stop DOM node of one component instance being nested inside the DOM node of another. Are you having an issue with it? |
It depends what you mean? Are you thinking of having an attachTo for a component called from inside another component or having components attached to DOM nodes that are decendants of a DOM node that has another component attached? If its the former, use with extreme caution because it can create strong coupling where you mind not want it. If the latter, then yes, that's very much the pattern Flight is designed to encourage. |
DOM nodes instantiation is important, but not in relation to the the point There needs to be an easy and thought out way for coders to be able to take It will also allow this to be used for the many mobile platforms that are This is a huge opportunity to have a great component system that will be The exact same patterns happens with CMS system. You have a component, and On 5 February 2013 19:27, Dan Webb notifications@github.com wrote:
Contact details: |
is the architecture designed for this ?
The text was updated successfully, but these errors were encountered: