For sure not when page is loaded, cause components has been added to already
loaded page.
Hmm...I just have an idea that in addedToParent I could check whether
component have "upgraded" tag which is required by MDL if it has I could
based on that upgrade it or not. Than I do not need this Bead
Up
FWIW, I've been wondering: Does anybody know why there is whitespace when
we call appendChild() on these children? The HTML looks like: with no whitespace between. I don't think there is a TextNode
in there, but I could be wrong about that. Is it just not possible to not
have whitespace betwe
Hi,
> Can you try adding “white-space: nowrap;” to HContainer in the defaults.css
> file in the HTML project?
Tried and it didn’t work. The attribute isn’t showing up in the generated html
so I could of done something wrong I guess.
Steps were I edited [1], mvn compile flex-asjs, mvn installed
Justin,
Can you try adding “white-space: nowrap;” to HContainer in the defaults.css
file in the HTML project?
Theoretically, that should fix the problem.
Thanks,
Harbs
> On Feb 24, 2017, at 9:01 AM, jus...@classsoftware.com wrote:
>
> Hi,
>
> And the issue is each of the images is display
Do you want to know when a component has been added to the DOM or when the
page is considered loaded?
-Alex
On 2/23/17, 10:47 PM, "piotrz" wrote:
>Alex,
>
>Do you know about the event which can tell me when component has been
>loaded
>in DOM?
>
>I may try to use that.
>
>Piotr
>
>
>
>-
>Ap
On 2/23/17, 6:28 PM, "Justin Mclean" wrote:
>HI,
>
>I’m getting this error:
>Uncaught TypeError: this.generateMXMLAttributes is not a function
>at new components.LinkButton (LinkButton.js:42)
>at components.LinkNavigation.set__links (LinkNavigation.js:102)
>
>When creating this componen
Hi,
And the issue is each of the images is display inline-block this will by
default wrap unless you add white-space nowrap to the container.
Just do this to fix:
Alex,
Do you know about the event which can tell me when component has been loaded
in DOM?
I may try to use that.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MDL-Dynamic-Child-Problem-tp59
Hi,
Just in case it helps here’s a simpler program (no List) that has the name
issue:
http://ns.adobe.com/mxml/2009";
xmlns:js="library://ns.apache.org/flexjs/basic">
On 2/23/17, 12:12 AM, "Harbs" wrote:
>It could return the body, but the body is not an IPopUpHost and it does
>not have addElement().
>
>The element of an embedded app will not be the body, so addElement() to
>that will blow up if it needs to be added to the body.
This is JavaScript right? We
FWIW, MXML cannot set constructor arguments. All components instantiated
via MXML must have no constructor arguments or optional constructor
arguments.
I still think the lifecycle should be able to tell you whether an addChild
is happening "dynamically" or not. Has that been explored and abandon
HI,
I’m getting this error:
Uncaught TypeError: this.generateMXMLAttributes is not a function
at new components.LinkButton (LinkButton.js:42)
at components.LinkNavigation.set__links (LinkNavigation.js:102)
When creating this component:
http://ns.adobe.com/mxml/2009";
xmlns:js="library:
I was thinking more about solution for this and I think that interface is not
the right way.
If my component will implement interface during creation I will always have
two lines of code:
var textField:TextField = new TextField();
textField.isDynamic = true:
I think I will just add field to c
Hi Carlos,
Basically the expected output is an application consists of multi-level of
tabs. So when you select a top-level tab, it's content window (TabBarPanel)
may have another sub-Tab section. That sub tab section's some component may
have another sub-sub-tab sections.
So this from a real wor
On 2/23/17, 1:54 AM, "Alex Harui" wrote:
>A few comments/questions:
>
>What does flex-box do when it runs out of room? Doesn't it wrap to a new
>row/column? Or can that be controlled? I think most folks expect
>VerticalLayout to not create a new column but to keep going vertically and
>be cl
Hi,
> Are you documenting your experience somewhere? That could be very useful.
I try to follow up on the list/in JIRA with any workarounds to issues I’ve
running but I’m also keeping a list of the issues I’ve run into and any
workarounds I’ve found.
Happy to share - may be useful for you tal
Hi Sankar,
I understand now the real problem. When Piotr and I was developing the
library found some limitations in components. For example, tabbars can't be
nested by design, and MDL guys defend that function since it would defeat a
clean design. So the problem could be due to navigation content
Justin,
Are you documenting your experience somewhere? That could be very useful.
Thanks,
Harbs
> On Feb 23, 2017, at 1:06 PM, Justin Mclean wrote:
>
> Hi,
>
>> DAYG is excellent. I also advocate R(eport)AYG.
>
> + 1 Reporting and hopefully documenting workarounds helps everyone one short
>
Hi,
> DAYG is excellent. I also advocate R(eport)AYG.
+ 1 Reporting and hopefully documenting workarounds helps everyone one short
term. Not everyone has the skills or indepth knowledge of the framework or time
to be able to fix all the bugs they may find and not every bug is going to be
fixed
Hi,
> Expect lots of bugs and missing features.
Or I could just be using it wrong :-) It’s not always 100% obvious if something
is a bug or user error.
Thanks,
Justin
Hi Carlos,
The problem is, when it's many level deeper (components in components) some
MDL components sizes became unpredictable.
As an example look into this following screenshot. It has three TabBarPanels
in their respective components:
- First TabBarPanel content has a sky-blue background an
I’ve never written an abstract before. If you have some examples, that would be
helpful to me figuring out what to write…
> On Feb 23, 2017, at 11:41 AM, Christofer Dutz
> wrote:
>
> Sure … just didn’t want to do that for you ☺
>
> And an abstract for the talks would be super
>
> Chris
>
>
Sure … just didn’t want to do that for you ☺
And an abstract for the talks would be super
Chris
Am 23.02.17, 10:32 schrieb "Harbs" :
I’m not sure what to write. Would the content on the team page do?
> On Feb 23, 2017, at 10:47 AM, Christofer Dutz
wrote:
>
> YE!! ☺
I’m not sure what to write. Would the content on the team page do?
> On Feb 23, 2017, at 10:47 AM, Christofer Dutz
> wrote:
>
> YE!! ☺
>
> Happy to have you on board … could you please prepare an Abstract, your bio,
> a picture for Justin etc.?
>
> Chris
>
>
>
> Am 23.02.17, 09:19 sch
YE!! ☺
Happy to have you on board … could you please prepare an Abstract, your bio, a
picture for Justin etc.?
Chris
Am 23.02.17, 09:19 schrieb "Harbs" :
Put me down for the migrating talk.
> On Feb 23, 2017, at 10:11 AM, Christofer Dutz
wrote:
>
> Hi Guys,
>
Put me down for the migrating talk.
> On Feb 23, 2017, at 10:11 AM, Christofer Dutz
> wrote:
>
> Hi Guys,
>
> So, I just added the official information for two more slots into the
> schedule.
> Still there are two talks to take care of “Introduction to FlexJS” and
> “Migrating from Flex to F
It could return the body, but the body is not an IPopUpHost and it does not
have addElement().
The element of an embedded app will not be the body, so addElement() to that
will blow up if it needs to be added to the body.
> On Feb 23, 2017, at 9:57 AM, Alex Harui wrote:
>
>
>
> On 2/22/17,
Hi Guys,
So, I just added the official information for two more slots into the schedule.
Still there are two talks to take care of “Introduction to FlexJS” and
“Migrating from Flex to FlexJS”.
Who hasn’t stepped up for a talk yet and would be capable and willing to do one
of these?
Otherwise I
28 matches
Mail list logo