I've seen this as a consistent issue with a lot of client side javascript eye candy.
If you can't print it, then its useless in a chunk of line of business applications. On Oct 31, 7:27 pm, Mark Derricutt <[email protected]> wrote: > One of the other interesting problems we've come up against is that we use > flot.js for client side charting, it's a pure javascript charting framework. > At some point awhile ago we were asked if we could also include our charts > on the PDFs we generate on the back end - in order to do that we'd probably > have to use some java charting tool which would then look different. > > Whilst this doen't really worry me - PDF/printable material isn't the > web/interactive - but others didn't like the idea of having totally > different looks for charts. > > -- > "Great artists are extremely selfish and arrogant things" — Steven Wilson, > Porcupine Tree > > > > > > > > On Sun, Oct 31, 2010 at 9:22 PM, Mark Derricutt <[email protected]> wrote: > > After a year or so of doing a RESTful application, with ext.js all on the > > front end I'm thinking one of the problems/issues I have with this model is > > that you tend to bleed A LOT of internal implementation details out to the > > client in order for it to do its work. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
