1,295
edits
CCK:Overview: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 89: | Line 89: | ||
For the menu lockdown, we should find out if admin want to lock the menu by default or they want to manage/change what to lock after deployment. I believe locking the menu by installer builder can meet most of the requirement. "Lock" is not the reason for it in management component. With installer builder, you can also lock some preferences by default. Management is about "change". What do you think? | For the menu lockdown, we should find out if admin want to lock the menu by default or they want to manage/change what to lock after deployment. I believe locking the menu by installer builder can meet most of the requirement. "Lock" is not the reason for it in management component. With installer builder, you can also lock some preferences by default. Management is about "change". What do you think? | ||
--[[User:Roc|Robert O'Callahan]] | |||
Just so you know ... Novell is working on code to use the gconf system pref service http://lxr.mozilla.org/mozilla/source/extensions/pref/system-pref/src/gconf/nsSystemPrefService.cpp. to lock prefs. gconf already supports "read only" system preferences that can't be overridden by users. We want to extend this support to the gconf system pref service so that the Mozilla pref is locked when the gconf pref is read-only. (Right now the way we do this is terrible, I need to fix it up.) | |||