CCK:Overview: Difference between revisions

CCK:Overview (view source)

Revision as of 02:51, 28 April 2005

1,616 bytes added , 28 April 2005

no edit summary

Robin

6

edits

@@ Line 54: / Line 54: @@
 Or should it be an extension to Mozilla/Firefox/Thunderbird?
+--[[User:Robin|Robin Lu]]-4/28 10:29:53 CST 2005
+We made an MCD like tool before with Java. It contained two componnents. One is Installer Builder to build a customized installation package. The other is Configuration Editor to generate autoconfig.jsc and encoded .cfg file for centralized management of preferences (including locking). However, the project was canceled for business reason at last although we have already got a workable product for Mozilla 1.2 and Mozilla 1.4.
+We chose Java because at that time xul application was not as easy to make as today. Now it is a good choice to build the installer builder as a XUL app. In the fontend, we can collect customizing information and generate script like this:
+http://lxr.mozilla.org/mozilla/source/cck/ib/script_Windows.ib
+In the backend, we can either use native xpcom or native package builder to generate installer packages for different platform for different needs. It is very flexible. Our Installer Builder for Mozilla was able to generate RMP(linux only), tar.gz and Mozilla installer package for both Linux and Solaris. Though we haven't tested, it could be easy to generate installer package on Windows too.
+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.