If you are referring to the main navigation menu:
<div id="main-navigation">
that uses a template instead of a menu widget - it is done that way
simply because no one has tried to do it differently. Personally, I
would like to see it changed to a menu widget.
Regarding the existing FreeMarker macros: those should be copied to the
Bootstrap theme and modified to output Bootstrap-specific HTML. To use
the Bootstrap theme, you will need to modify widget.properties to
reference the Bootstrap macros.
It would be nice to have a more dynamic way to change macros, but it
might be best to put that idea on the shelf for now. (Maybe we can make
the macro file locations Visual Theme resources - store them in the
database.)
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 10/29/2014 2:28 PM, Julien NICOLAS wrote:
Adrian,
It's just : Why html structure for sub-menu is not managed like main menu ?
Is it possible to use sub-menu like main menu ?
Maybe we can move macro from framework folder to theme folder.
hope you understand better in this way :)
Thanks for your help,
Julien.
Le 29/10/2014 15:22, Adrian Crum a écrit :
I don't understand the question. Could you ask it in another way please?
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 10/29/2014 1:39 PM, Julien NICOLAS wrote:
Hi Gavin, Adrian and all,
I was thinking about move sub-menu generation by header.ftl or
appbarOpen.ftl in theme folder like main menu...
Can we move the macro in the theme folder or create a service that send
sub-menu entry sorted list ?
It could be useful to create specific webdesign if this section could be
managed manually.
What's your opinion ?
Julien.
Le 29/10/2014 12:07, Gavin Mabie a écrit :
Hi,
As I'm working on the bootstrap theme branch, I notice that:
1. menuStringRenderer is out-commettted in the MacroScreenViewhandler
class;
2. This being the case, that menus get rendered by default through the
HtmlMenuRenderer class;
3. The latter automatically creates <ul><li><ul> opening tags for every
menus included in a screen definition with a menu item count bigger
than 0;
4. This results in an extra <ul> - the first one;
5. menu item count does not take sub-menus into account - in fact,
although defined in the xsd, I could not find any examples of the
sub-menu
attribute in any of the *menu,xml.
Is this an issue?Common sense tells me that the menuStringRendere was
(is)
part pf the architecture, but that a conscious decision was made to
rather
leave it out.
Some guidance please?
Gavin
