JBQ, Thank you for the answer! We will look into the code and keep your advices in mind. Potentially, we will have other questions in this thread.
Thanks, Zoneson On Fri, Dec 5, 2008 at 6:32 AM, Jean-Baptiste Queru <[EMAIL PROTECTED]> wrote: > > WebKit is probably the only really example for you to follow, so it's > the "best" example for lack of alternatives. > > That doesn't mean that the WebKit approach will work perfectly for > you, and you'll probably have to adapt it to whatever you're doing. > > It's worth mentioning that some of the difficulty in the WebKit > integration is the fact that WebKit is "slow" (from the point of view > that it can sometimes work for a few seconds at a time in a single > function call), and in order to deal with that all the WebKit-related > code is isolated into a separate thread in order to not clog the UI > thread. That in turns, causes problems with the fact that WebKit is > also not thread-safe. I can't predict whether your library will > require such an approach. > > JBQ > > On Thu, Dec 4, 2008 at 11:52 PM, zoneson <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > We are planning to port our own layout engine, written in C++, to > > Android. It will play the role similar to Webkit layout engine. We > > would like to know: > > > > 1. Are there any documents or guidelines to us since the applications > > will be written in Java? Is android.webkit.WebView class a good > > example to us? > > > > 2. For the different fonts and drawing, are they handled by the > > android.view.View if we follow android.webkit.WebView approach? Or we > > still need to handle them in C++ library code? > > > > Thanks, > > > > Zoneson > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
