An unofficial opensource Pokemon cursor theme for Windows and Linux.
Until 2021 my cursors projects were well funded by pling.com but since the pling-factor on the website has decreased and monthly payments are <500$, It is now dependent on community funding and sponsorships. If you want to help me to maintain Pokemon Cursor and my other open source projects actively, consider sponsoring my work on GitHub Sponsor or DM me on Twitter if your company would like to support my projects, I will gladly look into it and post your avatar in the project's README.
I appreciate all the wonderful people who patronize and sponsoring my work.
N/A
Note All cursor's
.svg
files are found in svg directory or you can also find them on Figma.
22 24 28 32 40 48 56 64 72 80 88 96
22 24 28 32 40 48 56 64 72 80 88 96
- 16x16 - Small
- 24x24 - Regular
- 32x32 - Large
- 48x48 - Extra Large
You can download latest stable
& development
releases from
Release Page.
Installation:
tar -xvf Pokemon.tar.gz # extract `Pokemon.tar.gz`
mv Pokemon ~/.icons/ # Install to local users
sudo mv Pokemon /usr/share/icons/ # Install to all users
Uninstallation:
rm ~/.icons/Pokemon # Remove from local users
sudo rm /usr/share/icons/Pokemon # Remove from all users
Installation:
- Unzip
.zip
file - Open unziped directory in Explorer, and right click on
install.inf
. - Click 'Install' from the context menu, and authorize the modifications to your system.
- Open Control Panel > Personalization and Appearance > Change mouse pointers, and select Pokemon Cursors.
- Click 'Apply'.
Uninstallation:
Run the uninstall.bat
script packed with the .zip
archive
OR follow these steps:
- Go to Registry Editor by typing the same in the start search box.
- Expand
HKEY_CURRENT_USER
folder and expandControl Panel
folder. - Go to
Cursors
folder and click onSchemes
folder - all the available custom cursors that are installed will be listed here. - Right Click on the name of cursor file you want to uninstall; for eg.: Pokemon Cursors and
click
Delete
. - Click 'yes' when prompted.
- Pokemon build configuration and cursor hotspot settings are bundled in the
build.toml
file. - Check out the scripts section in package.json to see how we build the cursor theme,
excluding the render scripts. They are useful for converting
.svg
files to.png
files. - yarn is optional, For building XCursors and Windows cursors from
.png
files or resizing them you don't need that. If you want to develop/modify Pokemon's colors, and bitmaps, or generate a png file from a svg, Then you can use yarn because bitmapper is written in TypeScript.
- Install build prerequisites on your system
https://github.com/ful1e5/pokemon-cursor
cd pokemon-cursor && yarn build
- See Installing Pokemon Cursor.
Note Bitmaps are already generated in the
bitmaps
directory and managed by the maintainer (do not edit them directly).
First make sure you installed the build prerequisites.
Now that you have the dependencies, you can try build individual themes from bitmaps and
customize sizes, target platform, and etc. with the ctgen
CLI (packed with clickgen
).
Here are the default commands we used to build the Pokemon-cursor and packed them into yarn build
:
ctgen build.toml
Afterwards, the themes can be found in the themes
directory.
Note You can change the cursor size up to 200 because pngs are rendered with 200x200. If the cursor is resized by more than rendered png size, the final cursor will be blurred.
To build Windows cursor with size 16
:
Warning Windows cursor supports only one size, if multiple sizes are given with
-s
the first size will be considered in build.
ctgen build.toml -s 16 -p windows -c 'An unofficial Pokemon cursors with size 16'
You can also customize output directory with -o
option:
ctgen build.toml -s 16 -p windows -o 'out' -c 'An unofficial Pokemon cursors with size 16'
To build XCursor with size 16
:
ctgen build.toml -s 16 -p x11 -c 'An unofficial Pokemon cursors with size 16'
You can also assign multiple sizes to ctgen
for XCursors build:
ctgen build.toml -s 16 24 32 -p x11 -c 'An unofficial Pokemon cursors with size 16'
Bugs should be reported here on the Github issues page.
You can create a issue, I will help you.
Check CONTRIBUTING.md, any suggestions for features and contributions to the continuing code masterelopment can be made via the issue tracker or code contributions via a Fork
& Pull requests
.