By Allon Moritz on 2017-03-31 05:52 in New Media Manager Team

Thursday 30th March 2017 on Google Hangouts

Time: 19:30 CEST


List of Attendees Overview

 

Attendee

 

A

   

A

Allon Moritz (Lead)

CH

x

     

Marco Dings

NL

       

Yves Hoppe

DE

       

David Neukirchen

DE

x

     

Dawn Russell

US

x

     

Britta Stender

DK

x

     

Dimitris Grammatiko

GR

 x

     

Ciaran Walsh

IR

x

     

Other Attendees:

na

       
           
           
           
           



General topics

UX Survey decisions

  • Q3 Edit mode

    • The template is deciding which background color it will have.

  • Q4 Breadcrumb

    • We keep the /.

  • Q5 Back button

    • Include this in the usability test, there are four options for going back technically which ones are used and how.

      • Back Arrow

      • Breadcrumbs

      • Browser Back Button

      • Folder Tree

  • Q6 Image preview in grid

    • Cropped image with filename and image size

    • We try different approaches

  • Q7 List thumbnail

    • Original dimensions

  • Q8 Image tools

    • We go with resize, crop and rotate

 

List Grid view mock ups

Ciaran made some mock ups of the list grid view. We need to decide which path we want to follow.

 

 

 

 

 

 

 

We follow that approach for the milestone 1

 

List view mock ups

Ciaran made some mock ups of the list view. We need to decide which path we want to follow.

 

 

Dev Topics

Edit view

 

The edit view is based on Joomla plugins which do add fieldsets to a JForm instance. Each plugin will be rendered then as tab. Code can be found in this branch

https://github.com/joomla-projects/media-manager-improvement/compare/feature/edit/view?expand=1

 

We need to decide:

  • If we want to go the JForm approach?

    • Yes.

  • How to add JS code, actually it is done trough plugin layouts

    • Just loading it in the oncontentprepare function.

  • About plugin JS activation/deactivation

    • Event Bus. We follow this approach, but we do some optimization on the existing code.

    • Events on DOM element

    • Direct call on plugin registry

    • Let the plugin decide by itself