DRAFT - Improve image cropping drawer

[Julien-Dubois-eXo]

Rationale Details of the GAP ( problem(s) to address ) expressed by few words using some screenshots. Note: avoid describing the solution here.

Currently, we have an issue when selecting an image into the News feature (specific to eXo) to properly address the display of the image in case of multiple screen sizes. The user has an issue knowing what the image will look like in the different size context.

We want to use the image cropping component to be able to manage the size and be able to crop propose a tool answering the need. So we could propose a harmonized experience using the component already used.

Additionally, following the rework of the login page, we can't display an illustration in the mobile version as the size are different:

• desktop: illustration is a vertical rectangle
• mobile: illustration should be a horizontal rectangle.

The solution described below may allow us to have an illustration on mobile too.

1. Functional requirements

Add in the cropping components additional option to be able to manage different layouts of images in a responsive context:

• A new section "Image layout" (extensibility should be implemented to be able to manage the name of the section in the different integration of the component)
• An descriptive text to explain what is the purpose of this option
• 4 layout selectors:
  • square
  • rectangle
  • large rectangle
  • vertical rectangle
• When downloading a picture, it's displayed with the cropping frame
• When switching from one layout to another we can visualize and adapt the image to the selected layout
• "Multiple image" option: allow to download a different image for each layout so if the image is can't be adapted to a specific layout we can use another one.
• We will use a ratio to define which layout should be used so we could efficiently manage the responsiveness of the page.

2. Non Functional Requirements

Expected volume & Performance requirements

Security requirements (Authentication, Authorizations, Audit track / traceability, data retention…)

Extensibility requirements (Identified extension points, plugables implementations...)

Configurability requirements (properties introduced, default settings, jobs, etc...)

Requirements related to existing users data

Requirements related to existing features (ex: Add a button to existing modules...)

Feature Flag (property name, default status, target audience, functional behaviour)

Other NFR (ex: Use of VueX, Vue, Vuetify)

3. Impacts

Requirements (Squash)

Documentation to update?

Training level / Change management needs

4. Software Architecture

• Security

• Access (GUI, API…)

  • Rest API design (Entry points, domain objects)
  • Portlet Vue & Vuetify, simple portlet, extension WAR ...

• Services & processing

  • Ex: Scheduled Jobs

• Data and persistence

  • Macro data model
  • Persistence layer (RDBMS, elasticsearch...)
  • Use of caches

• Support for clustering

• Support for multitenancy

• Integrations

• Migration strategy

5. Annexes
   • Reasoning that explain the technical choices
   • Impacts (ex: impact on public REST/Java API)
   • References (links...)

[Julien-Dubois-eXo]

@srenault-meeds to be discussed after the holiday break, please.

[srenault-meeds]

Hi, it seems it is completely different to Meeds usage and if you allow me, it seems to be very specific to eXo usage. However, opened to discuss it anytime

[srenault-meeds]

Hi, Is that still something planned to be done?

[Julien-Dubois-eXo]

Not for 6.5. For later I have not the visibility.

[srenault-meeds]

I Archive it as we don't have any news about it. If needed, a restore can be done