29 Mar
2005
29 Mar
'05
1:38 p.m.
From: Jan Depner <eviltwin69(a)cableone.net>
How to implement signal/slot mechanism in simplest terms with C?
In my opinion, sometimes it is unnecessary to link to a massive
code libraries if only one feature is needed.
AlsaModularSynth uses Qt's signals and slots in audio processing,
and thus requires the whole Qt and mixes GUI toolkit to audio side.
It could be wise to use sigc++ or minimal S/S code in audio processing
and Qt only in GUI.
But because Qt comes with every Linux distribution, maybe bad
dependencies can be allowed.
Juhana
--
http://music.columbia.edu/mailman/listinfo/linux-graphics-dev
for developers of open source graphics software
>No, imho one of the main advantages is
Qt's Signal/Slot mechanism
> sigc++ 
29 Mar
29 Mar
2:07 p.m.
Uh, I wasn't the one who said that about signals/slots. I do like them
but what I said was that you need to look at what you are trying to
accomplish before you decide on what toolkit to use. For anything that
is going to be near real-time I would keep the code as streamlined as
possible. For user interfaces that aren't hooked up to a near real-time
application I use Qt because it's much more well-defined, documented,
and mature than the other options. I think that Paul has taken the
correct path for what he is doing. I think Qt would be too much
overhead for Ardour.
Jan
On Tue, 2005-03-29 at 10:38, Juhana Sadeharju wrote:
From: Jan
Depner <eviltwin69(a)cableone.net>
How to implement signal/slot mechanism in simplest terms with C?
In my opinion, sometimes it is unnecessary to link to a massive
code libraries if only one feature is needed.
AlsaModularSynth uses Qt's signals and slots in audio processing,
and thus requires the whole Qt and mixes GUI toolkit to audio side.
It could be wise to use sigc++ or minimal S/S code in audio processing
and Qt only in GUI.
But because Qt comes with every Linux distribution, maybe bad
dependencies can be allowed.
Juhana >No, imho one of the main advantages is
Qt's Signal/Slot mechanism
> sigc++ 
4:21 p.m.
On Tuesday 29 Mar 2005 18:38, Juhana Sadeharju wrote:
It does? If memory serves me signals and slots are not realtime safe, moreover
they are only allowed to be used from one thread. Hence, if you have a GUI
only that thread can utilize these features.
From: Jan
Depner <eviltwin69(a)cableone.net>
> >No, imho one of the main advantages is Qt's Signal/Slot mechanism
>
> sigc++
How to implement signal/slot mechanism in simplest terms with C?
In my opinion, sometimes it is unnecessary to link to a massive
code libraries if only one feature is needed.
AlsaModularSynth uses Qt's signals and slots in audio processing, and thus requires the whole Qt and mixes GUI toolkit
to audio side.
It could be wise to use sigc++ or minimal S/S code in audio processing
and Qt only in GUI.
But because Qt comes with every Linux distribution, maybe bad
dependencies can be allowed.
I don't see why Qt is a bad dependency, on the contrary, having it all in one
place seems like a very good way to cut down on dependencies.
Since it's mostly used as a shared library the impact becomes much smaller as
soon as you use more than one program linked to Qt.
Though, if I'm right about the above, it might be the totally wrong choice.
--
http://spamatica.se/musicsite/
5:08 p.m.
On Tuesday 29 March 2005 21:21, Robert Jonsson wrote:
And as it is mostly agreed that qjackctl is a cool way of controlling jack you
already have qt installed and loaded...
Arnold
--
There is a theory which states that if ever anyone discovers exactly what the
Universe is for and why it is here, it will instantly disappear and be
replaced by something even more bizarre and inexplicable.
There is another theory which states that this has already happened.
-- Douglas Adams, The Restaurant at the End of the Universe
On Tuesday 29 Mar 2005 18:38, Juhana Sadeharju wrote:
Thats right, Qt`s signal/slot is inside-thread-only. But I think they have
some wrappers for multithread apps since they also provide the mechanism for
threads (->QThread)...
AlsaModularSynth uses Qt's signals and slots
in audio processing,
It does? If memory serves me signals and slots are not
realtime safe,
moreover they are only allowed to be used from one thread. Hence, if you
have a GUI only that thread can utilize these features. and thus
requires the whole Qt and mixes GUI toolkit to audio side.
It could be wise to use sigc++ or minimal S/S code in audio processing
and Qt only in GUI.
But because Qt comes with every Linux distribution, maybe bad
dependencies can be allowed.
I don't see why Qt is a bad dependency, on the
contrary, having it all in
one place seems like a very good way to cut down on dependencies.
Since it's mostly used as a shared library the impact becomes much smaller
as soon as you use more than one program linked to Qt.
7238
days inactive
7238
days old
linux-audio-dev@lists.linuxaudio.org
3 comments
4 participants
participants (4)
-
Arnold Krille -
Jan Depner -
Juhana Sadeharju -
Robert Jonsson