CCK:Overview: Difference between revisions

CCK:Overview (view source)

158 bytes added , 30 April 2005

no edit summary

6

edits

Revision as of 02:30, 30 April 2005 (view source) Robin (talk \| contribs) No edit summary ← Older edit		Revision as of 03:34, 30 April 2005 (view source) Robin (talk \| contribs) No edit summary Newer edit →
Line 88:		Line 88:
	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.		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. 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?