Hi Mark.

Hello

hi all

We are given the task to implement a horizontally scrollable grid of images that shows 4 rows and 5 colums on the screen (the number of columns can of course be larger than 5, but at most 5 are visible at any time). When an item in this grid is clicked the grid should be zoomed in (animated over 1 second) to a 3x3 grid where the selected image is centered and the surrounding 8 images are partly visible (partly outside the screen). In this 3x3 grid the user should be able to move to any of the surrounding 8 images by clicking on the visible part (again with an animation). When the centered image is clicked it should zoom out to the 4x5 grid again. Could you give some general pointers how to accomplish such a thing? Custom layouts and ViewFlippers, drawing bitmaps directly on a canvas, OpenGL or something else?

sorry about the length of that question :)

I have a question about scrolling. I want to get a fast scroll for a ListView like on my Contacts app - this is the HTC Hero so I think it might be a different UI. I've seen a couple of threads, one of which you contributed to (http://stackoverflow.com/questions/1201962…), giving some pointers, but I wondered whether you had any further help?

mmmm, Red Bull, I like this discussion already =P

I see..

sure

We have done a few tests, the horizontally scrollable grid is implemented with a Gallery where each view is in fact a whole column of 4 images.

LinearLayout (vertical)

The zooming on the other hand is a different matter..

There is padding in that Gallery adaption, so it looks more or less like a grid.

Ok, with a ViewFlipper? (or any other ViewAnimator)

Hello to everyone

Ok, another problem then, about the 3x3 grid. With the default layouts it seems hard to get something to show partly outside the screen

AbsoluteLayout is not an option

in our spec it is :)

we have tried an OpenGL approach, this works, but we wanted to know if it could be done simpler

but now we know. Thanks for your help

well, I have several fairly long ListViews, coming from a CursorAdapter, say 300 rows, and I want the user to be able to go directly to, say, entries beginning with A, quickly. I don't mind how this is achieved particularly, but the fast scrolling approach where it comes up with each letter seems sensible

is that on his blog?

ok, I'll do that thanks - I've looked at the source of the Android Contacts app, but it's a little beyond my level. Thanks for the pointer

I do, just typing

got a few

So I had some questions about implementing my own ArrayAdapter. I'm attaching it to a Spinner widget and the item list is only 4 items long. it's part of a dynamically generated ScrollView so that as items get selected, more widgets appear. I'm trying to modify the adapter so that after an item has been selected, it can no longer be selected in subsequent clicks on that spinner. How would I achieve this?

And the two ArrayLists will be part of the Adapter or outside of the adapter?

Again, thanks for the help and bye

K, also, I'm assuming that the spinner dialog that pops up is similar in execution as the ListView in that if that list is big enough to go outside the screen, it'll start reusing view. How could I prevent that if i know that any lists I did generate were for the most part going to be only about a dozen items? This is for a expandable list view where the sublists will have very custom rows.

This is *also for an expandable list view, sorry

the spinner "dialog" is the list that pops up when the spinner is clicked

yah, it's mainly for the expandable list view cause the sub lists' rows will be generated from a simplified xml code that i came up with and stored in the database along side the row items, if that makes sense. a lot of rows will end up being the same but not necessarily depending on what results from the db query so I want to ensure that no old incorrect view gets reused when it shouldn't be

but onwards and upwards, as I mentioned before with the spinner, it's part of a ScrollView. how do I get it to scroll all the way down to the newly generated views after the spinner item is clicked? Right now it's just adding the views but they disapear off the screen and it's annoying to have to manually scroll right off the bat.

oh nice, so simple

ok, here's another issue i've been having. My second activity is basically a big image that's been chopped up into multiple sections to act like buttons. When the activity starts it takes about 2 - 2.5 seconds to load and does about 5-6 GCs right off the bat as it's loading. Any suggestions on how to reduce this?

would the fact that the image is actually way too big for the screen size matter? right now i'm scaling it as the resources for each section are loaded

they are PNGs, is bmp a better format to use then?

how would i go about doing that at compile time?

well, i think that only thing I'm doing with the images is scaling them really, then loading them. Would caching the images in a seperate thread started during my first activity be an idea?

ya, wasn't sure if that's what you had meant before

K, then I have one last questions: what's the best way to get a hold of a cheap developer phone? besides buying one new from a carrier that just wants to rip me off that is(i'm in Canada, they suck up here)

um, I don't know? it's mainly for testing purposes for my app and so that client can test it out in their work setting

OK, I have kind of a more beginner's/general question regarding JUnit and functional testing using instrumentation. I've read the chapter in Adv.Android + Diego torres blog, but I'd like to see a more complete example of a testing suite for an entire end user use case. Say, starting with logging-in into an end user account, performing a sequence of related actions and logging out. How does one implement the driving logic? Any pointers/hints, especially if using Eclipse with a separate test project?

k, that's the answer i was looking for. Thanks for all the help! I'll let you get to Svetlin's question

OK, so I am accessing a web service -- do you suggest testing it "per se" is the way to go?

No point in trying to tie it all up?

but separately test the GUI vs. the web service?

Can't I just use SuiteBuilder and order the instrumentation test cases however I think the user is likely to hit them?

I see. OK, thanks for the feedback, appreciated.

Have a good weekend!