About | Features | Technologies | Making Themes | License |
The project is made using electron, the interaction with windows api is either done with Foreign Function Interface or with binaries compiled for this project.
Being made with electron means the Chrome overhead is existent, if you have a computer with ultra low RAM settings, avoid using Hyperbar. The average ram usage is arround 100MB
Hyper is modular and each theme may come with new or modified modules.
Default modules:
- WebnowPlaying module : Show/control currently playing music/video.
- Clock
- Weather
- Taskbar
- Workspace manages.
Cool things that i'm proud of:
- Gui configuration
- Custom theme and widget support
- Crafted with love
You can find your theme folder by right clicking the bar and then selecting Open themes folder.
The folder is actually located at your user folder (c:/users//.hyperbar)
Every theme must follow a specific directory structure with a index.html at it's root directory.
PS: THE THEME MUST HAVE THE CORE INDEX.JS FILE AT THE BODY END IN ORDER TO USE DEFAULT WIDGETS AND VARIABLES
Here's a simple theme structure:
.hyperbar/themes
└── Theme name/
├── widgets/
│ └── widgetname/
│ ├── widgetname.css
│ └── config.yaml
├── index.css
└── index.html
Making new widgets for your themes is as simple as creating .js files and including on your index.html
You can access two protocols from your theme:
theme://
Refers to the theme root directory, that is what you're going to use to load css and js files from your theme.core://
Refers to the hyperbar directory, i advice agains using the core protocol since updates may break your theme.
This project is licensed under GNU-GPL 3.0
What does that mean? it means you can make your own themes and even sell them but when sharing/distributing Hyperbar you must include credits and a copy of the license file with it.