modules/gallery/views/menu_dialog.html.php

<?php defined("SYSPATH") or die("No direct script access.") ?>
<li>
  <a <?= $menu->css_id ? "id='{$menu->css_id}'" : "" ?>
     class="g-dialog-link <?= $menu->css_class ?>"
     href="<?= $menu->url ?>"
     title="<?= $menu->label->for_html_attr() ?>">
    <?= $menu->label->for_html() ?>
  </a>
</li>
Change our menu building blocks to use PHP templates so that themes can override them and define their own menu formats. I worry a little bit that this approach may be too heavy since we're now doing a lot more template includes than we were before. Also, I had to change the Menu API to stop using __toString() because you can't throw exceptions from __toString() which would make it an unhappy experience for developers. 2009-10-27 13:46:24 -07:00			`<?php defined("SYSPATH") or die("No direct script access.") ?>`
			`<li>`
Some HTML validation fixes (don't render empty <ul> lists, empty id attributes, use & not &) 2010-02-12 20:59:26 -08:00			`<a <?= $menu->css_id ? "id='{$menu->css_id}'" : "" ?>`
Change our menu building blocks to use PHP templates so that themes can override them and define their own menu formats. I worry a little bit that this approach may be too heavy since we're now doing a lot more template includes than we were before. Also, I had to change the Menu API to stop using __toString() because you can't throw exceptions from __toString() which would make it an unhappy experience for developers. 2009-10-27 13:46:24 -07:00			`class="g-dialog-link <?= $menu->css_class ?>"`
			`href="<?= $menu->url ?>"`
			`title="<?= $menu->label->for_html_attr() ?>">`
			`<?= $menu->label->for_html() ?>`
			`</a>`
			`</li>`