What is the easiest way to create a custom css (global to all documents)
for the Jupyter Lab (Installed via anaconda)?
JupyterLab uses themes which are extensions. These themes have CSS rules. There's no "official" way to have custom CSS in JupyterLab the same way as Notebook had (custom.css file in ~/.jupyter/custom directory).
Because of the above I've developed an extension where you can place custom (global) CSS rules in the settings editor:
https://github.com/wallneradam/jupyterlab-custom-css
You can edit the index.css for one enviroment. It should be in:
~/anaconda3/envs/[ENVIRONMENT NAME]/share/jupyter/lab/#jupyterlab/theme-dark-extension/index.css
for the dark theme or in:
~/anaconda3/envs/[ENVIRONMENT NAME]/share/jupyter/lab/#jupyterlab/theme-light-extension/index.css
for the light theme.
Related
I have a question: how can i (easy) implement the functionality from this plugin documentation https://developer.shopware.com/docs/guides/plugins/plugins/storefront/add-scss-variables-via-subscriber in a (cloud) app? I want to access values from config.xml fields in the SCSS file. I would be reluctant to define this as inline CSS (how SwagCustomNotification does it).
In the documentation under https://developer.shopware.com/docs/guides/plugins/apps/configuration scss is not included. So it is not possible?
You can't access fields defined in config.xml in scss files of regular apps but you should be able to setup a theme within your app. In the theme.json you can then define theme specific config fields. These fields should then become available as variables in your theme's scss files. You can find and change the config fields in the administration in the theme settings when assigning the theme to a sales channel.
I've been following these instructions, in an attempt to migrate a theme from our 6.1 portal to Liferay 7. The initial issue I seem to be having is getting the imported and upgraded theme to use vm as the template extension. I've added a look-and-feel.xml file containing the correct template-extension element to the 6.1 theme before importing/upgrading, but I am still receiving a "portal_normal.ftl not found" error after applying the theme.
Additionally, after importing and upgrading the theme into the Liferay 7 toolkit, the theme seems to only contain the child-specific theme files, and not the "compiled" set that would include the parent files (as it would had it been generated by the old sdk).
Any help resolving these issues would be greatly appreciated!
Liferay DXP/7 support freemarker. So your template files should be .ftl not .vm.You have to migrate template files into freemarker manually.
Regarding CSS: once you migrated theme, you will find a folder named 'src', you should make changes in files, placed here. Once you will find another folder over here named 'build'here you will find theme like we had in webapps in older versions.
Hope it will help
VisualStudio Code has great support for Markdown by using markdown-it, and there is an extension named markdown-it-emoji to allow emojis in markdown directly. I tried to install that in VS Code, but I don't see emojis rendered in the VS Code Preview.
This is what I have done:
npm install markdown-it-emoji --save-dev
My package.json looks like that
"devDependencies": { "markdown-it": "^8.3.1", "markdown-it-emoji": "^1.3.0"}
What do I have to do to use markdown-it-emoji in VS Code?
I work on VSCode and maintain the builtin markdown extension. As of VSCode 1.12, you cannot extend VSCode's builtin markdown viewer to support emojis
However, we are exploring allowing extensions to contribute functionality to VSCode's builtin markdown preview: https://github.com/Microsoft/vscode/issues/22916 I've even created an example extension that adds emoji support to the preview. To try the preview extension:
Make sure you are on VSCode 1.12+
Install the VSIX from the extension repo
Add the setting "markdown.enableExperimentalExtensionApi": true to your user or workspace settings
Keep in mind that this functionality is experimental. We have not yet committed to markdown extension extensions yet and the API / functionality may change
Also, please let me know if you are developing a markdown extension extension for VSCode
Emoji direct are still unsupported in VSC as of version 1.12.1; See: Emoji Code Extension For VSC by Idleberg | idleberg.emoji-code ... | Includes snippets for inclusion into code (.htm), (.js), (.css), (.ts), (.py) and (.rb) | But, not for (.md) | Standard rendering of :emoji: in (.md) currently unavailable in VSC | Also, cannot raise idleberg snippet at key 'ji' in (.md) either ... :musical_note:
I am working on orchard CMS (version 1.8.1) sites with multiple language, I found this one (https://github.com/qt1/orchard_contrib-RM.Localization) is useful, and I would like to add this to my site, but failed to work (I just copied it into, but picker widget cannot be found in dashboard), may someone know how to do and give me some advice?
Regards,
David
If you want to use this module in you Orchard app, you need to add it the the Orchard.sln and compile the application - then the module will be visible in Modules section of the dashboard.
You can also try using an existing package from the Orchard Gallery
Download a package
Go to Modules, and enable Packaging module
Go to Modules -> Installed and click Install a module from your computer
Browse the package and click Install
Now enable the installed module
How can I properly install Twitter Bootstrap into my meteor project?
I know I can do meteor add bootstrap but I can't customize the variables (ie colors and the sorts). I've also looked at nemo64:bootstrap but same issue, I can only include and exclude modules of Twitter Bootstrap but not the variables.
How can I properly include Twitter Bootstrap and have access to the variables.less ?
In order to control the order in which Meteor loads .less files you need to add .import.less to the file extension. If you import the bootstrap less files into your project and rename them, you will have finite control of all the mixins and variables. Here is a great post that summarizes this. http://www.manuel-schoebel.com/blog/meteorjs-and-twitter-bootstrap---the-right-way