219
edits
CCK:Overview: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 65: | Line 65: | ||
For centralized management, autoconfig still works for Firefox/Thunderbird/Mozilla. We can build a tool like the configuration editor in MCD as we did before, but I think to make a web application is more convinient. By using configuration editor, you have to generate the autoconfig.jsc locally and deploy it to the central server. If we build a web application, admin can maintain the configuration directly on the central server. | For centralized management, autoconfig still works for Firefox/Thunderbird/Mozilla. We can build a tool like the configuration editor in MCD as we did before, but I think to make a web application is more convinient. By using configuration editor, you have to generate the autoconfig.jsc locally and deploy it to the central server. If we build a web application, admin can maintain the configuration directly on the central server. | ||
--[[User:MikeKaply|MikeKaply]] 08:38, 28 Apr 2005 (PDT) | |||
Was there any effort made in the beginning to move some of the CCK specific changes into preferences, or was it always assumed that DTD/properties files would be modified? | |||