33347.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p63919.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
I will have to do more investigation for #1. I don't know if magic
properties are the responsibility of the compiler or the IDE's code
intelligence.
I just pushed a change for #2. It should be using "_id" (with leading
underscore) instead of "id".
Thanks for catching that,
-Alex
On 8/17/17, 10
347.n4.nabble.com/file/n63903/local_id.png>
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.2333347.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p63903.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Bonjour,
En congés jusqu'au 4 septembre, je prendrais connaissance de votre message à
mon retour.
Cordialement,
Vincent/AFTER24
I pushed some code that tries to implement a "localId" property. It
seemed to work in a simple test.
-Alex
On 8/3/17, 10:58 AM, "piotrz" wrote:
>Hi All,
>
>This issue started to be real blocker for my client's application. If we
>could ask anyone from compiler sight to try to work on that it w
opment.2333347.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p63688.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
nion appear on that issue.
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.2333347.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p63338.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Hi Piotr,
I still don't think the compiler can tell if you will be using an id more
than once. At least not with a lot of flow analysis and even then I think
we'd miss cases.
You should be able to use the same id more than once. You might be
removing the first view and replacing it with a diffe
ion which I vote for ?
- Compiler will shot us some warning if we have duplicate "id" ?
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.2333347.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p63328.
Well, it makes no sense to me to invent some new property name that sets
the "id" of an HTMLElement. I would think we'd get a ton of questions
about it. If I"m the only one who thinks that, then I'll stop arguing
against it. I thought the consensus upthread was to add localId.
-Alex
On 7/16/1
ew this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p63315.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
quot; or "globalID" [4]
> Proposition 5: (Chris) [5]: Internal "id" based on parent components
>
> [1] https://goo.gl/CBkST5
> [2] https://goo.gl/C43Y4U
> [3] https://goo.gl/2aFghn
> [4] https://goo.gl/VTd25g
> [5] https://goo.gl/8rDMPU
>
> Thanks,
> Piot
[4]
Proposition 5: (Chris) [5]: Internal "id" based on parent components
[1] https://goo.gl/CBkST5
[2] https://goo.gl/C43Y4U
[3] https://goo.gl/2aFghn
[4] https://goo.gl/VTd25g
[5] https://goo.gl/8rDMPU
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this mes
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p61803.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
pache-flex-development.247.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p61804.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
er.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p61803.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Yes, browsers will allow multiple ids without error. I know for sure that
document.getElementById() will simply return the first element with the id
that it finds in the DOM. I'm not as sure about how duplicate ids in the
DOM are treated by CSS, but I wouldn't be surprised if you were right and
the
Well in that case wherever I run into something like this, the solution is to
simply append the row id as an intermediate.
containerId:rowId:localItemRendererId
Chris
Am 23.05.17, 16:34 schrieb "Alex Harui" :
On 5/23/17, 12:28 AM, "Christofer Dutz" wrote:
>Hi Piotr,
On 5/23/17, 7:32 AM, "Josh Tynjala" wrote:
>I didn't consider that ids were supported in classic Flex SDK CSS. In that
>case, I guess it really was global then.
I guess you can think of that as global, but really, there isn't any
restriction in regular Flex or FlexJS on having one and only one
On 5/23/17, 12:28 AM, "Christofer Dutz" wrote:
>Hi Piotr,
>
>Well in the old Flex world there was no global id like concept. There
>were only local ids, only in rare cases we needed to access stuff “above”
>and that’s what the parent was used for. So I guess that in general the
>same should ap
ght ?) - But that would break
> >>> existing
> >>> applications, cause we have right now "id" translation to HTML.
> >>>
> >>> Related to introduced new property:
> >>> 1) Have the compiler check that HTML ids are not used more than once.
> >>> (Harbs
> >>> - Globally ?, If id is used more than once in many views ?)
> >>> 2) Ability set HTML ids (Harbs I need a bit more elaboration on this,
> >>> cause
> >>> I do not fully understand)
> >>> 3) "id" should be generated based on "localId" or make generation
> >>>based on
> >>> Chris's suggestions (Piotr, Chris)
> >>>
> >>> If I miss something or didn't understand enough please correct me.
> >>>
> >>> Thanks for a good discussion on that!
> >>> Piotr
> >>>
> >>>
> >>>
> >>>
> >>> -
> >>> Apache Flex PMC
> >>> piotrzarzyck...@gmail.com
> >>> --
> >>> View this message in context: http://apache-flex-
> >>> development.247.n4.nabble.com/FlexJS-MXML-ids-and-
> >>> classNames-tp54361p61745.html
> >>> Sent from the Apache Flex Development mailing list archive at
> >>>Nabble.com.
> >>>
> >
>
>
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p61749.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
On 5/22/17, 10:34 PM, "piotrz" wrote:
>Hi Alex,
>
>You convinced me more to do not touch "id", and if we won't touch it and
>introduce "localId" not translatable to HTML we will achieve those what we
>want. However in order to resolve problems with third party library "id"
>still need to be gen
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p61754.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
gt; 1) Have the compiler check that HTML ids are not used more than once.
>>> (Harbs
>>> - Globally ?, If id is used more than once in many views ?)
>>> 2) Ability set HTML ids (Harbs I need a bit more elaboration on this,
>>> cause
>>> I do not fully understand)
>>> 3) "id" should be generated based on "localId" or make generation
>>>based on
>>> Chris's suggestions (Piotr, Chris)
>>>
>>> If I miss something or didn't understand enough please correct me.
>>>
>>> Thanks for a good discussion on that!
>>> Piotr
>>>
>>>
>>>
>>>
>>> -
>>> Apache Flex PMC
>>> piotrzarzyck...@gmail.com
>>> --
>>> View this message in context: http://apache-flex-
>>> development.247.n4.nabble.com/FlexJS-MXML-ids-and-
>>> classNames-tp54361p61745.html
>>> Sent from the Apache Flex Development mailing list archive at
>>>Nabble.com.
>>>
>
ause
>> I do not fully understand)
>> 3) "id" should be generated based on "localId" or make generation based on
>> Chris's suggestions (Piotr, Chris)
>>
>> If I miss something or didn't understand enough please correct me.
>>
>> Thanks for a good discussion on that!
>> Piotr
>>
>>
>>
>>
>> -
>> Apache Flex PMC
>> piotrzarzyck...@gmail.com
>> --
>> View this message in context: http://apache-flex-
>> development.247.n4.nabble.com/FlexJS-MXML-ids-and-
>> classNames-tp54361p61745.html
>> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>>
Agreed. This is something that should definitely be in the release notes.
- Josh
On Mon, May 22, 2017 at 3:44 PM, Justin Mclean
wrote:
> Hi,
>
> > This change would indeed break existing FlexJS applications that used the
> > HTML id in some way (like in CSS). However, we're pre-1.0, so breaking
Hi,
> This change would indeed break existing FlexJS applications that used the
> HTML id in some way (like in CSS). However, we're pre-1.0, so breaking
> changes are still to be expected while we smooth things over.
If we do break something we need to document how to work around it. Thee’s
proj
x-development.2333347.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p61749.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
rz
Datum: 22.05.17 20:51 (GMT+01:00)
An: dev@flex.apache.org
Betreff: Re: FlexJS MXML ids and classNames
Hi Alex,
I was going to expand my thoughts on same concerns what Chris mention. If we
introduce "localId" which will be responsible for identifying components in
MXML we need to
+1 to Josh's proposition.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p61747.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
h please correct me.
>
> Thanks for a good discussion on that!
> Piotr
>
>
>
>
> -
> Apache Flex PMC
> piotrzarzyck...@gmail.com
> --
> View this message in context: http://apache-flex-
> development.247.n4.nabble.com/FlexJS-MXML-ids-and-
> classNames-tp54361p61745.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>
stions (Piotr, Chris)
If I miss something or didn't understand enough please correct me.
Thanks for a good discussion on that!
Piotr
-----
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p61745.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.2333347.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p61729.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
nt.247.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p61729.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Yep I agree with Harbs and Josh as for not touch at all id and maybe
introduce another two.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p61726.html
Sent from
Going along these lines:
id could have the same behavior as today.
localID could only apply to the mxml.
globalID could only apply to the HTML and would be checked by the compiler for
uniqueness.
> On May 21, 2017, at 11:59 AM, Josh Tynjala wrote:
>
> I'm thinking my proposal of the name globa
I'm thinking my proposal of the name globalID is better than htmlID.
Calling it globalID would allow us to use it on the SWF side too. For
instance, someone could write some kind of utility function that provides
functionality similar to document.getElementById() that works
cross-platform to return
The more I think about it, the more I think we should keep the semantics of
id MXML-centric. It should create a member variable on the class like it
always has, but it should not set the id on the HTML element. Instead, we
should add a separate property for the HTML element's id. Maybe htmlID,
mayb
Alex,
You mean that I will not be able call property in AS3 like this ?
I'm not following where the problem is.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MXM
I don’t really what we call this, but I think the following is important:
I would like an option for the following:
1. Ability to set an id in mxml-only
2. Ability set HTML ids
3. Have the compiler check that HTML ids are not used more than once.
> On May 21, 2017, at 10:58 AM, Alex Harui wrote:
On 5/21/17, 1:38 AM, "yishayw" wrote:
>I like the idea. Sencha follows a similar pattern as far as I remember. I
>don't like mxmlID. Everything in MXML is MXML. I would go with 'localId',
>for the one that doesn't translate to HTML, and 'id' for the one that
>does.
>Also, there's nothing preven
Hi Yishay,
>From my perspective it is important to have such property. +1 for name
localID.
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p61712.h
class from accessing the so called
'mxmlID'.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p61710.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Hi Justin,
I just checked and yes I'm running into exactly same issue.
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p61709.html
Sent from the Apache
On 5/20/17, 3:17 PM, "Justin Mclean" wrote:
>Hi,
>
>If you make a component with something with an id in it and then use that
>multiple times in the same view (which is common pattern comping from the
>Flex world) are you going to run into this issue?
AIUI, it depends on if any code cares (exp
Hi,
If you make a component with something with an id in it and then use that
multiple times in the same view (which is common pattern comping from the Flex
world) are you going to run into this issue?
Thanks,
Justin
p://apache-flex-development.247.n4.nabble.com/FlexJS-MXML-ids-and-classNames-tp54361p61706.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
>
> Apparently, an issue with id selectors is that you really are only
> supposed to have a single element with that id in the DOM. I think I read
> that some folks translate id selectors to class selectors and assign
> className instead of id so you can have more than one element respond to
> t
On 8/8/16, 10:24 PM, "Harbs" wrote:
>Ah. I did not understand you.
>
>So you are saying that if you don’t care about multiple IDs (or are
>making sure your IDs are unique, you can just use id. If you don’t want
>the MXML id to propagate to the DOM, you’d use mxmlID for the MXML
>instead.
>
>Did
Ah. I did not understand you.
So you are saying that if you don’t care about multiple IDs (or are making sure
your IDs are unique, you can just use id. If you don’t want the MXML id to
propagate to the DOM, you’d use mxmlID for the MXML instead.
Did I get it?
> I also wonder if FlexJS should
On 8/8/16, 8:29 AM, "Harbs" wrote:
>I don’t get it.
>
>Why is having MXML tags the opposite?
>
>I don’t like the idea of having one property used for two very different
>things. I think that’s more confusing than requiring a slightly
>non-standard name.
I might be missing something, but I woul
I don’t get it.
Why is having MXML tags the opposite?
I don’t like the idea of having one property used for two very different
things. I think that’s more confusing than requiring a slightly non-standard
name.
On Aug 8, 2016, at 6:12 PM, Alex Harui wrote:
>
>
> On 8/8/16, 7:54 AM, "Harbs"
Agreed. That’s why I’m suggestion we using “elementID” instead.
On Aug 8, 2016, at 5:46 PM, Josh Tynjala wrote:
> Using id as the element id would probably lead to duplicate element ids
> somewhat frequently, I suspect. Any time there are multiple instances of
> the same component on screen, you
On 8/8/16, 7:54 AM, "Harbs" wrote:
>Agreed. That’s why I’m suggestion we using “elementID” instead.
IMO, that's more work for the less-sophisticated scenario, which is why I
would propose the opposite (another variant of PAYG). A "simple" app that
uses CSS id selectors that is going to be use
Using id as the element id would probably lead to duplicate element ids
somewhat frequently, I suspect. Any time there are multiple instances of
the same component on screen, you'd have duplicates. In the worst case, a
custom item renderer where a sub-component has an id would result in many
duplic
Browsers don’t blow up, but they arguably should…[1] ;-)
I’m not sure why “elementID” would be confusing.
The other way that I see doing it is to use “id” for the element id, and use
some other property for the Flex “id” (uid maybe?)
I don’t like the idea of making it a compiler option or MXML
On 8/7/16, 2:08 PM, "Harbs" wrote:
>
>Never mind. I was wrong about this.
>
>> Maybe we need an option about whether id gets set on the element. Or
>> maybe elements in the main view get their ids set. Andy is right about
>> MXML components, but lots of folks only have one instance of each MXM
On Aug 7, 2016, at 11:47 PM, Alex Harui wrote:
>
>
> On 8/7/16, 9:46 AM, "Harbs" wrote:
>
>> OK. That makes sense. (and yes, you understood me correctly)
>>
>> I do think that className should be assigned to the element though via
>> MXML, and there should be an “element id” which should be
On 8/7/16, 9:46 AM, "Harbs" wrote:
>OK. That makes sense. (and yes, you understood me correctly)
>
>I do think that className should be assigned to the element though via
>MXML, and there should be an “element id” which should be set-able via
>MXML.
>
> “id” is important if you want some extern
OK. That makes sense. (and yes, you understood me correctly)
I do think that className should be assigned to the element though via MXML,
and there should be an “element id” which should be set-able via MXML.
“id” is important if you want some external code to be able to address a piece
of you
On Sun, Aug 7, 2016 at 7:09 AM, Harbs wrote:
> I also noticed that setting the className of a UIBase sets the class of
> the element, but setting the id does not set the element id. That does not
> seem right to me. Any reason to not add the id to the element as well?
>
In MXML, the "id" propert
On 8/7/16, 4:09 AM, "Harbs" wrote:
>I thought that by adding an id and/or a className to MXML, that would set
>the id and class of a div, but it appears that it’s strictly an MXML
>property. Is that how it’s supposed to work?
Not sure I understand. What do you mean by "MXML property"?
>
>I a
I thought that by adding an id and/or a className to MXML, that would set the
id and class of a div, but it appears that it’s strictly an MXML property. Is
that how it’s supposed to work?
I also noticed that setting the className of a UIBase sets the class of the
element, but setting the id doe
64 matches
Mail list logo
