fvwm-themes-devel — Developing FVWM Themes

Re: Desk names

[Mikhael G. <mi...@ho...>]

On 28 Sep 2003 17:22:14 +0930, Alex Wallis wrote:
> 
> I've since begun to think laterally about this. Gnome uses the nautilus
> file manager to set the desktop background. Something I find most
> annoying personally. But the point is, if we are ever to become accepted
> again as a redhat package, we need more gnome compliance so we need to
> think more gnome-like. I believe kde uses a similar approach.
> 
> I propose desktop names should be set in the same component as the
> desktop background. Therefore ALL themes should have a desktop component
> to replace the background component that we currently use. The desktop
> component could therefore now contain also the ability to set the
> DesktopName as well.
> 
> I'm not sure how this could be implemented within my suggestion above,
> but it looks like a neat trick. I could however contrive a gui within my
> idea, that sets both the background (with FvwmBacker module) AND the
> desktop name. 

This may be thought out, but I don't really see benefits of combining
background and desknames components into one. I see disadvantages in
doing this, since one may want to use background image from one theme and
desk names from another (because he likes only the background image, but
not the names), or he may use the GNOME background and set the desk names
himself. I don't see a lot of correlation between both.

I think we should have 2 small GUI's, one for setting the root background
and one for setting desk names, but I may be wrong.

We may optionally disable setting of our desk names, i.e. use desk names
set by some other EWMH compliant application like Nautilus, but I don't
know yet what is the support of this in fvwm (I don't have Nautilus).

Regards,
Mikhael.

Re: Planning the new fvwm-themes release

[Mikhael G. <mi...@ho...>]

On 28 Sep 2003 21:24:21 +1000, Kathryn Andersen wrote:
> 
> On Sun, Sep 28, 2003 at 01:52:17AM +0300, Mikhael Goikhman wrote:
> > On 28 Sep 2003 07:04:37 +1000, Kathryn Andersen wrote:
> > > 
> > > On Sat, Sep 27, 2003 at 04:31:53PM +0300, Mikhael Goikhman wrote:
> > > >   * Do something with plainbow and celticbow themes, they don't seem to
> > > >   be finished. Probably add configurable colors like in CDE theme.
> > > 
> > > I didn't realize there was anything that needed doing.  How are they not
> > > "finished"?
> > 
> > Ok, if you think they are finished, then background.cpp and colors.cpp
> > may be removed, since they are not used.
> 
> Well... it all depends on what you mean by finished.  No, there is no
> colour-switching stuff in there, because I couldn't think of a simple
> easy way of translating what I had into something indepentent and purely
> fvwm-themes... so it got put in the too-hard basket and never taken out.

If you understand how CDE or Luthien colors work (colors.cfg and colors
directory), then it will be the same if you decide to do it configurable.
I will most probable convert them from using FvwmM4 to FvwmPerl.

In my emails here I always imply that we all use the latest fvwm cvs.

> > I think inactive window title in celticbow theme is a bit unreadable,
> > probably MultiPixmap may be used, or different colors.
> 
> I'm not sure I follow what you mean by using MultiPixmap for it...

I only meant that it may be done more readable by defining another
background under the text (MultiPixmap enables this). Or may be not.

> > Also fonts used in modules may be choosen to be more attractive, several
> > alternatives may be separated using a comma or a semicolon.
> 
> I never looked at fonts, I must admit.

It is a good opportunity to do it now. :)

Regards,
Mikhael.

Re: Planning the new fvwm-themes release

[Kathryn A. <kat...@ka...>]

On Sun, Sep 28, 2003 at 01:52:17AM +0300, Mikhael Goikhman wrote:
> On 28 Sep 2003 07:04:37 +1000, Kathryn Andersen wrote:
> > 
> > On Sat, Sep 27, 2003 at 04:31:53PM +0300, Mikhael Goikhman wrote:
> > >   * Do something with plainbow and celticbow themes, they don't seem to
> > >   be finished. Probably add configurable colors like in CDE theme.
> > 
> > I didn't realize there was anything that needed doing.  How are they not
> > "finished"?
> 
> Ok, if you think they are finished, then background.cpp and colors.cpp
> may be removed, since they are not used.

Well... it all depends on what you mean by finished.  No, there is no
colour-switching stuff in there, because I couldn't think of a simple
easy way of translating what I had into something indepentent and purely
fvwm-themes... so it got put in the too-hard basket and never taken out.
 
> I think inactive window title in celticbow theme is a bit unreadable,
> probably MultiPixmap may be used, or different colors.

I'm not sure I follow what you mean by using MultiPixmap for it...
 
> Also fonts used in modules may be choosen to be more attractive, several
> alternatives may be separated using a comma or a semicolon.

I never looked at fonts, I must admit.
 
Kathryn Andersen
-=-=-=-=-=-=-=-=-
Jim: What's this?
Blair: It's food, Jim. You remember that?	(Sentinel: Deep Water)
-- 
 _--_|\	    | Kathryn Andersen	<http://www.katspace.com>
/      \    | 
\_.--.*/    | GenFicCrit mailing list <http://www.katspace.com/gen_fic_crit/>
      v	    | 
------------| Melbourne -> Victoria -> Australia -> Southern Hemisphere
Maranatha!  |	-> Earth -> Sol -> Milky Way Galaxy -> Universe

Re: Desk names

[Alex W. <aw...@pr...>]

Mikhael Goikhman wrote:
> 
> On 22 Jan 2003 02:20:29 +1030, Alex Wallis wrote:
> >
> > Mikhael Goikhman wrote:
> >
> > In order for the above approach to work it is necessary to have
> > $FVWM_USERDIR set as an exported variable AND to have an existing
> > $FVWM_USERDIR/themes/personal/ directory, neither of which existed on my
> > newly installed redhat 8.0 system.
> 
> If $FVWM_USERDIR is not set by a user, then it is always set by fvwm and
> sometimes by fvwm-themes. Do you try to run something outside of fvwm?

No, at the time I wrote that it appeared that typing into an FvwmConsole
the command "Exec echo $FVWM_USERDIR" did NOT show the expected result
to the stdout on the console where X was running, but it does now. Maybe
something has changed? *shrug* Go figure!

> 
> > If these are now to become a
> > requirement for running fvwm-themes I think it may be more appropriate
> > for the install process to create and set these up rather than a gui
> > which may not even be run by a new user.
> 
> It is probably a good idea to automatically create directory
> $FVWM_USERDIR/themes/personal/ on startup together with some others.
> I think, it is currently only needed for menu editor.

Probably still a good idea!  ;)

> 
> > Alternatively, what about adding an extra section for Desk Names to the
> > Settings? Perhaps the menu could be made to display the list of current
> > $[desk.name<n>]'s and a mouse click activates the gui to change each one
> > specifically? I'm not sure how it may contrived to work with various
> > themes with different numbers of configured desktops. We may have to
> > impose a predefined set limit of the maximum number of desktop but I
> > would not favour this.
> 
> I like an idea of a menu, something like Configuration / Desk Names
> submenu with 4 items for names of desks 0, 1, 2, 3. There may be probably
> additional item "Set number of desks" to set the first and last numbers,
> every menu item recreates themes/personal/desknames. I think we should go
> with a new component desknames@, so it is integrated well and we may
> define dependancies rather than a number of hacks for each such problem.

I've since begun to think laterally about this. Gnome uses the nautilus
file manager to set the desktop background. Something I find most
annoying personally. But the point is, if we are ever to become accepted
again as a redhat package, we need more gnome compliance so we need to
think more gnome-like. I believe kde uses a similar approach.

I propose desktop names should be set in the same component as the
desktop background. Therefore ALL themes should have a desktop component
to replace the background component that we currently use. The desktop
component could therefore now contain also the ability to set the
DesktopName as well.

> 
> This component may look like:
> 
>   DesktopName 0 "Main"
>   DesktopName 1 "FVWM"
>   DesktopName 2 "Work"
>   DesktopName 3 "Fun"
> 
> This is the command that builds the menu from it (just an example):
> 
> PipeRead "perl -ne 's/[^ ]+ ([^ ]+) (.+)/+ "Desk $$1: "$$2 \
>         FuncFvwmPromptNewDeskName $$1/' \
>         <`fvwm-themes-config --component desknames --show-value read-file`"
> 
> Every menu item should actually recreate desknames@personal and restart
> themes after prompting for a new name. Maybe in the future we will have
> more advanced component options or/and settings@default that would enable
> generic editing of such things, but currently this seems to be a good
> solution. I will implement it if there are no other suggestions.

I'm not sure how this could be implemented within my suggestion above,
but it looks like a neat trick. I could however contrive a gui within my
idea, that sets both the background (with FvwmBacker module) AND the
desktop name. 

> 
> Regards,
> Mikhael.
> 

Has anyone looked at the new fedora.redhat.com project? It looks like an
excellent way to both improve fvwm-themes' user acceptance and it's user
base, not to mention fvwm itself. Most people on #fedora think fvwm is a
dead project apparently.

Cheers,
Alex
--
<joke>
P.S. Do you have a time machine? My original reply was 8 months ago and
the recent Changelog entries have a date that's a year old? 
</joke>

Re: Planing the new fvwm-themes release

[Alex W. <aw...@pr...>]

Mikhael Goikhman wrote:
>
<snip>
>   * Remove Awol theme. It was not updated for years. Optionally replace
>   it by a new Awol theme if Alex sends it in the following 2 weeks.

I should have an updated awol theme ready by the end of this week. It
may be best to replace the old awol theme totally as most of it has
changed now.

<snip>
> 
>   * Optionally. Have a generic FvwmButtons builder (perl script or
>   module) that gets input (bar size and some options) and enables to
>   add/replace application items using a dialog, each item has icon,
>   optional title and command line.  It may be used for several purposes:
>   configuring applications used in modules of all our themes, or
>   emulating Windows-like desktop icons.

Given FvwmButtons extreme configurability I'm not sure how useful this
may be? Everyone seems to have their own ideas how they want their
FvwmButtons to look. I would like to hear more ideas on your proposal
for this though, but I suspect perl may be the only tool powerful enough
to achieve this.


Cheers, 
Alex.

Re: Planing the new fvwm-themes release

[S. A. <sa...@xm...>]

On Sat, Sep 27, 2003 at 04:31:53PM +0300, Mikhael Goikhman wrote:
>   * Users didn't like modules in OSX, except for the top panel.
>   Shawn, can you design something (probably completely) different that is
>   more in the spirit of MacOS X? If no, I think the default should be not
>   to show modules at the bottom.

The modules at the bottom should definitely go... The only think I can
think of is to have a FvwmButton app launcher, similar to the one in the
top right corner of the Olicha theme. But this would be more Mac OS 9
style. Does anyone have an other idea?

>   * Images for RedmondXP panel should be transparent when possible.
>   I.e. they should not include the blue gradient-like background.
>   I tried to make a separator in PNG using alpha channel so that it is
>   possible to apply it to any background (not just blue gradient),
>   but it is not as nice as the non-transparent one. I am not an artist.
>   Shawn, can you help here? Basically all non-transparent images should be
>   converted to transparent except for the real background.
> 

I made a couple transparent test images, http://www.xmission.com/~sa/fvwm/
Let me know if they are ok, or should i try again...
Do you want the same kind of thing for the titlebar, etc?

Crux, Transparent theme, Task Switcher

[Timothy B. <be...@cs...>]

> Sorry for the long delay. We should return to work on finalizing 0.7.0.
> I plan to activaly work to make it happen in the second half of October.
> 
> My plans are these:
> 
>   * Remove Unsafe theme.
I really liked that one though, even if it was non-standard.


>   * Optionally. We need Transparent theme. Who wants to do it?

I have already made some progress on a transparent theme, and I would be 
willing to contribute when it is done.  In this theme, I would assume that you would
want a transparent:
pager	(done)
menus
decors

Anyway, I could get it done in about two weeks.

 
>   * Optionally. Add one theme from Susanne configs (Elberg, Crux?).

It would be great to see a Port of Susanne's Crux to Fvwm-themes, I would be willing to help.  
Just a question though, would it be difficult to grab the gtk+ theme color for the 
window decoration?

> Please help me doing in these things (and others if I missed something).
> Tell what you like to work on. I don't have a time to do it all myself.

I would like to make a function to improve the  fvwm task switcher.  Its decent,
though I would like to see one that switches on each keypress, and on the
keyrelease the menu would disappear.  Would adding something of this nature
be difficult to change without modifying fvwm's internals?

I made several attempts to improve it, but each was flawed, so I wasn't sure exactly what to do.
Anyway, I made numerous usability tweaks to my theme that would help other people make 
very interesting themes, but my decors are nothing that great at the current time.  
When I get that sorted out I will submit something.

Regards,
Tim

Re: Planning the new fvwm-themes release

[Mikhael G. <mi...@ho...>]

On 28 Sep 2003 07:04:37 +1000, Kathryn Andersen wrote:
> 
> On Sat, Sep 27, 2003 at 04:31:53PM +0300, Mikhael Goikhman wrote:
> >   * Do something with plainbow and celticbow themes, they don't seem to
> >   be finished. Probably add configurable colors like in CDE theme.
> 
> I didn't realize there was anything that needed doing.  How are they not
> "finished"?

Ok, if you think they are finished, then background.cpp and colors.cpp
may be removed, since they are not used.

I think inactive window title in celticbow theme is a bit unreadable,
probably MultiPixmap may be used, or different colors.

Also fonts used in modules may be choosen to be more attractive, several
alternatives may be separated using a comma or a semicolon.

Regards,
Mikhael.

Re: Planing the new fvwm-themes release

[Kathryn A. <kat...@ka...>]

On Sat, Sep 27, 2003 at 04:31:53PM +0300, Mikhael Goikhman wrote:
>   * Do something with plainbow and celticbow themes, they don't seem to
>   be finished. Probably add configurable colors like in CDE theme.
I didn't realize there was anything that needed doing.  How are they not
"finished"?

-- 
 _--_|\	    | Kathryn Andersen	<http://www.katspace.com>
/      \    | 
\_.--.*/    | GenFicCrit mailing list <http://www.katspace.com/gen_fic_crit/>
      v	    | 
------------| Melbourne -> Victoria -> Australia -> Southern Hemisphere
Maranatha!  |	-> Earth -> Sol -> Milky Way Galaxy -> Universe

Re: Desk names

[Mikhael G. <mi...@ho...>]

On 22 Jan 2003 02:20:29 +1030, Alex Wallis wrote:
> 
> Mikhael Goikhman wrote:
> > 
> > We need to let users to change the names of desks.
> > Currently we have this in modules/main:
> > 
> >   DesktopName 0 Main
> >   DesktopName 1 Internet
> >   DesktopName 2 Work
> >   DesktopName 3 Games
> > 
> > We may move this to a new component desknames or desktopnames.
> > Or leave as is, but still have this new component. This does not matter
> > for now. What matters is we need a form to create this component.
> > 
> > Alex, can you think about a way to do it conveniently. It may use some
> > unix commands like "touch $FVWM_USERDIR/themes/personal/desknames" and
> > "perl -pi -e 's{DesktopName 3 Games}{DesktopName 3 Media}'
> > $FVWM_USERDIR/themes/personal/desknames". You may choose whether to
> > use FvwmForm or FvwmGtk or whatever else. Whether to name only 4 desktops
> > or any numbers with possible gaps. Use $[desk.name2] after I fix it.
> 
> In order for the above approach to work it is necessary to have
> $FVWM_USERDIR set as an exported variable AND to have an existing
> $FVWM_USERDIR/themes/personal/ directory, neither of which existed on my
> newly installed redhat 8.0 system.

If $FVWM_USERDIR is not set by a user, then it is always set by fvwm and
sometimes by fvwm-themes. Do you try to run something outside of fvwm?

> If these are now to become a
> requirement for running fvwm-themes I think it may be more appropriate
> for the install process to create and set these up rather than a gui
> which may not even be run by a new user.

It is probably a good idea to automatically create directory
$FVWM_USERDIR/themes/personal/ on startup together with some others.
I think, it is currently only needed for menu editor.

> Alternatively, what about adding an extra section for Desk Names to the
> Settings? Perhaps the menu could be made to display the list of current
> $[desk.name<n>]'s and a mouse click activates the gui to change each one
> specifically? I'm not sure how it may contrived to work with various
> themes with different numbers of configured desktops. We may have to
> impose a predefined set limit of the maximum number of desktop but I
> would not favour this.

I like an idea of a menu, something like Configuration / Desk Names
submenu with 4 items for names of desks 0, 1, 2, 3. There may be probably
additional item "Set number of desks" to set the first and last numbers,
every menu item recreates themes/personal/desknames. I think we should go
with a new component desknames@, so it is integrated well and we may
define dependancies rather than a number of hacks for each such problem.

This component may look like:

  DesktopName 0 "Main"
  DesktopName 1 "FVWM"
  DesktopName 2 "Work"
  DesktopName 3 "Fun"

This is the command that builds the menu from it (just an example):

PipeRead "perl -ne 's/[^ ]+ ([^ ]+) (.+)/+ "Desk $$1: "$$2 \
	FuncFvwmPromptNewDeskName $$1/' \
	<`fvwm-themes-config --component desknames --show-value read-file`"

Every menu item should actually recreate desknames@personal and restart
themes after prompting for a new name. Maybe in the future we will have
more advanced component options or/and settings@default that would enable
generic editing of such things, but currently this seems to be a good
solution. I will implement it if there are no other suggestions.

Regards,
Mikhael.

Planing the new fvwm-themes release

[Mikhael G. <mi...@ho...>]

Sorry for the long delay. We should return to work on finalizing 0.7.0.
I plan to activaly work to make it happen in the second half of October.

My plans are these:

  * Remove Unsafe theme.

  * Remove Awol theme. It was not updated for years. Optionally replace
  it by a new Awol theme if Alex sends it in the following 2 weeks.

  * Replace all FvwmM4 and FvwmCpp preprocessing with FvwmPerl, since it
  seems to cause problems on systems without m4, cpp and non GNU awk.

  * Do something with plainbow and celticbow themes, they don't seem to
  be finished. Probably add configurable colors like in CDE theme.

  * Solve somehow the problem with colorsets. Some themes (RedmondXP,
  Migo, Sa) do not clean up some settings, so the next theme colors look
  incorrectly. Probably we need some help from Olivier in fvwm itself, so
  it is possible to clean up all Tint and Alpha attributes with a simple
  flag, like NoEffects. Then we add this flag to all colorsets. Thoughts?

  * Optionally. We need Transparent theme. Who wants to do it?

  * Optionally. Add one theme from Susanne configs (Elberg, Crux?).

  * Optionally. Add one theme from Dorothy configs (Purple, ABC?).

  * Optionally. Have a generic FvwmButtons builder (perl script or
  module) that gets input (bar size and some options) and enables to
  add/replace application items using a dialog, each item has icon,
  optional title and command line.  It may be used for several purposes:
  configuring applications used in modules of all our themes, or
  emulating Windows-like desktop icons.

Optional items should most probably be postponed to 0.7.1+. But if
someone may do it now, they will be included in 0.7.0.

I also repost the items that were posted some months ago:

  * Users didn't like modules in OSX, except for the top panel.
  Shawn, can you design something (probably completely) different that is
  more in the spirit of MacOS X? If no, I think the default should be not
  to show modules at the bottom.

  * Images for RedmondXP panel should be transparent when possible.
  I.e. they should not include the blue gradient-like background.
  I tried to make a separator in PNG using alpha channel so that it is
  possible to apply it to any background (not just blue gradient),
  but it is not as nice as the non-transparent one. I am not an artist.
  Shawn, can you help here? Basically all non-transparent images should be
  converted to transparent except for the real background.

Please help me doing in these things (and others if I missed something).
Tell what you like to work on. I don't have a time to do it all myself.

Regards,
Mikhael.

Re: FVWM-Themes-devel digest, Vol 1 #370 - 1 msg

[Mikhael G. <mi...@ho...>]

On 11 Sep 2003 17:16:35 -0700, Timothy Beyer wrote:
> 
> Thanks for the help Mikhael and Oliver, I'll try the pager font trick.
> 
> By the way, I can't believe my spelling in the last email! I should not
> have typed it in such haste. ;)

Please also always change the subject to something meaningful when you
reply to the digest message.

> Anyway, I have a few more theme related questions.  First of all, I am not
> sure exactly how to get the name of a font in the proper notation for
> FVWM.  Is that from the fonts.dir files in the fonts folder? I wanted to
> use the xft font Bitstream Sans 8, and I couldn't seem to get it to work.
> Is it possible to simply refer to the font in quotes?

Search for /FONT in your man page, it should describe the correct syntax.
There are 3 font sections in the current fvwm version.

> Second, regarding the menus in fvwm, is there a way to make the menu
> display in a fixed position (relative to a window or a fixed coordinate as
> opposed to focus follows mouse) without using modules from fvwm95? I
> looked at the Redmond and RedmondXP themes, and I was planning on doing
> something like that, but I didn't want to overuse modules if I don't need
> to do so.

You should use the menu position hints (the parameters following Menu
name). See the man page entry for the Menu command. Use "try and see"
approach, noone may say definitely what different contexts and offsets
do exactly without trying them.

> And third, is there a specific menu policy set for how the menu should be
> designed in fvwm-themes? I made a substantially different menu (or at
> least a much simpler menu) than the
> one used in the other themes, and I was wondering how I could make it more
> compliant.  I merged the content from menus-programs into the menus file,
> though I wasn't sure if this might cause problems with other themes.

You may create your own menus@ component, but be aware that any new item
that we will add to the menus@default will not be reflected in your
component and you should synchronize it later yourself (if needed). Other
than this, you may put anything you want in your menus@ and may have it
to include application menus (the ones that defined in menus-programs@)
and personal menu from menus-extra@personal. You don't really need to
define menus-programs@ component in your theme if you like the default.

Regards,
Mikhael.

Re: FVWM-Themes-devel digest, Vol 1 #370 - 1 msg

[Timothy B. <be...@cs...>]

Thanks for the help Mikhael and Oliver, I'll try the pager font trick.

By the way, I can't believe my spelling in the last email! I should not
have typed it in such haste. ;)

Anyway, I have a few more theme related questions.  First of all, I am not
sure exactly how to get the name of a font in the proper notation for
FVWM.  Is that from the fonts.dir files in the fonts folder? I wanted to
use the xft font Bitstream Sans 8, and I couldn't seem to get it to work.
Is it possible to simply refer to the font in quotes?

Second, regarding the menus in fvwm, is there a way to make the menu
display in a fixed position (relative to a window or a fixed coordinate as
opposed to focus follows mouse) without using modules from fvwm95? I
looked at the Redmond and RedmondXP themes, and I was planning on doing
something like that, but I didn't want to overuse modules if I don't need
to do so.

And third, is there a specific menu policy set for how the menu should be
designed in fvwm-themes? I made a substantially different menu (or at
least a much simpler menu) than the
one used in the other themes, and I was wondering how I could make it more
compliant.  I merged the content from menus-programs into the menus file,
though I wasn't sure if this might cause problems with other themes.

Regards,
Tim

Re: transparency, pager questions

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

On Tue, Sep 09, 2003 at 04:21:16PM -0700, Timothy Beyer wrote:
> Hello, I am designing a theme in which I have a transparent pager
> (Actually it uses Pager-Desker) and although the transparency works, I
> would like to make the pager "always on top."  My problem is that I want
> to be able to see applications below the pager, not just the wallpaper.
> Is that possible?
> 
> Also, is it possible to hide the name of each workspace on the
> Pager-Desker
> 

The good option is

*FvwmPager-Desker: Font none

Regards, Olivier

Re: transparency, pager questions

[Mikhael G. <mi...@ho...>]

On 09 Sep 2003 16:21:16 -0700, Timothy Beyer wrote:
> 
> Hello, I am designing a theme in which I have a transparent pager
> (Actually it uses Pager-Desker) and although the transparency works, I
> would like to make the pager "always on top."  My problem is that I want
> to be able to see applications below the pager, not just the wallpaper.
> Is that possible?

Not currently.

> Also, is it possible to hide the name of each workspace on the
> Pager-Desker

I thought there is an option for this, but I can't find it in the man
page. You may use ShapeLabels to reduce the number of labels to one.
You may also use tiny font or otherwise choose the HilightColorset so
that the label in invisible.

> Last but not least, I would like to make a gtk 1 or 2 menu in my theme in
> my theme, how would I go about doing that.

You may define Personal menu in menus-extra@personal, if you need
something else, specify what do you want to add exactly and to which
submenu. There is no easy answer, I would not redefine menus@ component
if possible, since then you will lose any additions we add in the future.

> By the way, I would like to submit my theme to fvwm-themes when it reaches
> completition.

Ok.

Regards,
Mikhael.

transparency, pager questions

[Timothy B. <be...@cs...>]

Hello, I am designing a theme in which I have a transparent pager
(Actually it uses Pager-Desker) and although the transparency works, I
would like to make the pager "always on top."  My problem is that I want
to be able to see applications below the pager, not just the wallpaper.
Is that possible?

Also, is it possible to hide the name of each workspace on the
Pager-Desker

ie. I want to change

---------
| fvwm  |
---------
|   |   |
|-------|
|   |   |
---------
|  net  |
---------
|   |   |
|-------|
|   |   |
---------

to

---------
|   |   |
|-------|
|   |   |
---------
|   |   |
|-------|
|   |   |
---------


(I apologize for my awful ascii artwork...)


Last but not least, I would like to make a gtk 1 or 2 menu in my theme in
my theme, how would I go about doing that.

By the way, I would like to submit my theme to fvwm-themes when it reaches
completition.

Regards,
Tim

Re: Button FRAME 0/1 question...

[Mikhael G. <mi...@ho...>]

On 21 Jul 2003 10:42:30 -0600, mik...@ag... wrote:
> 
> Buttons of FRAME type 1 (raised) will depress (sink) when clicked.  Can
> FRAME type 0 buttons be configured to depress as well?  The problem is
> that there is no visual feedback when a FRAME 0 is clicked, at lease in
> the theme I'm currently working with.  Any work-arounds?

To find a workaround we should understand and see the problem.
Which relevant theme components do you use? Which fvwm-themes version?

Regards,
Mikhael.

Button FRAME 0/1 question...

[<mik...@ag...>]

Buttons of FRAME type 1 (raised) will depress (sink) when clicked.  Can FRAME type 0 buttons
be configured to depress as well?  The problem is that there is no visual feedback when a FRAME 0 is
clicked, at lease in the theme I'm currently working with.  Any work-arounds?

Thanks,
MikeB

---
Michael A. Burns
Agilent Technologies
Engineering Services
Santa Rosa, CA

mik...@ag...
(707) 577-3682

RE: Themes window repaint problem?

[<mik...@ag...>]

Hi MikHael,

That fixed it.  The BackingStore option did it.  I also remember having
to set this in the XF86Conf file to get this app to work correctly. I
just didn't realize it was being turned off in themes.

Also, the link to the mail archive in:

   http://lists.sourceforge.net/lists/listinfo/fvwm-themes-devel

is having problems...for me anyway.

Thanks again for your prompt help.

Regards,
MikeB

> -----Original Message-----
> From: Mikhael Goikhman [mailto:mi...@ho...]
> Sent: Wednesday, July 09, 2003 1:51 PM
> To: mik...@ag...
> Cc: fvw...@li...
> Subject: Re: Themes window repaint problem?
> 
> 
> On 09 Jul 2003 14:19:52 -0600, mik...@ag... wrote:
> > 
> > We've recently come across a situation where one of our 
> X-window apps
> > is not repainting when another window is raised on top then 
> lowered. 
> > When running fvwm without themes, the problem doesn't exit. 
>  It's only
> > when themes is started do we see this anomaly.
> 
> Unfortunately this report is not very useful. I don't see 
> such problems.
> Can you somehow make it reproducible? One of the ways is to create a
> minimal-config and run "fvwm -f minimal-config" and writing exact
> instructions of what you do and exact applications that you 
> start. Then
> write similar instructions for fvwm-themes. Do "Reset all to default"
> before trying the test case, so we can easily reproduce this. 
> Report fvwm
> and fvwm-themes versions you use.
> 
> But I am a bit negative that fvwm and any configuration like 
> fvwm-themes
> may cause the application window repaint problems. It is more 
> likely that
> your application or X are problematic.
> 
> Actually there are some settings that may affect this a bit.
> Open FvwmConsole (Alt-F12) and try different combinations of:
> 
>   Style * SaveUnder     # or: SaveUnderOff
>   Style * BackingStore  # or: BackingStoreOff
> 
> > I couldn't get to the mail archives, so please excuse me if 
> this issue
> > has already been discussed.
> 
> What is the problem with the mail archives?
> Anyway, this topic was not discussed.
> 
> Regards,
> Mikhael.
> 

Re: Themes window repaint problem?

[Mikhael G. <mi...@ho...>]

On 09 Jul 2003 14:19:52 -0600, mik...@ag... wrote:
> 
> We've recently come across a situation where one of our X-window apps
> is not repainting when another window is raised on top then lowered. 
> When running fvwm without themes, the problem doesn't exit.  It's only
> when themes is started do we see this anomaly.

Unfortunately this report is not very useful. I don't see such problems.
Can you somehow make it reproducible? One of the ways is to create a
minimal-config and run "fvwm -f minimal-config" and writing exact
instructions of what you do and exact applications that you start. Then
write similar instructions for fvwm-themes. Do "Reset all to default"
before trying the test case, so we can easily reproduce this. Report fvwm
and fvwm-themes versions you use.

But I am a bit negative that fvwm and any configuration like fvwm-themes
may cause the application window repaint problems. It is more likely that
your application or X are problematic.

Actually there are some settings that may affect this a bit.
Open FvwmConsole (Alt-F12) and try different combinations of:

  Style * SaveUnder     # or: SaveUnderOff
  Style * BackingStore  # or: BackingStoreOff

> I couldn't get to the mail archives, so please excuse me if this issue
> has already been discussed.

What is the problem with the mail archives?
Anyway, this topic was not discussed.

Regards,
Mikhael.

Themes window repaint problem?

[<mik...@ag...>]

Hello Themes Team,

We've recently come across a situation where one of our X-window apps is not
repainting when another window is raised on top then lowered.  When running
fvwm without themes, the problem doesn't exit.  It's only when themes is started
do we see this anomaly.  I couldn't get to the mail archives, so please excuse 
me if this issue has already been discussed.

Any help/suggestions would be greatly appreciated.

Many Thanks,
MikeB

---
Michael A. Burns
Agilent Technologies
Engineering Services
Santa Rosa, CA

mik...@ag...
(707) 577-3682

Re: Question to Icons

[Mikhael G. <mi...@ho...>]

On 07 May 2003 17:18:18 +0200, Smiler wrote:
> 
> How can i disable the Icons from menu witch i have integrate from 
> /etc/X11/fvwm/menudefs.hook?
> Because the blackbox-theme display a wrong menu on Icons.

I don't understand this. What does it mean, "wrong menu on Icons"?
Do you mean, "wrong icons in menu"?

Show the menu configuration and components that you used and describe
exactly what you see and what you want to see.

In case you want to *enable* icons in menus, choose another component
than menustyle@blackbox, which has ItemFormat with no menu icons.

Regards,
Mikhael.

Question to Icons

[Smiler <smi...@we...>]

How can i disable the Icons from menu witch i have integrate from 
/etc/X11/fvwm/menudefs.hook?
Because the blackbox-theme display a wrong menu on Icons.

Grettings
Andrei

Re: Updated debian package

[Mikhael G. <mi...@ho...>]

On 03 May 2003 18:30:57 +0200, Smiler wrote:
> 
> >In the future someone else should maintain these packages.
> >We may discuss this later.
> 
> It is your decision, but explain pleace.
> Because i have many time spent, to this project.
> And you have many time spent to me.
> I can't understood this step. On that score it hits me strong.

I think you didn't understand me. By "someone else should maintain these
packages" I mean these packages should be added to several places.
I can do this now, but in the future someone else (not me) should do this.

Andrei, I would like you to maintain Debian packages if you are ready to
spend a time and create a package every time a new release is out.
Do you prefer to create Debian packages and submit it to this list or you
want to add fvwm-themes to the official Debian using the Debian policy?

I already said this several times: for me the best solution is to have an
automatic debian creation procedure in both fvwm and fvwm-themes
distribution so that anyone could create a debian package. This way noone
depends on the current fvwm maintainer (he didn't package fvwm-2.5.x yet
AFAIK) and noone will depend on the fvwm-themes packager (if he has no
time anymore).

> >Also try creating fvwm-themes_0.7.0_0.20030503_i386.deb from cvs.
> 
> I receive end of file from server. 
> I'm not shure if i can help you.

You may post an error message and I will try to help.

I forgot you to say that in order to create fvwm-themes-0.7.0 package
from cvs, you should first create and install fvwm-2.5.6 Debian package.

If this is a problem for you to work with cvs versions, I don't know what
to suggest.

It is your decision now, you may add fvwm-themes to Debian or create an
automatic procedure, so you don't work hard every time to build packages.
I think it is Debian users who should do one or another thing. I can't
help very much here. You should go and show an initiative. :)

Regards,
Mikhael.

end of file from server

[Smiler <smi...@we...>]

>In the future someone else should maintain these packages.
>We may discuss this later.

It is your decision, but explain pleace.
Because i have many time spent, to this project.
And you have many time spent to me.
I can't understood this step. On that score it hits me strong.

>Also try creating fvwm-themes_0.7.0_0.20030503_i386.deb from cvs.

I receive end of file from server. 
I'm not shure if i can help you.

Yours respectfully
Andrei