[Stk] STK Repository structure

[Stephen Sinclair]

Hi Ariel,

I think this deserves a response, but I think the reason no one is
jumping at it is that it's not clear why a re-organization is
necessary.  That doesn't necessarily mean it's a bad idea, just that
it doesn't seem obvious to me.

For example, what is it about moving source files to different
directories that would make it easier for supporting iOS?

Steve


On Tue, Oct 8, 2013 at 2:04 AM, Ariel Elkin <arielelkin at gmail.com> wrote:
> Great to see the STK git repository is coming along!
>
> I think that something that would really improve the STK's support for iOS, AND make it easier to create ports for other platforms, is if we clearly separate the STK's audio classes from the STK's helper classes. Classes solely dedicated to audio purposes (e.g. Sitar, PRCRev, etc.) should be grouped in their directory. The STK's helper classes, such as those for networking (e.g. Socket, TcpClient) multithreading (e.g. Mutex), or audio layer setup (e.g. RtAudio), should be in separate directories.
>
> I thought about this directory structure:
>
> STK/Classes                     <-- All the audio classes, both .h and .cpp (e.g. Guitar, Mandolin, Twang)
> STK/Rawwaves            <-- All the raw waves
> Utilities/Networking    <-- All the networking classes
> Utilities/IO                    <-- All the file I/O classes (e.g. RtAudio)
> Utilities/Multithreading
> Demo/OSX
> Demo/Windows
> Demo/iOS
>
> Let me know if you have comments or suggestions!
>
> Ariel
>
> _______________________________________________
> Stk mailing list
> Stk at ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/stk
>
>