menu-spec: Making menu-editing work, cleaning up <Move> semantics
bastian at kde.org
Thu Mar 31 13:28:42 EEST 2005
On Thursday 31 March 2005 11:25, Matt Kynaston wrote:
> On Wed, 30 Mar 2005 14:30:40 +0100, Waldo Bastian <bastian at kde.org> wrote:
> > Hi,
> > I would like to propose the attached change to the menu-spec, the
> > explanation is given below.
> This hasn't had much response, so I'll chip in my +1.
> It sounds like an excellent idea to me. The spec seems to be missing a
> trick when it says "<Move> is used primarily to fix up legacy
> directories". And the wording about using Moves in menu editing is
> most off-putting - to the point where it seems the most realistic way
> for a menu editor to accomplish a move is to <Deleted> the old menu
> and copy the contents to a new menu. Definitely not ideal.
> But I'm coming at this completely from the menu editing side. Am I
> right that they will be the only depth-first processing the menu
> parser needs to do? Will that add much overhead?
A typical recursion looks like:
for each child node
So if you are lucky you can just move a few lines of code around, and if you
are unlucky you will have to do a bit of copying and pasting and do the
> FWIW, in my current installs (KDE 3.4 and Gnome 2.10) I can only find
> Move being used once - in kde-essential.menu.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/xdg/attachments/20050331/09a34be1/attachment.pgp
More information about the xdg