- we need to change its name. this is the #1 comment i get from people who discover it's beauty because the name is usually what prevented them from trying it out sooner. people hate it when you hide cool stuff on them like that.
- we need to provide a way to make kiosk self documenting, preferably via KConfigXT files? i'm thinking we ought to extend the XML syntax to document kiosk related settings and effects.
- kiosktool v2. nuff said =)
are you going to be at aKademy and interested in taking kiosk to the next level? find me in malaga and let's talk. since becoming the kicker maintainer and doing more kiosk presentations lately i'm starting to build a healthy respect for the value of the system and how we need to improve it.
oh, and if you run into issues with kiosk, please communicate them. it seems people often just sit on their frustration. this is just a good way to ensure your frustration will be repeated ;)

5 comments:
You are spot on re. the name. I had suggested already 2 years ago to try find a better name (but couldn't think of one myself).
I find it quite hard to come up with something that sounds good, makes sense and is not taken already. Because I also thought about an alternative to FreeNX, or the upcoming KDE NX Client...
Uhmm... maybe we should ask your Gnome friends -- they are quite good to come up with "sexy" names. ;-)
Cheers,
Kurt
What is it about the name that makes people not try it? I have heard a number of users who simply don't try K named applications because of a general opinion about KDE. I thought Kiosk was fairly descriptive.
Bobby
> What is it about the name that
> makes people not try it?
system administrators don't create "kiosks", they create desktop deployments. it rarely occurs to them that something called "kiosk" would help them with that =)
Whatever happens to the 'Kiosk' (*insert new name here*) GUI front-end, it should probably be integrated more into any new KControl infrastructure in KDE 4 in a nicely laid out and logical interface.
If you want to learn how not to integrate administration GUI tools into a control centre set-up then you need look no further then the Group Policy and Active Directory tools in Windows 2003. They're not logically placed, and they're just plain awful to use.
We recently had Aaron do a Kiosk workshop for us. We marketed the event as a method for sys-admins to setup Kiosk systems. When we completed the workshop it was very obvious we could have had a larger turn out if we marketed a "KDE desktop deployment" workshop instead. We learned the error of our ways, but only after the fact.
So, a name other than "kiosk" would likely go a long way to reaching the appropriate people...
sgrover
Post a Comment