Versions Compared

Old Version 11

changes.mady.by.user Mikaël Geljić

Saved on

compared with

New Version 12

changes.mady.by.user Mikaël Geljić

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: added status

...

Table of Contents
maxLevel2

 

Info
titleStatus

(warning) Support for SASS in 3rd-party apps needs proper configuration of mappings for the VaadinServlet in magnolia, so that it is responsible for serving those CSS resources.

(warning) Project structure needs decision for magnolia-ui-theme and widgets, whether we keep them in magnolia_ui or build them upstream.

(error) Installing modules which come with custom widgets needs to recompile the whole widgetset, this is a major blocker right now.

 

1. Themeing

Problem

  • We don't have true themeing so far, only fields in dialogs have decent styles
    • If I add a TextField and a Button in my app, they should also have the Magnolia style
  • Stylesheets are a real mess
    • They're not properly modularized
    • Some rules don't belong to the right stylesheet
    • Widget styles and app styles are also mixed up inside these stylesheets
    • Some style rules are simply duplicated across several stylesheets (forms vs. dialogs)
  • All vaadin standard UI components should look visually integrated into magnolia
  • Styling could be applied in a more light-weight way

...