Re: [Linuxsampler-devel] status update for LinuxSampler -- GUI and native format

[Josh G. <jg...@us...>]

On Tue, 2003-03-25 at 03:41, Marek Peteraj wrote:
> On Tue, 2003-03-25 at 05:34, Josh Green wrote:
> > 
> > I myself can see many nice eye candy widgets being written for GTK or QT
> > and integrated with other apps. In this sense I don't see it as really
> > writing the GUI from scratch but more extending existing ones. 
> 
> But we really should derive from the look&feel of other pro samplers in
> this regard.
> 

Sure, why not. But from my perspective the GUI interface is secondary,
and one can have multiple looks & feels :)

> > Its nice to have things like menus, 
> > trees, lists, etc and not have to implement
> > them all by hand :) 
> 
> My guess is that in the main app window the lists and trees won't be
> needed at all.
> 

We're probably talking about different uses here. I'm talking about
Swami in particular which the current scope is as a patch editor. I find
things like trees, etc very useful when it comes to editing patches :) I
forsee the scope of Swami going more into the realm of what you are
talking about, which is a tool for doing real time instrument
manipulation. The current architecture, I believe, lends itself to many
uses. In the future I can see applications developed off of libswami
that won't resemble the Swami GUI at all. One example of this is a
Python driven instrument database for the web and possibly to manage
ones local library as well. libswami has plugin support, so extra
functionality could also be implemented via plugins.

> > I'm looking into using the GnomeCanvas widget for
> > all waveform displays (ardour uses the GTK+ version of this canvas) as
> > well as all envelope, LFO and other graph based GUI widgets. 
> 
> GnomeCanvas 2 was reported to be buggy, and smowhat deprecated now that
> people use a foo-canvas module which takes use of gtk2 built-in stuff.
> But Paul Davis is considering the port of gtk-canvas to gtk2 so maybe we
> could use, ulilise, help improving, bug-fixing, porting as well. :) 
> 

I'm not particularly attached to which canvas it is, they all have
relatively the same API (actually I'm not real familiar with foo-canvas'
API). I did have reservations about using libgnomecanvas2, but when I
was informed that it does not actually depend on gnome (by the guy who
ported the GTK1.2 canvas), I felt more comfortable using it. If
foo-canvas is robust enough (I heard it doesn't have anti aliasing
support, which seems nice for those who have the CPU/graphics cards to
do it) then I probably would use that. Any particulars on what kind of
bugs gnomecanvas has?

> 
> Marek
> 

Cheers.
	Josh Green