Re: [Octal-dev] porting thoughts

[Luka Frelih]

> 1. Since GTK+ is working on windows and beos, OCTAL can be ported to
> both. (Someone already did a quickie port of an older version to Win32,
> but as there is no GUI or threading code yet anyway, this was probably
> deceptively easy.) 

Since BeOS has its own a/v "modular signal network" called Media Kit, i see 
three paths of "porting" octal to BeOS. 

first one would be a straigh port, replacing the audio output with
beos code and relying on GTK+ (which is underway, but not really
released afaik)

second one would be to turn the whole tracker into a Media Kit node, 
able to provide music to any app with just a few calls to the media
roster. (and an octal music file) 

third thing to try would be a wrapper for machines to turn each of them
into a "node" - this way you could use different sequencers and editors
with octal machines and make it possible to add just the machines neeeded
to your app without the whole tracker. the example of this idea is the
cortex app on beos, and i guess more development in this direction is
coming...

> 2. The GUI is rewritten for those other operating systems. This sounds
> like a big time-waster if there are ways to port instead, but if people
> who are expert in programming those GUI's can help out this would go
> much more quickly. 

the time spent on a native gui for an os might be worth the trouble it the
glue libraries are not available or if they perform poorly

what about text guis?

L