Re: Determining which MXML elements are containers

2014-12-13 Thread Héctor A
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

RE: Determining which MXML elements are containers

2014-12-13 Thread Gordon Smith
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

Re: Determining which MXML elements are containers

2014-12-06 Thread Darrell Loverin
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

Re: Determining which MXML elements are containers

2014-12-05 Thread Darrell Loverin
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

Re: Determining which MXML elements are containers

2014-12-04 Thread Héctor A
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

Re: Determining which MXML elements are containers

2014-11-24 Thread Darrell Loverin
>>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

Re: Determining which MXML elements are containers

2014-11-23 Thread Héctor A
> >>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

Re: Determining which MXML elements are containers

2014-11-23 Thread Darrell Loverin
>>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

Re: Determining which MXML elements are containers

2014-11-23 Thread Héctor A
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

Re: Determining which MXML elements are containers

2014-11-23 Thread Darrell Loverin
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

Re: Determining which MXML elements are containers

2014-11-21 Thread Héctor A
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

Re: Determining which MXML elements are containers

2014-11-21 Thread Darrell Loverin
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

Re: Determining which MXML elements are containers

2014-11-20 Thread Héctor A
> > 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,

Re: Determining which MXML elements are containers

2014-11-20 Thread OmPrakash Muppirala
Thanks for the update! Cc-ing Gordon and Darrell here, in case they missed this thread. Thanks, Om On Thu, Nov 20, 2014 at 1:10 PM, Neverbirth wrote: > I added support for DefaultProperty today, but there are many cases to > check > to make sure everything is supported as expected. > > Well, a

Re: Determining which MXML elements are containers

2014-11-20 Thread Neverbirth
I added support for DefaultProperty today, but there are many cases to check to make sure everything is supported as expected. Well, at any rate this is a nice improvement, many cases where the completion list wasn't showing any type are now working, but there are cases still showing more than the

Re: Determining which MXML elements are containers

2014-10-14 Thread Alex Harui
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

Re: Determining which MXML elements are containers

2014-10-14 Thread OmPrakash Muppirala
Neverbirth, please make sure you are subscribed to the dev@flex.apache.org mailing list. Every email of yours is getting into the moderation queue. I am guessing that is because you are not subscribed to this list. Send an email to: dev-subscr...@flex.apache.org to subscribe. Thanks, Om On Tue,

Re: Determining which MXML elements are containers

2014-10-14 Thread Neverbirth
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.ht

Re: Determining which MXML elements are containers

2014-10-14 Thread Alex Harui
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

Re: Determining which MXML elements are containers

2014-10-14 Thread Neverbirth
Thanks for your replies. My doubt comes from containers and the like, for example, how does an IDE know the direct child of can be objects inheriting from, eg, a GraphicElement? I'm a bit familiar with DefaultProperty (and ArrayElementType), but I didn't see it in that case, did I overlook it? o

Re: Determining which MXML elements are containers

2014-10-14 Thread Alex Harui
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

Re: Determining which MXML elements are containers

2014-10-14 Thread Alex Harui
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

Re: Determining which MXML elements are containers

2014-10-14 Thread jude
I would like to know the official way too. FYI The Application is a special case. It is typed object so developers can add their own properties and methods to it without the compiler complaining. It should probably be treated as a special case. In Flex 4 I've used IVisualElementContainer. For Fle