Re: winemenubuilder: eliminate wineshelllink
On Thu, 4 Sep 2008, Damjan Jovanovic wrote:
Changelog: * moved the functionality of wineshelllink into winemenubuilder, and eliminated wineshelllink
What is the rational for eliminating wineshelllink? It seems to me that by eliminating it we are losing a lot of flexibility for handling special setups (and there are a lot of these in menuing systems). -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ Research is the transformation of money to knowledge. Innovation is the transformation of knowledge to money. -- Dr. Hans Meixner
On Fri, Sep 5, 2008 at 1:20 PM, Francois Gouget <fgouget(a)free.fr> wrote:
On Thu, 4 Sep 2008, Damjan Jovanovic wrote:
Changelog: * moved the functionality of wineshelllink into winemenubuilder, and eliminated wineshelllink
What is the rational for eliminating wineshelllink?
Alexandre asked for it when I tried to send a patch that gets .url files to link into fd.o menus and the desktop. I'm not sure why, but I agree: having 2 programs to create menus adds complexity, fewer people understand both C and bash, patching both is ugly, debugging bash is hard, and personally wineshelllink has always felt like a thorn in my side when I tried to understand/change the menu code.
It seems to me that by eliminating it we are losing a lot of flexibility for handling special setups (and there are a lot of these in menuing systems).
There shouldn't be any "special" setups, fd.o is there just for that reason. Menus and desktop files should be bog standard now, and should have been that way from the very beginning.
-- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ Research is the transformation of money to knowledge. Innovation is the transformation of knowledge to money. -- Dr. Hans Meixner
Damjan Jovanovic
On Fri, Sep 5, 2008 at 7:59 AM, Damjan Jovanovic <damjan.jov(a)gmail.com> wrote:
There shouldn't be any "special" setups, fd.o is there just for that reason. Menus and desktop files should be bog standard now, and should have been that way from the very beginning.
Amen. -- Steven Edwards "There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo
On Fri, 5 Sep 2008, Damjan Jovanovic wrote: [...]
There shouldn't be any "special" setups, fd.o is there just for that reason.
Riiiiight. Like that's going to be true any day soon. Already on many distros you need to generate separate .menu files for Gnome and KDE (and yet another one for KDE 4 sometimes). -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ Demander si un ordinateur peut penser revient à demander si un sous-marin peut nager.
Francois Gouget <fgouget(a)free.fr> writes:
What is the rational for eliminating wineshelllink?
It seems to me that by eliminating it we are losing a lot of flexibility for handling special setups (and there are a lot of these in menuing systems).
We don't gain much flexibility by splitting functionality in a C half and a shell half, but it adds a lot of complexity and an ill-defined interface. The original design was to do everything in shell but that turns out to not be possible, so doing everything in C is the next best choice. -- Alexandre Julliard julliard(a)winehq.org
participants (4)
-
Alexandre Julliard -
Damjan Jovanovic -
Francois Gouget -
Steven Edwards