May be slashdotted, I'm having "forbidden" errors. Try later I guess.
This points something we've said for ages: the chief problem the
"agile" systems have is that the graphics is not built in .. which
often drives folks to Java (NetLogo, Processing). Javascript has
always had graphics, and is enjoying a huge resurgence due to its
being not only a "scripting language" but with graphics and UI
capabilities.
-- Owen
On May 9, 2008, at 12:20 PM, Stephen Guerin wrote:
>> From /. this morning:
>
> The Processing API is now partially implemented in Javascript by
> John Resig.
> wow. This could allow for some very speedy development times for web-
> based
> visualizations without loading the Java JVM, Flash or Shockwave in a
> browser.
> http://ejohn.org/blog/processingjs/
>
> This is very related to what Greg Malone is working on with his
> Javascript-based
> Game Engines...
>
> -S
>
> --- -. . ..-. .. ... .... - .-- --- ..-. .. ... ....
> [EMAIL PROTECTED]
> www.Redfish.com
> 624 Agua Fria Street, Santa Fe, NM 87501
> mobile: (505)577-5828
> office: Santa Fe, NM (505)995-0206 / London, UK +44 (0) 20 7993 4769
>
>
> ============================================================
> FRIAM Applied Complexity Group listserv
> Meets Fridays 9a-11:30 at cafe at St. John's College
> lectures, archives, unsubscribe, maps at http://www.friam.org
============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
lectures, archives, unsubscribe, maps at http://www.friam.org
