Re: (Possible) menu code rewrite
On Tue, 16 Jul 2002, Craig Dickson wrote:
> Henrique de Moraes Holschuh wrote:
> > The snippets would need to be all read, and XSLT-processed in the user's
> > system, every time an entry is updated.
> Which only occurs when packages are installed, updated, or removed,
> right? Even on unstable machines (aside from package developers), that's
No. The menu system allows local user overrides, and a lot of other very
nice and very neat features that make such updates more frequent, I think.
I am not sure it is always handled by update-menus, or if some of the menu
code for window managers actually does dynamic refresh...
> Well, it should be way more flexible, and way easier for new developers
> to learn, since it will be based on industry standard tools rather than
> some homebrew parser/translator.
Well, complexity is overrated. The menu syntax is very clean and very easy
to understand. I don't know about the .desktop syntax, though.
> I've been doing a lot of work lately with XML and XSLT, and I haven't
> found xsltproc to be a performance problem at all. Though in the
> interest of full disclosure, I should admit that I haven't run it on
> anything slower than a 700 MHz Celeron with 384MB RAM.
Yes. And you can bet some of us still want Debian to non-suck on a 486 with
16MB of RAM... If the XSLT transforms are rare, that's not a problem. But
if they are not...
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org