6
edits
No edit summary |
No edit summary |
||
| Line 68: | Line 68: | ||
--[[User:MikeKaply|MikeKaply]] 08:38, 28 Apr 2005 (PDT) | --[[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? | 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? | ||
--[[User:Robin|Robin Lu]]-4/29 09:38:01 CST 2005 | |||
No. Some changes have to be in DTD/properties files for l10n reason. | |||
Can we divide CCK to two components? One cares about the default settings. Installer package builder if for that. A lot of changes can be made here, including preferences, DTD/properties, bookmarks, icons, RDF and more. The other cares about managing. MCD had both of the components while Netscape CCK only has the first one - installer builder. | |||
Right now, only preferences can be managed. Although we can use extension but it highly depends on the users, which is not a good way for management. What do you think should be managed besides preferences? | |||
edits