In a bit more detail, the following needs to be done:

Add a possibility to specify a custom css file in the preference dialog.

jabref/src/main/java/org/jabref/gui/preferences/AppearanceTab.fxml

Lines 30 to 31 in 2a5507f

    
           <RadioButton fx:id="themeLight" text="%Light theme" toggleGroup="$theme"/> 
        
           <RadioButton fx:id="themeDark" text="%Dark theme" toggleGroup="$theme"/>

The following code needs to be slightly modified to allow loading of external css files:

jabref/src/main/java/org/jabref/gui/util/ThemeLoader.java

Lines 62 to 70 in b6c2663

    
           // Otherwise load css from preference 
        
           URL cssResource = JabRefFrame.class.getResource(cssPreferences); 
        
           if (cssResource != null) { 
        
               LOGGER.debug("Using css " + cssResource); 
        
               additionalCssToLoad = Optional.of(cssResource); 
        
           } else { 
        
               additionalCssToLoad = Optional.empty(); 
        
               LOGGER.warn("Cannot load css " + cssPreferences); 
        
           }

As a workaround, it is already possible to specify the css as a command line argument as described here:

jabref/src/main/java/org/jabref/gui/util/ThemeLoader.java

Lines 24 to 35 in b6c2663

    
            * Installs the style file and provides live reloading. 
        
            * <p> 
        
            * The live reloading has to be turned on by setting the <code>-Djabref.theme.css</code> property. 
        
            * There two possible modes: 
        
            * (1) When only <code>-Djabref.theme.css</code> is specified, then the standard <code>Base.css</code> that is found will be watched 
        
            * and on changes in that file, the style-sheet will be reloaded and changes are immediately visible. 
        
            * (2) When a path to a css file is passed to <code>-Djabref.theme.css</code>, then the given style is loaded in addition to the base css file. 
        
            * Changes in the specified css file lead to an immediate redraw of the interface. 
        
            * <p> 
        
            * When working from an IDE, this usually means that the <code>Base.css</code> is located in the build folder. 
        
            * To use the css-file that is located in the sources directly, the full path can be given as value for the "VM option": 
        
            * <code>-Djabref.theme.css="/path/to/src/Base.css"</code>

This method should be properly documented by adding it with a bit more details to http://devdocs.jabref.org.

	<RadioButton fx:id="themeLight" text="%Light theme" toggleGroup="$theme"/>
	<RadioButton fx:id="themeDark" text="%Dark theme" toggleGroup="$theme"/>

	// Otherwise load css from preference
	URL cssResource = JabRefFrame.class.getResource(cssPreferences);
	if (cssResource != null) {
	LOGGER.debug("Using css " + cssResource);
	additionalCssToLoad = Optional.of(cssResource);
	} else {
	additionalCssToLoad = Optional.empty();
	LOGGER.warn("Cannot load css " + cssPreferences);
	}

	* Installs the style file and provides live reloading.
	* <p>
	* The live reloading has to be turned on by setting the <code>-Djabref.theme.css</code> property.
	* There two possible modes:
	* (1) When only <code>-Djabref.theme.css</code> is specified, then the standard <code>Base.css</code> that is found will be watched
	* and on changes in that file, the style-sheet will be reloaded and changes are immediately visible.
	* (2) When a path to a css file is passed to <code>-Djabref.theme.css</code>, then the given style is loaded in addition to the base css file.
	* Changes in the specified css file lead to an immediate redraw of the interface.
	* <p>
	* When working from an IDE, this usually means that the <code>Base.css</code> is located in the build folder.
	* To use the css-file that is located in the sources directly, the full path can be given as value for the "VM option":
	* <code>-Djabref.theme.css="/path/to/src/Base.css"</code>

Uh oh!

Allow to load customized css #5790

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions