[META] Desktop layout and mobile responsive design issues

Appreciate your efforts working on this. Given the browser simply comes from a view, it seems the expectations are each user of the module comes up with a design or layout. An out of the box design would be very useful and increase consistency across all Drupal sites using media.

I've opened #2707469: Create a design for the media browser. for aGov, but perhaps efforts should be focused on the module itself?

for aGov, but perhaps efforts should be focused on the module itself?

I think that it is a good idea to join forces and first fix things in core and entity_browser module and then continue with custom implementations.

The "file_browser" project creates and styles a default view for file entities. Perhaps the equivalent is needed for media entity and design improvements should go in there?

I didn't check a lot file_browser module, but judging to it screenshot on https://www.drupal.org/files/project-images/file_browser_screenshot.png but that better&simillar look and a lot more we would want to have also in entity_browser.

Are there somewhere design/plan issues for file_browser what other improvements module would do?

You'll have to ask the module author. I was made aware of the project today. I do wonder if "ENTITY_NAME_browser" modules are going to be able to provide the best user experience vs something generic in entity_browser. It might be difficult to be entity agnostic? How will entity browser know what fields are available to display in a view for any entity type?

I'm considering creating media_entity_browser which provides a "media_entity" specific view, styled similar to file_browser to solve this problem.

How will entity browser know what fields are available to display in a view for any entity type?

This is little bit outside of my current knowledge of entity_browser, i'm not too deep into project, just over-viewing current entity_browser ui/ux initiative that @Nenad is doing.

Regarding 'what fields are available to display in view' - i don't think that we should/will use fields directly when rendering various entity types in entity_browser views, but we should use some teaser display for that and each entity type should provide a good default teaser display which we can use.

@slashrsm can probably add more info on this subject.

That's possible, but it still leaves the user to configure the view mode which is a significant part of the display. It also might be difficult path because views fields are required for the selection checkbox, which is required to be present.

That's possible, but it still leaves the user to configure the view mode which is a significant part of the display.

Little bit confused about this (although not fully sure how stuff works currentlly), but user should not configure nothing out of the box, all modules should provide sensible defaults for everything and also including display and views modes that works OK out of the box.

If user wants some custom behaviour then fine, he need to know advance configuration stuff and then do what ever he wants.

It also might be difficult path because views fields are required for the selection checkbox, which is required to be present.

Hmmm, yeah this can be a problem then if it is like that, we should see can we re-factor this if possible because using fields for view rendering is a problem and is adding complexity.

Discussed the technical approach on IRC, logs as follows: http://codepad.org/OS5RNkzn.