Grid View: suggestions

[ChristianGruen]

I have fallen in love with the NTMB Grid View. I realize this all the more when I compare the app with BC.

I was wondering…

• if it would be difficult to provide support for the pinch zoom in/out gesture to resize the images? It may also be helpful in the list view (where I would expect it to be only applied to three images). It would be much faster than doing this in the corresponding style settings (something I regularly do, in particular when I use NTMB on different devices).
• As mentioned before, I would love if the three-dot icon could disappear (to provide more room for the image grid) and be replaced with a long-tap on the image. Even though you had indicated that long taps are not welcomed by everybody, I think it would be the most consistent choice, as it works like that in the list view.

If removing the the icon is no option, I may be recommendable to also include it in the list (e.g. top right) and remove the long tap. If the long-tap option wins (…which would certainly be my favorite), it would be great if it could also be added to the images in both modes.

Whatever you decide, I am already so grateful for your lightning fast replies and all your work on the app.

[tfonteyn]

first: 7.1 is coming by next weekend, I'm not available for some days and did not want to disappear immediately after releasing, so I postponed 7.1 with a week.

support for the pinch zoom in/out gesture to resize the images?

I presume you mean the "replace/rotate/crop..." menu you get on the covers on "book detail" screen?
I'm not sure what you mean with the style settings in this context? Or maybe I misunderstand. Please clarify.

three-dot icon [in grid mode]

quite possible I misunderstand this one as well, adding-long-press is something I can do... but you know you can remove those 3dot/detail buttons already?

[ChristianGruen]

first: 7.1 is coming by next weekend, I'm not available for some days and did not want to disappear immediately after releasing, so I postponed 7.1 with a week.

Great!

I presume you mean the "replace/rotate/crop..." menu you get on the covers on "book detail" screen? I'm not sure what you mean with the style settings in this context? Or maybe I misunderstand. Please clarify.

Sorry, I should be more precise: In the Grid View, I see all covers in a specific size that can be changed in the Style Settings via »Cover size«. I change this size fairly often – for example, when I switch to a larger device with more screen space – and it takes multiple clicks to do this. It would be nice if I could increase the cover size directly in the grid view, by moving two fingers apart (and decrease them similarly).

but you know you can remove those 3dot/detail buttons already?

Oh, I didn’t know. I just found the "Row context menu" option in the global settings. When I choose "Alwayse use long-click", it doesn’t seem to have an effect in the grid view. Maybe it only applies to the List View (at least on my current device)?

[tfonteyn]

»Cover size«

ah, I get it now.

more screen space –

I'm curious now which exact size(s) you have. There is some automatic sizing decision for the rough categories of phones 4"..6.99", 7" tablet and 10" tablets. Maybe that (little) logic is not enough to suit all displays and needs updating.

If you run a bug-report on the device, you can take a look in the generated info-files where the display specs are listed; no need to upload all, just that snippet would be useful.

increase the cover size directly in the grid view

nice idea; no promises but I might look into the possibilities.

. I just found the "Row context menu

yes, my docs always come after a question.... I need to improve documenting it.

The below MIGHT CONTAIN ERRORS, or be incomplete but I tried constructing an overview:

ExtMenuButton (3dot-contextmenu global option)

• Always
• IfRoom
• None

CoverClick

• Zoom
• OpenBookDetails

CoverLongClick

• Ignore
• PopupMenu

=========================================
List-mode:

• style option: cover-click: Zoom/OpenBookDetails

• cover:
  click: Zoom/OpenBookDetails as per style-option
  long-click: IGNORED, SAME AS CLICK

• background/row:
  click: book-details
  long-click: book-menu

• 3dot: book-menu as per global-ui-option

=========================================
Grid-mode:

• style option: cover-click: Zoom/OpenBookDetails

• style option: book-menu: 3dot-btn OR long-click-cover

• cover
  click: Zoom or OpenBookDetails as per style option

  • zoom, adds a "details" button

  • OpenBookDetails, no "details" button

  • long-click: book-menu

• no cover
  click: OpenBookDetails
  long-click: book-menu

[ChristianGruen]

I'm curious now which exact size(s) you have.

You are welcome:

configuration:
  screenWidthDp=711
  screenHeightDp=1064
  orientation=PORTRAIT
  densityDpi=360
metrics:
  widthPixels=1600
  heightPixels=2454
  density=2.25

configuration:
  screenWidthDp=485
  screenHeightDp=1079
  orientation=PORTRAIT
  densityDpi=356
metrics:
  widthPixels=1080
  heightPixels=2400
  density=2.2250001

configuration:
  screenWidthDp=411
  screenHeightDp=813
  orientation=PORTRAIT
  densityDpi=420
metrics:
  widthPixels=1080
  heightPixels=2133
  density=2.625

configuration:
  screenWidthDp=349
  screenHeightDp=597
  orientation=PORTRAIT
  densityDpi=220
metrics:
  widthPixels=480
  heightPixels=854
  density=1.375

As can be seen, it's mostly the third device that behaves differently (but I also tend to use larger images on the smallest device, a Jelly Star).

The below MIGHT CONTAIN ERRORS, or be incomplete but I tried constructing an overview:

Wow, I think it's all there. Great. I must confess I only checked the global options. I am certainly getting greedy asking if all usability options could be defined once over there ;) …after all, it's a matter of minutes to adjust all styles.

[tfonteyn]

I use the google guidelines from Use window size classes

Yours translate to:

• M/E
• C/E
• C/M
• C/M

However, the dpi is also taken into account with sw360 / 320dpi as my lower boundary for which I design the screens (sw == smallest screen width). This is the so called "Small phone" template.

   "Small Phone" - sw360dp
    Density: 320 dpi
    Density: 2.0
    Resolution (px): 720 x 1280
    Resolution (dp): 360 x 640 == Compact/Medium

My test setup in the comments of that xml file.
(tablets are generic, only the sw values really count, dpi does not)

Your last device is 220dpi which means .. "ouch" :) best-effort as we say.
Or in other words, my "dimen"-sions are defined for sw320 (and lower),
sw360,sw600,sw800
The dpi values are tested manually as there are no good resource-sizing rules in android based on dpi. The main ones are on smallest-width and on absolute width and height.

Personally I find their 3 buckets a bit restricting, as "Medium" covers too many phone sizes.

But the above is just me rambling a bit as a form of documentation of course.

Back to the question:

You basically only have two models: Medium width and Compact width which is what decides the auto-sizing for the covers. The amount of covers (the span of the grid) is manual.

I'll fiddle a bit and see what the options are when I get some time.

[tfonteyn]

as an afterthought and meant for any other user reading this.... if anyone wants me to support a folding phone... they will have to send me one 😇

[tfonteyn]

nearly forgot: that inconsistency is fixed in 7.1 - it was actually a bug handling the dpi

The rest is something for later

[ChristianGruen]

…again, thanks a lot for the new release! Looks good.