Hi Steve,

Yes, that's what needs to be done.  I think the reason why nobody has gotten
time to work on it is because those old menu* components were written using
the old "faces minor" APIs for rendering whereas the new navigationPane
component is using the newer faces APIs.  I think the trick will be to
figure out how to make the conversion.  This definitely needs to get done so
if you can help, I'm sure we all would appreciate that.

Thanks,
Matt

On 10/5/06, Steve Vangasse <[EMAIL PROTECTED]> wrote:

Thanks for getting back to me Matt. That makes sense.

Would it be a case of moving the old code over from the ADF CoreMenuTabs
and
CoreMenuBar classes as I guess the implementation was functional there.
I'm
fairly new to Apache projects but would love to get more involved. Is
there
anything I can do to help?

Thanks again,

Steve Vangasse
www.boardshop.co.uk

----- Original Message -----
From: "Matt Cooper" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, October 03, 2006 6:20 PM
Subject: Re: MenuModel and navigationPane


> Hi Steve,
>
> I am not using this component but the last I heard, the APIs for a
> MenuModel
> have been defined (the value/var/level etc. are present on the tag) but
> like
> you are indicating, the underlying implementation is not actually
> functional/implemented.
>
> I think navigationPane actually only works if you use indexed children
> (which unfortunately means that the MenuModel isn't being consumed).
>
> Regards,
> Matt
>
> On 10/3/06, Steve Vangasse <[EMAIL PROTECTED]> wrote:
>>
>> Is anyone else using a MenuModel with a panelPage? It works fine with a
>> navigationTree but I'm still not having any success with
navigationPanes.
>> I
>> would really like to use tabbed navigation in my app but this is
holding
>> things up. Is this a known issue?
>>
>> Thanks,
>>
>> Steve Vangasse
>> www.boardshop.co.uk
>>
>> P.S. Previous Message:
>>
>> I'm using MenuModel navigation with a navigationTree component within
the
>> "navigation3" facet of a panelPage component. This has been working
fine
>> without any problems. Today I thought I would try using tabbed
navigation
>> with my MenuModel using the "navigation1" facet and a navigationPane:
>> <f:facet name="navigation1">
>>
>> <af:navigationPane var="node" hint="tabs" value="#{menuModel.model}"
>> level="1">
>>     <f:facet name="nodeStamp">
>>
>> <af:commandNavigationItem text="#{node.label}" action="#{
node.getOutcome
>> }"/>
>>     </f:facet>
>>    </af:navigationPane>
>>   </f:facet>
>>
>>
>> This doesn't seem to work. Clicking on a tab just refreshes the current
>> page
>> without any error messages in my logs. I tried it with a hardcoded
action
>> string that I know works elsewhere on the page and it still didn't
work.
>> I
>> then tried it with some hard coded child commandNavigationItems without
>> the
>> MenuModel and it did work. Is there a problem with navigationPanes and
>> MenuModels (I'm running on the latest trinidad build downloaded today)?
>> Thanks,
>>
>> Steve Vangasse
>> www.boardshop.co.uk
>>
>>
>



Reply via email to