Qlik Sense desktop: custom theme - qliksense

I have Qlik Sense Desktop installed and trying to create a custom theme based on 'highvis' theme that's built in. my question is that what is the directory should I put my theme in? please note that i am using desktop version which does not have XXX/Qlik/Sense/Client/themes as in server version.
also since we can access through localhost:4848/resource/theme/highvis/... i guess that those resource files are published to some directory, does anyone know the directory?
Thanks!

The local theme folder is:
C:\Program Files\Qlik\Sense\Client\themes\SOMENEWTHEMENAMEFOLDER
then add the new theme name to the URL like you do with High Vis theme as described on this useful blog post:
http://webofwork.com/qlik-sense-high-vis-mode/
This is not a supported way of doing themes.
Thanks,
Adam

Pretty old post, but in case you need it for Qlik Sense 3 here is a good community post:
https://community.qlik.com/docs/DOC-13517
On Sense Server themes are found here
C:\Program Files\Qlik\Sense\Client\themes
On Sense Dekstop (>= 3.0) themes are found here
C:\Users\\AppData\Local\Programs\Qlik\Sense\Client\themes
Hope it helps, cheers!
Azucena

Related

Moodle 4.0 problems with Moove 3.11.05 theme (the site is not showing breadcrumbs)

Basically I've installed the Moove 3.11.05 theme and everything seems to work except the breadcrumbs. I've done the research and didn't find any solution. Has someone else encountered this problem and how can it be fixed?
Moove for Moodle 4.0 is already available. You can donwnload it from its page: https://moodle.org/plugins/theme_moove/versions
There are significant changes to the user interface in Moodle 4.0 - many of which will require changes to any custom / third-party theme.
If you want to use any such themes with Moodle 4.0, then the best advice would be to hold off upgrading until the maintainer of that theme has released a Moodle 4.0 version.
In the meantime, you may find some useful information at: https://docs.moodle.org/dev/Moodle_4.0_developer_update

How to create custom themes in Anycharts Qlik extension

I am trying to create custom themes in our Anycharts Qlik sense extension. I used the following article as a guide, https://www.anychart.com/blog/2019/01/16/qlik-data-visualization-custom-drawing/
The article names these files as the key to adding themes:
"To add a custom theme to the AnyChart Qlik Extension, edit the file at ..\Users\Documents\Qlik\Sense\Extensions\AnyChart-Qlik\lib\themes-combined.js by putting the code of your custom theme at the end.
To use the theme by default in the future, edit the config.js file at ..\Users\Documents\Qlik\Sense\Extensions\AnyChart-Qlik"
I cannot find these files (or even the "lib" folder mentioned) in either a desktop or enterprise installation.
has anyone:
1) found these files/folders ?
2) successfully created a custom theme for teh Anycharts qlik sense extension ?
Thanks
Already searched Qlik installation for the files.
The thing is that the article is related to the 2.4 version of Qlik. But the current version is 3.x, and the feature is not supported there. Perhaps it'll be restored in the future.

How to Enhance social office theme for Liferay

I would like to enhance the social office theme for liferay : so-theme.
I tried to create a new theme with the liferay IDE but the default theme is still used.
Has anyone modified the social office theme?
Thanks a lot for yours answers
Ok, I found the answer on the liferay forum, answer from Liferay staff:
Unfortunately, changing so-theme is the only way to do it. We locked down the ability to deploy a theme because the majority of (most likely all) of the portal themes would be incompatible with the way we do a few things in SO.
Suggestion in the same forum post by Liferay Staff:
My suggestion for now would be to add another "include" line in the main.css at the very end and keep your changes there. I think this will make maintainability easier for you until we find a permanent solution for theming Social Office.
So it's not possible to create a new liferay theme based on so-theme. The only way is to directly modify the deploy theme.

Why can't I find the default Magento theme being loaded?

Should be pretty simple. I am trying to find what theme is being loaded in Magento to create my own custom theme. The problem is the mine (ver. 1.7.0.2) has no files in the frontend->default->default folder so I can't put any print statements there or see which template Magento is loading to learn more about it. Print statements in base->default don't seem to work either.
And where is the home page template located?
I don't know why Magento makes this so hard or maybe I'm just looking at old info that's not applicable anymore.
Turn on template path hints. Also disable the cache from System > Cache Management while you are doing any theme work.
+1 for other answer suggesting you turn on template path hints. That is a great way to figure out the structure of how things work in Magento.
I would also recommend the user guide. It's been updated to apply to 1.7. You used to have to pay for the guide but they make it available for free now.
http://www.magentocommerce.com/resources/magento-user-guide
As well as the latest designers guide that has info specific for templates etc.
http://www.magentocommerce.com/design_guide

Plugins + Extensions on Safari 5.0.1

My question is very simple: Is it possible to pack plugins into extensions for Safari? For instance, the exact NPAPI plugins which work on Google Chrome also work on Safari. However in Chrome I'm shipping the plugins as a part of an extension (a CRX package). This is needed because HTML and JavaScript is injected into a specific web page, and this code uses the plugins. I do not see an option in Extension Builder to specify plugin files and I haven't come across any proper documentation saying that plugins cannot be packed into extensions.
Any help will be greatly appreciated!
The first comment:
I don't think that is supported. A workaround could be a custom installer that installs both the plugin and the extension. – Georg Fritzsche
This is the only possible way to do it! FYI: Apple guys are against the idea of extensions accessing native code (ie, plugins). An obvious security loop-hole, but a necessity here! :)