Alp Özmert | 17 Jun 14:23 2007
Picon
Picon

libgnome: gnome-open.c


Hello there!

I came upon 'gnome-open' while looking for a way to make Emacs/Gnus
call the application associated by Gnome as an external viewer for
attached files.  The impediment is that I couldn't make gnome-open
wait until the process finishes, neither did I have success with
gnome_url_show().

I would be delighted by any given insight to this first-time gnome
hacker to enable him to construct a blocking call to
gnome_url_show().

Kind regards,
Alp Özmert
Wouter Bolsterlee | 17 Jun 14:41 2007
Picon
Picon

Re: libgnome: gnome-open.c


2007-06-17 klockan 14:23 skrev Alp Özmert:
> I came upon 'gnome-open' while looking for a way to make Emacs/Gnus
> call the application associated by Gnome as an external viewer for
> attached files.  The impediment is that I couldn't make gnome-open
> wait until the process finishes, neither did I have success with
> gnome_url_show().
> 
> I would be delighted by any given insight to this first-time gnome
> hacker to enable him to construct a blocking call to
> gnome_url_show().

This is not really possible to do reliably. Many Gnome applications are
single instance apps (e.g. Evince). This means that a second application
instance will just pass through the command line arguments (e.g. the
filename to show) to the already running applications, and quit immediately
afterwards.

  mvrgr, Wouter

--

-- 
:wq                                                       mail uws <at> xs4all.nl
                                                      web http://uwstopia.nl

who's gonna take it like this? :: no way :: you are, you are        -- gomez
_______________________________________________
(Continue reading)

Alp Özmert | 17 Jun 17:32 2007
Picon
Picon

Re: libgnome: gnome-open.c


Wouter Bolsterlee <uws+gnome <at> xs4all.nl> writes:

> 2007-06-17 klockan 14:23 skrev Alp Özmert:
>> I came upon 'gnome-open' while looking for a way to make Emacs/Gnus
>> call the application associated by Gnome as an external viewer for
>> attached files.  The impediment is that I couldn't make gnome-open
>> wait until the process finishes, neither did I have success with
>> gnome_url_show().
>> 
>> I would be delighted by any given insight to this first-time gnome
>> hacker to enable him to construct a blocking call to
>> gnome_url_show().
>
> This is not really possible to do reliably. Many Gnome
> applications are single instance apps (e.g. Evince). This means
> that a second application instance will just pass through the
> command line arguments (e.g. the filename to show) to the already
> running applications, and quit immediately afterwards.

Is there a simple way to find the path to the associated
application? For now that would be sufficient.

Regards,
Alp Özmert
Nickolay V. Shmyrev | 17 Jun 21:58 2007
Picon

Re: libgnome: gnome-open.c


В Вск, 17/06/2007 в 17:32 +0200, Alp Özmert пишет:
> Wouter Bolsterlee <uws+gnome <at> xs4all.nl> writes:
> 
> > 2007-06-17 klockan 14:23 skrev Alp Özmert:
> >> I came upon 'gnome-open' while looking for a way to make Emacs/Gnus
> >> call the application associated by Gnome as an external viewer for
> >> attached files.  The impediment is that I couldn't make gnome-open
> >> wait until the process finishes, neither did I have success with
> >> gnome_url_show().
> >> 
> >> I would be delighted by any given insight to this first-time gnome
> >> hacker to enable him to construct a blocking call to
> >> gnome_url_show().
> >
> > This is not really possible to do reliably. Many Gnome
> > applications are single instance apps (e.g. Evince). This means
> > that a second application instance will just pass through the
> > command line arguments (e.g. the filename to show) to the already
> > running applications, and quit immediately afterwards.
> 
> Is there a simple way to find the path to the associated
> application? For now that would be sufficient.
> 
> Regards,
> Alp Özmert

I suppose it's much easier to write your own little program which will
(Continue reading)

Michael Lamothe | 17 Jun 23:31 2007
Picon

Use of the word GNOME


As always, I apologise if this is the wrong place for this question.  Please educate me.

Down to business, I've written a nice little DVB client using libgnome.  Now, I'm not very creative when it comes to names so I called it 'GNOME TV'. If/when I ever distribute the application (GPL'd of course) am I allowed to use the word "GNOME" in its title, or is it trademarked.  Is it a bad idea, in general, to use GNOME in the title.

Thanks in advance.

_______________________________________________
gnome-devel-list mailing list
gnome-devel-list <at> gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-devel-list
Alp Özmert | 18 Jun 00:22 2007
Picon
Picon

Re: libgnome: gnome-open.c


Nickolay V. Shmyrev <nshmyrev <at> yandex.ru> writes:

> В Вск, 17/06/2007 в 17:32 +0200, Alp Özmert пишет:
>> Wouter Bolsterlee <uws+gnome <at> xs4all.nl> writes:
>> 
>> > 2007-06-17 klockan 14:23 skrev Alp Özmert:
>> >> I came upon 'gnome-open' while looking for a way to make Emacs/Gnus
>> >> call the application associated by Gnome as an external viewer for
>> >> attached files.  The impediment is that I couldn't make gnome-open
>> >> wait until the process finishes, neither did I have success with
>> >> gnome_url_show().
>> >> 
>> >> I would be delighted by any given insight to this first-time gnome
>> >> hacker to enable him to construct a blocking call to
>> >> gnome_url_show().
>> >
>> > This is not really possible to do reliably. Many Gnome
>> > applications are single instance apps (e.g. Evince). This means
>> > that a second application instance will just pass through the
>> > command line arguments (e.g. the filename to show) to the already
>> > running applications, and quit immediately afterwards.
>> 
>> Is there a simple way to find the path to the associated
>> application? For now that would be sufficient.
>
> I suppose it's much easier to write your own little program which will
> use gnomevfs in similar way like gnome-open does. In addition you can
> suggest a patch to gnome-open to print this information.
>
(Continue reading)

Calum Benson | 18 Jun 15:12 2007
Picon

Re: Use of the word GNOME


On Mon, 2007-06-18 at 07:31 +1000, Michael Lamothe wrote:

> Down to business, I've written a nice little DVB client using
> libgnome.  Now, I'm not very creative when it comes to names so I
> called it 'GNOME TV'. If/when I ever distribute the application (GPL'd
> of course) am I allowed to use the word "GNOME" in its title, or is it
> trademarked.  Is it a bad idea, in general, to use GNOME in the
> title. 

I don't know about the trademark issue, but in general it's not usually
a great idea to call your app "GNOME Foo" because:

- Your app will probably run quite happily on KDE and other desktop
environments too, so the fact that it has anything to do with GNOME is
mostly irrelevant to your users.

- If everybody called their GNOME apps "GNOME Foo", then they'd all be
listed under "G" on the Applications menu, which makes them harder to
find.  (See also
http://developer.gnome.org/projects/gup/hig/2.0/desktop-integration.html#menu-item-names)

What you choose to call the binary is a separate issue; we do still have
a lot of apps called $EPREFIX/bin/gnome-foo, and I'm not sure if we
actually have any guidelines about that. (I'd like to think that we do,
though.)

Cheeri,
Calum.

(Continue reading)

Magnus Therning | 17 Jun 19:40 2007

Re: libgnome: gnome-open.c


On Sun, Jun 17, 2007 at 17:32:30 +0200, Alp Özmert wrote:
>
>Wouter Bolsterlee <uws+gnome <at> xs4all.nl> writes:
>
>> 2007-06-17 klockan 14:23 skrev Alp Özmert:
>>> I came upon 'gnome-open' while looking for a way to make Emacs/Gnus
>>> call the application associated by Gnome as an external viewer for
>>> attached files.  The impediment is that I couldn't make gnome-open
>>> wait until the process finishes, neither did I have success with
>>> gnome_url_show().
>>> 
>>> I would be delighted by any given insight to this first-time gnome
>>> hacker to enable him to construct a blocking call to
>>> gnome_url_show().
>>
>> This is not really possible to do reliably. Many Gnome
>> applications are single instance apps (e.g. Evince). This means
>> that a second application instance will just pass through the
>> command line arguments (e.g. the filename to show) to the already
>> running applications, and quit immediately afterwards.
>
>Is there a simple way to find the path to the associated
>application? For now that would be sufficient.

I ran into that problem a while ago.  Don't know if it helps but here's
a dirty Python script I hacked up and run from inside mutt in order to
use GNOME's MIME data rather than mailcap:
(Continue reading)


Gmane