That's some great info Gordon. Once I finish some of my current tasks I'll
look again into MXML.
I'm working with the old compiler in mind, I'd love to see Falcon finished,
and being able to use it for code completion would be great if it proves to
be fast enough. Using the compiler services is ho
I have a few points to belatedly make on this thread:
1. The 'specifications' folder of the 'flex-external' repository has a spec for
MXML 2006 and 2009. It's incomplete, but it's the best one that exists. If you
find that it doesn't answer your questions about which elements are allowed
insid
Setting the itemRenderer goes thru the same error checking as any other
assignment statement so that why there is no special case error checking
code for IFactory. There is special handling for IFactory. For the inline
MXML assignment to itemRenderer the compiler generates a "new
ClassFactory()" an
I'll have some time this weekend to look at this a bit.
-Darrell
On Thu, Dec 4, 2014 at 3:29 AM, Héctor A wrote:
> Hello again Darrell, and sorry for bothering one more time,
>
> I've been browsing the MXMLC source looking for IFactory info, but I
> couldn't find what I need. How do I determ
Hello again Darrell, and sorry for bothering one more time,
I've been browsing the MXMLC source looking for IFactory info, but I
couldn't find what I need. How do I determine the type of class/interface
expected by an IFactory? is it posible or must I add it case by case? I've
seen that when the
>>Right now none because the property is private, and if it wasn't, just
subclasses.
That sounds right to me.
-Darrell
On Sun, Nov 23, 2014 at 8:34 PM, Héctor A wrote:
>
> >>property of type NavigationStack, marked with [ExcludeClass], what does
>> that mean?
>>
>> [ExcludeClass] prevents Flas
> >>property of type NavigationStack, marked with [ExcludeClass], what does
> that mean?
>
> [ExcludeClass] prevents FlashBuilder from hinting the class and excludes
> it from ASDoc.
>
> I know, I guess I made myself not too clear. I meant with regards to
children nodes auto-completion, subclasses
>>property of type NavigationStack, marked with [ExcludeClass], what does
that mean?
[ExcludeClass] prevents FlashBuilder from hinting the class and excludes it
from ASDoc.
-Darrell
On Sun, Nov 23, 2014 at 6:49 PM, Darrell Loverin
wrote:
> I not sure how complete the MXML support in the falco
Thanks for the tip, it will be rather helpful when the time comes, right
now I've hit some sort of roadblock, I've extended support for
ArrayElementType and DefaultProperty, and I've seen the more classes FD has
to check, the more time it takes to check type constraints. There isn't any
sort of cac
I not sure how complete the MXML support in the falcon compiler so I
checked the old mxmlc compiler. The old mxmlc validates with specialized
if/else statements based on parent and child types for elements that do not
provide [DefaultProperty]. For example, here is a code snippet from
ComponentBuil
Thank you very much for the reply Darrell, your help would be highly
appreciated. I have some doubts, and I guess some more will be popping up,
but if I can avoid having to find out about them the less time it will take
to have a better IDE.
I've seen ViewNavigatorApplication and ViewNavigator has
Sorry I missed this thread. Using [DefaultProperty] and [ArrayElementType]
sounds right for Spark components but I don't see [DefaultProperty]
declared in mx containers and I don't remember how mx containers were
validated. I'll investigate to see how it works this weekend.
-Darrell
On Thu, Nov
>
> Cc-ing Gordon and Darrell here, in case they missed this thread.
>
Thanks, that would be the better source of information and the best way to
make sure I implement everything as it should.
I didn't mention it, but of course I added support for ArrayElementType and
InstanceType metas as well,
bit of a shame as it would
> ease all of the process.
>
>
>
> --
> View this message in context:
> http://apache-flex-development.247.n4.nabble.com/Determining-which-MXML-elements-are-containers-tp41370p42583.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>
than they should and a few missing cases.
Gordon and/or Darrell didn't drop by, which is a bit of a shame as it would
ease all of the process.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Determining-which-MXML-elements-are-containers-tp41370p42583
On 10/14/14, 3:04 PM, "Neverbirth" wrote:
>And how could I contact Gordon and/or Darrell? Or could someone forward
>them
>to this thread?
They both subscribe to the list, but don’t answer every day.
-Alex
development.247.n4.nabble.com/Determining-which-MXML-elements-are-containers-tp41370p41385.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>
And how could I contact Gordon and/or Darrell? Or could someone forward them
to this thread?
Thanks in advance, and sorry for the inconvenience.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Determining-which-MXML-elements-are-containers-tp41370p41385
This is why Gordon and Darrell are probably better suited to answer these
questions. mx:Container is probably special-cased as I don’t see metadata
for it either. IIRC, the compiler generates these things called
UIComponentDescriptors for mx containers. For Spark and FlexJS, we are
using [Defaul
orrectly.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Determining-which-MXML-elements-are-containers-tp41370p41381.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
On 10/14/14, 1:42 PM, "jude" wrote:
>FYI There may not be an official way yet. In which case this would be a
>good discussion point. For example, there is not an official way to know
>if
>a class is a skin class.
Again, Gordon or Darrell (or better yet Ryan Frishberg if he’s still
lurking) mi
Assuming you tried to contact me, I did not see anything from you, but in
general asking on this list is best.
On 10/14/14, 12:34 PM, "Neverbirth" wrote:
>
> In particular, I want to know when a class can have another class as a
>children. For example may have a as a child.
I’m not sure I u
was thinking that
> maybe
> it should check for both all those interfaces and a DefaultProperty
> implementation, but I'm not too fond of that solution (unless there is no
> other way, of course).
>
> Thanks for your help.
>
>
>
> --
> View this message in context:
> http://apache-flex-development.247.n4.nabble.com/Determining-which-MXML-elements-are-containers-tp41370.html
> Sent from the Apache Flex Development mailing list archive at Nabble.com.
>
se).
Thanks for your help.
--
View this message in context:
http://apache-flex-development.247.n4.nabble.com/Determining-which-MXML-elements-are-containers-tp41370.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
24 matches
Mail list logo
