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

[Dana Jansens]

On Tue, Aug 13, 2013 at 8:01 PM, Das <dasfox at gmail.com> wrote:

> Hi Dana,
>
> Sorry if I've created some confusion, its not about learning XML, I was
> just thinkng of this from the stand point I guess as a new user coming into
> this....
>
> So maybe I'm just thinking about this all wrong and when anyone sees a
> .xml file they just need to know and learn that anything goes as long as
> it's validated XML, then make whatever you feel like...
>

It's not really make whatever you feel like. The format just allows you to
define a <menu> inline or somewhere else, and you can refer to the menu to
insert it into other menus as many times as you please. If the docs are not
clear I'd love improvements there.


>
>  I guess I was looking at it like HTML, like how many ways can you really
> make a hyper link or hotlink, seems like in some code you can only do
> things one or two ways, so I guess I was thinking the same for the menu.xml
> like that was really the only way in which to create this type of
> thing/syntax....
>
> Thanks...
>
>
> On Tue, Aug 13, 2013 at 1:49 PM, Dana Jansens <dana at orodu.net> wrote:
>
>> On Tue, Aug 13, 2013 at 7:45 PM, Das <dasfox at gmail.com> wrote:
>>
>>> Great thanks, now we're getting somewhere! :)
>>>
>>> Ok again, this is what I meant by a standard, I'm attaching a file
>>> menu_test.xml so as to not confuse the name with another menu.xml...
>>>
>>> Since this is XML I guess now that I've had some time to consider it, as
>>> long as you make the XML syntax correct anything will work, so I'm no XML
>>> pro, how many ways then does that leave use to be able to create a menu?
>>>
>>> This was all I meant by making the menu a standard so it's only written
>>> one way, so as to not confuse end-users across different distros, or menu
>>> making applications, etc., when they come across many various formats as
>>> I've now seen and then people are scratching their heads wondering what's
>>> going on, because I'm not familiar with any desktops or other Window
>>> Managers that allow for a menu to be coded in many different syntax ways...
>>>
>>>
>> If you don't want to learn how to write XML I'd recommend
>> http://obmenu.sourceforge.net/. There's no need to learn this stuff for
>> making menus.
>>
>>
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Aug 13, 2013 at 5:35 AM, Xyne <xyne at archlinux.ca> wrote:
>>>
>>>> Das wrote:
>>>>
>>>> >I think you need to LOOK HARDER at the menu.xml in the source
>>>> >...
>>>> >so pelase don't patronize people
>>>>
>>>> no comment
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ><menu id="apps-accessories-menu" label="Accessories">
>>>> ><separator/>
>>>>
>>>> You have placed the separator in the definition of the accessories
>>>> menu, so it
>>>> appears in the accessories menu. According to your previous posts, you
>>>> want the
>>>> separator to appear after the accessories menu, *in the root menu*, so
>>>> you
>>>> should place it there:
>>>>
>>>> <menu id="root-menu" label="Openbox 3">
>>>>   <separator label="Applications" />
>>>>   <menu id="apps-accessories-menu"/>
>>>>   <separator/>
>>>>
>>>> I have attached an updated version of your file.
>>>>
>>>> Regards,
>>>> Xyne
>>>>
>>>> _______________________________________________
>>>> 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
>>
>>
>
> _______________________________________________
> 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/20130813/ad74e2ca/attachment.html>