I think it depends whether you will show me some scenario where it need it. I
think some components you may never use as dynamic - you will always use it
in mxml.
I know that we have states where components even in mxml can be dynamically
created, but I need to see such scenario to make them
piotrz wrote
> I just introduce another bead which may be helpful for custom component,
> but in most cases will be used inside MDL components UpgradeChildren.
>
> I've just make as default possible to create dynamically following
> components:
> Button,
> RadioButton,
> CheckBox,
> TextArea,
>
Hi Carlos,
No problem :) Thanks!
Santanau,
I just introduce another bead which may be helpful for custom component, but
in most cases will be used inside MDL components UpgradeChildren.
I've just make as default possible to create dynamically following
components:
Button,
RadioButton,
Hi Piotr,
sorry, just see this, but as you said I'm very busy this days and even
can't take the time to look to all the threads going on.
I can't analyze right now the changes you want to do, but I trust you and
I'm sure what you plan will be the right way to go.
Hope I can return in some days as
piotrz wrote
> I'm thinking on adding as "default" to components ability for dynamic
> creation without any "isDynamic" property etc. I wanted to discuss it with
> Carlos in the other thread, but he is busy currently, so I'm still waiting
> for his input.
Hi Piotr,
That sounds nice. Although I
Hi Santanau,
I'm thinking on adding as "default" to components ability for dynamic
creation without any "isDynamic" property etc. I wanted to discuss it with
Carlos in the other thread, but he is busy currently, so I'm still waiting
for his input. If I got it positiv I will start work and you
piotrz wrote
> In that case it was problem with function which I've called from
> javascript [1]
>
> [1] https://paste.apache.org/FyB8
Hi Piotr,
I was busy for quite some time from the updates here. Thank you! for the
link you shared. That actually fix the problem for dynamically adding
Carlos,
I'm bringing back to live this thread with question about default upgrade.
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-tp59595p60154.html
Sent from the
Hi Piotr,
Congratulations on finding the problem. You might want to make a set of
externs or typedefs for MDL. That would prevent renaming of these
functions and type check those functions as well. See the way I put
together the BarcodeScanner.swc in the flex-tourjs repo.
-Alex
On 3/4/17,
Santanau,
I just pushed fix for problem with release version of your application.
Alex,
In that case it was problem with function which I've called from javascript
[1]
[1] https://paste.apache.org/FyB8
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
I have found in MDL library that process of upgrade won't occur if component
is already upgraded. In this case I could get rid off this isDynamic
property and just add upgrade ability as default.
What do you think Carlos ?
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this
In order to refresh dynamically created element in some cases I have to
upgrade also subcomponent.
In each scenario it can be something else. I've created UpgradeElement which
can upgrade only simple component.
In case of Button this will be working:
var btn:Button = new Button();
On 3/3/17, 8:00 AM, "piotrz" wrote:
>I didn't think about such scenario, so it look like we should expose
>isDynamic also to MXML.
That might work, although it can't be a constructor parameter. MXML
doesn't allow constructor parameters.
I would rather explore why
I didn't think about such scenario, so it look like we should expose
isDynamic also to MXML.
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-tp59595p60043.html
Sent
Yeah. Debugging these things are not fun.
Chrome also allows you to set breakpoints on DOM elements.
I’ve found this useful in breaking at a specific place in the lifecycle to see
what’s going on.
> On Mar 3, 2017, at 7:24 AM, Alex Harui wrote:
>
>
>
> On 3/2/17, 8:51 PM,
On 3/2/17, 8:51 PM, "piotrz" wrote:
>I will try to fight with this. The problem is that in this case I don't
>have
>any exception in the console. :)
Yuk. I think I would next examine the DOM. Compare it against the
js-debug version. If DOM objects are missing in
I will try to fight with this. The problem is that in this case I don't have
any exception in the console. :)
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
On 3/2/17, 5:59 PM, "piotrz" wrote:
>Alex,
>
>What could help you to fix that. Should I try to find in minified JS my
>potential class and show it here?
I don't know how much time you have, but it would be great if you simply
tried to debug into it on your own.
Alex,
What could help you to fix that. Should I try to find in minified JS my
potential class and show it here?
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
On 3/2/17, 9:19 AM, "piotrz" wrote:
>Alex,
>
>Do you think because it is something with variable renaming in release
>version?
>I remember that this problem come back to us.
Almost every time js-debug works and js-release doesn't, it has to do with
renaming. It is
Alex,
Do you think because it is something with variable renaming in release
version?
I remember that this problem come back to us.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
piotrz wrote
> var tmpComp:Button = new Button(true); - need to be true in constructor.
I've seen such usage of addition do not works in compiled "bin-release"
version. Things not works like 'ripple' etc. in "bin-release" version.
Thanks!
--
View this message in context:
Piotr,
Santanu may be right that there are dynamic MXML scenarios involving
states and includeIn/excludeFrom. In those cases, the instances are
created by MXMLDataInterpreter just like other MXML tags, but may not be
added to the DOM until much later, or removed and re-added as states
change.
I
Sankar,
Code which you are showing me should work without the problem.
var tmpComp:Button = new Button(true); - need to be true in constructor.
This:
You don't need any action cause MDL will handle this one.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this
piotrz wrote
> Ok but you didn't add this Grid to MXML, you will add this component by
> addElement yes ?
>
> Maybe I do not understand your use cases - provide me an example if you
> can.
Hi Piotr,
My test was pretty basic with FlexJS MDL default components only. Here's the
basic test case
Sankar,
Ok but you didn't add this Grid to MXML, you will add this component by
addElement yes ?
If you are adding Grid in MXML - It will be initialized on his own - MDL
will upgrade it automatically.
Maybe I do not understand your use cases - provide me an example if you can.
If you have
Hi Piotr,
I may oppose this your opinion:
piotrz wrote
> I don't see any advantage to have this property in MXML. Dynamic component
> is supposed to be created from code new Button(true).
Say I have an external Grid component which has many buttons and TextFields
declared in MXML tag - and I
Hi Sankar,
I don't see any advantage to have this property in MXML. Dynamic component
is supposed to be created from code new Button(true).
If you need more dynamic components which is already in our MDL library let
me know. I've changed only few of them to be dynamic.
If component do not have
Hi,
I recently updated my local framework source from Git repository. I am not
sure where we're standing now with this but I wanted to give Piotr's Button
and TextField implementation a try with new UpgradeElement bead.
So far I able to get the dynamic element upgraded by this way:
var
> and in some
> situations, it might need to be the parent document's body if you are in
> an IFrame.
That’s not going to work unless there’s some way to create elements in the
outer document which we currently don’t have.
I think the simplest way to go about it, is to leave it as-is for now.
On 2/24/17, 3:00 AM, "Harbs" wrote:
>Having two discussions in one thread is confusing… ;-)
>
>I guess we could make a custom object, but I’m not sure what the point
>is. AIUI, the purpose of IPopUpHost is to support many levels of popups.
>Assuming we are right that
31 matches
Mail list logo