Yup. Just don't do it. You can parse HTML into a TextView using Html.fromHtml(String string) if you are loading data from HTML content, or use a RelativeLayout to layout a bunch of Text/ImageViews etc.
On Jul 23, 6:36 am, Kumar Bibek <coomar....@gmail.com> wrote: > WebViews are pretty heavy components. I don't see a situation where a > WebView cannot be replaced by a text view or a combination of other > compoenents. I still think this is a bad idea. I am sure, you wouldn't > be running scripts inside those web view items in your list, or do > you? > > Thanks and Regards, > Kumar Bibekhttp://tech-droid.blogspot.com > > On Jul 23, 8:59 am, Ken <ken0624...@gmail.com> wrote: > > > I've implemented a list with each item as a WebView. The WebViews are > > loaded in their own threads so the UI doesn't have to wait. > > > The problem I've ran into is after the list is loaded, some webview > > items disappears or repeat after the list is scrolled. I've read posts > > from Romain Guy and others about how this is a bad idea. Just > > wondering if it's still a bad idea or a solution has been found since > > Cupcake. > > > Thanks! > > > Ken -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
