Here's the XML the script returns:
<menuitems>
<menuitem label="Retail" data="top">
<menuitem label="Current Year Reservation" data=""/>
<menuitem label="Next Year Reservations" data=""/>
</menuitem>
<menuitem label="Charter" data="top">
<menuitem label="Charter Contact Information" data=""/>
</menuitem>
<menuitem label="Utilities" data="top">
<menuitem label="Time Management" data="load: empTime"/>
</menuitem>
</menuitems>
This is what I have in my function to assign the dataprovider:
var resultXML:XML = new XML(evt.result);
Alert.show(resultXML.toString());
mainAppMenuBar.dataProvider = resultXML.menuitems.menuitem;
But all I get with this is a blank menubar, I've also tried:
resultXML.menuitems
And that still gave me just a blank menubar.
Thanks for the help!
-David
--- In [email protected], "David C. Moody" <[EMAIL PROTECTED]>
wrote:
>
> OK guys,
>
> in my example I'm returning XML to set as the dataProvider for my
> menuBar
>
> Example of what's being returned:
> <root><menuitem label="Retail" data="top"><menuitem label="Current
> Year Reservation" data="" /><menuitem label="Next Year
Reservations"
> data="" /></menuitem></root>
>
> But when I set this string as the dataprovider, the button on the
> menubar is what you see above, then it actually has the menu items
> when you click on the button.
>
> Not exactly what I wanted, so I figured, OK lets take off the
<root>
> tags. When I do this I get this error:
>
> TypeError: Error #1088: The markup in the document following the
root
> element must be well-formed.
>
>
> So I could possibly be headed on a track that will work, but need a
> little help.
>
> Or a completely different idea.
>
> Thanks,
> -David
>
> --- In [email protected], "David C. Moody" <davidm@>
> wrote:
> >
> > Hi guys,
> >
> > I'm developing a pretty large multi-user application. I need a
> good
> > menu system for and was looking for some help, maybe someone has
> come
> > up with something they'd like to share or at least has some ideas.
> >
> > The general menu will be the same for everyone. But some users
> will
> > have access to certain features while others will not.
> >
> > I'm thinking of using a menuBar. But this isn't necessary, I'm
> just
> > trying to come up with the best way to accomplish this.
> >
> > What i was thinking now is have 2 databases:
> >
> > Menu & UserMenu
> >
> > Menu would hold all menu options, and then UserMenu would hold
> access
> > rights to each menu?
> >
> > But the only way I can think of doing this is:
> > Loop through menu and then for each menu item, check Usermenu for
> > access rights.
> >
> > Can anyone else think of a better way to do this? Or maybe have
a
> > menu they'd like to share?
> >
> > Thanks,
> > -David
> >
>
