Hi Chris,

All the message could be said that way: why trying to replace flash by html when html is worse. Ok to have degraded version for "non willing to be compatible" devices but imposing it for all user is counter productive. Also why converting a pdf version to a more verbose and less optimize markup language, that hangs computers and lacks fidelity, when all the flash conversions purpose is to be lighter faster and easier to integrate in custom interfaces... Bringing apple into this conversation is logical because they are the origin of these attempts to replace flash where it's still a lot better.

Best regards

Raph

Le 03/04/2011 09:30, Chris a écrit :
On Wed, 30 Mar 2011 11:05:34 +0300
Raphaël Benzazon<[email protected]>  wrote:
Hi,

I hope the dev is moving ahead nicely.
I think it is proceeding well.

I have to admit that the first and last scribd publication that I visited
was making my powerful desktop PC hang.
That could be caused by anything - user error? ;o)  But why bring scribd
into this?

It seems that the html is not the solution when it comes to reproduce or
convert publication for internet.
Sweeping statement. Not necessarily true either. Markup changes constantly.

It was so slow compared the the previous flash version, that was
painful to accept that scribd made such a bad technological choice.
Again, not sure what that statement has to do with SWFTools.

Maybe they listen too much the the pseudo prohet Jobs.
.. co-founder and CEO of consumer electronics company Apple Inc? ;o)
What has he to do with all this?

Regards,



Chris ( retiring - not surprisedly - somewhat confused )


Greetings

Raphaël

Le 09/05/2010 05:41, Matthias Kramm a écrit :
On Sat, May 08, 2010 at 12:44:57PM +0200, filip sound<[email protected]>   
wrote:
Matthias, i can't believe all this...
are you serious? you want the browser to render complex
graphics/shapes/gradients and texts (pdf) all in html?
Well, what Scribd currently does is text and bitmaps.
Vector shapes (gradients etc.) are in my queue, problem is that cross-browser
compatibilty of SVG, Canvas etc. is much worse than that of custom
fonts.

the performance will
not be anything near the performance you get when running it on a plugin
that has full access to the cpu.
Why? The browser has full access to the CPU, too, after all.
Also, Javascript engines have gotten ridiculously fast.

Matthias






--



Reply via email to