Databases
StackOverflow2013
Postsdbo
POVaadin, applying own theme doesn't work
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POVaadin, applying own theme doesn't work
    primarykey
    data
    text
    <p>I am trying to add custom theme to my Vaadin 7 project. I used the Vaadin plug-in theme creater, it created the necessary files and I included a simple background-color setting to my table, but even though reindeer theme is included it doesn't seem to work. After I apply my theme with <code>@Theme()</code> annotation on my UI class my table disappears and I get this (without the custom theme it looks fine):</p> <p><img src="https://i.stack.imgur.com/3Ay0I.png" alt="enter image description here"></p> <p>I read the part of the Book of Vaadin that describes this (<a href="https://vaadin.com/book/-/page/themes.creating.html" rel="nofollow noreferrer">https://vaadin.com/book/-/page/themes.creating.html</a>) but it still doesn't work for me. I read this part: <a href="https://vaadin.com/book/-/page/themes.html#figure.themes.theme-contents" rel="nofollow noreferrer">https://vaadin.com/book/-/page/themes.html#figure.themes.theme-contents</a> and it shows reindeer should be under themes, but it says I have to include the vaadin-themes.jar and it will work fine. I did add it, my filestructure looks like this: </p> <p><img src="https://i.stack.imgur.com/vif2P.png" alt="enter image description here"> </p> <p>airlinedb_customtheme.scss file's code:</p> <pre><code>@import "../reindeer/reindeer.scss"; @mixin airlinedb_customtheme { @include reindeer; .v-table { background-color: red; } } </code></pre> <p>and my theme's styles.scss:</p> <pre><code>@import "airlinedb_customtheme.scss"; .airlinedb_customtheme { @include airlinedb_customtheme; } </code></pre> <p>What am I missing? It looks like to me that reindeer style isn't included but I have no idea why.</p> <p>EDIT:Furthermore, how can I give background color for my button and my table-row?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. UScatfood
    1. USfrauneworld
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POVaadin, applying own theme doesn't work
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    2. VO
      singulars
      1. POVaadin, applying own theme doesn't work
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCan you repost your screenshot ? Are you running in production or debug mode ? Any error in logs ?
      singulars
      1. POVaadin, applying own theme doesn't work
      1. USSerge Farny
    2. COthere are no error in logs and i am running it in production mode, which creenshot do you mean? aren't they visible?
      singulars
      1. POVaadin, applying own theme doesn't work
      1. USfrauneworld
    3. COTry running in debug mode. In debug mode, the css file is generated on the fly. If it works, you have to add the generating process to your build system for the production mode. See this question: http://stackoverflow.com/questions/16561633/vaadin-cannot-find-themes-when-in-productionmode?rq=1
      singulars
      1. POVaadin, applying own theme doesn't work
      1. USSerge Farny
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload