View Single Post
Old 10-16-2010, 01:16 AM   #6
Tiersten
Guru
Tiersten shines like a glazed doughnut.Tiersten shines like a glazed doughnut.Tiersten shines like a glazed doughnut.Tiersten shines like a glazed doughnut.Tiersten shines like a glazed doughnut.Tiersten shines like a glazed doughnut.Tiersten shines like a glazed doughnut.Tiersten shines like a glazed doughnut.Tiersten shines like a glazed doughnut.Tiersten shines like a glazed doughnut.Tiersten shines like a glazed doughnut.
 
Posts: 987
Karma: 8641
Join Date: Aug 2010
Device: Kindle 3G+WiFi
There isn't anything technically stopping Amazon from doing this apart from promoting it as a benefit of upgrading to a Kindle 3.

However for us to do it, it would require a lot of work as its not a simple switch. To even get it running you'd need a large amount of work to get all the necessary libraries like the WebKit core, font rendering system, fonts themselves and other support files working on the Kindle 2 whilst making sure nothing conflicts.

You'll also have to modify the Java based launcher that actually runs the Kindle UI to start the Kindle 3 browser instead and make it compatible with the Kindle store if you completely replace the old browser.

For Amazon to do this themselves would be significantly simpler since they can integrate it into the Kindle firmware with the benefits of having the source code to everything available. We only get partial source as the Amazon proprietory items are all closed source.

In short, it won't be simple. It'd require some major modifications to the Kindle 2 if we were to do it. The browser APIs and libraries are poorly documented for both the Kindle 2 and Kindle 3 so you'd have to do a lot of work and research yourself if you take on this project.

Last edited by Tiersten; 10-16-2010 at 01:18 AM.
Tiersten is offline   Reply With Quote