adamsp / wookmark Goto Github PK

Examples include slow loading of images when scrolling up (especially with lots of columns). Eventually the application runs out of memory - suspect that there may be something wrong with the algorithm for chopping views off the bottom, or the code may be "filling down" when scrolling up, even though it shouldn't. Suspect this because while scrolling back up, the app can be seen (by the loading bar) to be downloading a new set of images.

Should hide the results and bring back the color search window - especially as searches often produce no results

It's just a plain text list at the moment. Could do with some styling to make it nice to look at - icons maybe?

Should be able to lock the screen rotation when viewing an image, so the image doesn't rotate along with you when you twist the phone.

Annoying when you do a search and then you go to another view and the bar stays there. Should disappear after the search begins.

On the image view page if you have a really tall image, it doesn't zoom in far enough. Zoom limit should be something like 4x width of image when it fills the width of the screen. Also, these images aren't being "scaled" by the image loader are they? They often seem pixelated.

The built in auto-link feature should only link urls and not phone numbers etc, like it currently is - for the extra details on the image view.

Not an issue for me and my uses, could be an issue for someone else if they try to use it.

If you search for a color and then go back and search for another, it doesn't replace the existing items - rather adding on to the end (like we're scrolling).

The method names reflect an earlier iteration ("refresh" doesn't really make any sense, especially in context of how it's being used, etc). Needs a refactor to make more sense.

Broke that, somehow. Oops. The buttons aren't in their positions in the layout where they used to be.

Currently it's just a list of text items as a quick hack to make it display something. Needs to be properly styled, perhaps?

Only on first response - ie if you supply a negative value for a color search, the API returns an empty array - this crashes the app, it appears.

They made sense when I made them! Need a refactor now to better represent what they actually do.