[openbox] menu.xml - I thought It Only Had One Format/Standard?

[Dana Jansens]

Separator should be placed between items regardless of whether you inline
submenus or not, or whether you use wmname in startupnotify or not. I don't
think I understand your question.


On Tue, Aug 6, 2013 at 5:47 PM, Das <dasfox at gmail.com> wrote:

> Thanks for the reply Dana...
>
> I'm just saying if the menu can be written several different ways, then
> why not put in the source the example menu.xml that is most prefered and is
> going to work out the box, because what's in the source right now I can't
> seem to get it to work with a <separator/> line and I've tried this just
> like how I see it in a menu/xml that does work...
>
> This is in a menu.xml I found on livearp distro that works in these two
> examples below;
>
>  </item>
>                 <separator/>
>                 <menu execute="~/.config/openbox/cb-places-pipemenu.sh"
> id="Places" label="places"/>
>                 <separator/>
>
>  </item>
>        <separator/>
>        <menu id="config_openbox-help" label="help">
>
>
> Now I go and try the same thing from the example menu.xml in the source
> and it won't work...
>
>
> <item label="Xkill"
> icon="/home/slack/.icons/AwOken/clear/24x24/apps/xkill.png">
>     <action name="Execute">
>       <command>xkill</command>
>
>       <startupnotify>
>         <enabled>yes</enabled>
>       </startupnotify>
>     </action>
>   </item>
> <separator/>
>
> All I see is in the working menu.xml the <separator/> is placed below the
> </item> or below the <menu execute= or <menu id=
>
>
>
>
>
>
>
> On Tue, Aug 6, 2013 at 9:45 AM, Dana Jansens <dana at orodu.net> wrote:
>
>> http://openbox.org/wiki/Help:Menus
>>
>> On Mon, Aug 5, 2013 at 1:38 AM, Das <dasfox at gmail.com> wrote:
>>
>>> I've been using Openbox many years in Slackware compiling my own and in
>>> all these years I have always thought that the menu.xml that came with the
>>> source is the only method...
>>>
>>> After I've compiled from the source in  /etc/xdg/openbox/ I'll find the
>>> menu.xml I'll use that follows this format;
>>>
>>> <menu id="apps-accessories-menu" label="Accessories">
>>>   <item label="XCalculator">
>>>     <action name="Execute">
>>>       <command>xcalc</command>
>>>       <startupnotify>
>>>         <enabled>yes</enabled>
>>>       </startupnotify>
>>>     </action>
>>>   </item>
>>>
>>>  <menu id="apps-accessories-menu"/>
>>>
>>
>> menu-id lets you define the menu in one place and insert as a submenu
>> somewhere else. You can also just define the menu in place.
>>
>>
>>>
>>> Then I opened up the source and noticed it had a different line I've
>>> never used before(wmclass)
>>>
>>>
>>> <menu id="apps-net-menu" label="Internet">
>>>   <item label="Firefox">
>>>     <action name="Execute">
>>>       <command>firefox</command>
>>>       <startupnotify>
>>>         <enabled>yes</enabled>
>>> ---------->   <wmclass>Firefox</wmclass>
>>>       </startupnotify>
>>>     </action>
>>>   </item>
>>>
>>
>> http://openbox.org/wiki/Help:Actions#Execute
>>
>> wmclass is optional value to control startup notification.
>>
>>
>>>  Then, this past week I was playing around with livarp distro in
>>> Virtualbox to see what they are doing with Openbpx and to my surprise I
>>> found another format for the menu.xml; now this 'execute' and no 'menu id'
>>> anywhere in this menu.xml either...
>>>
>>>
>>> <item label="web browser">
>>>                         <action name="Execute">
>>> ---------------->                  <execute>firefox</execute>
>>>                         <startupnotify>
>>>                           <enabled>yes</enabled>
>>>                         </startupnotify>
>>>                         </action>
>>>                 </item>
>>>
>>>
>>> So I'm a bit confused, I thought Openbox was following some type of
>>> standard for the menu, not where you can do things in several different
>>> formats, all the years I've been using it this way, I've never been able to
>>> get the separator lines to appear with the menu.xml that ships with the
>>> source, so why ship something with the source if it's not going to work?
>>>
>>> I know there is obmenu you can use, but if it's creating the menu.xml in
>>> a different and a preferred format that users should follow then why isn't
>>> this format being included as an example in the source for the end-user to
>>> follow as well?
>>>
>>> YES I know this could all just be about FLEXIBILITY, picking and
>>> choosing the menthod you like,  but I think for new users to Openbox who
>>> might just follow the menu.xml in the source then it shoild be an example
>>> like the obmenu examples, or whatever example we should be following...
>>>
>>> To say the least, I can't belive all these years I've used Openbox with
>>> the menu.xml from the source and I've never had my menus display the
>>> seperator lines till  now with the livarop distro and the format they
>>> used...
>>>
>>> Now I'm scratching my head after all these years wondering what is the
>>> format to use and follow?
>>>
>>> Look I'm a Slacker I like control and flexibility but this is
>>> confusing...
>>>
>>> THANKS
>>>
>>> _______________________________________________
>>> openbox mailing list
>>> openbox at icculus.org
>>> http://icculus.org/mailman/listinfo/openbox
>>>
>>>
>>
>> _______________________________________________
>> openbox mailing list
>> openbox at icculus.org
>> http://icculus.org/mailman/listinfo/openbox
>>
>>
>
> _______________________________________________
> openbox mailing list
> openbox at icculus.org
> http://icculus.org/mailman/listinfo/openbox
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/openbox/attachments/20130806/c1c82bf8/attachment.html>