242
edits
CCK:Overview: Difference between revisions
m
no edit summary
No edit summary |
mNo edit summary |
||
| (10 intermediate revisions by 7 users not shown) | |||
| Line 84: | Line 84: | ||
And perhaps we can make the install piece use a mozilla.cfg file if it is available to combine the two (not just putting the jsc file on a server) | And perhaps we can make the install piece use a mozilla.cfg file if it is available to combine the two (not just putting the jsc file on a server) | ||
--[[User:Robin|Robin Lu]] 4/30 10:21:50 CST 2005 | |||
You are right. The mozilla.cfg should be added into install package by installer builder to enable the autoconfig by default. It is the connection point. | |||
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.) | |||
[[category:CCK|Overview]] | |||