*** dimas has quit IRC
*** SachaS has quit IRC
*** kilo has joined #gnuenterprise
*** btami has joined #gnuenterprise
*** SachaS has joined #gnuenterprise
*** reinhard has joined #gnuenterprise
*** btami has quit IRC
*** kilo has left #gnuenterprise
*** jamest has joined #gnuenterprise
<reinhard> jamest: I've been playing around with dynamic menus lately
<jamest> cool
<reinhard> currently you can have <menu> and <menuitem> tags in your gfd that are added to the main menu
<reinhard> but we've once talked about making it possible to replace/hide standard menu items by putting some magic in the gfd
*** jcater has joined #gnuenterprise
<reinhard> so I thought about introducing a config file with the xml code of the standard menu and the standard toolbar
<reinhard> which would be merged with the menu given in the gfd
<reinhard> where gfd has higher priority
<reinhard> so config file could have something like
<jamest> i think that could be handy
<reinhard> <menu name="__main__">
<jamest> i assume this would work like the conf file now right?
<reinhard>   <menu name="file" label="File">
<reinhard>     <menuitem name="save" label="Save" />
<reinhard>   :
<reinhard>   :
<reinhard>   </menu>
<reinhard> </menu>
<reinhard> and in your gfd you could do something like
<reinhard> <menu name="__main__"
<reinhard>   <menuitem name="file">
<reinhard>     <menuitem name="save" hidden="True" />
<reinhard>     <menuitem name="something_new" label="Something that's not in the std menu" />
<reinhard> etc
<reinhard> (minus all the typos of course that I've now made)
<reinhard> I had considered making it an xml file instead of a typical [foo] style config file
<jcater> what is the point of this?
<jcater> (that's not a loaded question)
<reinhard> we could even consider to have a --menuconfig=foo.xml command line switch to override the standard menu to use
<jcater> so users can customize the menu?
<jcater> or so developers can customize the menu?
<jcater> users == users or sysadmins, of course
<reinhard> brb phone
<reinhard> well, the point where I came from was
<reinhard> for dynamic menus (additional menu items in the menu bar, local context menus), I added <menu> and <menuitem> elements to gfd
<reinhard> so I need some means of merging the standard menu with the custom menu
<reinhard> so my idea was why not just have the standard menu as GMenu and GMenuBar elements like the custom menu
<reinhard> so all can be merged into a single XML tree
<reinhard> and instead of hard coding the creation of these XML elements, the next thought was "why not read it from a file"
<reinhard> so actually the starting point was common handling of standard menu and custom menu as well as "not hardcoding things"
<reinhard> and being able to site-customize menus is only an interesting side effect
<reinhard> so what do you think?
<jcater> I'm indifferent
<reinhard> off for today, but will read logs
<reinhard> cu all
*** reinhard has quit IRC
*** siesel has joined #gnuenterprise
*** lupo__ has joined #gnuenterprise
*** SachaS has quit IRC
*** derek_ has joined #gnuenterprise
*** btami has joined #gnuenterprise
*** siesel has quit IRC
*** SachaS has joined #gnuenterprise
*** btami has quit IRC
<jamest> reinhard: I don't see a problem putting it in a file and I could see some advantages
*** lupo__ has quit IRC
*** dimas has joined #gnuenterprise
*** SachaS has quit IRC
*** derek_ has quit IRC
*** SachaS has joined #gnuenterprise
*** jamest has quit IRC
*** derek_ has joined #gnuenterprise
*** jcater has quit IRC
*** jcater has joined #gnuenterprise
*** jamest has joined #gnuenterprise
*** jcater has quit IRC
*** derek_ has quit IRC
*** jamest has quit IRC
*** jcater has joined #gnuenterprise