Theme / Wisej Installation Issue

0
0

Hi Guys,

We have just released an upgrade to an application and we can see multiple theme warnings in the browser developer console.

I initially assumed that we had a theme issue on the server but on investigation we can also see these same warnings in debug on our dev machine. I have tried reinstalling Wisej but the problem persists. In fact before even running our own application in the new installation I can see the same warnings within the Hello World application created by the installer – I have attached a screen shot of the browser window. Note the “qx.theme.manager.Appearance” messages.

Can you review and let me know what we are doing wrong or what we need to do to correct?

 

Many Thanks,

Sean

 

  • You must to post comments
0
0

Set debug=false in web.config. The logged warnings are as intended, don’t indicate any problem with the theme.

  • You must to post comments
0
0

can you explain what you mean and how to correct?

  • You must to post comments
0
0

Hi Luca,

Thanks for the follow up.

We have 2 applications built using Wisej. When we review the browser console for the application that we have not recently changed there are no such console messages. If as you say the messages are a normal occurrence, why do we have them in one application and not the other?

Also, on further investigation we can see that our mixim does not render within the application that generates the warnings.

Thanks . . .

  • Luca (ITG)
    One site probably is in debug mode. When debug mode is off there is no logging.
  • You must to post comments
0
0

Those warnings are normal. Our theme system is rendered progressively, when a widget is first loaded the corresponding appearance keys are converted to css and cached in the browser. When it finds a child control, for example an icon in a split button, it looks for an appearance for the child control that can override the default. i.e. “button/icon” instead of “icon”.

  • You must to post comments
Showing 4 results
Your Answer

Please first to submit.