Re: A colorset spec

[Olivier C. <oli...@fr...>]

Mikhael Goikhman wrote:
> 
> On 28 Jul 2000 22:29:00 +0200, Olivier Chapuis wrote:

> > * Modules Colorsets
> > -------------------
> >
> > Colorset 10: default module colorset: FvwmPager FvwmButtonColorset.
> >  Can be use for *FvwmIconMan*Colorset FvwmIconBoxColorset (see also
> >  colorset 12)
> >
> > Colorset 11: hilight default colorset: for hilighting a part of
> >  of an FvwmButton or a certain swallowed applications.
> >
> > Colorset 12: special colorset: as 10 but a more funny colors a gradien
> >  or a pixmap.
> 
> I know you mean blackbox theme. 

No, this special color is already use in other themes as default,
olicha, aftersetp. The modules theme may want to have a clean
colorset for setting say the background of IconMan/Box or a more
funny color for these.

> Somehow I don't like the trick with
> substituting another colorset at run time when using certain theme.
> Maybe we should introduce an auto-conditional options in our CDDS, which
> are like current user-definable options, but switch is done automatically
> accourding to the given conditions. 

This will be great.


> > Colorset 13: Pager hilight colorset
> 
> Can't colorset 11 be used for this? I don't quite understand colorset 11.
>

Yes
 
> > Colorset 14: tips colorset (Pager, TaskBar)
> >
> > Colorset 15: colorsets for swallowed applications
> 
> Maybe swallowed applications should use colorsets 10/11? I don't know.
> 
> > Colorset 16: colorset for more colors in a swallowed application
> >  (e.g., xclock & xload have -hl & -hd color)
> 
> My previous idea to have -hl & -hd in one colorset (fg/bg) pobably can't
> work, because black/black is bad for bg/fg and I don't want to make this
> xclock/xload specific. On the other hand I have no better ideas.
> 
> > Colorset 17: colorset for a normal button in the AppMans (IconBox, IconMan,
> >  TaskBar, WinList)
> 
> AppMan name is ok, but I like more a generic name WinList for modules that
> show a list of windows. :)  AppList? But why app, it handles any window,
> it may be several windows per application. Somewhat off-topic.
> 
> > Colorset 18: colorset for a button which represent a window
> >  with the focus in the AppMans.
> >
> > Colorset 19: colorset for a button which represent an iconified
> >  window in the AppMans.
> 
> Still 3 colorsets for WinLists? There are so many boolean window states
> like iconified (maximized, shaded, sticky, visible), some of them may be
> supported in some feature, maybe to leave a colorset for this additional
> state? Or a bad idea?
> 
> But at least we need a way to mark a selected window button (i.e. the one
> with a mouse pointer on it). FvwmIconMan supports this. Alex wanted this
> and I promissed to do something here.
> 

So I have to add a colorset pointed button and reserve one colorset
for future use or more?

> > Colorset 20: FvwmIdentColorset
> >
> > Colorset 21: FvwmScrollColorset (do we need this colorset, colorset 32 is
> >   ok? or Colorset 0?)
> 
> Or 10. :) Well, probably we don't need this, but what colorset to use?
> Is it a good idea to suggest colorset 0 *or* 32 for FvwmScrollColorset?
> 
> > Colorset 22: FvwmConsole
> 
> Don't you like it to be the same color as a root term? :)
> 

I prefer a specific color, it can be the root colorset in some color
themes :)

> > Colorset 23: dynamic colorset (a colorset that can change during use
> >   without affecting the whole look, e.g., for FvwmScript-ColorsetBrowser)
> 
> Ok, temporary colorset. But should it belong to module colorsets?
> 
> > Colorset 24 to 25: reserved for modules themes
> >
> > Colorset 26 to 29: reserved for future use
> >
> > * Applications colorsets (Form and Script are here!)
> >
> > Colorset 30: default (text) colorset for terminal like application
> >   (E.g., xterm in our menu)
> >
> > Colorset 31: (text) colorset for remote shell/applications
> >
> > Colorset 32: (text) root colorset
> 
> We need a special term colorset (current 22), we use it in a special xterm
> viewer windows (top/less/tail -f), I worry about it more than about a root
> term colorset. Root term is not even that some people have, maybe to call
> it admin term colorset and include FvwmConsole term in it? :) Anyway in
> the future FvwmConsole will be FvwmCommand in xterm.
>

Yes but the future may be in a very long time ...
 
> I think it is ok to have a separate colorset for special viewers and text
> editors. The following was supposed to be should be 33, I think.
>

Yes, it is a good idea, but we may want to use a special colorset.

Olivier