I'd say it greatly depends on what functionality you plan to offer.
If it is just straight rendering of HTML content with perhaps some ability to capture certain events, then a gecko wrapper is fine.
If you are looking to extend and control the layout and do something more dynamic, then I'm not sure how gecko would fit in. In that case it depends on if you own the generation of the content. If you can guarantee XHTML + CSS (flying saucer) is easy and extendable. If you don't own the content and can't vouch for it, all bets are off and you better start looking for a paddle.
There have been many times where I've wanted to render uncontrolled HTML but then I think of the user experience. I generally now just popup a browser and point it at the content. The user has already chosen the weapon for viewing HTML, use it. |
java.net RSS Feeds
