Note that there are some explanatory texts on larger screens.

plurals
  1. POClient-side image processing
    primarykey
    data
    text
    <p>We're building a web-based application that requires heavy image processing. We'd like this processing load to be on the client as much as possible and we'd like to support as much platforms (even mobiles) as much as possible. </p> <p>Yeah, I know, <em>wishful thinking</em></p> <p>Here's the info:</p> <ol> <li><p>Image processing is rasterization from some data. Think like creating a PNG image from a PDF file.</p></li> <li><p>We don't have a lot of server power. So client-side processing is a bit of a must.</p></li> </ol> <p>So, we're considering:</p> <ol> <li><p>Flash - most widespread, but from what i read has lackluster development tools. (and no iPhone/iPad support for now). </p></li> <li><p>Silverlight - allows us to use .NET CLR, so a big ++ (a lot of code is in .NET). But is not supported for most mobiles ( rumored android support in the future)</p></li> <li><p>HTML5 + Javascript - probably the most "portable" option. The problem is having to rewrite all that image processing code in Javascript. </p></li> </ol> <p>Any thoughts or architectures that might help? Clarification: I don't need further ideas on what libraries are available for Silverlight and Javascript. My dilemma is</p> <ul> <li>choosing Silverlight means no support for most mobiles</li> <li>choosing Flash means we have to redevelop most of our code AND no iPhone/iPad support</li> <li>HTML5 + Javascript we have to redevelop most of our code and not fully supported yet in all browsers</li> <li>choosing two (Silverlight + Flash) will be too costly</li> </ul> <p>Any out-of-the-box or bright ideas / alternatives I might be missing?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload