Greg P is My HERO!
New member
http://www.mobile-review.com/review/nokia-webbrowser-en.shtml
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
A Review of Nokia's WebKit 2.0 Browser
- Thread starter Greg P is My HERO!
- Start date
ghazaleh r
New member
Now the only question is when will this be usable on my E61?
So Blessed
New member
the e61 doesnt have series 60 3rd like the n80?
Get off the sinking ship!
New member
Does the N80 IE use this then? I'm guessing no.
hotchick123
New member
no it doesnt have the me or ie but its a s60v3
well you would think that nokia's software developers could just remove whatever features are not backwards compatible and still have a very respectable 2nd edition of the web browser. I would imagine 95% of the features could be compiled and made available for the s60v3 models with minimal developmental effort. someone please correct me if i am out of my mind.
well, I'm a software developer, and I program in the .net framework 2.0, and if someone wanted me to go from 2.0 back to 1.1, I would say hell no for a couple reasons.
the main reason would be that there are less methods to begin with. I know this isnt a perfect example, but hopefully you will see what I'm talking about.
in .net 2.0, when you develop an ASP.net page, you can use whats called master pages. basically you can make 1 layout, and tell every other asp.net page to copy that page in looks (use same background color, image, fonts, etc)
these dont exist in 1.1, so if I wanted to build the same ASP.net page, I would have to make every page the same by hand. imagine if the .net application is 100 pages!
what I mean is that sometimes there is internal features that just make it easier to program for, so going backwards would require jumping through all kinds of hoops that just doesnt make the software worht it, especially if it were free.
secondly it might be because of the software architecture. sometimes the newer operating systems or runtimes will be reworked internally with new versions, and things will run more efficiently. a good example would be trying to run a website from your home computer using IIS with Windows 2000. its good, but if you run it in Vista its supposed to be better, because vista has IIS built in as part of the operating system, not just as an installable add in like Windows 2000.
I hope I didnt lose you there
the main reason would be that there are less methods to begin with. I know this isnt a perfect example, but hopefully you will see what I'm talking about.
in .net 2.0, when you develop an ASP.net page, you can use whats called master pages. basically you can make 1 layout, and tell every other asp.net page to copy that page in looks (use same background color, image, fonts, etc)
these dont exist in 1.1, so if I wanted to build the same ASP.net page, I would have to make every page the same by hand. imagine if the .net application is 100 pages!
what I mean is that sometimes there is internal features that just make it easier to program for, so going backwards would require jumping through all kinds of hoops that just doesnt make the software worht it, especially if it were free.
secondly it might be because of the software architecture. sometimes the newer operating systems or runtimes will be reworked internally with new versions, and things will run more efficiently. a good example would be trying to run a website from your home computer using IIS with Windows 2000. its good, but if you run it in Vista its supposed to be better, because vista has IIS built in as part of the operating system, not just as an installable add in like Windows 2000.
I hope I didnt lose you there
Cocozzzzzzz
New member
great. i have no idea what you just said and you made me look bad