Heh, 3 hours ago I was about to drop this little project. 3 hours later, I'm back thinking I can't do that. I can't just drop it and go away. I'm not that kind of person. I think blogging about one's complaints and stopping coding for 3 hours helps thinking better. Really, try it. I guess I didn't sleep enough, was stuck with the project and as a result I got a hit by the frustration. I was even thinking of joining the Gnom... nah! that's just not possible 
So what will I do to solve those library problems? Not sure, but even if I have to clone and rewrite ksvg to embed the code in, I'll do it. Anyway, enough of ranting for today. Oh, and sorry lyp :/
kdmthemes
You are talking about kdenonbeta/kdmthemes, right? I looked at the code a while ago, and I thought, "bleh, theme compatability with gdm just doesn't look like it was worth it".. I think most people would be perfectly happy with a flexibily themeable kdm and a quick and dirty gdm->kdm converter written in perl
" I think most people would b
" I think most people would be perfectly happy with a flexibily themeable kdm and a quick and dirty gdm->kdm converter written in perl"
I think you didn't bother reading the gdm themes spec. I don't think anyone got in mind to create a theme standard as flexible as that one
I've seen approaches in kde-look... but those are far less flexible than the gdm approach
more information on kdmthemes?
I never heard of kdmthemes, and google didn't tell me much either. That's probably the main reason for having few responses.
Is a web site about is planned?
What exactly is its purpose?
Which dependencies do exist?
>Is a web site about is plann
>Is a web site about is planned?
With the purpose of? This is not a separate project. It's based on kdm. You can browse the code under the KDE cvs servers.
>What exactly is its purpose?
To make kdm support 100% gdm themes, and use it as a standard, instead of creating tons of different standards. This way existing themes can be reused. I guess in future new features can be added, but so far this is the goal
> Which dependencies do exist?
SVG. Currently the svg render libs are under the module kdegraphics, while kdm is under kdebase. The other option is using external svg libraries, but that creates additional dependancies for KDE
kdelibs?
Shouldn't the SVG render libs be moved to the kdelibs module sometime anyway, with SVG icon rendering and ideally SVG graphic rendering in different KDE apps taking over the job of rendering static images in wizards and the likes? I really hope that all existing pixel graphics in KDE get converted to vector graphics in the long run.
kdmthemes
well, there is alot talkin' about kdm/gdm theming (on kde-look and bugs.kde.org), and I think compatibility whould be nice. Of course a converter whould do the same, but whouldnt it be nicer if kdm and gdm whould share their themes??? I'm no programmer, but I guess gdm's way of theming isnt that bad, at least it can do alot nice things...
btw and I really appreciate the work - right now I use gdm because of it's look, so if kdm could support gdm themes... i'd be very happy!