| 
     
      
      
      From: Mikhael G. <mi...@co...> - 2000-09-30 21:58:13
      
     
   | 
On 30 Sep 2000 13:39:29 +0200, Jos van Riswick wrote: > > Im currently working on the cde theme, but I have some trouble > understanding what to do with the .cfg files. I don't really understand > the contents of the cfg files. And which of the files does the > theme-designer have to provide? In the man page for fvwm-theme-config > it says, that fvwm-themes-config --fresh generates 'theme.cfg', but > if I run that one, no file is produced. What files should I provide, > and what should be their contents? --fresh only generates theme.cfg in the user's current theme, it does not write any .cfg files in @cde or other themes, which are always read-only. Only 'current' theme is writable, it is auto-generated with help of theme.cfg files of all currently used themes (those components are used). ~/.fvwm/themes/current/theme.cfg should not be very interesting to you, this is a composition of all used theme.cfg's. The more interesting files for you are ~/.fvwm/themes-rc (and ~/.fvwm/themes-rc-2), this is .fvwm2rc. Sorry, but you should try to understand the format of .cfg files yourself until I write some readable doc (I may partially use this message). It is not hard if you undersand what are options & choices of a given component. Technically, component options are rc files, which are Read'd before or after the component's rc, the details are configurable in <component>.cfg. Every theme has its theme.cfg (if no, the default/theme.cfg is used). You should not really deal with theme.cfg, the one that is already in cde theme is good, just leave it as is. theme.cfg usually includes other .cfg files like colors.cfg, modules.cfg, you should only suply these files if you want to define properties of your component, like options, choices, their names, commands etc. You don't need colors.cfg if your colors@ component is simple and has no options. I suggest you to get some modules@ component in any theme as an example. See modules.cfg and modules/* rc files. Also after choosing this modules@ component, go to menu "Theme Management"/current/modules. You will see options. These options are defined in an appropriate modules.cfg. Again, if you don't need options in modules@cde, remove cde/modules.cfg and supply only modules/main, which can "Read" other files in cde/modules/. If you prefer an online talk (like irc), write to me about a day and hour. But without some homework, it will not be fully clear anyway. Regards, Mikhael.  |