Re: [Traverso-devel] Demo Projects

[plutek-infinity]

>Date: Mon, 9 Feb 2009 13:10:46 -0800
>From: ben levitt <address@hidden>
>
>Maybe a good compromise would be:
> - have a separate directory in cvs for the demo projects outside of
>the main traverso directory (so you wouldn't have to check them out if
>you didn't want them)
> - create separate release source tarballs for source and demos
> - create separate linux packages for traverso and traverso-demos
> - have a known location on each platform where the demos get
>installed, and where traverso looks for them
> - in traverso, we could check to see if the demos are installed, and
>if so, enable an otherwise grayed-out menu item for Open Demo
> - when saving a modified demo, we should probably save a copy of the
>demo project to the user's projects directory
> - maybe we could offer versions with and without the demos for the
>windows and mac releases?
> - the demo audio could be compressed, at least with wavpack, to reduce the 
> size
>
>This way, the demos would be versioned per release, not live updating
>and downloadable from within the app.  But it sounds like that's an
>okay trade-off to make.
>
>And I think we probably don't want to tie demo installation to the
>build system, since I imagine most users won't be building from
>source.
>
>What do you think?

these sound like reasonable suggestions to me.

>On Sun, Feb 8, 2009 at 2:59 AM, Ingmar Vanhassel <address@hidden> wrote:
>> On Sat, Feb 07, 2009 at 08:16:59PM -0500, plutek-infinity wrote:
>>>
>>> >From: Remon Sijrier <address@hidden>
>>>
>>> >It should be relatively easy to add a menu to Traverso which shows 
>>> >available
>>> >demo Project which can be downloaded by Traverso itself (Qt makes this very
>>> >easy)
>>> >
>>> >If you guys think this isn't a good idea, or have suggestions, please let 
>>> >me
>>> >know.
>>
>> Having demo projects available is definitely a good idea.
>>
>>> i think there *needs* to be an option to disable this, or to compile 
>>> without download support, for two reasons:
>>>
>>> 1. i would consider it "bloat" to be adding *any* network functionality to 
>>> DAW software -- any potential for performance penalties or security risks 
>>> due to something like this would be most unwelcome by those of us who 
>>> maintain lean, DAW-specific machines.
>>
>> Ditto, I'm not convinced that you want to have code for downloading
>> those in Traverso. Maybe it's nicer to have an extra tarball
>> traverso-$version-demo-projects.tar.gz that's unpacked over the sources
>> tarball. Then 'cmake -DWANT_DEMOS=TRUE' could install them?


-- 
.pltk.