Re: Patch for build system

En/na Trevor Fancher ha escrit:
>
> I was attempting to build CLAM on my Mac and I hit a bug with the
> build system. The problem is the CheckPkgConfigFile function defined
> in scons/libs/clam_build_helpers.py assumes the environmental
> variable PKG_CONFIG is set.  Since the MacPorts installation
> documentation doesn't tell the user to set PKG_CONFIG and it doesn't
> get set after installing pkgconfig, I am assuming PKG_CONFIG isn't
> set on most systems using Macports.
>
> The attached patch fixes the problem for me.  I'm not sure if this
> is the proper way to solve the problem, but it's a start.

Both patches commited (#11220). Thanks a lot Trevor!

Pau

QConsole at CLAM

Hi, Houssem and Mondrian.

I didn't found a QConsole mailing list or similar, so that's why i am mailing 
you directly to the sf address.

I am part of the comunity developing the CLAM audio framework[1]. We would 
like to add live scripting capabilities to our framework graphical tool[2] 
and I gladly found QConsole project via the Qt-Interest mailinglist. It is a 
very smart implementation and it even integrates python that it is something 
we thought we needed to do ourselves. So I am pretty happy with it.

Being about to integrate it, i have two main questions.

First of all, it is a class, not a library, so i am suposing that the 
preferred way to integrate it is moving files to our project. I dislike that 
because i'd rather prefer avoiding any duplication of external code in our 
svn. Maybe i am missing something, maybe you wellcome converting it into a 
library. In any case, we will forward you as patches any modifications we do 
to the code to avoid divergence as much as we can.

The other issue is the usage of Qt3Support classes. Our project is Qt4 and we 
removed any dependency on Qt3 migration classes. I would like to keep it like 
that. So my inertia will go toward making QConsole a pure Qt4 widget. Taking 
a look at the code i saw that using Qt3Support enables sharing a lot of qt3 
and qt4 code, but i dont know whether you would like a pleanty qt4 migration.

Feel free to join our #clam irc channel at freenode and share your thoughts.

Regards.
David.

Re: Commit #11195: templated plugins generator

I have added a new script in the same line: TemplateGenerator.py

Usage: ./TemplateGenerator TEMPLATEFILE

Example of input file:
Name:TestTemplate
BaseClass:Processing
i:AudioInPort
i:AudioInPort
i:AudioInPort
i:AudioInPort
o:AudioOutPort
o:AudioOutPort
ic:i,0,100
ic:i,0,100
ic:i,0,100
ic:i,0,100

Convention:
i (input) | o (output): type
ic (input control) | oc (output control): integer/float, range

Then these two commands:
./TemplateGenerator.py exampleinputfile
./TemplatedPluginsGenerator.py TestProcessing TestTemplate "Fundació
Barcelona Media Universitat Pompeu Fabra" GPL 2007

Generates:

"TestProcessing.hxx"

Call for GSoC 2008 project proposals

Google Summer of Code program is back this year. Last year, GSoC was very 
successful and brought new developers and features to CLAM. If we are lucky, 
we might be chosen again this year as mentoring organization. 

We are updating the wiki with new project proposals for the GSoC application. 
We would like to open up this brainstorming process to users and developers. 
If you are missing some feature you would like to be addressed by GSoC 
students, just send it on the list.

Our working set of ideas:
http://clam.iua.upf.edu/wikis/clam/index.php/SoC_ideas

The number of projects is also proportional to the number of mentors. If you 
have experience developing with CLAM and want to help us as mentor, just drop 
us a line.

--

-- 
David García Garzón
(Work) dgarcia at iua dot upf anotherdot es
http://www.iua.upf.edu/~dgarcia

_______________________________________________
Clam-devel mailing list
Clam-devel@...
https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel

Re: Commit #11195: templated plugins generator

Great, Hernan.

Shouldn't be the port type an important input to specify?

On Tuesday 04 Març 2008, Hernán Ordiales wrote:
> I have added a new script in the same line: TemplateGenerator.py
>
> Usage: ./TemplateGenerator TEMPLATEFILE
>
> Example of input file:
> Name:TestTemplate
> BaseClass:Processing
> i:AudioInPort
> i:AudioInPort
> i:AudioInPort
> i:AudioInPort
> o:AudioOutPort
> o:AudioOutPort
> ic:i,0,100
> ic:i,0,100
> ic:i,0,100
> ic:i,0,100
>
> Convention:
> i (input) | o (output): type
> ic (input control) | oc (output control): integer/float, range
>
> Then these two commands:
> ./TemplateGenerator.py exampleinputfile
> ./TemplatedPluginsGenerator.py TestProcessing TestTemplate "Fundació

Re: Commit #11195: templated plugins generator

Oh, yes, what you are specifying is the type, then what is missing is the name 
of the port.

On Tuesday 04 Març 2008, David García Garzón wrote:
> Great, Hernan.
>
> Shouldn't be the port type an important input to specify?
>
> On Tuesday 04 Març 2008, Hernán Ordiales wrote:
> > I have added a new script in the same line: TemplateGenerator.py
> >
> > Usage: ./TemplateGenerator TEMPLATEFILE
> >
> > Example of input file:
> > Name:TestTemplate
> > BaseClass:Processing
> > i:AudioInPort
> > i:AudioInPort
> > i:AudioInPort
> > i:AudioInPort
> > o:AudioOutPort
> > o:AudioOutPort
> > ic:i,0,100
> > ic:i,0,100
> > ic:i,0,100
> > ic:i,0,100
> >
> > Convention:
> > i (input) | o (output): type
> > ic (input control) | oc (output control): integer/float, range

Re: QConsole at CLAM

Having already a full qt4 version are great news!

So, let me volunteer myself to build the library. I am used to that kind of 
task because my involving in CLAM. So as soon as you upload the qt4 code to 
the svn i'll take it a look. 

David.

On Tuesday 04 Març 2008, Mondrian Nuessle wrote:
> Hello,
> I think that would be great. Houssem, it'd be very interested in the qt4
> version of course 
> And I totally agree on the library issue. Volunteers?
>
> Regards,
> Mondrian
>
> Houssem BDIOUI wrote:
> > Hi David,
> >
> >   I recently have ported QConsole completely into Qt4
> > (no usage fot Qt3Support) but I did'nt yet managed to release
> > it!
> >   I'll send you this version as soon as possible.
> >   As for the library issue, you're right. It should be the best way.
> >
> > Regards,
> > Houssem
> >
> > On Mon, Mar 3, 2008 at 6:24 PM, David García Garzón <dgarcia@...f.edu>

Re: Commit #11195: templated plugins generator

On 3/4/08, David García Garzón <dgarcia@...> wrote:
> Oh, yes, what you are specifying is the type, then what is missing is the name
>  of the port.

yep, but in the TODO list:

# TODO:
#* Add controls range
#* pyqt or NetworkEditor GUI instead of the input file
#* Add config options
#* Define ports and controls names through the input file
(i:AudioInPort, Audio Input)

I forgot to mention that with a simple edit in the script you can
select the member style that you prefer :P

member_style = "m"
#member_style = "_"

cheers,
--

-- 
Hernán
http://h.ordia.com.ar
GnuPG: 0xEE8A3FE9

Re: Re: QConsole at CLAM

_______________________________________________
Clam-devel mailing list
Clam-devel@...
https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel

Re: Re: QConsole at CLAM

There are several development ways regarding python-CLAM integration. Most of 
them are discussed as CLAM GSoC proposals.

One way is using SIP [1], SWIG[2] or similar to wrap CLAM API and just 
programming CLAM using python. SIP is a C++ to Python API wrapper. The 
problem is that CLAM has a too extensive API that we would like to reduce. We 
could pick the key bits.
[1] http://www.riverbankcomputing.co.uk/sip/
[2] http://www.swig.org/

Other, that does not imply forcedly Python, would be wrapping just the network 
construction API (create, connect, delete, move, configure, select...) and 
offer it to an interactive console with completition on the NetworkEditor 
alla AutoCAD. Macros (non-interactive) could be are also usefull in this 
context. This one could use the QConsole widget.

We hadn't any festival related idea and i am not able to get it on what you 
say. If you could develop it further?

David.

On Tuesday 04 Març 2008, abe kazemzadeh wrote:
> Hi All,
> The console idea sounds interesting.... what are you planning? (in a
> previous email you mentioned sip, but I wasn't sure what that stands for).
>  Maybe you already have this in mind, but the console could be used for
> issuing commands to the festival speech synthesizer (it uses scheme for
> scripting) and piping the output to other processings.  Well, just curious
> about the console idea...
> Abe
>
> On 3/4/08, David García Garzón <dgarcia@...> wrote:
> > Having already a full qt4 version are great news!
> >
> > So, let me volunteer myself to build the library. I am used to that kind
> > of
> > task because my involving in CLAM. So as soon as you upload the qt4 code
> > to
> > the svn i'll take it a look. 
> >
> > David.
> >
> > On Tuesday 04 Març 2008, Mondrian Nuessle wrote:
> > > Hello,
> > > I think that would be great. Houssem, it'd be very interested in the
> > > qt4 version of course 
> > > And I totally agree on the library issue. Volunteers?
> > >
> > > Regards,
> > > Mondrian
> > >
> > > Houssem BDIOUI wrote:
> > > > Hi David,
> > > >
> > > >   I recently have ported QConsole completely into Qt4
> > > > (no usage fot Qt3Support) but I did'nt yet managed to release
> > > > it!
> > > >   I'll send you this version as soon as possible.
> > > >   As for the library issue, you're right. It should be the best way.
> > > >
> > > > Regards,
> > > > Houssem
> > > >
> > > > On Mon, Mar 3, 2008 at 6:24 PM, David García Garzón <
> >
> > dgarcia@...>
> >
> > > > wrote:
> > > >> Hi, Houssem and Mondrian.
> > > >>
> > > >> I didn't found a QConsole mailing list or similar, so that's why i
> > > >> am mailing
> > > >> you directly to the sf address.
> > > >>
> > > >> I am part of the comunity developing the CLAM audio framework[1]. We
> > > >> would like to add live scripting capabilities to our framework
> >
> > graphical
> >
> > > >> tool[2] and I gladly found QConsole project via the Qt-Interest
> > > >> mailinglist. It is a
> > > >> very smart implementation and it even integrates python that it is
> > > >> something
> > > >> we thought we needed to do ourselves. So I am pretty happy with it.
> > > >>
> > > >> Being about to integrate it, i have two main questions.
> > > >>
> > > >> First of all, it is a class, not a library, so i am suposing that
> > > >> the preferred way to integrate it is moving files to our project. I
> >
> > dislike
> >
> > > >> that
> > > >> because i'd rather prefer avoiding any duplication of external code
> >
> > in
> >
> > > >> our svn. Maybe i am missing something, maybe you wellcome converting
> >
> > it
> >
> > > >> into a library. In any case, we will forward you as patches any
> > > >> modifications we do
> > > >> to the code to avoid divergence as much as we can.
> > > >>
> > > >> The other issue is the usage of Qt3Support classes. Our project is
> >
> > Qt4
> >
> > > >> and we
> > > >> removed any dependency on Qt3 migration classes. I would like to
> > > >> keep
> >
> > it
> >
> > > >> like
> > > >> that. So my inertia will go toward making QConsole a pure Qt4
> > > >> widget. Taking
> > > >> a look at the code i saw that using Qt3Support enables sharing a lot
> >
> > of
> >
> > > >> qt3
> > > >> and qt4 code, but i dont know whether you would like a pleanty qt4
> > > >> migration.
> > > >>
> > > >> Feel free to join our #clam irc channel at freenode and share your
> > > >> thoughts.
> > > >>
> > > >> Regards.
> > > >> David.
> > > >>
> > > >> [1] http://clam.iua.upf.edu
> > > >> [2]
> >
> > http://clam.iua.upf.edu/wikis/clam/index.php/Network_Editor_tutorial
> >
> >
> >
> >
> > --
> > David García Garzón
> > (Work) dgarcia at iua dot upf anotherdot es
> > http://www.iua.upf.edu/~dgarcia
> >
> > _______________________________________________
> > Clam-devel mailing list
> > Clam-devel@...
> > https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel

--

-- 
David García Garzón
(Work) dgarcia at iua dot upf anotherdot es
http://www.iua.upf.edu/~dgarcia

_______________________________________________
Clam-devel mailing list
Clam-devel@...
https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel