Vaadin 7 - Themes compilation - themes

In my application I've more than one theme.
When I try to compile themes it compiles only one theme (the oldest I don't use anymore).
If I cancel that old theme it goes in error.
Where are stored names of themes to be compiled ?
Can I change them ?
Running the application in debug mode it compiles on the fly the correct one.
Tks
Tullio

Partially solved. I found in the plugin configuration the tag theme
and I corrected it. But I didn't find the way to compile more than one theme. Is it possible ? How ?

It should compile all the themes by default without needing to configure anything. Have you tried to remove the configuration?

Related

change packages icon in intellij idea

I used a plugin or theme or some thing like that in intellij idea and it make my packages even files icon in project different . Unfortunately i changed my intellij version and it gone
entities and services and controllers packages also shown differently.
if you used it can you help me to add this extensions?
Try using plugin's search for Theme and User Interface tags to search for the UI Theme plugin.
FILE >> SETTINGS >> Plugins >> install Atom Material Icons
Warning: this changes Ide icons too

Applying third-party themes to QtCreator (dracula)

So I just downloaded the open-source QtCreator and I hoped to set the Dracula theme for this IDE, but I failed to do so, and I have no clue what I'm doing wrong.
So far, every where I looked for third party themes, they've been telling me to put it in a map on location "$HOME.config\QtProject\qtcreator\styles" (windows). Fine, but after I've copied the file into that folder, the theme is not showing up in the theme list when I'm trying to set a new theme in QtCreator, selecting Tools > Options > Text Editor > Theme-button :/
I'm quite (90%) sure the path/location is correct, but I assume the themes have moved to somewhere else. I would like to set-up this theme, instead of the default dark-theme. Thanks in advance!
So I found out the themes were located in PathToQt\Qt\Tools\QtCreator\share\qtcreator\styles. The developpers must have changed moved the theme folder, but now between the other .xml files, the Dracula.xml file works just fine.
I hope I fixed every one else's problem, who came to ask himself where the heck they had to put that theme.

themes on intellij idea

I'm using intellij idea 15 community with dracula theme but on files html I see several green line in the code How can I disable them?
Well, Fanally I found the solution:
Go Language Injections Setting and cofigure the language
Change it here :
View->Quick Switch Themes Scheme->Look and Feel-> Default/Darcula

slow scrolling when using responsive bootstrap theme

I am using a bootstrap 3 template and have noticed on some that scrolling is not smooth and kind of bumpy. I am not even sure what to look for. This only happens in Chrome. It does NOT happen in Safari or Firefox.
Is this a javascript or css problem? I have never run across this before.
This seems to happen worse in Chrome for mac, but also happens in chrome for windows.
It seems to happen when I make the window smaller and then make it bigger again. If I leave the window the same size, it seems to scroll fine.
Link:
http://demo.phppointofsalestaging.com --> Click Sales then resize the window in Chrome and then scroll down and then up. You will notice it is very bumpy and not smooth
:root { scroll-behavior: auto; }
Add this simple code to your custom CSS file.
"scroll-behavior" declared as "smooth" in bootstrap css/bootstrap.reboot.css.
So we need to overwrite it using our custom css.
The problem is in the jquery.nicescroll plugin that is used with the theme, the function jQuery.fn.scrollTop make the problem, it takes more than 75% from the cpu when run. my solution is :
You are using the jquery.nicescroll plugin version 3.4.0 use the latest version currently version 3.5.0 available.
If not working as expected, downgrade to version 3.2.0 I'm using it with my site without any problem.
Also check that if the hwacceleration in the Configuration parameters of the plugin is set to (default: true).
Update 1:
nicescroll plugin is a solution to have a custom scrollbars compatible with desktop, tablet and phone devices and to override the default scrollbars of the browser " more information her ", "you didn't see the diffrence because the plugin used in your project works when your browser window under 767px" so another solution if you don't need it you can remove the plugin from your files by following this steps:
Delete the plugin file (jquery.nicescroll.js) from your script folder.
Delete the plugin link from all your files.
Delete the plugin function lines (21 to 36), (49 to 66), (149) from (unicorn.js) file.
Update 2:
I made some tweaks for the (unicorn.js), download it from her, then replace your original one.
Hope this will help you.

Magento - How to debug layout problems

I've just upgraded Magento from 1.4 to 1.5. The update went (almost) smoothly and admin appears to be all working etc.
The problem is with the theme. Something (a module or some bad code somewhere) is causing memory issues somewhere down the page (Error tried to allocate memory etc). The top layout areas load ok. I know this because I get a fatal error on a deprecated method call and when I correct this error I see the problem
How can I track down the offending code/module?
Thanks
** EDIT ** The admin area is working just fine which is why I am assuming it is theme related
** EDIT ** I see the problem even with different themes
If you can see the problem with the default theme, it's unlikely that the theme itself is causing the problem. This is backed up by the fact that you say that you have the same issue with multiple themes.
Assuming that you made no updates to the core code (right? right?), try replacing your entire core class folder with a clean copy from your version of Magento. Try doing the same with your default theme (if you have edits to the default theme, create a "new" theme with the default code and use that). Then, try again. If you still have problems, it's very likely that some of your custom code is causing the problem.
Hope that helps!
Thanks,
Joe
EDIT: Make sure to disable caching, the Magento compiler, etc.

Resources