I've just spent the last few hours nosing around to see what's new in this 1.5 pre-release. I decided to implement an app widget to try out the new package. From the provider end it's very straightforward, but I'm not certain about the performance implications.
Specifically, I decided to implement a clock (see http://www.tomgibara.com/android/babilo for a screenshot). In my implementation I render the clock image into a bitmap and have a very simple remote view that consists of a single image view to display it. This means that the bitmap must be marshalled on every update and the process must be in memory too of course. That's a lot of memory for a clock. Is there a better approach? Or is a non-digital clock ill suited as a widget? Also is there a way for the widget provider to know (receive a hint for) the size at which the widget will be rendered? This is useful in this instance since one doesn't want to make the bitmap any larger than necessary. A final question: is there a way for a provider to request that a wedget be 'oversized' (like the search bar or media control)? Answers to any of these questions would help me to get a better idea of what widgets might be effective. Tom. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
