Do we want to move in a direction where every base application has
dynamic links like these? IMO the answer is no.
In the MyPortal application it would make sense to do this, but in the
Example app because of what it is meant for we should just use a
static menu widget and not have a dyna
+ 1 (good idea!)
Jacques
From: "Adrian Crum"
One of the things that would be worth looking into is using the tree
widget for menus. It already has the code for converting DB values to
links and of course it supports a nested structure.
-Adrian
Jacopo Cappellato wrote:
Bruno, Hans,
thanks
One of the things that would be worth looking into is using the tree
widget for menus. It already has the code for converting DB values to
links and of course it supports a nested structure.
-Adrian
Jacopo Cappellato wrote:
Bruno, Hans,
thanks for the info and insight... well I see two diffe
I agree,
this will let the Example application to be a demonstration for both the
menu widget based AppBar and the dynamic portal pages.
-Bruno
2009/2/4 Jacopo Cappellato
> Bruno, Hans,
>
> thanks for the info and insight... well I see two different interesting
> items in this:
>
> a) enhancing
Bruno, Hans,
thanks for the info and insight... well I see two different
interesting items in this:
a) enhancing the Menu Widget to support dynamically retrieved menu
items (as you propose)
b) having the Example application document the most common best
practices
What I am suggesting is
Hi Jacopo.
I completely agree with you and perhaps you can help here? The thing we
can do in ftl and not in a menu is the processing of a list of buttons.
If there could be a iterate function in a menu (similar to a <#list in
ftl) to list the buttons from a list, then sure we can use a menu
again
Hi Jacopo,
I agree with you, the Example (and all application) should follow the common
pattern to implement the AppBarMenu (with menu widget).
The reason the example component has been reverted to use a .ftl AppBar was
to have a dynamic AppBar.
Actually the menu-items that are displayed in the Exa
Hi all,
due to recent work on the Portal now the Example application is
rendering the top menu using an ftl template and not as a Menu widget
definition (as it was previously, if I am not wrong).
Is there a reason for the switch (sorry but I still don't know much
about the Portal framework)
