« Return to Thread: building csound into Chrome OS
Re: Re: building csound into Chrome OS
by Brian Redfern-2
::
Rate this Message:
Android only allows java coding, they did have it open to native code
on sdk 1.0 but have since closed that down. Also its only for cell
phones, so its likely just too limited for something like csound. But
if Chrome OS allows for native linux code then it might be possible to
port over OLPC version of csound, or create a cut-down version minus
python for Chrome OS.
There's no reason why it couldn't be done. I don't think Google knows
about the importance of enabling content creation on netbooks. Without
it, its just a consumer device. This is why the OLPC is so great, its
not just a limited consumer device, its a full on creative platform on
super cheap hardware.
They should have python on Chrome OS. I think it will be a failure if
they make it a consumer only device. They should seriously be looking
at what the OLPC can do, its both a lightweight inexpensive device,
but also supports creative computing.
However OLPC is for kids. I'd love to have something like it that is
built for "grownups," maybe it can't run the Gimp, but maybe the Gimp
could be ported over over. I think it will fail to beat MS if they
don't look at how to support creative computing and not just create
some brain dead consumer device.
On Wed, Jul 8, 2009 at 1:02 PM, '2+<electriclightheads@...> wrote:
> hmm android, chrome-os, native-client...
> a custom python script written for csound might be good on anywhere but
> i wonder where csound should actually run on
> would olpc-like mean something like
> browser > native-client(python) > local-csound
> i thought chrome-os is about their cloud so
> browser > google-appsengine(python) > csound@google's-server
> or maybe that
> http://dream.cs.bath.ac.uk/netcsound/
> is always enough?
> i kinda think so but .. yes web-interactive with gui-funs can be somethang
> a competitent to twitter by google based on csound
> that will result into a frequently automatically episode-updated
> podcast of algo-comps
> something like a gui-communication2sound stream
> is what i'd expect
> oh skype-like direct sound in the track might turn the whole thang esperanto!
>
> btw what's android(local-java-apps) after all?
> anyway chrome-os definately sounds csound friendly than android .. and
> that's nice
>
> On Thu, Jul 9, 2009 at 2:15 AM, Brian Redfern<brianwredfern@...> wrote:
>> Google just announced the development of a Linux-based "Chrome OS,"
>> now if it were only going to be an in-house Google development it
>> wouldn't be so exciting. But they plan on having community development
>> as part of the process. It seems like a great opportunity to take the
>> same kind of approach to sound that you have on the OLPC, where csound
>> could be used as a standard audio/synthesis engine. I'm certain Google
>> hasn't thought of this, but because they plan to open the development
>> up to the whole Linux community it might be possible to carry over the
>> same kind of idea that was started in OLPC into an os for generalized
>> netbook use.
>>
>
> --
> SaRiGaMa's Oil Vending Orchestra
> is podcasting:
> http://sarigama.namaste.jp/podcast/rss.xml
> and supplying oil.py for free:
> http://oilpy.blogspot.com/
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>
Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"
on sdk 1.0 but have since closed that down. Also its only for cell
phones, so its likely just too limited for something like csound. But
if Chrome OS allows for native linux code then it might be possible to
port over OLPC version of csound, or create a cut-down version minus
python for Chrome OS.
There's no reason why it couldn't be done. I don't think Google knows
about the importance of enabling content creation on netbooks. Without
it, its just a consumer device. This is why the OLPC is so great, its
not just a limited consumer device, its a full on creative platform on
super cheap hardware.
They should have python on Chrome OS. I think it will be a failure if
they make it a consumer only device. They should seriously be looking
at what the OLPC can do, its both a lightweight inexpensive device,
but also supports creative computing.
However OLPC is for kids. I'd love to have something like it that is
built for "grownups," maybe it can't run the Gimp, but maybe the Gimp
could be ported over over. I think it will fail to beat MS if they
don't look at how to support creative computing and not just create
some brain dead consumer device.
On Wed, Jul 8, 2009 at 1:02 PM, '2+<electriclightheads@...> wrote:
> hmm android, chrome-os, native-client...
> a custom python script written for csound might be good on anywhere but
> i wonder where csound should actually run on
> would olpc-like mean something like
> browser > native-client(python) > local-csound
> i thought chrome-os is about their cloud so
> browser > google-appsengine(python) > csound@google's-server
> or maybe that
> http://dream.cs.bath.ac.uk/netcsound/
> is always enough?
> i kinda think so but .. yes web-interactive with gui-funs can be somethang
> a competitent to twitter by google based on csound
> that will result into a frequently automatically episode-updated
> podcast of algo-comps
> something like a gui-communication2sound stream
> is what i'd expect
> oh skype-like direct sound in the track might turn the whole thang esperanto!
>
> btw what's android(local-java-apps) after all?
> anyway chrome-os definately sounds csound friendly than android .. and
> that's nice
>
> On Thu, Jul 9, 2009 at 2:15 AM, Brian Redfern<brianwredfern@...> wrote:
>> Google just announced the development of a Linux-based "Chrome OS,"
>> now if it were only going to be an in-house Google development it
>> wouldn't be so exciting. But they plan on having community development
>> as part of the process. It seems like a great opportunity to take the
>> same kind of approach to sound that you have on the OLPC, where csound
>> could be used as a standard audio/synthesis engine. I'm certain Google
>> hasn't thought of this, but because they plan to open the development
>> up to the whole Linux community it might be possible to carry over the
>> same kind of idea that was started in OLPC into an os for generalized
>> netbook use.
>>
>
> --
> SaRiGaMa's Oil Vending Orchestra
> is podcasting:
> http://sarigama.namaste.jp/podcast/rss.xml
> and supplying oil.py for free:
> http://oilpy.blogspot.com/
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@... with body "unsubscribe csound"
>
Send bugs reports to this list.
To unsubscribe, send email sympa@... with body "unsubscribe csound"
« Return to Thread: building csound into Chrome OS
| Free embeddable forum powered by Nabble | Forum Help |
