> For the record, charts4j is fully > active:http://code.google.com/p/charts4j/source/list
Ah, indeed it is! :) > BTW, you can still use charts4j as-is in the GWT, as long as you use > charts4j on "the server-side" -- behind the servlet. I hope that makes > sense. Right, that makes sense. At the end of the day a URL just need to be created, doesn't matter if it's server-side or client-side. > Also, I have been busy working on my weather site which uses the > Google Chart API and charts4j extensively:http://weathermole.com Looks good so far! Nice straightforward (and peppy!) implementation. > I have to go home now, but this topic probably merits further > discussion. > > Good luck with google-charts-for-gwt! Thanks! Yes, I'd be interested in discussing further. While I'm fully aware of the current limitations of my implementation (incomplete feature set, lack of documentation), I definitely favor being able to directly use it as a GWT project. While I can't go into too much detail, a project I've been working on requires that we have charts/graphs of data but in an environment where we can't rely on the server always being around or having a good connection, and we can't utilize Flash or other advanced technologies (so no Ext-GWT-based charts). So the client-side implementation allows me to download data once to the client and let the user render many views of charts without server interaction. That said, I appreciate the completeness of charts4j, certainly seems very complete from my perusing. As I've had a decent look at the Google Charts API and all the features available, I have to say that boasting a complete feature set it very impressive! I know you mentioned you don't have a lot of knowledge of GWT, but do you know offhand what the bits of code are prevent it from being able to run client-side? Is it just the collection types used? Google Charts for GWT does have a bit of code binding it to GWT, including a call to a native javascript function to do the encoding, but nothing that can't be pulled out and allow it to be used client or server side. Anyway, I'll probably pull down charts4j sometime this week and give it a test drive. Would definitely be interesting in seeing if/how this can be ported to be usable on the client in GWT -- from what I've been reading, the demand is really just for an OO-API which is what you have, but with a GWT-aware implementation. Also interesting in seeing how many steps there are to actually make a chart. I've been trying, with varying success, to have my implementation not require too much verbosity to get a result. Thanks for your time and assistance, Julien! -- Carl Scott Software Developer, Solertium Corporation --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Chart API" group. To post to this group, send email to google-chart-api@googlegroups.com To unsubscribe from this group, send email to google-chart-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-chart-api?hl=en -~----------~----~----~----~------~----~------~--~---
