I am migrating a 3.x eclipse RCP to e4.
I was able to successfully use eclipse's predefined themes. But I have done it by adding an extension to org.eclipse.e4.ui.css.swt.theme and copying all the css and images folder found in org.eclipse.ui.themes to my application.
I am not going to ever modify those themes I copied. So I was wondering if I can use the themes directly without copying the already made css files and images folder. This is also not future proof, if I ever upgrade eclipse platform where there was an update in the themes I would have to recopy the new theme resources.
What is the right way to do things? What is the e4 way?
Based on greg-449 answer I have added the following:
<property
name="applicationCSS"
value="platform:/plugin/com.example.rcp4/css/default.css">
</property>
Where default.css contains:
#import url("platform:/plugin/org.eclipse.ui.themes/css/e4_default_win7.css");
This works just fine. But now I am facing this look:
You can import existing CSS files in to your CSS using #import so you don't need to copy them.
Something like:
#import url("platform:/plugin/greg.music.e4.rcp/css/helvneue.css");
In this platform:/plugin/greg.music.e4.rcp is selecting the plugin containing the css (a plugin with id greg.music.e4.rcp in this case). /css/helvneue.css is the path to the CSS within the plugin.
Related
I was working on translating Alfresco share to Arabic i.e to RTL format.
Reading a comment from here I found out that the best way to proceed is to Create a custom extension pulling in an additional CSS file with the styling modifications.
Now coming to the question, I've encountered a problem while altering the css files to support RTL. The problem was that some css files were situated inside aikau-1.0.101.10.jar file. Can anyone help me on how to alter these css files ? or Can I override these files somehow ?
Some ways to do this:
You can create your own theme
Override LESS variable link
Fork Aikau and build your own jar link
Create an extension to include your own css file link
I recently started using Drupal for a new website I am trying to build. Front-end is normally what I focus on and I'd use external services to integrate backend functions. In this (and potentially from now on) I want to start using Drupal. Now, I have installed a bootstrap module and want to start adding own css from there but I can't seem to figure out how/where. I can't do it straight into the bootstrap style files so I - apparently - need to create my own theme and place css files in there. This is what I have done so far:
1: Have my css file with the code.
2: Created a new folder next to the bootstrap folder in sites/all/themes.
3: Put the css file in there.
4: Created an my_theme.info file.
But it is not resulting in any changes on the website (it also does not show up in the source code) most likely because it is not being called by Drupal. How can I make sure Drupal calls my css code?
Thanks in advance and take care!
Assuming this is DRUPAL 7 (Drupal 8 uses yaml)
Create a subtheme of the theme you choose.
In the YOURTHEME.info you add a line like stylesheets[all][] = css/style.css
In YOURTHEME/css directory, here you can start writing your css rules in the file style.css
Make sure caching is off or else you will not see your css being updated.
I tried to take a look around here and on the Liferay forums but I couldn't find a documented solution to my issue.
I am currently using Liferay 6.2 and am very new to the environment. My issue arises from CSS #import functions. Our architecture is one main stylesheet with all supporting stylesheets imported into this document. Those CSS documents in the same directory present no issue - for example #import url(document.css);. We do have a master stylesheet located in another portlet and all other portlets reference this stylesheet with an import call similar to #import url(../../../../folder/folder/document.css);. When using this command, the CSS in this file isn't imported into the portlet. If I place the master stylesheet in the same directory as the CSS for that portlet and adjust the import path accordingly, the stylesheet is imported without any issues. I can also place it one directory up such as #import url(../folder/document.css); and the CSS is imported correctly.
Several team members do not have this issue, while several members do experience this issue - all running the same version of Liferay and on identical machines.
I'm sure my question is fairly vague due to me being new with the environment so if I can clarify or provide any additional details, please let me know!
If all of the portlets reference the same CSS file they shouldn't: Just assume that the necessary CSS is deployed through the theme and add it to the theme once. This is way more elegant than delivering it multiple times, relying on relative paths to not have changed, and potentially not being available (at runtime, nobody guarantees that an appserver even unzipps your warfiles).
Through enforcing the assumption that you're running in an environment that has proper styling, life will be so much easier.
Prestashop theme folder contains a SASS folder. Where I am having .scss files for my newly developing theme. Am clear in compiling sass to css files locally, but prestashop is not having any inbuilt sass compiler, so does it makes any sense in uploading the sass folder to the server???
it does only make sense if you're using css-maps so you can actually use the scss instead of the compiled css to see the right lines in the inspect-element-console.
otherwise you don't need it.
//Edit might sounded confusing, what i mean is: You can actually see your scss-lines if you're using css-maps (the map needs the source to your scss-file) where all scss-commands you did are linked to the compiled css. if you inspect an element while having this css-map and the scss on the server and all file-directories correct then you'll see the scss-commands instead of the compiled css-commands. it makes developing much easier.
The problem is like this:
We're trying to implement a versioning scheme for our CSS and wherever we have accessed CSS through href (like \themes\ssss\abc.css) we append this link with a build number programatically (such as \themes\ssss\abc.css?1011) so that with new build the client gets the latest css files.
The problem is coming in themes. For e.g. under App_Themes we created a theme folder with the name MyTheme; now wherever this theme is used we need the CSS for this theme to be replaced by latest build files. How to do that?
why don't you create a new theme folder on each build/deploy?
Something similar to \themes\ssss-1011\abc.css.
Add some extra hash to your css url ("#somethingnew"). You can also you tools like SquishIt. It also can minify you css/js files.