Chitti Babu said:
Hi Sudheer,
Yes, I had a similar use-case and faced the same problem.
I ensured that my daemon was properly osso-initialised to ensure that its
triggered properly by gui-app via dbus-daemon successfully.
But, in your use-case, you seem to use QT. I am not aware of the
Twas brillig at 10:05:38 07.05.2010 UTC-07 when scifi@hotmail.com
did gyre and gimble:
SG Could you please elaborate what you mean by upon first access?
There is elaborate documentation.
http://dbus.freedesktop.org/doc/dbus-specification.html#message-bus-starting-services
--
Hi All,
I am developing a Qt4.6 based application that monitors outgoing international
calls (by connecting to relevant DBUS signals) and routes
them via a calling card number. I have developed a configuration UI widget
(QWidget subclass) to enable/disable such routing.
The problem is that
which way.
cheers
Ram
- Original Message -
From: Scifi Guy
Sent: 05/07/10 03:26 PM
To: maemo-developers@maemo.org
Subject: Noob question re Qt Application structure
Hi All,
I am developing a Qt4.6 based application that monitors outgoing international
calls (by connecting to relevant
interact with your daemon, via
files, sockets, any which way.
cheers
Ram
- Original Message -
From: Scifi Guy
Sent: 05/07/10 03:26 PM
To: maemo-developers@maemo.org
Subject: Noob question re Qt Application structure
Hi All,
I am developing a Qt4.6 based application that monitors
: Re: Noob question re Qt Application structure
From: ian...@gmail.com
To: rkma...@gmx.com
CC: scifi@hotmail.com; maemo-developers@maemo.org
I second that opinion. Subclassing by functionality is definitely good
for a single app, but if you need to have the two parts running at
different
Message -
From: Scifi Guy
Sent: 05/07/10 04:24 PM
To: ian...@gmail.com, rkma...@gmx.com
Subject: RE: Noob question re Qt Application structure
Hi Ram ianaré,
Thank you for the response. Creating two apps makes sense. I was trying to
avoid user having to install two apps for one feature
: Fri, 7 May 2010 10:54:15 -0400
Subject: Re: Noob question re Qt Application structure
From: ian...@gmail.com
To: rkma...@gmx.com
CC: scifi@hotmail.com; maemo-developers@maemo.org
I second that opinion. Subclassing by functionality is definitely good
for a single app, but if you
Twas brillig at 08:24:06 07.05.2010 UTC-07 when scifi@hotmail.com
did gyre and gimble:
SG I can exit the daemon by receiving a custom DBUS signal but how do
SG I launch it?
Register it as a D-Bus service and daemon will be started by D-Bus upon
first access.
--
From: dotted...@dottedmag.net
To: scifi@hotmail.com
CC: ian...@gmail.com; rkma...@gmx.com; maemo-developers@maemo.org
Subject: Re: Noob question re Qt Application structure
Date: Fri, 7 May 2010 23:26:50 +0700
Twas brillig at 08:24:06 07.05.2010 UTC-07 when scifi@hotmail.com
ianaré
wrote:
Right, one way is to have two separate deb packages, making the GUI depend on
the daemon. This is expecially useful if you envision the daemon to be
accessed by other apps or does not need the GUI in all cases.
Another way is to package both apps (executables) in the same deb
Twas brillig at 10:05:38 07.05.2010 UTC-07 when scifi@hotmail.com
did gyre and gimble:
SG Could you please elaborate what you mean by upon first access?
There is elaborate documentation.
http://dbus.freedesktop.org/doc/dbus-specification.html#message-bus-starting-services
--
From: dotted...@dottedmag.net
To: scifi@hotmail.com
CC: ian...@gmail.com; rkma...@gmx.com; maemo-developers@maemo.org
Subject: Re: Noob question re Qt Application structure
Date: Sat, 8 May 2010 00:19:03 +0700
Twas brillig at 10:05:38 07.05.2010 UTC-07 when scifi@hotmail.com
13 matches
Mail list logo
