Wednesday, January 28th, 2009

Timescope: to mobile and beyond

Category: GWT, Showcase

Ray Cromwell has the ability to do amazing things in the browser. We have often linked to his work on Chronoscope and more, and this time he has a screencast showing of Timescope “our charting engine, written in GWT, runnable as Servlet or Android native application, renders huge numbers of points at interactive rates, scriptable, annotatable like Google Maps, and stylable via CSS-like stylesheet mechanism.”

For those who know of Chronoscope, this is the commercial version, big changes include more accurate multiresolution filtering algorithm, Android native version, Chart Server, iPhone integration, synthetic datasets, a number of other things. We eventually hope to include a subset of complete implementation of R in GWT, to allow statistical work to be done totally in browser.

At the 7:20 mark, you can see GSS, which is an implementation of a CSS parsing and cascade engine in GWT, to support our totally custom set of properties, elements, and pseudo-classes.

Very cool indeed Ray.

Posted by Dion Almaer at 8:08 am

2.7 rating from 64 votes


Comments feed TrackBack URI

What happen´s withe Ajaxian layout in Google Chrome???
Please adjust this!

Comment by cicerofeijo — January 28, 2009

It’s a missing double quote in an anchor tag. I’m sure it will be fixed soon.

Comment by AdamBackstrom — January 28, 2009

Since when do we need to read Ajaxian with firebug to read all the content???

Comment by SchizoDuckie — January 28, 2009

Hey, look at me! I’m over in the right column! Woo hoo!

Comment by Nosredna — January 28, 2009

I think this should be reposted to get a clearer vote ranking.

Comment by zachleat — January 28, 2009

I this some sort of test? I sort of like the idea of a web development site forcing developers to use their tools to read it.

Comment by MichaelThompson — January 28, 2009

Yikes, a 1.6 rating! Either Ajaxians really don’t like GWT or canvas charting, or something is amiss.

Comment by cromwellian — January 28, 2009

@cromwellian – I think its because of the layout problem :) (which looks fine to me so it must be fixed)
As for me, I think its totally bad ass.

Comment by genericallyloud — January 28, 2009

Should link to the showcase — Let’s you play around with the same thing he is showing in the video –

Comment by JonathanLeech — January 28, 2009

@MichaelThompson – agreed. Replace the current, easy CAPTCHA with more difficult developer aimed puzzles, almost like a riddle.

Comment by tj111 — January 28, 2009

>>Yikes, a 1.6 rating! Either Ajaxians really don’t like GWT or canvas charting, or something is amiss.

Well, considering this morning the story stopped in the middle of the second sentence, I’m not surprised.

Comment by Nosredna — January 28, 2009

Still very buggy and easy to lock up.

Comment by unscriptable — January 28, 2009

Pretty impressive Cromwellian :)

Comment by ThomasHansen — January 28, 2009

What’s easy to lockup? The showcase? Are you using IE? The showcase wasn’t supposed to be live yet. It’s a debug build that loads up vast amounts of JS, so it wouldn’t surprise me if you got a slow script warning. I have to recompile it for production, as well as make the sample datasets (some very large JSON files with 20k points) load on demand instead of load everything in the HEAD.

I’ll post a notice on my blog when the showcase goes live.

Comment by cromwellian — January 28, 2009

You (probably) shouldn’t load the scripts in the HEAD of the document…
Check up the YSlow rules if you don’t believe me … ;)

Comment by ThomasHansen — January 28, 2009

Leave a comment

You must be logged in to post a comment.