Skip to content

Externalisation of UnifiedViews theme#414

Merged
skrchnavy merged 2 commits intodevelopfrom
feature/separate_theme
Jun 19, 2015
Merged

Externalisation of UnifiedViews theme#414
skrchnavy merged 2 commits intodevelopfrom
feature/separate_theme

Conversation

@farky
Copy link
Copy Markdown

@farky farky commented Jun 12, 2015

refactoring which allows to develop and use themes separately from then UnifiedViews

  • for creating new Theme is no longer necessary to create class which extends AppEntry
  • name of Theme has to be set in frontend/config.properties in frontend.theme property
  • all static content for Theme with name XYZ (frontend.theme = XYZ) has to be placed in VAADIN/themes/XYZ folder
  • theme can be created separately without UnifiedViews and then copied to the deployed UV. set correctly frontend.theme property and afterward context restart is necessary

@skrchnavy skrchnavy changed the title Feature/separate theme Externalisation of UnifiedViews theme Jun 12, 2015
@skrchnavy skrchnavy added this to the Release v2.1.0 milestone Jun 12, 2015
@farky farky assigned tomas-knap and unassigned farky Jun 12, 2015
@tomas-knap tomas-knap assigned farky and unassigned tomas-knap Jun 16, 2015
@skrchnavy
Copy link
Copy Markdown

@farky please finish feature

@skrchnavy skrchnavy merged commit dbb04ae into develop Jun 19, 2015
@skrchnavy skrchnavy deleted the feature/separate_theme branch June 19, 2015 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants