MXML Components Explorer

[joshtynjala]

No description provided.

[teotigraphix]

Would you want help with this?

[joshtynjala]

Sure! That would save me some time.

[teotigraphix]

Maybe if you got it started so I can see how you want it structured, then I could start working on each Screen and do a pull request?

[joshtynjala]

Yeah, that seems like a good idea. I'll try to get it started in the next week.

[teotigraphix]

I'm using it pretty extensively in my apps now(ported most view AS to MXML), so giving it a good test. :)

[joshtynjala]

Great! Sounds like things are pretty stable then.

[teotigraphix]

Knock on wood I have only had one problem and that was creating a subclass of LayoutGroup IE VGroup, then trying to use the VGroup as a base class in MXML.

The compiler barfed and said the my MXML needed to be a subclass of starling.events.EventDispatcher, which is was.

I need to file that bug in this repo actually.

[joshtynjala]

That sounds like a bug that I fixed in this commit: bd8049c

Did you update to the stable build of 2.2.0?

[teotigraphix]

AH! Actually, I just did today ironically. So I will try it again and let you know.

[teotigraphix]

Yes, seems to be fixed, right on!

[quick6black]

HI Josh, I think this is related to a component explorer. Would you be able to provide an example of how to use the drawer component in MXML? thanks

[joshtynjala]

You can use <f:DrawersApplication> if you want the Drawers at the root of your display list:

<?xml version="1.0" encoding="utf-8"?>
<f:DrawersApplication xmlns:f="library://ns.feathersui.com/mxml"
    xmlns:fx="http://ns.adobe.com/mxml/2009"
    theme="feathers.themes.MetalWorksMobileTheme">

    <f:leftDrawer>
        <f:PanelScreen title="Drawer">
        </f:PanelScreen>
    </f:leftDrawer>

    <f:PanelScreen title="Content">
    </f:PanelScreen>

</f:DrawersApplication>

The topDrawer, rightDrawer, bottomDrawer, and leftDrawer properties let you set the drawers on each side. I made the content property the default property for MXML, so you you don't need to actually type out <f:content></f:content>. Just specify any single component as a child element, and it will be the content.

<f:Drawers> works pretty much the same way, if you don't want it to be the root of your application.

[quick6black]

awesome, thanks for the help.