sfMenuGeneratorPlugin
Overview
Simple menu structure generator.
Requires Prototype 1.6.0, if your symfony doesn't come it that version , use the sfPrototypePlugin
YES
NO
No fancy behaviors
No css
Just plain old html!
Installation
symfony plugin-install http://plugins.symfony-project.com/sfN1IterationPlugin
Quick & Dirty
Configuration at 'app.yml' and 'module.yml'
all:
...
...
sf_menu_generator:
root:
text: 'Choose'
items: [contacts](users,)
contacts:
text: 'Contacts'
link: 'contacts/list'
shortcut: 'c'
deny: [contenteditor](manager,)
users:
text: 'Users Menu Node'
link: 'users/list'
items: [newuser, modifyuser](listusers,)
allow: [admin]
listusers:
text: 'User List'
link: 'users/list'
shortcut: 'ctrl+lu'
newuser:
text: 'New user'
link: 'users/new'
shortcut: 'ctrl+nu'
modifyuser:
text: 'Modify user'
link: 'users/modify'
Use of the helper
'menu'))?>
Generated HTML
config explained
The plugins use 'menu items' defined in app.yml or module.yml.
These items are not defined hierarchically. Instead of that each menu item has an items sections which refers to the other menu items that are to be considered childs.
Each menu item is defined as follows:
itemName:
text: 'text to show'
link: 'link to be fed into link_to()'
shortcut: 'sh1+ctrl'
items: [subitem2](subitem1,)
allow: [credential2](credential1,)
deny: [credential4](credential3,)
html_id: 'idItem'
html_style: 'float:left;color:#FF00FF;'
html_class: 'mypersonalclassname'
a_id: 'idAItem'
a_target: 'blank'
params explained
text: this is the text meant to be inside the li element. Can be anything, even html tags. Not mandatory.
link: this is the link the menu item will point to. it's not mandatory if nothing is set, then an '#' is generated.
shortcut: if you want to have a keyboard shortcut to make the browser goes to the url defined by the 'link' attribute, type it here. any character combination that can be seen on any editor is valid. you can only indicate one modifier: ctrl (or not).
items: this is an array of the menu items (defined just like this one elsewhere in the yml file) which are supposed to be the childs of this one.
allow: Array of the credentials a user must have to view this particular item . If none is given , 'any' wildcard is assumed .
deny: Array of the credentials a user must not have to view this particular item. If there is collision between this parameter and the allow parameter, the most resctrictive approach is taken.
a_*: attributes for the "a" tag. can be anything .
html_*: attributes for the "li" tag.
default classnames
If no 'html_class' is providen, the "li" tags have the class="mg node_".
If there is an 'html_class' parameter, then the "li" tag will have that class name, plus "node_".
user:
text: 'Users'
html_class: 'soft'
will generate ..
...
<li class="soft node_user">
....
<a ..>Users</a>
</li>
parameters preference . Use of the module.yml
The helper will read its configuration from both app.yml and module.yml.
Items can be defined in both files.
app.yml:
user:
text: 'users'
items: [user2](user1,)
user1:
text: 'user1'
module.yml:
user2:
text: 'user2'
As you see in the previous example, you can use child items that are defined elsewhere.
In case of overlapping, the module.yml definitions have precedence.
app.yml:
user:
text: 'user from the root menu'
items: [user2](user1,)
..
module.yml:
user:
text: 'user from the module'
is equivalent to:
user:
text: 'user from the module'
items: [user2](user1,)
Overlapping the items, allow and deny section
Regarding the 'items' , 'allow' and 'deny' sections, special rules apply when there is overlapping. The syntax is similar to the one used on stylesheets section of view.yml.
The items|allow|deny section defined for an overlapping menu item at module.yml file are added to the items|allow|deny section defined at the app.yml configuration file.
If there is a '-' prefix for one of the elements of the items|allow|deny array, then that element is removed from the childs.
The special '-' instructs to remove all the elements that are already defined at the *items|allow|deny section , at the moment the parser reads that special character. (The following elements are not affected).
so, if we have these two overlapping menu items:
app.yml:
user:
...
items: [user2, user3, user4](user1,)
allow: [cred2](cred1,)
module1.yml:
user:
items: [-user2](user5,)
deny: [cred2]
module2.yml:
user:
items: [-*,user6]
allow: [-cred1]
In module1.yml, the 'user5' child will be added, and the 'user2' will be removed. The 'cred2' credential is denied
In module2.yml all the childs defined in app.yml will be removed, and the 'user6' child will be added. The cred1 is no longer allowed
Shortcuts explained
In order to assure maximun compatibility, shortcuts are kept simple.
a shortcut defined in any menu item will just make the browser go to the address specified by the 'link' param. No more, No less
shortcuts can be made of single characters or words.
shortcuts are defined by the 'keypress' event, so any character combination that can be seen on an editor is admisible: 'a' , 'a8', '#er', etc ...
The only modifier which is to be taken into account is 'ctrl', and is specified like this 'ctrl+a' or 'bebe + ctrl' or '111+ctrl' , etc ...
In case the cursor is inside a text input only the shortcuts defined with the ctrl modifiers will work.
you can always un-focus any input field by pressing and releasing the ctrl or ESC key.
in case the shortcut is made of more than one character (a 'word' shortcut), you have two seconds between keypresses, if you take longer than that, the system empty the 'shortcut buffer'.
helper explained
The helper is fairly simple to use:
....
'menu','style'=>'display:inline;'))?>
The first argument is an array with the menu nodenames, as they are defined and discussed in the previous section.
The second argument are html attributes to pass to the main "ul" tag of the menu.
Jose Zarate 
-
Make a donation -
"symfony" is a trademark of Fabien Potencier. All rights reserved.
