This content has been marked as final. Show 6 replies
Not really a big difference between them as far as I know. Depends on what you find working for you the best. All mxml objects are actually classes in the background. Only syntax differs, not the functionality.
This is what I was thinking, it's all classes in the end.
His thoughts are that you should maintain that seperation of behaviour and structure in the same way as we do with CSS/HTML and linked in JS for better managability (not performance as with HTML).
I kind of see where he's coming from but wanted to find out the general opinion, I'm not sure myself, it can sometimes be handy to have a block of MXML with attributes to arrange some functionality quite tidily.
Anyone have a view on this? Thanks all,
Interesting topic :)
Like you I also see his point (not that I agree with him though ;) ). But the nice part is, if someone likes to look at it that way, that's fine too. I think it all comes down to preference and consistency. There is no "good" or "bad" way, just pick one and use it consistantly throughout your work.
If you e.g. like to make small non-visible tags and your other teammembers "get" why you are doing it,nothing wrong with that. It's just symantics.
My 2 cents though :)
Separation of UI and logic is good, but it need not necessarily occur based on file types.
AS can produce UI, and mxml can contain logic.
Thanks Ben, ntsiii. appreciate that.