[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: app wrappers and gworkspace

From: Adrian Robert
Subject: Re: app wrappers and gworkspace
Date: Thu, 5 Aug 2004 17:50:50 -0400

Why does gworkspace have to use app wrappers?  App wrappers are
virtually useless (sorry).  Firstly, they are no where near a

Hmm, FWIW I really like the app-wrappers.. they provide an easy way to make ordinary executables behave as at least rudimentary GNUstep citizens. Their structure follows that for a regular GNUstep .app application, and they let you pass extra arguments to the program, or do filtering if need be. They package icons for both the app itself and the files it works on.

The /etc/mailcap format is too impoverished to support what GNUstep needs, and can't be assumed to be available on all GNUstep systems. One thing that might alleviate some of the problem is to write a script to convert a mailcap into a set of (iconless) app wrappers.. Similarly, conversion from the mini-files used by the Gnome and KDE linux desktops could be attempted. Actually, I think there is a command-line tool for doing part of this for KDE apps, it is installed by default in $GNUSTEP_SYSTEM_ROOT/Tools.

If you are missing ones for the apps you use most, it is pretty easy to make them. Probably there should be some sort of online repository for these, but you might send them to Enrico or someone else working on GWorkspace for now, and they can add them to the distribution.

As far as making every program installed accessible, how would GWorkspace determine this? I would hate to be selecting from a gigantic list of every program in /bin, /usr/bin, /usr/local/bin, etc. (all with the same or no icon) every time I want to make a new file association or do an "open with"...

reply via email to

[Prev in Thread] Current Thread [Next in Thread]