piotrz wrote
> Deeper investigation points me to componentHandler.register method - It
> looks like created component need to be registered and maybe than
> upgradeElement method will work.
>
> Method register take:
>
> /**
> * Describes the type of a registered component type managed by
> * componentHandler. Provided for benefit of the Closure compiler.
> *
> * @typedef {{
> * constructor: Function,
> * classAsString: string,
> * cssClass: string,
> * widget: (string|boolean|undefined)
> * }}
> */
> componentHandler.ComponentConfigPublic;
>
> How actually register my created Tab ? :)
>
> Piotr
I'm not sure about if it (FlexJS components) needs to be registered, I took
out a simple test. I took the example that I supplied to the dynamic
add/remove tab requirement JIRA for this test.
What I did is I added a basic 'setInterval' script in wrapper HTML which
calls a method and runs the 'componentHandler' methods. I made the
'setInterval' in few seconds' delay so I can add the dynamic child before
them.
After above command fired, I saw there still probably a few things not
working. Here's a list of things which I found worked and not-worked after
the command (I had TextField and Button only):
Worked:
1. Button ripple effect
2. TextField floating label
3. TextField expanding search field
Not worked:
1. TextField tooltip
2. There could be some more..
So my point is, Piotr, it seems when FlexJS adds component to the HTML, they
anyway get registered or maybe they don't need to be explicitly registered
to get called for 'componentHandler' codes.
Thanks.
--
View this message in context:
http://apache-flex-development.2333347.n4.nabble.com/FlexJS-MDL-Dynamic-Child-Problem-tp59595p59668.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
