I won't go into the minor details of the theme building process, however I will talk about the high level details of what is accomplished.
All themes have a base template that they inherit from. Themes have the ability to choose their inherited parent. Each child has the ability to override any attributes defined by the parent. This mitigates any one-off issues for themes that are not captured by the global shared style.
If this is your first time working on a Eclipse plugin, then it's a good idea to complete the eclipse plugin development. This should give you a good introduction as what to expect, when developing for this plugin. This way you can re-evaluate your life decisions and choose a better IDE with superior plugins.
- Yarn package manager
- Node 14
- Eclipse
- Java 11
Set up Yarn Globals
I heavily use Node/Typescript to build all of my themes, and I have a fair amount of global tools installed.
Just run
yarn global add typescript ts-node nodemonNote: if you already have these globally installed please make sure you are up to date!
yarn global upgrade typescript ts-nodeGet the Master Themes
Since this theme suite expands across multiple platforms, in order to maintain consistency of the look and feel across platforms, there is a central theme definition repository
This repository needs to be cloned as a directory called masterThemes. If you are running Linux/MacOS, you can
run getMasterThemes.sh located at the root of this repository. This script does exactly what is required, if you are
on Windows, have you considered Linux? Just kidding (mostly), you'll need to run this command
git clone https://github.com/doki-theme/doki-master-theme.git masterThemesYour directory structure should have at least these directories, (there will probably be more, but these are the important ones to know).
your-workspace/
├─ doki-theme-eclipse/
│ ├─ masterThemes/
│ ├─ buildSrc/
Inside the masterThemes directory, you'll want to make sure all the dependencies are available to the build scripts.
To accomplish this, just run this command in the masterThemes directory.
yarnNavigate to the root of the buildSource directory and run the following command.
yarnThis will install all the required dependencies to run the theme build process.
You should be good to edit and add themes after that!
I have too many themes to maintain manually, so theme creation/maintenance is automated and shared common parts to reduce overhead.
The standardized approach used by all the plugins supporting the Doki Theme suite, is that there is a buildSrc
directory.
Inside the buildSrc directory, there will be 2 directories:
src- holds the code that builds the themes.assets- defines the platform specific assets needed to build the themes. This directory normally contains two child directories.themes- holds the application definitionstemplates- if not empty, normally contains various text files that can be evaluated to replace variables with values. Some cases, they also contain templates for evaluating things such as look and feel, colors, and other things.
The buildSrc directory houses a buildThemes script that generates the application specific files necessary for apply
the Doki Theme Suite.
IMPORTANT! Do not create brand new Doki-Themes using the Eclipse plugin. New themes should be created from the original JetBrains plugin which uses all the colors defined. There is also Doki Theme creation assistance provided by the IDE as well.
Please follow the theme creation contributions in the JetBrains Plugin repository for more details on how to build new themes.
- Follow the editing themes setup
- Set up the doki-build-source
- You'll also probably want to have completed the Doki Theme VS-Code process. As this plugin uses the sticker assets of the VS-Code plugin. So it helps to have those in place!
This part is mostly automated, for the most part. There is only one script you'll need to run.
Once you have a new master theme definitions merged into the default branch, it's now time to generate the application specific templates, which allow us to control individual theme specific settings.
You'll want to edit the function used by buildApplicationTemplate
and appName defined here
in your masterThemes directory.
In the case of this plugin the buildApplicationsTemplate should use the eclipseTemplate and appName should
be eclipse.
We need run the generateTemplates script. Which will walk the master theme definitions and create the new templates in
the <repo-root>/buildSrc/assets/themes directory (and update existing ones). In
the <your-workspace>/doki-theme-eclipse/masterThemes run this command:
yarn generateTemplatesIf you added a new anime, you'll need to add
a new group mapping
to the Doki Build source. Please see
the handy development setup for more details on what to do
. You'll need to link doki-build-source in this plugin's build source.
For clarity, you'll have to run this command in this directory <your-workspace>/doki-theme-eclipse/buildSrc:
yarn link doki-build-sourceThe code defined in the buildSrc/src directory is part of the common Doki Theme construction suite. All other plugins
work the same way, just some details change for each plugin, looking at
you doki-theme-web. This group of code exposes a buildThemes node
script.
This script does all the annoying tedious stuff such as:
- Evaluating the
DokiThemeDefinitionsfrom the templates.