That is actually kind if annoying and greatly limits the things we can
do with widgets. Are there any plans to change this or do I have to
kiss my xeyes port goodbye forever.
On Apr 21, 3:17 pm, Tom Gibara m...@tomgibara.com wrote:
It's an intentional limitation. Only views that are implemented
This is an unfortunate limitation indeed but given our constraints
this is the only way we could provide *secure* appwidgets in the
platform.
On Tue, May 5, 2009 at 9:21 PM, bra...@gmail.com peacoc...@gmail.com wrote:
That is actually kind if annoying and greatly limits the things we can
do
DOH. AndroidEyes I barely knew thee :)
On May 6, 12:25 am, Romain Guy romain...@google.com wrote:
This is an unfortunate limitation indeed but given our constraints
this is the only way we could provide *secure* appwidgets in the
platform.
On Tue, May 5, 2009 at 9:21 PM, bra...@gmail.com
Hi Tom
I have some questions about the RemoteViews functionality.
I want to know that it is possible to implement animation effect with
AppWidget using RemoteViews object.
On the Service routine, I've created RemoteViews object but I can't
find any method to relate animation.
I doubt some way
There's no way of applying an animation to the views within a remote view
because you're constrained to what you can declare in the layout XML and the
actions RemoteViews provides for. Neither of these provide for setting
animations.
AppWidgetHostView, RemoteViews's apply() , reapply()
These
Hi Tom
Thanks for your reply .
Is there any ways to apply animation effect to HomeScreen?
I doubted and tested it by using AppWidget API, but it's failed.
I can see some changes on RemoteViews' imageView.
On May 1, 3:26 am, Tom Gibara m...@tomgibara.com wrote:
There's no way of applying an
I'm excited about the app widget functionality, and I've been playing
with it for a bit. I love the idea that downloadable apps can
customize the home screen with arbitrary data.
Is it possible to create my own custom views and use them inside of an
app widget? For instance, if I wanted to
It's an intentional limitation. Only views that are implemented by the
framework can be used, and only those that are annotated as safe for
remoting.
I don't know if there is a list provided in the SDK docs, but as of 1.5 the
supported Views are:
AbsoluteLayout
AnalogClock
Button
Chronometer
Awesome, great to hear people are jumping into it. :)
For performance, the one thing to keep in mind is that each widget
update will spin up your process, which is somewhat expensive. (So
you probably want to avoid updating more often than once per hour to
help save battery.) Also, while
I tried setting various combinations of android:minWidth and
android:minHeight on the appwidget-provider element and on my ImageView, but
nothing seemed to have an effect...
...okay I've just worked out why - obvious in retrospect - the minimum
dimensions specified by the appwidget provider are
I just started taking a closer look at what would be needed to make a
well-functioning gadget and have an observation.
I'm assuming that the intention of the design is that I can grab a
AppWidgetManager instance for my application's context any time I want, so
that I can push an update to my
I'm assuming that the intention of the design is that I can grab a
AppWidgetManager instance for my application's context any time I want, so
that I can push an update to my gadgets.
Yep, exactly. If you already have a background service running for
other updates, that's a perfect time to
I'm assuming that the intention of the design is that I can grab a
AppWidgetManager instance for my application's context any time I want, so
that I can push an update to my gadgets.
Yep, exactly. If you already have a background service running for
other updates, that's a perfect time to
13 matches
Mail list logo
