On 12/7/2006, "D. Michael 'Silvan' McIntyre"
<[EMAIL PROTECTED]> wrote:
>On Tuesday 11 July 2006 5:05 am, Jaakko Kyro wrote:
>
>> How about using a file paradigm for the instrument definition? Like a
>> "Load" button that would pop up a file dialog in the location where the
>> instrument definitions are in the filesystem?
>
>OK, more thoughts...
>
>I've decided against a Load button and a collection of files. A flute is a
>flute, no matter whether you're using ZynAddSubFX or Hydrogen to play the
>flute, so it really doesn't need to be tied up with the studio at all.
>
>These are just going to be preset suggestions that behave something like the
>new canned texts in the notation insert text dialog. Picking a text from the
>combo changes the text entry widget, but it's the text entry widget itself
>that actually provides the text that gets inserted, so you can change it by
>hand.
>
>
>With these, the Preset combo box will inject settings into all the widgets
>under it as you dial through the choices. If you change one of the settings,
>the preset combo will revert to None.
OK, sounds good.
>This way you can take care of your own needs if you write for something that
>isn't included, and if you really want your instrument included in our
>collection, we can certainly add it to the collection.
How about presenting a "Remember this" button that would allow
saving/modifying a preset? It would help aggregating the presets by
contribution. I think that the actual persistence mechamism will be
quite easy to do.
I agree that once the collection is done, it's probably going to be
quite static.
>As to the collection of presets, I'm probably going to hard code a few of them
>just to get things going, and then switch it over to a mechanism that works
>like note head styles in the notation editor. The combo gets populated from
>style files in a directory at runtime. End users can edit these files, but
>rarely have any occasion to do so, so there is no GUI, nor an end-user
>friendly file format provided.
>If I run through my dictionary of orchestration and add presets for anything
>that seems useful, I think we will have enough factory presets that people
>will rarely have any need to edit their own files.
>
>This whole thing is going to get implemented in stages over what is shaping up
>to look like a long, hard time. Presets are at the end of the road, after
>I've actually made all of these parameters *do* something. Then I'll put
>together collections of parameters for specific instruments, and then it will
>be cigar time.
>
>I doubt I'll make 1.3 with all of this. It's a lot of little things to get
>right along the way.
I'd be happy to help, my time is a bit limited though.
--
-jaakko
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
