optimizing iris browser for TP

[dishe]

Originally Posted by JBundy

Iris takes a lot of its transacting code from PIE's stack (this is verified for which I must say the source is anonymous ... I know I know you want names ... let the poo fly , but if you are CE-literate, break down the ROM in an SDK and take a look at the programming for both PIE and Iris). Anyways, with that said, we all know what a hog PIE is on current WM devices with lower hardware requirements than are requested you have by Torch Mobile for the Iris Browser. That said, Iris will be in direct competition with IE6 Mobile, so I consider it still a little ahead of its time for what current devices can quickly make happen for users. It is slow and uses a barrel of RAM with every use. It isn't finger-friendly, which Fennec is. Otherwise, it's on the right track

Huh?

Iris is webkit based for rendering, and has its own display routines along with a kinetic scrolling navigation system (that outperforms Opera in frame rates). The rendering engine and display methods are what define how a browser looks and acts to the end user, neither of which have ANYTHING to do with IE.

I'm not sure where you're getting your information from, but "break down the ROM in an SDK and take a look at the programming for both PIE and Iris" makes about as much sense as saying Opera is based on PIE. And yes, I'm CE literate.

The only thing perhaps based on IE is the network interface. And since that works fine, I'd expect the same of ANY web browser for WM.