[opensuse] Disable ability to switch between menu systems, how-to?
Hi list, I don't want my users to be able to switch away from the traditional SuSE/KDE menu system (i.e., select the new system). How do I do that? I suspect I'll need to put a "[$i]" into some KDE config file to lock it. Which and where ? -- ------------------------------------------------------------------------- Med venlig hilsen/Best regards Verner Kjærsgaard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 11 February 2007 09:39, Verner Kjærsgaard wrote:
I don't want my users to be able to switch away from the traditional SuSE/KDE menu system (i.e., select the new system). There are many ways of locking down the desktop (although most folks on this list will kringe at the very thought of such a thinng... too windoze like) so maybe if you spelled out a little further what it is (the big picture) that you are trying to accomplish with your user desktop.
When I was designing a user client-only desktop I started from scratch and built the desk with *only* the features I wanted the user to have. The user never gets a terminal, must run in X, KDM login (controlled), and only has access to the enterprise apps that they have a need to run. Is this what you are trying to do, or something else? -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mandag 12 februar 2007 22:23 skrev M Harris:
On Sunday 11 February 2007 09:39, Verner Kjærsgaard wrote:
I don't want my users to be able to switch away from the traditional SuSE/KDE menu system (i.e., select the new system).
There are many ways of locking down the desktop (although most folks on this list will kringe at the very thought of such a thinng... too windoze like) so maybe if you spelled out a little further what it is (the big picture) that you are trying to accomplish with your user desktop.
When I was designing a user client-only desktop I started from scratch and built the desk with *only* the features I wanted the user to have. The user never gets a terminal, must run in X, KDM login (controlled), and only has access to the enterprise apps that they have a need to run. Is this what you are trying to do, or something else?
-- Kind regards,
M Harris <><
Hi and thank you for your time! - I'm simply trying to prevent users from switching between the two KDE menusystems now offered in SuSE10.2. - I.e., I want them to stay on the "classsic" menusystem and not be able to select the new menu system in KDE. - But your answer was in another aspect very interesting... - I've used kiosktool a lot, it's not perfect, but it gets the job done. And then I use the kmenueditor to delete lots of stuff from the standard menu, as much as I really can. Then I copy the /home/myself/.config/menus/app...menu to the same location of the user in question. This gives the user a reduced menu. I then delete/rename my own copy - giving me my full menu back. - but I'd really like to be able to 100% tailor the KDE menu from the very beginning. Is this what you say you're able to do.. Quote: "When I was designing a user client-only desktop I started from scratch and built the desk with *only* the features I wanted the user to have" - eh, how did you start from scatch?? -- ------------------------------------------------------------------------- Med venlig hilsen/Best regards Verner Kjærsgaard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 14 February 2007 03:46, Verner Kjærsgaard wrote:
- but I'd really like to be able to 100% tailor the KDE menu from the very beginning. Is this what you say you're able to do..
Quote: "When I was designing a user client-only desktop I started from scratch and built the desk with *only* the features I wanted the user to have"
- eh, how did you start from scatch?? In my case the goal was to provide a very easy to use controlled (locked) interface so that maintenance clerks monitoring the four primary servers could run "only" a specified number of service apps in a controlled way. The user can not modify anything (read, can not delete|hurt anything), can not start a terminal--- they simply have a desk (clock, monitors, message panel, etc) and a non configurable menu list of stuff they are authorized to do... with options greyed out depending on user class. This may be the disappointing part for you... I didn't use kde. Initially the desk was built over twm. I later eventually decided to build the production service desk over fvwm. I wanted something with a *very* small footprint in memory and could be completely customized (literally from scratch) without any annoying hooks, etc. When I say *from scratch* I mean that I tailored an rc file for fvwm with my project specifically in mind from a blank text file. Typically Linux users want just the opposite from their workstation desktops... they want extensibility, flexibility, infinite configureability and so on... but I specifically wanted to create a server monitor and service desktop that was specifically designed (and locked) so that authorized service clerks could perform routine administration functions but without having a dangerous run of the system... if you know what I mean. Of course there is no reason why I could not have used kde (or any other desktop) for the same purpose with a larger footprint in memory... but the way I figure it if what you want is a customized service van then the best way is to proceed is to build-up from a panel van... not strip-down from a commercial luxury van.
As to your first question... wait patiently and someone with 10.2 expertise may answer your specific question... but you might snoop around first in ~/.kde/share Most of the kde specific control files are there. Just out of curiosity is the reason you want the second menu option removed to to prevent having to customize two sets of menus, or what? -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 14 February 2007 11:22, M Harris wrote:
- but I'd really like to be able to 100% tailor the KDE menu from the very beginning. Is this what you say you're able to do.. This is of course theoretically possible---absolutely. Most everything in Linux is a text file "someplace". (unlike windoze which uses binaries, ini files, and other hidden evil) You can make kde "look like" and "behave like" anything you want simply by altering several text files with your favorite text editor. (I still prefer vi but that is OT and completely another discussion) Suse has made kde look and feel like a well organized integrated homogeneous product that has a specific "Suse Aura". You could take a default kde built (and I would recommend that actually) and customize it so that it had your own look and feel... from scratch if you will. Suse went a step further and customized *customizing applications* like (yast, sax2, control panel specifics, system etc) which all integrate well with their own look and feel of kde (another way to say this is that Suse has lots of hooks into their flavor of kde). If you want to customize kde for your own complete look and feel, you would do better to start with the default kde from sources and build from there. IMHO.
-- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Onsdag 14 februar 2007 18:44 skrev M Harris:
On Wednesday 14 February 2007 11:22, M Harris wrote:
- but I'd really like to be able to 100% tailor the KDE menu from the very beginning. Is this what you say you're able to do..
This is of course theoretically possible---absolutely. Most everything in Linux is a text file "someplace". (unlike windoze which uses binaries, ini files, and other hidden evil) You can make kde "look like" and "behave like" anything you want simply by altering several text files with your favorite text editor. (I still prefer vi but that is OT and completely another discussion) Suse has made kde look and feel like a well organized integrated homogeneous product that has a specific "Suse Aura". You could take a default kde built (and I would recommend that actually) and customize it so that it had your own look and feel... from scratch if you will. Suse went a step further and customized *customizing applications* like (yast, sax2, control panel specifics, system etc) which all integrate well with their own look and feel of kde (another way to say this is that Suse has lots of hooks into their flavor of kde). If you want to customize kde for your own complete look and feel, you would do better to start with the default kde from sources and build from there. IMHO.
-- Kind regards,
M Harris <><
- thank you for your answers. They are of great help! - curiosity...yes. I don't want to maintain two menus, just one :-) - I see your point depicted by the van analogy... - I wish to use KDE due to all its eye candy. After all, the users are students from zero grade to 10th. grade. Never mind, thanks a lot for your answers! I'm off to it. -- ------------------------------------------------------------------------- Med venlig hilsen/Best regards Verner Kjærsgaard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
M Harris wrote:
Most everything in Linux is a text file "someplace". (unlike windoze which uses binaries, ini files, and other hidden evil) Taking that further: nearly everything in the whole system is from a text file. And those files are freely available. Configs, as stated, but also executable binaries, documents, even some pictures. You can change any part of the system with relative ease. And that is /the whole point/ of free software :-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
M Harris -
Russell Jones -
Verner Kjærsgaard