This sounds like a good idea, but it's a bit weird to have an icon the
menu that does nothing (i.e. print "usage: gargoyle <gamefile>" in
~/.xsession-errors ;)).
Maybe gargoyle could show an "Open Game" dialog instead?
> b) A simple icon, modified from the one from lxterminal, with a '>' in
> its screen. Unfortunately, it seems that I cannot post attachments
> here. I placed this icon, gargoyle.png in /usr/share/pixmaps.
>
> After that, I could right-click a .z5 or whatever if file and
> associate it easily with Gargoyle, so Gargoyle will be launched every
> time the file is clicked from then on.
>
> I like Gargoyle very much; nice work and thank you.
That's a nice idea too :)
There's even a way to automatically associate .z5 and other extensions
to gargoyle.
See:
http://git.savannah.gnu.org/cgit/freedink/dfarc.git/tree/share/freedink-mime.xml.in
for an example and
http://git.savannah.gnu.org/cgit/freedink/dfarc.git/tree/share/Makefile.am
for how to make Gnome/KDE take it into account.
See also
http://kapo-cpp.blogspot.com/2008/02/register-your-own-mime-type-on-free.html
for an introduction. We probably need a few "magic numbers" to
identify Z-Machine games and other type of games.
--
Sylvain
On the bad side, the latest release is from 2006, and it doesn't seem
to be packaged in distros.
--
Sylvain
However, another possibility is to convert the gargoyle script for
UNIX in a GTK application, I've also wondered why the Windows version
has a binary selector while the Linux one is a simple script, with
less functionality (at least, until now). It could even be possible to
create a cross-platform launcher in Gtk. I can do that, provided there
is interest. I mean, the same program would be the same for all
platforms. Or maybe I'm missing something big and this cannot be done.
Hi !
> This is indeed my intention - to port
> launcher.c<http://code.google.com/p/garglk/source/browse/trunk/garglk/launcher.c>to
> GTK. I just haven't found the time to do it yet, but it should be
> straightforward. I think that makes more sense than introducing another
> package dependency on the Linux side. If you want to take a crack at the
> port, please feel free. I would be delighted to accept patches.
Mmm... I think that what you want is to have a cross-platform launcher.c. I mean, if it uses GTK, then it will be needed to provide the Gtk libraries in Windows (in Linux that's taken for granted). So you want something that, with conditional compilation, will use native Windows in Win32 and Gtk in UNIX. Is that it?
-- Baltasar García Perez-Schofield (jbga...@uvigo.es)
Dpt. Informática, Universidad de Vigo, España
http://webs.uvigo.es/jbgarcia/
Mmm... I think that what you want is to have a cross-platform launcher.c. I mean, if it uses GTK, then it will be needed to provide the Gtk libraries in Windows (in Linux that's taken for granted). So you want something that, with conditional compilation, will use native Windows in Win32 and Gtk in UNIX. Is that it?