| Re: Too appleish
Mar 24 2008 on content tux logo proposal |
> Your logo seems to be inspired by the apple logo.
No it wasn't. It's a shape suggestion. I'm mere not skilled enough in vector graphics to make a neat "complete" logo. |
|  | | Re: userlist
Feb 20 2006 on content BlueTheme KDM Theme |
thx for your advice, just added the list on the left side. |
| | | Re: userlist
Feb 20 2006 on content BlueTheme KDM Theme |
thx for your advice, just added the list on the left pic. |
| | | Re: user list required
Aug 27 2005 on content BlueTheme KDM Theme |
State of the art: kdm doesn't support userlists (yet?). I dont know if this will change with the next main kde release (KDE4). For now you have to stuck with gdm as not all features and properties of its xml definition are ported to kdm. ;) |
| | | Re: Re: Re: Can't start
Jun 30 2005 on content ButtonMaker |
PIL (Python Image Library) is also needed. |
| | | Re: Can't start is
Jun 26 2005 on content ButtonMaker |
Yes. You have to get the qt-bindings for python, PyQT. There is no way around within this script, believe me. :) |
| | | Re: Re: Re: error
Jun 26 2005 on content ButtonMaker |
Plz check your system for all fontconfig-package related stuff. It should contain this file. Maybe it is missing in the debian package as another poster got the same problem, see above. Removing the doctype-tag may cause trouble with your font setup, it's your risk. |
| | | Re: Re: Re: error
Jun 21 2005 on content ButtonMaker |
Ok, I expected such errors due to my font implementation. At the moment the app only supports TT-fonts with "Times New Roman" as default. If the app couldnt find it at the beginning the fontDialog requests to choose another one. At this point I forgot to handle your cancel action, sorry for this, I will fix it(@SWaN).
@SWaN: Please make sure you have some TT-fonts installed (or FreeType), all non-TT-fonts from the dialog wont do it.
@ATAHUALPA: I couldnt find another way to catch the real path of the fontfile then by parsing your font installation. So the app looks into "etc/fonts"(where fonts-paths normally should be set up), catches all dirs from the conf-files and processes the font-cache of the found font dirs. This awkward way is expected to produce errors and if your font installation doesnt fit the above at any point, it will fail. Regarding your problem: the error says: "unknown url type: /etc/fonts/fonts.dtd" which means that you havent the "fonts.dtd" file in etc/fonts, so the conf-files couldnt be parsed because of the lack of the definition file. Just get this file and place it there. I dont know your dist., for SuSE you can find it in the fontconfig-package.
I am displeased about the font situation as well. If there is some interest in this program I plan to get rid of the PIL-Package, wich causes all these problems, maybe the whole thing becomes pure Qt-c++ code with a new design. |
| | | Re: $KDEDIR
Apr 8 2005 on content BlueTheme KDM Theme |
Sorry, don't know anything about PCLinuxOS' way of handling KDE-stuff, but $KDEDIR is a placeholder for the default install directory of the KDE-packages. Most often it will be in /opt/kde... or /usr/... . To simplify things, just try to get your kde-dir and replace $KDEDIR with the real path. |
| | | Re: Re: the big label
Apr 6 2005 on content LastSpring |
Now its all to my satifaction and a great theme, indeed ;-). Sorry for disturbing you (and the harsh tone before). |
| |
Search people
Current visitors
New users
Birthdays
Most active users
Back
|
|
