[Flow] Plugable Application Menu with Signals & Slots

Axel Wüstemann awu at qbus.de
Sun Apr 13 12:15:25 CEST 2014


Hi there,

I try to build a menu for my application by which the packages/moduls 
should be able to add themselfe to the menu by the means of signal/slot.

My first problem is, that I can't get signals/slots to run. I made it, 
as described in the documentation.

I have a MenuBuilderUtility class with an "emit" stub function. Within 
an abstract controller I defined a slot function and in the package 
bootstrap i wired both together.

By var_dump the $dispacher in the package bootstrap class I will see the 
entry of my wiring among with all others. In the proxy of my 
MenuBuilderUtility I can see the implementation of the "emit" stub function.

But if I try to var_dump something in my slot function - nothing will 
happen.

Has anybody an advice what I've might have oversean?

The other question is, how to structure those pluggable menus properly. 
Each package should have its menu structure in the setting.yaml:

Qbus:
   Bestdesq:
     Dashboard:
       packageLabel: Übersicht
       packageIcon: fa-dashboard
       packageOrder: 1
       packageModules:
         Dashboard: 'Kennzahlen'
         Planning: 'Planung'
         TimePlanning: 'Zeitplanung'

... something like this...

There is an abstract controller. In its initializeView function I will 
use the MenuBuilderUtility class to ask around, what package wants to 
participate to the menu. But where to put the slot function? Can I put 
this in the backage class? I'm afraid, that the package is not yet 
compeltely initialized...

Thanks
Yxel





More information about the Flow mailing list