Many people have forked and modified this over the years -- and are still using it! I find this awesome, but I also wish that more people would contribute their changes back...
To make this project easier to find and to receive contributions, I've put it onto github:
https://github.com/ewindisch/sd2xc
hi!
thanks for this piece of software, i am very keen to give it a try. but it works not for me. my suse81-perl fails with this message
---
Can't locate Config/IniFiles.pm in @INC (@INC contains: /usr/lib/perl5/5.8.0/i586-linux-thread-multi /usr/lib/perl5/5.8.0 /usr/lib/perl5/site_perl/5.8.0/i586-linux-thread-multi /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl .) at SD2XC-0.0.1.perl line 8.
BEGIN failed--compilation aborted at SD2XC-0.0.1.perl line 8.
---
i am neither programmer nor do i have perl -knowledge. i am sure that i have all "ImageMagick" dependend perl-packages installed.
am i stupid? ;)
bye,
pippi
I only get
Failed to open *main::INI: Filen eller katalogen finns inte at ./SD2XC-0.0.1.perl line 38
Cannot open Scheme.ini - at ./SD2XC-0.0.1.perl line 38.
How do i specify the .ini file to use
You should run it from within the directory of the theme, make sure it has been unpacked properly.
Extract the .CurXPTheme file(s) and then run the script. The CursorXP themes *must* have a Scheme.ini file.
The Xcursor-compatable theme will be extracted into a subdirectory called 'theme' which will be created, if it does not exist.
I've discovered that many were, infact, getting this while using the software properly.
It was an incompatability with perl versions under 5.8
Versions of SD2XC over 0.0.2 now work with perl 5.6.1 and possibly earlier.
I had a look at the code, and... at first glance I would say you're missing some symlinks to make qt work with the cursors. But otherwise looks good. (not tested _yet_ ;-P )
It just generates the theme, it doesn't install it.
I am looking at a few things now, in this order:
1. Convert native "Mighty Mouse" cursors (http://www.unsanity.com/haxies/mightymouse/)
2. Write packager for .deb and .rpm.
3. Convert Windows .ani and .cur files.
I'll let someone else write the KDE and Gnome theme selectors, for now.
I've had reports of problems by users of KDE using this program.
The user 'Deciare' states here
that users should create a ~/.icons/default directory and use that for their cursors.
Those instructions are incorrect and will cause an endless loop with the themes generated by this program (because the themes by default inherit from 'default').
The PROPER way to change the cursor is to edit the Xresources, setting
Xcursor.theme to the name of the theme.
Put in .Xdefaults (or .Xresources),
Xcursor.theme: ThemeName
And move your theme to:
~/.icons/ThemeName
or
/usr/X11R6/lib/X11/icons/
Hope this clears things up.
... unless you write "inherits=whiteglass/redglass" in the index.theme file.
Anyway, I wish somebody writes down an "official" manual about Xcursor, since this seems to be more or less a guess-work to know how it works, what-can-we-do, and what-we-shouldn't-do
The other "unknown" standard seems to be the icon location. The installation paths for cursors *were* in /usr/X11R6/lib/X11/icons (at least when I compiled last time).
But at least some packagers (see mdk) have changed it to /usr/share/icons
One needs to know where to install those icons before everyone chooses their own method, and we create several incompatible packages
XCursor is currently based on the freedesktop.org Icon Theme spec, which states that themes should be installed in either ~/.icons, /usr/share/icons, /usr/share/pixmaps, and optionally other app-specific directories (in that order).
The spec can be found at http://www.freedesktop.org/standards/icon-theme-spec.html
uga replied to the bit about the infinite loop, so I'll give you useless trivia instead. ;)
Another "proper" way to set the XCursor theme (without having to touch ~/.icons/default) is by adding
export XCURSOR_THEME=name_of_theme
to your ~/.bash_profile file and relogging in.
If you have root access, put your XCursor themes in /usr/share/icons/name_of_theme to make them accessible to all users.
Ratings & Comments
14 Comments
Many people have forked and modified this over the years -- and are still using it! I find this awesome, but I also wish that more people would contribute their changes back... To make this project easier to find and to receive contributions, I've put it onto github: https://github.com/ewindisch/sd2xc
hi! thanks for this piece of software, i am very keen to give it a try. but it works not for me. my suse81-perl fails with this message --- Can't locate Config/IniFiles.pm in @INC (@INC contains: /usr/lib/perl5/5.8.0/i586-linux-thread-multi /usr/lib/perl5/5.8.0 /usr/lib/perl5/site_perl/5.8.0/i586-linux-thread-multi /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl .) at SD2XC-0.0.1.perl line 8. BEGIN failed--compilation aborted at SD2XC-0.0.1.perl line 8. --- i am neither programmer nor do i have perl -knowledge. i am sure that i have all "ImageMagick" dependend perl-packages installed. am i stupid? ;) bye, pippi
I only get Failed to open *main::INI: Filen eller katalogen finns inte at ./SD2XC-0.0.1.perl line 38 Cannot open Scheme.ini - at ./SD2XC-0.0.1.perl line 38. How do i specify the .ini file to use
You should run it from within the directory of the theme, make sure it has been unpacked properly. Extract the .CurXPTheme file(s) and then run the script. The CursorXP themes *must* have a Scheme.ini file. The Xcursor-compatable theme will be extracted into a subdirectory called 'theme' which will be created, if it does not exist.
The format of .CurXPTheme files is .zip, so just extract it with 'unzip' or ark.
I've discovered that many were, infact, getting this while using the software properly. It was an incompatability with perl versions under 5.8 Versions of SD2XC over 0.0.2 now work with perl 5.6.1 and possibly earlier.
... it a try definetely ;-)
I had a look at the code, and... at first glance I would say you're missing some symlinks to make qt work with the cursors. But otherwise looks good. (not tested _yet_ ;-P )
It just generates the theme, it doesn't install it. I am looking at a few things now, in this order: 1. Convert native "Mighty Mouse" cursors (http://www.unsanity.com/haxies/mightymouse/) 2. Write packager for .deb and .rpm. 3. Convert Windows .ani and .cur files. I'll let someone else write the KDE and Gnome theme selectors, for now.
I've had reports of problems by users of KDE using this program. The user 'Deciare' states here that users should create a ~/.icons/default directory and use that for their cursors. Those instructions are incorrect and will cause an endless loop with the themes generated by this program (because the themes by default inherit from 'default'). The PROPER way to change the cursor is to edit the Xresources, setting Xcursor.theme to the name of the theme. Put in .Xdefaults (or .Xresources), Xcursor.theme: ThemeName And move your theme to: ~/.icons/ThemeName or /usr/X11R6/lib/X11/icons/ Hope this clears things up.
... unless you write "inherits=whiteglass/redglass" in the index.theme file. Anyway, I wish somebody writes down an "official" manual about Xcursor, since this seems to be more or less a guess-work to know how it works, what-can-we-do, and what-we-shouldn't-do
The other "unknown" standard seems to be the icon location. The installation paths for cursors *were* in /usr/X11R6/lib/X11/icons (at least when I compiled last time). But at least some packagers (see mdk) have changed it to /usr/share/icons One needs to know where to install those icons before everyone chooses their own method, and we create several incompatible packages
XCursor is currently based on the freedesktop.org Icon Theme spec, which states that themes should be installed in either ~/.icons, /usr/share/icons, /usr/share/pixmaps, and optionally other app-specific directories (in that order). The spec can be found at http://www.freedesktop.org/standards/icon-theme-spec.html
uga replied to the bit about the infinite loop, so I'll give you useless trivia instead. ;) Another "proper" way to set the XCursor theme (without having to touch ~/.icons/default) is by adding export XCURSOR_THEME=name_of_theme to your ~/.bash_profile file and relogging in. If you have root access, put your XCursor themes in /usr/share/icons/name_of_theme to make them accessible to all users.