No, line 90:
macroLibraryPath = UtilProperties.getPropertyValue("widget", getName() +
".menurenderer");
loads the macro menu renderer.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 10/29/2014 11:07 AM, Gavin Mabie wrote:
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
