| My 2 cents:
Use Boa Constructor to make Python wxPython GUIs, as I demontrated at
NYCSUG...
Or use FLTK C++ code (not Csound orchestra code) to do the same thing (this
would be really tight, really professional).
In both cases you could use the channel or buss opcodes to bind the GUI to
Csound.
You can keep all your code in just one file. You talk about embedding Csound
FLTK code in your Csound orchestra, you can just as easily embed the Csound
orchestra and score code in your Python or C++ source code.
FLTK has a GUI builder named fluid (which I used to make CsoundVST's GUI).
If you go that route instead of coding the GUI by hand, you have 2 source
code files instead of 1. You can still compile and link everything with one
batch file, no need for a makefile.
My hunch is that this will be more robust, more cross-platform, and much
much more powerful than the FLTK opcodes, at some slight cost in learning
curve and design complexity -- but not much cost, for myself I find the
channel and buss opcodes easier to get my head around than the FLTK opcodes.
Regards,
Mike
----- Original Message -----
From: "Rory Walsh"
To:
Sent: Wednesday, October 24, 2007 8:19 PM
Subject: Re: [Csnd] FLmenu?
> MacCsound is available on Intel Mac's afaik but cross-platform GUI's are
> great so if you don't feel like learning python or another GUI toolkit go
> ahead with fltk. Iain McCurdy has posted a load of great fltk instruments
> at http://iainmccurdy.org, perhaps they can give you more ideas. All the
> best.
>
> Rory.
>
>
> Lou Cohen wrote:
>> Thanks for your replies, Oeyvind and Rory.
>>
>> Having been burnt on other (non-csound) projects, my goal is stay with
>> cross-platform tools as much as possible.
>>
>> So it would seem that fltk should be the way for me. Despite the lack of
>> menus, there are many strengths to the widgets, including the ability for
>> the user to modify sliders with arrow keys. And I like the idea of all
>> the code being in the orchestra, not spread across more than one IDE.
>>
>> BTW, I am working on OSX, so Lettuce does not appear to be an option. I
>> have been using MacCsound, but I’m contemplating upgrading to an intel
>> Mac. As far as I can tell, I won’t be able to use MacCsound on an intel
>> Mac, so it seems to be time to move the GUI implementation to a
>> platform-independent base.
>>
>> cheers!
>>
>> -Lou
>>
>>
>> On 10/24/07 18:19, "Oeyvind Brandtsegg " wrote:
>>
>> I agree to the suggestions about Python/GUI, using Lettuce, and about
>> using FLTK for a simple crossplatform csound-only setup.
>> I just wanted to mention that I discovered today that FLTK actually
>> has a menu widget and a choice box, they are just not implemented as
>> csound opcodes (yet).
>> Maybe Gabriel has done it in his csound version ?
>>
>> Oeyvind
>>
>> 2007/10/24, Rory Walsh :
>> > I'm not sure if this exists. From what I can tell fltk has not
>> really
>> > been updated in quite a while. A lot of people who required GUI's
>> these
>> > days seem to build them themselves using their preferred GUI
>> toolkit and
>> > then link to Csound using the API. More and more people seem to be
>> using
>> > Python for this as it is pretty easy to learn. In fact I would
>> imagine
>> > that after learning Csound Python should not prove difficult at
>> all.
>> > Finally, if you are working on windows Lettuce has a menu object
>> you can
>> > use. Lettuce GUI components are different than fltk opcodes as
>> they use
>> > the channel software bus to communicate with Csound. They're are
>> some
>> > simple examples of the menu item in the installation directory.
>> Note
>> > that to implement the menu you have to hard code it rather than
>> drop it
>> > onto a GUI frame. The latest unreleased version of lettuce is
>> available
>> > here: http://rorywalsh.ear.ie/Lettuce32Setup.exe The reason why
>> this
>> > version hasn't been publically released is that I don't have time
>> to
>> > support it!
>> >
>> > Rory.
>> >
>> > p.s. if you want cross-platform-ness use fltk!
>> >
>> >
>> >
>> >
>> >
>> >
>> > Lou Cohen wrote:
>> > > Hi, everyone,
>> > >
>> > > I'm considering implementing a new GUI for my csound
>> improvisation
>> > > orchestra.
>> > >
>> > > I'm impressed by the FLxxx series of opcodes and in my tentative
>> > > experiments they behave well. One GUI object that I would have
>> expected
>> > > to see, however, seems to be missing: a menu. What I mean is a
>> kind of
>> > > popup menu in which the current selection appears in somewhere
>> in the
>> > > body of a panel. The user clicks on it, and set of
>> text-identified
>> > > choices appears. When one of them is selected, the menu outputs
>> a value
>> > > that tells the csound orchestra which menu item was selected (or
>> is
>> > > currently selected.)
>> > >
>> > > I'm reading documentation for 5.04, and I'm wondering whether
>> the FL
>> > > opcodes might have been extended after this version.
>> > >
>> > > Or perhaps there's another way to implement such a menu?
>> > >
>> > > As always, thanks in advance for your help!
>> > >
>> > > -Lou Cohen
>> > >
>> > > ---------------------------
>> > > Permanent email: loucohen@jolc.net
>> > > Music and video: http://ruccas.org/wiki.pl/Lou_Cohen
>> > > More music and video: http://www.youtube.com/loucohen
>> > > Astronomy: http://www.jolc.net
>> > > ----------------------------
>> > >
>> > --
>> > Send bugs reports to this list.
>> > To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>> >
>>
>>
>>
>> ---------------------------
>> Permanent email: loucohen@jolc.net
>> Music and video: http://ruccas.org/wiki.pl/Lou_Cohen
>> More music and video: http://www.youtube.com/loucohen
>> Astronomy: http://www.jolc.net
>> ----------------------------
>>
> --
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk |