This is something I really can't understand. Why can't the android
engineers give us a way to create custom views for appwidgets? Diane
Hackborn argues not to abuse them and yet why does she care? After all
it's up to the user to decide if the impact on the experience is worth
it or not. If they do
On Thursday, August 25, 2011 6:41:33 PM UTC+1, Dianne Hackborn wrote:
But please please please -- don't abuse widgets by consuming lots of
> resources with them, this has a direct impact on the overall experience.
>
Yeah, I hear you, honestly I do.
It's a situation, though, where users complain
That said, you could probably get around this with a content provider. But
please please please -- don't abuse widgets by consuming lots of resources
with them, this has a direct impact on the overall experience.
On Thu, Aug 25, 2011 at 10:40 AM, Dianne Hackborn wrote:
> I am continually glad fo
I am continually glad for this limitation. Shoving over a MB of memory that
the launcher needs to keep in its process for a widget is not desirable.
Sorry.
On Thu, Aug 25, 2011 at 9:39 AM, Mark Murphy wrote:
> On Thu, Aug 25, 2011 at 11:11 AM, String
> wrote:
> > The funny thing is, that doesn
On Thu, Aug 25, 2011 at 11:11 AM, String wrote:
> The funny thing is, that doesn't actually help. The FAILED BINDER
> TRANSACTION seems to occur whenever you send too much data through IPC
> (where "too much" is on the order of 1MB), but it doesn't seem to matter if
> that 1MB is in a single trans
On Thursday, August 25, 2011 3:38:33 PM UTC+1, Mark Murphy (a Commons Guy)
wrote:
>
> > Anyway, what I was saying was that 360px square was as large as I could
> go
> > before running into the dreaded "!!! FAILED BINDER TRANSACTION !!!" bug.
> I'd
> > really hoped that would be fixed by now, but
On Thu, Aug 25, 2011 at 7:42 AM, String wrote:
> If your give the root of your appwidget's layout a width & height of
> match_parent, then it will expand to fill all available space that the OS
> gives it as the user resizes. Seems obvious in retrospect, but none of us
> mentioned it the first tim
Posted too soon, argh.
Anyway, what I was saying was that 360px square was as large as I could go
before running into the dreaded "!!! FAILED BINDER TRANSACTION !!!" bug. I'd
really hoped that would be fixed by now, but apparently not.
I'd also like to say that the resizable widget support coul
Now that I've come back to it after some time has passed, I've found a
partial solution to this issue, one that I'm surprised none of us thought of
before.
If your give the root of your appwidget's layout a width & height of
match_parent, then it will expand to fill all available space that the
Um, that was in my original
post?
https://groups.google.com/d/msg/android-developers/oAl2Ix9erSY/tGvvqqbf9soJ
--
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 unsu
HI String,
add the following red attribute
http://schemas.android.com/apk/res/android";
android:minWidth="294dip"
android:minHeight="220dip"
android:initialLayout="@layout/abc_layout"
android:updatePeriodMillis="8640"
*android:resizeMode="horizontal|vertical"*
/>
2011/6/24
This seems to be a design constrant, with the idea of keeping
AppWidgetProvider processes in memory as little as possible.
I can see this being useful for regular widget rendering, but loading the
process for the one current widget the user is interacting with doesn't seem
too bad.
Besides, this c
On Thursday, June 23, 2011 4:45:40 PM UTC+1, TreKing wrote:
>
> On Thu, Jun 23, 2011 at 3:44 AM, String wrote:
>
>> "1* Would be 5* if the widgets were expandable, rather than cluttering up
>> my widget picker with 8 different sizes."
>
>
> Can't you disable Widgets such that they don't show up i
Ahh yeah - forgot about our friend RemoteView :(
On Jun 24, 9:05 am, Mark Murphy wrote:
> On Thu, Jun 23, 2011 at 6:28 PM, Ed wrote:
> > Can you have a custom view inside the widget that is fill_parent and
> > do what you need to do in the onDraw?
>
> No. You cannot have custom Views in app widg
On Thu, Jun 23, 2011 at 6:28 PM, Ed wrote:
> Can you have a custom view inside the widget that is fill_parent and
> do what you need to do in the onDraw?
No. You cannot have custom Views in app widgets, period.
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
Can you have a custom view inside the widget that is fill_parent and
do what you need to do in the onDraw?
Not sure on how often onDraw would get called in a widget on a 3.1
homescreen but I imagine you'll want to be careful about the
efficiency of the code or at least run some benchmarks to see h
Tiles in a GridView might well work if you could solve the column count
problem, but d@mn, that'd be a big rewrite of my widgets. Possibly the best
option under the circumstances, though.
String
--
You received this message because you are subscribed to the Google
Groups "Android Developers"
On Thu, Jun 23, 2011 at 3:44 AM, String wrote:
> "1* Would be 5* if the widgets were expandable, rather than cluttering up
> my widget picker with 8 different sizes."
Can't you disable Widgets such that they don't show up in the Widget Picker?
---
On Thu, Jun 23, 2011 at 4:44 AM, String wrote:
> My widgets in question are all based around a single (if composited) image
> which does "intrinsically have an expandable amount of content." A
> reasonable analogy would be Honeycomb's Picture Frame widget: not
> list-based, but it could easily be
I was afraid of that.
My widgets in question are all based around a single (if composited) image
which does "intrinsically have an expandable amount of content." A
reasonable analogy would be Honeycomb's Picture Frame widget: not
list-based, but it could easily be expandable, it would just need
I suppose there might be a way to check the runtime size of your
widget and hide/show views based on the available space. I don't know
if that's possible.
On Jun 23, 9:19 am, Dianne Hackborn wrote:
> Yes this is for widgets whose layouts can resize. Specifically, it is for
> things like the new
Yes this is for widgets whose layouts can resize. Specifically, it is for
things like the new list app widgets and such that intrinsically have an
expandable amount of content.
On Wed, Jun 22, 2011 at 4:03 PM, Zsolt Vasvari wrote:
> While I don't know the answer. I think resizable widgets are
While I don't know the answer. I think resizable widgets are for
things like lists where you would use a weight="1" type of setup to
fill up all the space given to you.
So basically, you need to fit your entire layout into the smallest
possible size you gave in the desriptor and then size one or
23 matches
Mail list logo
