Re: [jazzplusplus-devel] It's a night. Reduced trackwin's global variable dependence

[joakim v. <jo...@ve...>]

Patrick Earl wrote:

>>It has the disadvantage of having the project spread out into a
>>bunch of small files.  We can optimize for that, since midi files
>>are so small we can still load the whole project into memory, and
>>just clear out memory when something gets pushed to the history
>>queue.  There might be other ways to approach the problem of having
>>all these files strewn about a directory hierarchy, but I think the
>>advantages far outweigh the disadvantages and am fully prepared to
>>defend this idea.  :)
>>    
>>
>
>Okay, let's hash it out. :)  My opinion is that it's good if midi 
>tracks are self contained entities and there are multiple tracks 
>within a single song file.
>
>         Patrick
>

Just an idea:

You could store the entire projectfile in an archive file.

This is a well known and useful practice in the web world

For Yazz, it would have the added benefit that other tools could easily 
manipulate the
Yazz file data(like copying tracks from a project to another, XSLT 
transform them and so on)

Im all for a more transparent format(but lets get what we got working ok 
first)

Cheers,
/Joakim


>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IBM Linux Tutorials
>Free Linux tutorial presented by Daniel Robbins, President and CEO of
>GenToo technologies. Learn everything from fundamentals to system
>administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>_______________________________________________
>jazzplusplus-devel mailing list
>jaz...@li...
>https://lists.sourceforge.net/lists/listinfo/jazzplusplus-devel
>  
>