pksampler-devel

[pksampler-devel] CLAM and PK widgets

[David <dg...@iu...>]

Hi, patrick and any one on the list.

I am working on a C++ designer plugin version of pk widgets to integrate th=
em=20
with CLAM audio application prototyping framework. The framework allows you=
=20
to visually build audio applications by prototyping the audio core with a=20
patch tool and the interface with Qt Designer.

I just ported some of the pkwidgets: a generic button and a generic slider.=
=20
Both offer properties to base pixmap from the designer interface. [2] They=
=20
really look nice!!

I am open to any collaboration, to split the widgets from CLAM as an=20
independent library or check the new PyQt4 method to build plugins in pytho=
n=20
(published today!). I know we also share some interests on VST/Qt integrati=
on=20
so drop us a line.


=2D-=20
David Garc=C3=ADa Garz=C3=B3n
(Work) dgarcia at iua dot upf anotherdot es
(Home) vokimon at telefonica adot net
http://www.iua.upf.edu/~dgarcia

Re: [pksampler-devel] CLAM and PK widgets

[Patrick S. <pat...@gm...>]

Are you working on a project written in python? If so, I would suggest
that you keep as much code in python as possible!

I developed an interesting way to do this in designer in C++. It is
kind of complicated, though.

I have a basic subclass for each standard widget like knob and button.
They all have myStyle, myObject, and myValue (not the real names - the
real names have our code name in them), string properties declared
with Q_PROPERTY. When a plugin widget is loaded, the host wrapper
checks all children with QWidget::findChildren() that have the myStyle
property, and creates the appropriate style and sets it on the widget.
It took me a while to write the styles, but know that I know the
proper enums and virtual functions (hint: read qwindowsstyle.cpp and
qcommonstyle.cpp for QWidget subclass usage, in that order) it's
rpetty easy to write a style.

PyQt doesn't support QStyle subclasses because of a casting problem -
that's why I wrote my simple custom classes. My classes expect the
pixmaps to be in a certain format (not so unreasonable), and the
subclasses are all centered around a pythonic way to set a pixmap path
on a widget easily. I don't know how this integrates into your
project.

What are your requirements for your widgets? do you just want to
display pixmaps widgets from a designer form? You can do whatever you
want with my code, just leave a reference somewhere that says you
learned something from me so I can get hired again when I quit my
current job.

On 4/11/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> Hi, patrick and any one on the list.
>
> I am working on a C++ designer plugin version of pk widgets to integrate =
them
> with CLAM audio application prototyping framework. The framework allows y=
ou
> to visually build audio applications by prototyping the audio core with a
> patch tool and the interface with Qt Designer.
>
> I just ported some of the pkwidgets: a generic button and a generic slide=
r.
> Both offer properties to base pixmap from the designer interface. [2] The=
y
> really look nice!!
>
> I am open to any collaboration, to split the widgets from CLAM as an
> independent library or check the new PyQt4 method to build plugins in pyt=
hon
> (published today!). I know we also share some interests on VST/Qt integra=
tion
> so drop us a line.
>
>
> --
> David Garc=EDa Garz=F3n
> (Work) dgarcia at iua dot upf anotherdot es
> (Home) vokimon at telefonica adot net
> http://www.iua.upf.edu/~dgarcia
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> pksampler-devel mailing list
> pks...@li...
> https://lists.sourceforge.net/lists/listinfo/pksampler-devel
>
>
>


--=20
Patrick Kidd Stinson
http://www.patrickkidd.com/
http://pkaudio.sourceforge.net/
http://pksampler.sourceforge.net/

Re: [pksampler-devel] CLAM and PK widgets

[David <dg...@iu...>]

On Dijous 12 Abril 2007, Patrick Stinson wrote:
> Are you working on a project written in python?=20

No, it is C++. Although we want to provide bindings soon.

> If so, I would suggest=20
> that you keep as much code in python as possible!

Yes, i understand why. Now i have to take a look at the features you added=
=20
since the original port i did in 2004. Afortunatelly, C++ code is nearly as=
=20
tiny and simple as Python code.

Any way i just need being able to load the plugin, and just rely on the=20
AbstractButton and AbstractSlider interface, so i would like to check if i=
=20
the new announced PyQt feature (python designer plugins) really works.


> I developed an interesting way to do this in designer in C++. It is
> kind of complicated, though.
>
> I have a basic subclass for each standard widget like knob and button.
> They all have myStyle, myObject, and myValue (not the real names - the
> real names have our code name in them), string properties declared
> with Q_PROPERTY. When a plugin widget is loaded, the host wrapper
> checks all children with QWidget::findChildren() that have the myStyle
> property, and creates the appropriate style and sets it on the widget.
> It took me a while to write the styles, but know that I know the
> proper enums and virtual functions (hint: read qwindowsstyle.cpp and
> qcommonstyle.cpp for QWidget subclass usage, in that order) it's
> rpetty easy to write a style.
>
> PyQt doesn't support QStyle subclasses because of a casting problem -
> that's why I wrote my simple custom classes. My classes expect the
> pixmaps to be in a certain format (not so unreasonable), and the
> subclasses are all centered around a pythonic way to set a pixmap path
> on a widget easily. I don't know how this integrates into your
> project.
>
> What are your requirements for your widgets? do you just want to
> display pixmaps widgets from a designer form?=20

Well, i think that the current approach we are taking is more suited for ou=
r=20
purposes. Just a property with the base name for the pixmap. Our project is=
 a=20
prototyping tool, as i told you. We want to allow a maximum flexibility=20
without programming. A user can build his own interface and bind it to a=20
processing core which is also constructed by another visual tool, the=20
NetworkEditor. Check the newer development snapshots. They have been=20
assembled using pixmap widgets from the designer plugin.

http://clam.iua.upf.edu/wikis/clam/index.php/Development_screenshots

=46or the pixmap widgets i would like to have a fast way they can change th=
e=20
image without compilation, that's why i made it a property.

In fact, I don't like my current property implementation. I would like a=20
pixmap property so you can use the resource dialog, but then i don't know h=
ow=20
to get the file name from the pixmap in order to extrapolate the other name=
s.=20
I also would like to provide some default implementations classes not=20
requiring to setup any property. But definitely this approach is more=20
flexible than building a QStyle.

I would like also that our users could have your povray based widget=20
construction kit available on a handy place. So that they can generate new=
=20
widgets easily. I have to talk more to you about that. I am not a povray=20
expert. Also debian and your programs' dependencies are in some kind of=20
trouble. Which ditribution are you programming on?


> You can do whatever you=20
> want with my code, just leave a reference somewhere that says you
> learned something from me so I can get hired again when I quit my
> current job.


Of course. Thanks. And when you need to be hired, feel free to refer our=20
project as a success history for your developments. Definitely, we are goin=
g=20
to use it a lot. :-)



> On 4/11/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> > Hi, patrick and any one on the list.
> >
> > I am working on a C++ designer plugin version of pk widgets to integrate
> > them with CLAM audio application prototyping framework. The framework
> > allows you to visually build audio applications by prototyping the audio
> > core with a patch tool and the interface with Qt Designer.
> >
> > I just ported some of the pkwidgets: a generic button and a generic
> > slider. Both offer properties to base pixmap from the designer interfac=
e.
> > [2] They really look nice!!
> >
> > I am open to any collaboration, to split the widgets from CLAM as an
> > independent library or check the new PyQt4 method to build plugins in
> > python (published today!). I know we also share some interests on VST/Qt
> > integration so drop us a line.
> >
> >
> > --
> > David Garc=EDa Garz=F3n
> > (Work) dgarcia at iua dot upf anotherdot es
> > (Home) vokimon at telefonica adot net
> > http://www.iua.upf.edu/~dgarcia
> >
> > -----------------------------------------------------------------------=
=2D-
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share
> > your opinions on IT & business topics through brief surveys-and earn ca=
sh
> > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=
=3DDEVDEV
> > _______________________________________________
> > pksampler-devel mailing list
> > pks...@li...
> > https://lists.sourceforge.net/lists/listinfo/pksampler-devel



=2D-=20
David Garc=EDa Garz=F3n
(Work) dgarcia at iua dot upf anotherdot es
(Home) vokimon at telefonica adot net
http://www.iua.upf.edu/~dgarcia

Re: [pksampler-devel] CLAM and PK widgets

[Patrick S. <pat...@gm...>]

I wish I had more brain to use to listen to your description, but i am
in the middle of a totally unrelated commercial release for my client.
I built our system around the specific requirements for our product
plugin system, so it probably won't make much sense for you.\

I program against the latest PyQt4 and for any platform. I always
build from source. I suggest you do too.

I'd be happy to answer questions about the povray stuff. That facet of
my code is pretty interesting, as it lets you focus on the povray
scenes. I can't remember what state the pkpov tool is in, but I was
just writing the scenes myself in python anyway, so I suggest you try
that.

Keep me informed how your work goes. I'm glad to hear my code helped.

On 4/11/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> On Dijous 12 Abril 2007, Patrick Stinson wrote:
> > Are you working on a project written in python?
>
> No, it is C++. Although we want to provide bindings soon.
>
> > If so, I would suggest
> > that you keep as much code in python as possible!
>
> Yes, i understand why. Now i have to take a look at the features you adde=
d
> since the original port i did in 2004. Afortunatelly, C++ code is nearly =
as
> tiny and simple as Python code.
>
> Any way i just need being able to load the plugin, and just rely on the
> AbstractButton and AbstractSlider interface, so i would like to check if =
i
> the new announced PyQt feature (python designer plugins) really works.
>
>
> > I developed an interesting way to do this in designer in C++. It is
> > kind of complicated, though.
> >
> > I have a basic subclass for each standard widget like knob and button.
> > They all have myStyle, myObject, and myValue (not the real names - the
> > real names have our code name in them), string properties declared
> > with Q_PROPERTY. When a plugin widget is loaded, the host wrapper
> > checks all children with QWidget::findChildren() that have the myStyle
> > property, and creates the appropriate style and sets it on the widget.
> > It took me a while to write the styles, but know that I know the
> > proper enums and virtual functions (hint: read qwindowsstyle.cpp and
> > qcommonstyle.cpp for QWidget subclass usage, in that order) it's
> > rpetty easy to write a style.
> >
> > PyQt doesn't support QStyle subclasses because of a casting problem -
> > that's why I wrote my simple custom classes. My classes expect the
> > pixmaps to be in a certain format (not so unreasonable), and the
> > subclasses are all centered around a pythonic way to set a pixmap path
> > on a widget easily. I don't know how this integrates into your
> > project.
> >
> > What are your requirements for your widgets? do you just want to
> > display pixmaps widgets from a designer form?
>
> Well, i think that the current approach we are taking is more suited for =
our
> purposes. Just a property with the base name for the pixmap. Our project =
is a
> prototyping tool, as i told you. We want to allow a maximum flexibility
> without programming. A user can build his own interface and bind it to a
> processing core which is also constructed by another visual tool, the
> NetworkEditor. Check the newer development snapshots. They have been
> assembled using pixmap widgets from the designer plugin.
>
> http://clam.iua.upf.edu/wikis/clam/index.php/Development_screenshots
>
> For the pixmap widgets i would like to have a fast way they can change th=
e
> image without compilation, that's why i made it a property.
>
> In fact, I don't like my current property implementation. I would like a
> pixmap property so you can use the resource dialog, but then i don't know=
 how
> to get the file name from the pixmap in order to extrapolate the other na=
mes.
> I also would like to provide some default implementations classes not
> requiring to setup any property. But definitely this approach is more
> flexible than building a QStyle.
>
> I would like also that our users could have your povray based widget
> construction kit available on a handy place. So that they can generate ne=
w
> widgets easily. I have to talk more to you about that. I am not a povray
> expert. Also debian and your programs' dependencies are in some kind of
> trouble. Which ditribution are you programming on?
>
>
> > You can do whatever you
> > want with my code, just leave a reference somewhere that says you
> > learned something from me so I can get hired again when I quit my
> > current job.
>
>
> Of course. Thanks. And when you need to be hired, feel free to refer our
> project as a success history for your developments. Definitely, we are go=
ing
> to use it a lot. :-)
>
>
>
> > On 4/11/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> > > Hi, patrick and any one on the list.
> > >
> > > I am working on a C++ designer plugin version of pk widgets to integr=
ate
> > > them with CLAM audio application prototyping framework. The framework
> > > allows you to visually build audio applications by prototyping the au=
dio
> > > core with a patch tool and the interface with Qt Designer.
> > >
> > > I just ported some of the pkwidgets: a generic button and a generic
> > > slider. Both offer properties to base pixmap from the designer interf=
ace.
> > > [2] They really look nice!!
> > >
> > > I am open to any collaboration, to split the widgets from CLAM as an
> > > independent library or check the new PyQt4 method to build plugins in
> > > python (published today!). I know we also share some interests on VST=
/Qt
> > > integration so drop us a line.
> > >
> > >
> > > --
> > > David Garc=EDa Garz=F3n
> > > (Work) dgarcia at iua dot upf anotherdot es
> > > (Home) vokimon at telefonica adot net
> > > http://www.iua.upf.edu/~dgarcia
> > >
> > > ---------------------------------------------------------------------=
----
> > > Take Surveys. Earn Cash. Influence the Future of IT
> > > Join SourceForge.net's Techsay panel and you'll get the chance to sha=
re
> > > your opinions on IT & business topics through brief surveys-and earn =
cash
> > > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CI=
D=3DDEVDEV
> > > _______________________________________________
> > > pksampler-devel mailing list
> > > pks...@li...
> > > https://lists.sourceforge.net/lists/listinfo/pksampler-devel
>
>
>
> --
> David Garc=EDa Garz=F3n
> (Work) dgarcia at iua dot upf anotherdot es
> (Home) vokimon at telefonica adot net
> http://www.iua.upf.edu/~dgarcia
>
>


--=20
Patrick Kidd Stinson
http://www.patrickkidd.com/
http://pkaudio.sourceforge.net/
http://pksampler.sourceforge.net/

Re: [pksampler-devel] CLAM and PK widgets

[David <dg...@iu...>]

On Thursday 12 April 2007 04:14:49 Patrick Stinson wrote:
> I wish I had more brain to use to listen to your description, but i am
> in the middle of a totally unrelated commercial release for my client.

No problem. Let's talk afterwards then.

> I built our system around the specific requirements for our product
> plugin system, so it probably won't make much sense for you.\
>
> I program against the latest PyQt4 and for any platform. I always
> build from source. I suggest you do too.

I do, but we offer a development platform and distribute packages for a lot=
 of=20
platforms so in some way we will like to distribute the widget toolchain to=
o=20
in a similar way or providing some howto.

> I'd be happy to answer questions about the povray stuff. That facet of
> my code is pretty interesting, as it lets you focus on the povray
> scenes. I can't remember what state the pkpov tool is in, but I was
> just writing the scenes myself in python anyway, so I suggest you try
> that.

I did some experiments by changing parameters such as colors and size of=20
buttons, and works pretty well. :-) I need to know how to crop them but i a=
m=20
on the track.

What i miss is some way of making the background transparent. Adding pkwidg=
ets=20
to an interface forces you to use the widget background for all the interfa=
ce=20
to avoid awkward aspect. By having an alpha background we could remove this=
=20
limitation. I spotted several interesting links:
http://www.imagico.de/pov/icons.html
http://www.econym.demon.co.uk/shadowtut/index.htm

> Keep me informed how your work goes. I'm glad to hear my code helped.

At the moment i'll use the existing widgets and pixmaps and i'll extend bot=
h=20
as i need more. Our packaging must not to be changed for that. Eventually i=
=20
would like to integrate things further and porting other widgets. So let's=
=20
talk then. I'll keep you informed. Warn me also when your release is over a=
nd=20
lets chat a little.

Regards


> On 4/11/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> > On Dijous 12 Abril 2007, Patrick Stinson wrote:
> > > Are you working on a project written in python?
> >
> > No, it is C++. Although we want to provide bindings soon.
> >
> > > If so, I would suggest
> > > that you keep as much code in python as possible!
> >
> > Yes, i understand why. Now i have to take a look at the features you
> > added since the original port i did in 2004. Afortunatelly, C++ code is
> > nearly as tiny and simple as Python code.
> >
> > Any way i just need being able to load the plugin, and just rely on the
> > AbstractButton and AbstractSlider interface, so i would like to check if
> > i the new announced PyQt feature (python designer plugins) really works.
> >
> > > I developed an interesting way to do this in designer in C++. It is
> > > kind of complicated, though.
> > >
> > > I have a basic subclass for each standard widget like knob and button.
> > > They all have myStyle, myObject, and myValue (not the real names - the
> > > real names have our code name in them), string properties declared
> > > with Q_PROPERTY. When a plugin widget is loaded, the host wrapper
> > > checks all children with QWidget::findChildren() that have the myStyle
> > > property, and creates the appropriate style and sets it on the widget.
> > > It took me a while to write the styles, but know that I know the
> > > proper enums and virtual functions (hint: read qwindowsstyle.cpp and
> > > qcommonstyle.cpp for QWidget subclass usage, in that order) it's
> > > rpetty easy to write a style.
> > >
> > > PyQt doesn't support QStyle subclasses because of a casting problem -
> > > that's why I wrote my simple custom classes. My classes expect the
> > > pixmaps to be in a certain format (not so unreasonable), and the
> > > subclasses are all centered around a pythonic way to set a pixmap path
> > > on a widget easily. I don't know how this integrates into your
> > > project.
> > >
> > > What are your requirements for your widgets? do you just want to
> > > display pixmaps widgets from a designer form?
> >
> > Well, i think that the current approach we are taking is more suited for
> > our purposes. Just a property with the base name for the pixmap. Our
> > project is a prototyping tool, as i told you. We want to allow a maximum
> > flexibility without programming. A user can build his own interface and
> > bind it to a processing core which is also constructed by another visual
> > tool, the NetworkEditor. Check the newer development snapshots. They ha=
ve
> > been assembled using pixmap widgets from the designer plugin.
> >
> > http://clam.iua.upf.edu/wikis/clam/index.php/Development_screenshots
> >
> > For the pixmap widgets i would like to have a fast way they can change
> > the image without compilation, that's why i made it a property.
> >
> > In fact, I don't like my current property implementation. I would like a
> > pixmap property so you can use the resource dialog, but then i don't kn=
ow
> > how to get the file name from the pixmap in order to extrapolate the
> > other names. I also would like to provide some default implementations
> > classes not requiring to setup any property. But definitely this approa=
ch
> > is more flexible than building a QStyle.
> >
> > I would like also that our users could have your povray based widget
> > construction kit available on a handy place. So that they can generate
> > new widgets easily. I have to talk more to you about that. I am not a
> > povray expert. Also debian and your programs' dependencies are in some
> > kind of trouble. Which ditribution are you programming on?
> >
> > > You can do whatever you
> > > want with my code, just leave a reference somewhere that says you
> > > learned something from me so I can get hired again when I quit my
> > > current job.
> >
> > Of course. Thanks. And when you need to be hired, feel free to refer our
> > project as a success history for your developments. Definitely, we are
> > going to use it a lot. :-)
> >
> > > On 4/11/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> > > > Hi, patrick and any one on the list.
> > > >
> > > > I am working on a C++ designer plugin version of pk widgets to
> > > > integrate them with CLAM audio application prototyping framework. T=
he
> > > > framework allows you to visually build audio applications by
> > > > prototyping the audio core with a patch tool and the interface with
> > > > Qt Designer.
> > > >
> > > > I just ported some of the pkwidgets: a generic button and a generic
> > > > slider. Both offer properties to base pixmap from the designer
> > > > interface. [2] They really look nice!!
> > > >
> > > > I am open to any collaboration, to split the widgets from CLAM as an
> > > > independent library or check the new PyQt4 method to build plugins =
in
> > > > python (published today!). I know we also share some interests on
> > > > VST/Qt integration so drop us a line.
> > > >
> > > >
> > > > --
> > > > David Garc=EDa Garz=F3n
> > > > (Work) dgarcia at iua dot upf anotherdot es
> > > > (Home) vokimon at telefonica adot net
> > > > http://www.iua.upf.edu/~dgarcia
> > > >
> > > > -------------------------------------------------------------------=
=2D-
> > > >---- Take Surveys. Earn Cash. Influence the Future of IT
> > > > Join SourceForge.net's Techsay panel and you'll get the chance to
> > > > share your opinions on IT & business topics through brief surveys-a=
nd
> > > > earn cash
> > > > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&=
CID=3DDE
> > > >VDEV _______________________________________________
> > > > pksampler-devel mailing list
> > > > pks...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/pksampler-devel
> >
> > --
> > David Garc=EDa Garz=F3n
> > (Work) dgarcia at iua dot upf anotherdot es
> > (Home) vokimon at telefonica adot net
> > http://www.iua.upf.edu/~dgarcia

Re: [pksampler-devel] CLAM and PK widgets

[Patrick S. <pat...@gm...>]

On 4/12/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> On Thursday 12 April 2007 04:14:49 Patrick Stinson wrote:
> > I wish I had more brain to use to listen to your description, but i am
> > in the middle of a totally unrelated commercial release for my client.
>
> No problem. Let's talk afterwards then.

Sure. This topic is really fun because the work is really high level and ea=
sy!

>
> > I built our system around the specific requirements for our product
> > plugin system, so it probably won't make much sense for you.\
> >
> > I program against the latest PyQt4 and for any platform. I always
> > build from source. I suggest you do too.
>
> I do, but we offer a development platform and distribute packages for a l=
ot of
> platforms so in some way we will like to distribute the widget toolchain =
too
> in a similar way or providing some howto.

Gotchya. Packaging is the usually the biggest problem with sip/pyqt stuff, =
IMO.

>
> > I'd be happy to answer questions about the povray stuff. That facet of
> > my code is pretty interesting, as it lets you focus on the povray
> > scenes. I can't remember what state the pkpov tool is in, but I was
> > just writing the scenes myself in python anyway, so I suggest you try
> > that.
>
> I did some experiments by changing parameters such as colors and size of
> buttons, and works pretty well. :-) I need to know how to crop them but i=
 am
> on the track.

Right. I wrote a tool to do that a while ago, but it isn't in my
repository anymore because I took a different direction with the
widgets I have now. I could write it again in a day or less if I
wasn't so busy... We release early june (hopefully) and this stuff
would be fun to get back into then (no promises!)

>
> What i miss is some way of making the background transparent. Adding pkwi=
dgets
> to an interface forces you to use the widget background for all the inter=
face
> to avoid awkward aspect. By having an alpha background we could remove th=
is
> limitation. I spotted several interesting links:
> http://www.imagico.de/pov/icons.html
> http://www.econym.demon.co.uk/shadowtut/index.htm

This was one of two major problems I never tackled.. I thought about
using some sort of mask, but I'm not sure. The purest way would be to
get povray to do it, but I haven't looked into it. If it isn't
immediately possible using the povray docs, then a post to the povray
mailing list and/or community forums would probably be worth it. If
not, creating some sort of mask might be the way to go, but that would
be difficult with the shadow.

>
> > Keep me informed how your work goes. I'm glad to hear my code helped.
>
> At the moment i'll use the existing widgets and pixmaps and i'll extend b=
oth
> as i need more. Our packaging must not to be changed for that. Eventually=
 i
> would like to integrate things further and porting other widgets. So let'=
s
> talk then. I'll keep you informed. Warn me also when your release is over=
 and
> lets chat a little.

I may not remember (we are REALLY busy), so drop me another line if I
don't get back to you. This is what we are working on:
www.soundsonline.com.

Are you doing anything commercially?


>
> Regards
>
>
> > On 4/11/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> > > On Dijous 12 Abril 2007, Patrick Stinson wrote:
> > > > Are you working on a project written in python?
> > >
> > > No, it is C++. Although we want to provide bindings soon.
> > >
> > > > If so, I would suggest
> > > > that you keep as much code in python as possible!
> > >
> > > Yes, i understand why. Now i have to take a look at the features you
> > > added since the original port i did in 2004. Afortunatelly, C++ code =
is
> > > nearly as tiny and simple as Python code.
> > >
> > > Any way i just need being able to load the plugin, and just rely on t=
he
> > > AbstractButton and AbstractSlider interface, so i would like to check=
 if
> > > i the new announced PyQt feature (python designer plugins) really wor=
ks.
> > >
> > > > I developed an interesting way to do this in designer in C++. It is
> > > > kind of complicated, though.
> > > >
> > > > I have a basic subclass for each standard widget like knob and butt=
on.
> > > > They all have myStyle, myObject, and myValue (not the real names - =
the
> > > > real names have our code name in them), string properties declared
> > > > with Q_PROPERTY. When a plugin widget is loaded, the host wrapper
> > > > checks all children with QWidget::findChildren() that have the mySt=
yle
> > > > property, and creates the appropriate style and sets it on the widg=
et.
> > > > It took me a while to write the styles, but know that I know the
> > > > proper enums and virtual functions (hint: read qwindowsstyle.cpp an=
d
> > > > qcommonstyle.cpp for QWidget subclass usage, in that order) it's
> > > > rpetty easy to write a style.
> > > >
> > > > PyQt doesn't support QStyle subclasses because of a casting problem=
 -
> > > > that's why I wrote my simple custom classes. My classes expect the
> > > > pixmaps to be in a certain format (not so unreasonable), and the
> > > > subclasses are all centered around a pythonic way to set a pixmap p=
ath
> > > > on a widget easily. I don't know how this integrates into your
> > > > project.
> > > >
> > > > What are your requirements for your widgets? do you just want to
> > > > display pixmaps widgets from a designer form?
> > >
> > > Well, i think that the current approach we are taking is more suited =
for
> > > our purposes. Just a property with the base name for the pixmap. Our
> > > project is a prototyping tool, as i told you. We want to allow a maxi=
mum
> > > flexibility without programming. A user can build his own interface a=
nd
> > > bind it to a processing core which is also constructed by another vis=
ual
> > > tool, the NetworkEditor. Check the newer development snapshots. They =
have
> > > been assembled using pixmap widgets from the designer plugin.
> > >
> > > http://clam.iua.upf.edu/wikis/clam/index.php/Development_screenshots
> > >
> > > For the pixmap widgets i would like to have a fast way they can chang=
e
> > > the image without compilation, that's why i made it a property.
> > >
> > > In fact, I don't like my current property implementation. I would lik=
e a
> > > pixmap property so you can use the resource dialog, but then i don't =
know
> > > how to get the file name from the pixmap in order to extrapolate the
> > > other names. I also would like to provide some default implementation=
s
> > > classes not requiring to setup any property. But definitely this appr=
oach
> > > is more flexible than building a QStyle.
> > >
> > > I would like also that our users could have your povray based widget
> > > construction kit available on a handy place. So that they can generat=
e
> > > new widgets easily. I have to talk more to you about that. I am not a
> > > povray expert. Also debian and your programs' dependencies are in som=
e
> > > kind of trouble. Which ditribution are you programming on?
> > >
> > > > You can do whatever you
> > > > want with my code, just leave a reference somewhere that says you
> > > > learned something from me so I can get hired again when I quit my
> > > > current job.
> > >
> > > Of course. Thanks. And when you need to be hired, feel free to refer =
our
> > > project as a success history for your developments. Definitely, we ar=
e
> > > going to use it a lot. :-)
> > >
> > > > On 4/11/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> > > > > Hi, patrick and any one on the list.
> > > > >
> > > > > I am working on a C++ designer plugin version of pk widgets to
> > > > > integrate them with CLAM audio application prototyping framework.=
 The
> > > > > framework allows you to visually build audio applications by
> > > > > prototyping the audio core with a patch tool and the interface wi=
th
> > > > > Qt Designer.
> > > > >
> > > > > I just ported some of the pkwidgets: a generic button and a gener=
ic
> > > > > slider. Both offer properties to base pixmap from the designer
> > > > > interface. [2] They really look nice!!
> > > > >
> > > > > I am open to any collaboration, to split the widgets from CLAM as=
 an
> > > > > independent library or check the new PyQt4 method to build plugin=
s in
> > > > > python (published today!). I know we also share some interests on
> > > > > VST/Qt integration so drop us a line.
> > > > >
> > > > >
> > > > > --
> > > > > David Garc=EDa Garz=F3n
> > > > > (Work) dgarcia at iua dot upf anotherdot es
> > > > > (Home) vokimon at telefonica adot net
> > > > > http://www.iua.upf.edu/~dgarcia
> > > > >
> > > > > -----------------------------------------------------------------=
----
> > > > >---- Take Surveys. Earn Cash. Influence the Future of IT
> > > > > Join SourceForge.net's Techsay panel and you'll get the chance to
> > > > > share your opinions on IT & business topics through brief surveys=
-and
> > > > > earn cash
> > > > > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforg=
e&CID=3DDE
> > > > >VDEV _______________________________________________
> > > > > pksampler-devel mailing list
> > > > > pks...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/pksampler-devel
> > >
> > > --
> > > David Garc=EDa Garz=F3n
> > > (Work) dgarcia at iua dot upf anotherdot es
> > > (Home) vokimon at telefonica adot net
> > > http://www.iua.upf.edu/~dgarcia
>
>
>


--=20
Patrick Kidd Stinson
http://www.patrickkidd.com/
http://pkaudio.sourceforge.net/
http://pksampler.sourceforge.net/

Re: [pksampler-devel] CLAM and PK widgets

[David <dg...@iu...>]

On Dijous 12 Abril 2007, Patrick Stinson wrote:
> > I did some experiments by changing parameters such as colors and size of
> > buttons, and works pretty well. :-) I need to know how to crop them but=
 i
> > am on the track.
>
> Right. I wrote a tool to do that a while ago, but it isn't in my
> repository anymore because I took a different direction with the
> widgets I have now. I could write it again in a day or less if I
> wasn't so busy... We release early june (hopefully) and this stuff
> would be fun to get back into then (no promises!)

Nice to know. If i need it before i think i could do it myself.

> > What i miss is some way of making the background transparent. Adding
> > pkwidgets to an interface forces you to use the widget background for a=
ll
> > the interface to avoid awkward aspect. By having an alpha background we
> > could remove this limitation. I spotted several interesting links:
> > http://www.imagico.de/pov/icons.html
> > http://www.econym.demon.co.uk/shadowtut/index.htm
>
> This was one of two major problems I never tackled.. I thought about
> using some sort of mask, but I'm not sure. The purest way would be to
> get povray to do it, but I haven't looked into it. If it isn't
> immediately possible using the povray docs, then a post to the povray
> mailing list and/or community forums would probably be worth it. If
> not, creating some sort of mask might be the way to go, but that would
> be difficult with the shadow.

Have you checked the links? Ok, you are in release ;-) i can just describe=
=20
them, they explain how to do icons with alpha by doing 2 or 3 povray runs=20
with different parameters. By doing that we could get some alpha shadowed=20
backgrounds. I promise to get on that, well, if you don't before ;-)


> > > Keep me informed how your work goes. I'm glad to hear my code helped.
> >
> > At the moment i'll use the existing widgets and pixmaps and i'll extend
> > both as i need more. Our packaging must not to be changed for that.
> > Eventually i would like to integrate things further and porting other
> > widgets. So let's talk then. I'll keep you informed. Warn me also when
> > your release is over and lets chat a little.
>
> I may not remember (we are REALLY busy), so drop me another line if I
> don't get back to you. This is what we are working on:
> www.soundsonline.com.
>
> Are you doing anything commercially?

Not so, but we are currently seeking commercial projects involving CLAM. He=
re=20
comercial does not mean non-free but we also are able to drop non=20
relicenceable dependencies if non-free is a requirement.

Good luck with the release.

=2D-=20
David Garc=EDa Garz=F3n
(Work) dgarcia at iua dot upf anotherdot es
(Home) vokimon at telefonica adot net
http://www.iua.upf.edu/~dgarcia

Re: [pksampler-devel] CLAM and PK widgets

[Patrick S. <pat...@gm...>]

On 4/12/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> On Dijous 12 Abril 2007, Patrick Stinson wrote:
> > > I did some experiments by changing parameters such as colors and size=
 of
> > > buttons, and works pretty well. :-) I need to know how to crop them b=
ut i
> > > am on the track.
> >
> > Right. I wrote a tool to do that a while ago, but it isn't in my
> > repository anymore because I took a different direction with the
> > widgets I have now. I could write it again in a day or less if I
> > wasn't so busy... We release early june (hopefully) and this stuff
> > would be fun to get back into then (no promises!)
>
> Nice to know. If i need it before i think i could do it myself.
>
> > > What i miss is some way of making the background transparent. Adding
> > > pkwidgets to an interface forces you to use the widget background for=
 all
> > > the interface to avoid awkward aspect. By having an alpha background =
we
> > > could remove this limitation. I spotted several interesting links:
> > > http://www.imagico.de/pov/icons.html
> > > http://www.econym.demon.co.uk/shadowtut/index.htm
> >
> > This was one of two major problems I never tackled.. I thought about
> > using some sort of mask, but I'm not sure. The purest way would be to
> > get povray to do it, but I haven't looked into it. If it isn't
> > immediately possible using the povray docs, then a post to the povray
> > mailing list and/or community forums would probably be worth it. If
> > not, creating some sort of mask might be the way to go, but that would
> > be difficult with the shadow.
>
> Have you checked the links? Ok, you are in release ;-) i can just describ=
e
> them, they explain how to do icons with alpha by doing 2 or 3 povray runs
> with different parameters. By doing that we could get some alpha shadowed
> backgrounds. I promise to get on that, well, if you don't before ;-)

you probably will before me

>
>
> > > > Keep me informed how your work goes. I'm glad to hear my code helpe=
d.
> > >
> > > At the moment i'll use the existing widgets and pixmaps and i'll exte=
nd
> > > both as i need more. Our packaging must not to be changed for that.
> > > Eventually i would like to integrate things further and porting other
> > > widgets. So let's talk then. I'll keep you informed. Warn me also whe=
n
> > > your release is over and lets chat a little.
> >
> > I may not remember (we are REALLY busy), so drop me another line if I
> > don't get back to you. This is what we are working on:
> > www.soundsonline.com.
> >
> > Are you doing anything commercially?
>
> Not so, but we are currently seeking commercial projects involving CLAM. =
Here
> comercial does not mean non-free but we also are able to drop non
> relicenceable dependencies if non-free is a requirement.
>
> Good luck with the release.
>
> --
> David Garc=EDa Garz=F3n
> (Work) dgarcia at iua dot upf anotherdot es
> (Home) vokimon at telefonica adot net
> http://www.iua.upf.edu/~dgarcia
>
>


--=20
Patrick Kidd Stinson
http://www.patrickkidd.com/
http://pkaudio.sourceforge.net/
http://pksampler.sourceforge.net/

Re: [pksampler-devel] CLAM and PK widgets

[Patrick S. <pat...@gm...>]

I just had a look at some of the screenshots. Good greif! I thouht I
recognized those widgets...I wish I had some time to play with it and
make it better...

On 4/12/07, Patrick Stinson <pat...@gm...> wrote:
> On 4/12/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> > On Dijous 12 Abril 2007, Patrick Stinson wrote:
> > > > I did some experiments by changing parameters such as colors and si=
ze of
> > > > buttons, and works pretty well. :-) I need to know how to crop them=
 but i
> > > > am on the track.
> > >
> > > Right. I wrote a tool to do that a while ago, but it isn't in my
> > > repository anymore because I took a different direction with the
> > > widgets I have now. I could write it again in a day or less if I
> > > wasn't so busy... We release early june (hopefully) and this stuff
> > > would be fun to get back into then (no promises!)
> >
> > Nice to know. If i need it before i think i could do it myself.
> >
> > > > What i miss is some way of making the background transparent. Addin=
g
> > > > pkwidgets to an interface forces you to use the widget background f=
or all
> > > > the interface to avoid awkward aspect. By having an alpha backgroun=
d we
> > > > could remove this limitation. I spotted several interesting links:
> > > > http://www.imagico.de/pov/icons.html
> > > > http://www.econym.demon.co.uk/shadowtut/index.htm
> > >
> > > This was one of two major problems I never tackled.. I thought about
> > > using some sort of mask, but I'm not sure. The purest way would be to
> > > get povray to do it, but I haven't looked into it. If it isn't
> > > immediately possible using the povray docs, then a post to the povray
> > > mailing list and/or community forums would probably be worth it. If
> > > not, creating some sort of mask might be the way to go, but that woul=
d
> > > be difficult with the shadow.
> >
> > Have you checked the links? Ok, you are in release ;-) i can just descr=
ibe
> > them, they explain how to do icons with alpha by doing 2 or 3 povray ru=
ns
> > with different parameters. By doing that we could get some alpha shadow=
ed
> > backgrounds. I promise to get on that, well, if you don't before ;-)
>
> you probably will before me
>
> >
> >
> > > > > Keep me informed how your work goes. I'm glad to hear my code hel=
ped.
> > > >
> > > > At the moment i'll use the existing widgets and pixmaps and i'll ex=
tend
> > > > both as i need more. Our packaging must not to be changed for that.
> > > > Eventually i would like to integrate things further and porting oth=
er
> > > > widgets. So let's talk then. I'll keep you informed. Warn me also w=
hen
> > > > your release is over and lets chat a little.
> > >
> > > I may not remember (we are REALLY busy), so drop me another line if I
> > > don't get back to you. This is what we are working on:
> > > www.soundsonline.com.
> > >
> > > Are you doing anything commercially?
> >
> > Not so, but we are currently seeking commercial projects involving CLAM=
. Here
> > comercial does not mean non-free but we also are able to drop non
> > relicenceable dependencies if non-free is a requirement.
> >
> > Good luck with the release.
> >
> > --
> > David Garc=EDa Garz=F3n
> > (Work) dgarcia at iua dot upf anotherdot es
> > (Home) vokimon at telefonica adot net
> > http://www.iua.upf.edu/~dgarcia
> >
> >
>
>
> --
> Patrick Kidd Stinson
> http://www.patrickkidd.com/
> http://pkaudio.sourceforge.net/
> http://pksampler.sourceforge.net/
>


--=20
Patrick Kidd Stinson
http://www.patrickkidd.com/
http://pkaudio.sourceforge.net/
http://pksampler.sourceforge.net/

Re: [pksampler-devel] CLAM and PK widgets

[David <dg...@iu...>]

Any enhancement would be really very wellcome, Patrick.

I am starting to adapt also widgets from Rui Nuno Capella and Pedro Lopez=20
Cabanillas (QSynth/Qtractor/QJackCtl...), and Chris Cannam=20
(SonicVisualizer,Rosegarden...). Let's make Linux interfaces cool ;-)

David.


On Dimecres 18 Abril 2007, Patrick Stinson wrote:
> I just had a look at some of the screenshots. Good greif! I thouht I
> recognized those widgets...I wish I had some time to play with it and
> make it better...
>
> On 4/12/07, Patrick Stinson <pat...@gm...> wrote:
> > On 4/12/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> > > On Dijous 12 Abril 2007, Patrick Stinson wrote:
> > > > > I did some experiments by changing parameters such as colors and
> > > > > size of buttons, and works pretty well. :-) I need to know how to
> > > > > crop them but i am on the track.
> > > >
> > > > Right. I wrote a tool to do that a while ago, but it isn't in my
> > > > repository anymore because I took a different direction with the
> > > > widgets I have now. I could write it again in a day or less if I
> > > > wasn't so busy... We release early june (hopefully) and this stuff
> > > > would be fun to get back into then (no promises!)
> > >
> > > Nice to know. If i need it before i think i could do it myself.
> > >
> > > > > What i miss is some way of making the background transparent.
> > > > > Adding pkwidgets to an interface forces you to use the widget
> > > > > background for all the interface to avoid awkward aspect. By havi=
ng
> > > > > an alpha background we could remove this limitation. I spotted
> > > > > several interesting links: http://www.imagico.de/pov/icons.html
> > > > > http://www.econym.demon.co.uk/shadowtut/index.htm
> > > >
> > > > This was one of two major problems I never tackled.. I thought about
> > > > using some sort of mask, but I'm not sure. The purest way would be =
to
> > > > get povray to do it, but I haven't looked into it. If it isn't
> > > > immediately possible using the povray docs, then a post to the povr=
ay
> > > > mailing list and/or community forums would probably be worth it. If
> > > > not, creating some sort of mask might be the way to go, but that
> > > > would be difficult with the shadow.
> > >
> > > Have you checked the links? Ok, you are in release ;-) i can just
> > > describe them, they explain how to do icons with alpha by doing 2 or 3
> > > povray runs with different parameters. By doing that we could get some
> > > alpha shadowed backgrounds. I promise to get on that, well, if you
> > > don't before ;-)
> >
> > you probably will before me
> >
> > > > > > Keep me informed how your work goes. I'm glad to hear my code
> > > > > > helped.
> > > > >
> > > > > At the moment i'll use the existing widgets and pixmaps and i'll
> > > > > extend both as i need more. Our packaging must not to be changed
> > > > > for that. Eventually i would like to integrate things further and
> > > > > porting other widgets. So let's talk then. I'll keep you informed.
> > > > > Warn me also when your release is over and lets chat a little.
> > > >
> > > > I may not remember (we are REALLY busy), so drop me another line if=
 I
> > > > don't get back to you. This is what we are working on:
> > > > www.soundsonline.com.
> > > >
> > > > Are you doing anything commercially?
> > >
> > > Not so, but we are currently seeking commercial projects involving
> > > CLAM. Here comercial does not mean non-free but we also are able to
> > > drop non relicenceable dependencies if non-free is a requirement.
> > >
> > > Good luck with the release.
> > >
> > > --
> > > David Garc=EDa Garz=F3n
> > > (Work) dgarcia at iua dot upf anotherdot es
> > > (Home) vokimon at telefonica adot net
> > > http://www.iua.upf.edu/~dgarcia
> >
> > --
> > Patrick Kidd Stinson
> > http://www.patrickkidd.com/
> > http://pkaudio.sourceforge.net/
> > http://pksampler.sourceforge.net/



=2D-=20
David Garc=EDa Garz=F3n
(Work) dgarcia at iua dot upf anotherdot es
(Home) vokimon at telefonica adot net
http://www.iua.upf.edu/~dgarcia

Re: [pksampler-devel] CLAM and PK widgets

[Patrick S. <pat...@gm...>]

Sounds cool. I had a look at the links about creating good transparent
povray widgets. It would take a little getting used to, but the
workflow could be automated and integrated into the python-based
solution that I already started with the pk.povray package, and
respective rendering tools in repos/resources. We are using
alpha-blended widgets with Play, and they are great to work with.

There are some things that need to be cleaned up with the widgets
along the lines of cleaner implementation. I have a few different
implementations for the knob that rely on modifier keys and make it a
little easier to get course and fine adjustments. The pixmap frames
for the pk.widgets.povwidgets should be all in one file instead of
separated out like they are in the implementation that you got from
me. This provides for resource and memory footprint.

Also, the next thing I'd like to do is have a look at using python in
common audio plugin hosts. This will mostly involve project templates,
but that would kill two birds with one stone: using Qt with VST, and
AU, and using PyQt with them as well.

fun stuff, and all in good time...

On 4/18/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
>
> Any enhancement would be really very wellcome, Patrick.
>
> I am starting to adapt also widgets from Rui Nuno Capella and Pedro Lopez
> Cabanillas (QSynth/Qtractor/QJackCtl...), and Chris Cannam
> (SonicVisualizer,Rosegarden...). Let's make Linux interfaces cool ;-)
>
> David.
>
>
> On Dimecres 18 Abril 2007, Patrick Stinson wrote:
> > I just had a look at some of the screenshots. Good greif! I thouht I
> > recognized those widgets...I wish I had some time to play with it and
> > make it better...
> >
> > On 4/12/07, Patrick Stinson <pat...@gm...> wrote:
> > > On 4/12/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> > > > On Dijous 12 Abril 2007, Patrick Stinson wrote:
> > > > > > I did some experiments by changing parameters such as colors an=
d
> > > > > > size of buttons, and works pretty well. :-) I need to know how =
to
> > > > > > crop them but i am on the track.
> > > > >
> > > > > Right. I wrote a tool to do that a while ago, but it isn't in my
> > > > > repository anymore because I took a different direction with the
> > > > > widgets I have now. I could write it again in a day or less if I
> > > > > wasn't so busy... We release early june (hopefully) and this stuf=
f
> > > > > would be fun to get back into then (no promises!)
> > > >
> > > > Nice to know. If i need it before i think i could do it myself.
> > > >
> > > > > > What i miss is some way of making the background transparent.
> > > > > > Adding pkwidgets to an interface forces you to use the widget
> > > > > > background for all the interface to avoid awkward aspect. By ha=
ving
> > > > > > an alpha background we could remove this limitation. I spotted
> > > > > > several interesting links: http://www.imagico.de/pov/icons.html
> > > > > > http://www.econym.demon.co.uk/shadowtut/index.htm
> > > > >
> > > > > This was one of two major problems I never tackled.. I thought ab=
out
> > > > > using some sort of mask, but I'm not sure. The purest way would b=
e to
> > > > > get povray to do it, but I haven't looked into it. If it isn't
> > > > > immediately possible using the povray docs, then a post to the po=
vray
> > > > > mailing list and/or community forums would probably be worth it. =
If
> > > > > not, creating some sort of mask might be the way to go, but that
> > > > > would be difficult with the shadow.
> > > >
> > > > Have you checked the links? Ok, you are in release ;-) i can just
> > > > describe them, they explain how to do icons with alpha by doing 2 o=
r 3
> > > > povray runs with different parameters. By doing that we could get s=
ome
> > > > alpha shadowed backgrounds. I promise to get on that, well, if you
> > > > don't before ;-)
> > >
> > > you probably will before me
> > >
> > > > > > > Keep me informed how your work goes. I'm glad to hear my code
> > > > > > > helped.
> > > > > >
> > > > > > At the moment i'll use the existing widgets and pixmaps and i'l=
l
> > > > > > extend both as i need more. Our packaging must not to be change=
d
> > > > > > for that. Eventually i would like to integrate things further a=
nd
> > > > > > porting other widgets. So let's talk then. I'll keep you inform=
ed.
> > > > > > Warn me also when your release is over and lets chat a little.
> > > > >
> > > > > I may not remember (we are REALLY busy), so drop me another line =
if I
> > > > > don't get back to you. This is what we are working on:
> > > > > www.soundsonline.com.
> > > > >
> > > > > Are you doing anything commercially?
> > > >
> > > > Not so, but we are currently seeking commercial projects involving
> > > > CLAM. Here comercial does not mean non-free but we also are able to
> > > > drop non relicenceable dependencies if non-free is a requirement.
> > > >
> > > > Good luck with the release.
> > > >
> > > > --
> > > > David Garc=EDa Garz=F3n
> > > > (Work) dgarcia at iua dot upf anotherdot es
> > > > (Home) vokimon at telefonica adot net
> > > > http://www.iua.upf.edu/~dgarcia
> > >
> > > --
> > > Patrick Kidd Stinson
> > > http://www.patrickkidd.com/
> > > http://pkaudio.sourceforge.net/
> > > http://pksampler.sourceforge.net/
>
>
>
> --
> David Garc=EDa Garz=F3n
> (Work) dgarcia at iua dot upf anotherdot es
> (Home) vokimon at telefonica adot net
> http://www.iua.upf.edu/~dgarcia
>
>


--=20
Patrick Kidd Stinson
http://www.patrickkidd.com/
http://pkaudio.sourceforge.net/
http://pksampler.sourceforge.net/

Re: [pksampler-devel] CLAM and PK widgets

[David <dg...@iu...>]

On Dimecres 18 Abril 2007, Patrick Stinson wrote:
> Sounds cool. I had a look at the links about creating good transparent
> povray widgets. It would take a little getting used to, but the
> workflow could be automated and integrated into the python-based
> solution that I already started with the pk.povray package, and
> respective rendering tools in repos/resources. We are using
> alpha-blended widgets with Play, and they are great to work with.

Great news. So you finished the release, didn't you? ;-)

I am just casting transparent shadows on QSynth knobs. It was easier to do=
=20
than with povray. Of course the effect is not the same but it is cool. Chec=
k=20
the last screenshots.
http://iua-share.upf.edu/wikis/clam/images/5/58/Qsynth-knobs-shadows2.png
http://iua-share.upf.edu/wikis/clam/images/4/43/Qsynth-knobs-shadows1.png

Not 3D but almost ;-)

> There are some things that need to be cleaned up with the widgets
> along the lines of cleaner implementation. I have a few different
> implementations for the knob that rely on modifier keys and make it a
> little easier to get course and fine adjustments. The pixmap frames
> for the pk.widgets.povwidgets should be all in one file instead of
> separated out like they are in the implementation that you got from
> me. This provides for resource and memory footprint.

Modifier keys are really a good idea.

> Also, the next thing I'd like to do is have a look at using python in
> common audio plugin hosts. This will mostly involve project templates,
> but that would kill two birds with one stone: using Qt with VST, and
> AU, and using PyQt with them as well.

Did i tell you we are also very much interested in mixing Qt and VST. Sure,=
 i=20
did. We want to extend the prototyper idea to VST plugins. We have the=20
processing part solved but we lack a way of running the Qt interface. Drop =
us=20
a line as soon as you start addressing such problem.

> fun stuff, and all in good time...

Definitely. :-)


> On 4/18/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> > Any enhancement would be really very wellcome, Patrick.
> >
> > I am starting to adapt also widgets from Rui Nuno Capella and Pedro Lop=
ez
> > Cabanillas (QSynth/Qtractor/QJackCtl...), and Chris Cannam
> > (SonicVisualizer,Rosegarden...). Let's make Linux interfaces cool ;-)
> >
> > David.
> >
> > On Dimecres 18 Abril 2007, Patrick Stinson wrote:
> > > I just had a look at some of the screenshots. Good greif! I thouht I
> > > recognized those widgets...I wish I had some time to play with it and
> > > make it better...
> > >
> > > On 4/12/07, Patrick Stinson <pat...@gm...> wrote:
> > > > On 4/12/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> > > > > On Dijous 12 Abril 2007, Patrick Stinson wrote:
> > > > > > > I did some experiments by changing parameters such as colors
> > > > > > > and size of buttons, and works pretty well. :-) I need to know
> > > > > > > how to crop them but i am on the track.
> > > > > >
> > > > > > Right. I wrote a tool to do that a while ago, but it isn't in my
> > > > > > repository anymore because I took a different direction with the
> > > > > > widgets I have now. I could write it again in a day or less if I
> > > > > > wasn't so busy... We release early june (hopefully) and this
> > > > > > stuff would be fun to get back into then (no promises!)
> > > > >
> > > > > Nice to know. If i need it before i think i could do it myself.
> > > > >
> > > > > > > What i miss is some way of making the background transparent.
> > > > > > > Adding pkwidgets to an interface forces you to use the widget
> > > > > > > background for all the interface to avoid awkward aspect. By
> > > > > > > having an alpha background we could remove this limitation. I
> > > > > > > spotted several interesting links:
> > > > > > > http://www.imagico.de/pov/icons.html
> > > > > > > http://www.econym.demon.co.uk/shadowtut/index.htm
> > > > > >
> > > > > > This was one of two major problems I never tackled.. I thought
> > > > > > about using some sort of mask, but I'm not sure. The purest way
> > > > > > would be to get povray to do it, but I haven't looked into it. =
If
> > > > > > it isn't immediately possible using the povray docs, then a post
> > > > > > to the povray mailing list and/or community forums would probab=
ly
> > > > > > be worth it. If not, creating some sort of mask might be the way
> > > > > > to go, but that would be difficult with the shadow.
> > > > >
> > > > > Have you checked the links? Ok, you are in release ;-) i can just
> > > > > describe them, they explain how to do icons with alpha by doing 2
> > > > > or 3 povray runs with different parameters. By doing that we could
> > > > > get some alpha shadowed backgrounds. I promise to get on that,
> > > > > well, if you don't before ;-)
> > > >
> > > > you probably will before me
> > > >
> > > > > > > > Keep me informed how your work goes. I'm glad to hear my co=
de
> > > > > > > > helped.
> > > > > > >
> > > > > > > At the moment i'll use the existing widgets and pixmaps and
> > > > > > > i'll extend both as i need more. Our packaging must not to be
> > > > > > > changed for that. Eventually i would like to integrate things
> > > > > > > further and porting other widgets. So let's talk then. I'll
> > > > > > > keep you informed. Warn me also when your release is over and
> > > > > > > lets chat a little.
> > > > > >
> > > > > > I may not remember (we are REALLY busy), so drop me another line
> > > > > > if I don't get back to you. This is what we are working on:
> > > > > > www.soundsonline.com.
> > > > > >
> > > > > > Are you doing anything commercially?
> > > > >
> > > > > Not so, but we are currently seeking commercial projects involving
> > > > > CLAM. Here comercial does not mean non-free but we also are able =
to
> > > > > drop non relicenceable dependencies if non-free is a requirement.
> > > > >
> > > > > Good luck with the release.
> > > > >
> > > > > --
> > > > > David Garc=EDa Garz=F3n
> > > > > (Work) dgarcia at iua dot upf anotherdot es
> > > > > (Home) vokimon at telefonica adot net
> > > > > http://www.iua.upf.edu/~dgarcia
> > > >
> > > > --
> > > > Patrick Kidd Stinson
> > > > http://www.patrickkidd.com/
> > > > http://pkaudio.sourceforge.net/
> > > > http://pksampler.sourceforge.net/
> >
> > --
> > David Garc=EDa Garz=F3n
> > (Work) dgarcia at iua dot upf anotherdot es
> > (Home) vokimon at telefonica adot net
> > http://www.iua.upf.edu/~dgarcia



=2D-=20
David Garc=EDa Garz=F3n
(Work) dgarcia at iua dot upf anotherdot es
(Home) vokimon at telefonica adot net
http://www.iua.upf.edu/~dgarcia

Re: [pksampler-devel] CLAM and PK widgets

[Patrick S. <pat...@gm...>]

On 4/18/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> On Dimecres 18 Abril 2007, Patrick Stinson wrote:
> > Sounds cool. I had a look at the links about creating good transparent
> > povray widgets. It would take a little getting used to, but the
> > workflow could be automated and integrated into the python-based
> > solution that I already started with the pk.povray package, and
> > respective rendering tools in repos/resources. We are using
> > alpha-blended widgets with Play, and they are great to work with.
>
> Great news. So you finished the release, didn't you? ;-)

We've got another month of PLANNED work. who knows when we get to
chill out a little.

>
> I am just casting transparent shadows on QSynth knobs. It was easier to d=
o
> than with povray. Of course the effect is not the same but it is cool. Ch=
eck
> the last screenshots.
> http://iua-share.upf.edu/wikis/clam/images/5/58/Qsynth-knobs-shadows2.png
> http://iua-share.upf.edu/wikis/clam/images/4/43/Qsynth-knobs-shadows1.png
>
> Not 3D but almost ;-)

Cool. Once you get some interface stability it would be nice to work
towards some continuity as well. Developing the semi-transparent
widget method would help a lot, so you could get rid of the old 136,
136, 136 that all my stuff uses. My Allen and Heath xone:3D mixer uses
black plastic with white indicators for all of it's controls - jog
wheels, faders, knobs, buttons, etc. Obviously this only makes sense
if you are building a toolkit or one app, but it appears that that is
what you are trying to do.

>
> > There are some things that need to be cleaned up with the widgets
> > along the lines of cleaner implementation. I have a few different
> > implementations for the knob that rely on modifier keys and make it a
> > little easier to get course and fine adjustments. The pixmap frames
> > for the pk.widgets.povwidgets should be all in one file instead of
> > separated out like they are in the implementation that you got from
> > me. This provides for resource and memory footprint.
>
> Modifier keys are really a good idea.
>
> > Also, the next thing I'd like to do is have a look at using python in
> > common audio plugin hosts. This will mostly involve project templates,
> > but that would kill two birds with one stone: using Qt with VST, and
> > AU, and using PyQt with them as well.
>
> Did i tell you we are also very much interested in mixing Qt and VST. Sur=
e, i
> did. We want to extend the prototyper idea to VST plugins. We have the
> processing part solved but we lack a way of running the Qt interface. Dro=
p us
> a line as soon as you start addressing such problem.
>

Actually, as far as I know all you have to do is create a
QApplication, then use QWidget *QWidget::create(WId) to create the
window. There is no event translation required. Be prepared for
inconsistent behavior between window systems, though. That's what I'm
working on at the moment.

> > fun stuff, and all in good time...
>
> Definitely. :-)
>
>
> > On 4/18/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> > > Any enhancement would be really very wellcome, Patrick.
> > >
> > > I am starting to adapt also widgets from Rui Nuno Capella and Pedro L=
opez
> > > Cabanillas (QSynth/Qtractor/QJackCtl...), and Chris Cannam
> > > (SonicVisualizer,Rosegarden...). Let's make Linux interfaces cool ;-)
> > >
> > > David.
> > >
> > > On Dimecres 18 Abril 2007, Patrick Stinson wrote:
> > > > I just had a look at some of the screenshots. Good greif! I thouht =
I
> > > > recognized those widgets...I wish I had some time to play with it a=
nd
> > > > make it better...
> > > >
> > > > On 4/12/07, Patrick Stinson <pat...@gm...> wrote:
> > > > > On 4/12/07, David Garc=EDa Garz=F3n <dg...@iu...> wrote:
> > > > > > On Dijous 12 Abril 2007, Patrick Stinson wrote:
> > > > > > > > I did some experiments by changing parameters such as color=
s
> > > > > > > > and size of buttons, and works pretty well. :-) I need to k=
now
> > > > > > > > how to crop them but i am on the track.
> > > > > > >
> > > > > > > Right. I wrote a tool to do that a while ago, but it isn't in=
 my
> > > > > > > repository anymore because I took a different direction with =
the
> > > > > > > widgets I have now. I could write it again in a day or less i=
f I
> > > > > > > wasn't so busy... We release early june (hopefully) and this
> > > > > > > stuff would be fun to get back into then (no promises!)
> > > > > >
> > > > > > Nice to know. If i need it before i think i could do it myself.
> > > > > >
> > > > > > > > What i miss is some way of making the background transparen=
t.
> > > > > > > > Adding pkwidgets to an interface forces you to use the widg=
et
> > > > > > > > background for all the interface to avoid awkward aspect. B=
y
> > > > > > > > having an alpha background we could remove this limitation.=
 I
> > > > > > > > spotted several interesting links:
> > > > > > > > http://www.imagico.de/pov/icons.html
> > > > > > > > http://www.econym.demon.co.uk/shadowtut/index.htm
> > > > > > >
> > > > > > > This was one of two major problems I never tackled.. I though=
t
> > > > > > > about using some sort of mask, but I'm not sure. The purest w=
ay
> > > > > > > would be to get povray to do it, but I haven't looked into it=
. If
> > > > > > > it isn't immediately possible using the povray docs, then a p=
ost
> > > > > > > to the povray mailing list and/or community forums would prob=
ably
> > > > > > > be worth it. If not, creating some sort of mask might be the =
way
> > > > > > > to go, but that would be difficult with the shadow.
> > > > > >
> > > > > > Have you checked the links? Ok, you are in release ;-) i can ju=
st
> > > > > > describe them, they explain how to do icons with alpha by doing=
 2
> > > > > > or 3 povray runs with different parameters. By doing that we co=
uld
> > > > > > get some alpha shadowed backgrounds. I promise to get on that,
> > > > > > well, if you don't before ;-)
> > > > >
> > > > > you probably will before me
> > > > >
> > > > > > > > > Keep me informed how your work goes. I'm glad to hear my =
code
> > > > > > > > > helped.
> > > > > > > >
> > > > > > > > At the moment i'll use the existing widgets and pixmaps and
> > > > > > > > i'll extend both as i need more. Our packaging must not to =
be
> > > > > > > > changed for that. Eventually i would like to integrate thin=
gs
> > > > > > > > further and porting other widgets. So let's talk then. I'll
> > > > > > > > keep you informed. Warn me also when your release is over a=
nd
> > > > > > > > lets chat a little.
> > > > > > >
> > > > > > > I may not remember (we are REALLY busy), so drop me another l=
ine
> > > > > > > if I don't get back to you. This is what we are working on:
> > > > > > > www.soundsonline.com.
> > > > > > >
> > > > > > > Are you doing anything commercially?
> > > > > >
> > > > > > Not so, but we are currently seeking commercial projects involv=
ing
> > > > > > CLAM. Here comercial does not mean non-free but we also are abl=
e to
> > > > > > drop non relicenceable dependencies if non-free is a requiremen=
t.
> > > > > >
> > > > > > Good luck with the release.
> > > > > >
> > > > > > --
> > > > > > David Garc=EDa Garz=F3n
> > > > > > (Work) dgarcia at iua dot upf anotherdot es
> > > > > > (Home) vokimon at telefonica adot net
> > > > > > http://www.iua.upf.edu/~dgarcia
> > > > >
> > > > > --
> > > > > Patrick Kidd Stinson
> > > > > http://www.patrickkidd.com/
> > > > > http://pkaudio.sourceforge.net/
> > > > > http://pksampler.sourceforge.net/
> > >
> > > --
> > > David Garc=EDa Garz=F3n
> > > (Work) dgarcia at iua dot upf anotherdot es
> > > (Home) vokimon at telefonica adot net
> > > http://www.iua.upf.edu/~dgarcia
>
>
>
> --
> David Garc=EDa Garz=F3n
> (Work) dgarcia at iua dot upf anotherdot es
> (Home) vokimon at telefonica adot net
> http://www.iua.upf.edu/~dgarcia
>
>


--=20
Patrick Kidd Stinson
http://www.patrickkidd.com/
http://pkaudio.sourceforge.net/
http://pksampler.sourceforge.net/