fvwm-themes-devel — Developing FVWM Themes

Re: FINALLY!!! Now Online! http://fvwm.themes.org/

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

Mikhael Goikhman wrote:
> 
> 
> Ok, here are some comments.
> 
> First of all Joe Staffer is anyone from the staff? Not very helpful.
> It's hard to see who wrote what at http://www.themes.org/users/joestaffer/
> and links on this page are broken, they miss a subdirectory.

Every section whether window manager, resource, skin or whatever, was
required to have at least 3 documents at the very minimum.
1. Version Compatibilty
2. Submission Guidelines
3. How to Save and Package

For the first _required_ 3 docs joestaffer was created to be a generic
user to allow any of the staff to edit the docs to get the site up and
running. Otherwise the necessary permissions made the situation much
more complex than it needed to be. Future documentation submissions will
have the actual author credited.

> 
> I suggest to add 2 docs:
> 
>   * Here is a simple example FVWM theme to start with...
>     In this doc create and post a simple as possible theme, don't use any
>     options or variants, don't include any *.cfg files, don't even mention
>     anything complex. Explain that a theme is a directory and components
>     are files, use these files:
> 
>       example/
>         background    - use xsetroot, so no images needed
>         buttons       - use Vector with @0, @1, @2, @3 colors
>         colors-decors - try to use minimal number of images or zero
>         cursors       - create new file or get any existing one
>         menustyles    - create new file or get any existing one
>         windowlook    - create new file or get any existing one
> 
>   * Creating advanced FVWM theme...
>     This explain all aspects like dependencies, special functions,
>     options, variants, *.cfg, location of images, sounds and so on.
>     Show and explain how existing themes are structured.
> 
> Alex, can you create the first doc? The second is harder, so maybe Olivier
> or I may help here. 

The first document was always going to be part of the plan but I really
do appreciate the advice and tips. The second doc would be beyond my
capabilities indeed. :) It's very easy for anyone to submit docs once
they have their own login. Just go to the commitments page and add
whatever tasks you wish to participate in. Once submitted the doc enters
a queue for me or someone else to approve for final posting. The hardest
part is using the tiny editing box on the form provided and embedding
the necessary html tags.

I'll get that first doc into the system ASAP.

> Also we probably need this doc:
> 
>   * Creating modules component...
>     This starts from creating a single file for modules without all these
>     add-ons that we use in our modules@, then explain how to break it to a
>     directory with separate files and add support for menus, options etc.
> 

Is that just for modules? Because I already had thought about a "How to
Create a Complex Component" document. Probably just simply explained for
newbies.


Alex

P.S. Any errors with the themes.org site or any of its pages can be
reported to fee...@th... anytime if you have the time. Like most
things though, it's still a work in progress.

Re: FINALLY!!! Now Online! http://fvwm.themes.org/

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

On 26 Oct 2001 17:03:08 +0930, Alex Wallis wrote:
> 
> Any suggestions for improvement are certainly most welcome.

Ok, here are some comments.

First of all Joe Staffer is anyone from the staff? Not very helpful.
It's hard to see who wrote what at http://www.themes.org/users/joestaffer/
and links on this page are broken, they miss a subdirectory.

I suggest to add 2 docs:

  * Here is a simple example FVWM theme to start with...
    In this doc create and post a simple as possible theme, don't use any
    options or variants, don't include any *.cfg files, don't even mention
    anything complex. Explain that a theme is a directory and components
    are files, use these files:

      example/
        background    - use xsetroot, so no images needed
        buttons       - use Vector with @0, @1, @2, @3 colors
        colors-decors - try to use minimal number of images or zero
        cursors       - create new file or get any existing one
        menustyles    - create new file or get any existing one
        windowlook    - create new file or get any existing one

  * Creating advanced FVWM theme...
    This explain all aspects like dependencies, special functions,
    options, variants, *.cfg, location of images, sounds and so on.
    Show and explain how existing themes are structured.

Alex, can you create the first doc? The second is harder, so maybe Olivier
or I may help here. Also we probably need this doc:

  * Creating modules component...
    This starts from creating a single file for modules without all these
    add-ons that we use in our modules@, then explain how to break it to a
    directory with separate files and add support for menus, options etc.

Regards,
Mikhael.

FINALLY!!! Now Online! http://fvwm.themes.org/

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

There's still nothing to see so far, since no themes have been uploaded
yet, but the 3 main required docs are now in place and theme submissions
can now be made. Volunteers for all areas are most welcome and there is
a volunteers handbook in place to demonstarte how easy it is to
participate. Anyone can do it! Even you! Go to
http://www.themes.org/docs/handbook.php to find out more.

Site policy is that the actual theme designer's upload their themes to
themes.org for other users to download. This allows the theme author
field to credit the designer for their work, (at the moment whoever
uploads is credited in the "by" field), and further allows them to add
comments about the theme or it's installation. Screenshots can also be
submitted in .jpg or .png formats. Only tarballs of the form .tar.gz
will be accepted and approved.

The site is geared towards fvwm-themes but older versions of fvwm may
yet be supported at a later date if interest improves.

Since fvwm-themes is mainly the work of 2 core developer's (Mikhael &
Olivier), but also contains contributions from others, I thought it best
to invite discussion on upload procedural issues. From time to time all
themes within the project will need tweaking for bugfixing and new
features. Requiring the re-upload of submitted themes to themes.org.
This is no problem as such, but some people just may not have enough
hours in the day to complete their obligations. 

There is still a little editing to do on the documentation, but if
anyone notices a glaring discrepancy please email fv...@th... with
details of the parts under question.
Any suggestions for improvement are certainly most welcome.

In fact, any comments at all would be appreciated.  :)


Alex

=========================================
Project Leader for http://fvwm.themes.org

Re: 0.5.1

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

On Wed, Oct 24, 2001 at 04:23:43PM +0000, Mikhael Goikhman wrote:
> On 24 Oct 2001 07:40:56 +0200, Olivier Chapuis wrote:
> > 
> > If every things go normally, I will realese fvwm-themes-0.5.1
> > the 25th between 6:00 and 10:00 (UTC).
> > 
> > IMHO this version is "a major version" (it is the first time
> > that I am happy with the theme switching speed). So maybe,
> > this version can be call 0.6.0. Any opinion?
> 
> You may choose any number from 0.5.1 to 0.9.0 including.
>

I will go with 0.6.0.
 
> > I get one problem to build the rpm: the manpages are bzip2ed
> > (mdk feature). I hope that I will be able to fix this today
> > (by editing the good file), but I am not sure to succed.
> > If I fail, Mikheal, can you release the rpm's?
> 
> Actually now (I hope) Glen creates rpms for fvwm, so I or you may ask him.
>

I've fixed the problem so I will release the rpm's this time.
 
> > I any case I would like to announce this version to the world.
> > The world is fvwm-announce, freashmeat and fcola.
> 
> And fvwm-themes-users.
> 
> There is a problem with colors in modules@cde with colors@luthien.
> The date field has its own gradient rectangle (say, 54x54 instead of
> 64x64). And font for weekday and month is cut from the top (it is seen
> well in large button bar, in "Oct"). I thought these are simple problems,
> but I didn't manage to solve them from the first try. Not very critical.
>

I hope that I've fixed that.

Regards, Olivier

Re: 0.5.1

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

On 24 Oct 2001 07:40:56 +0200, Olivier Chapuis wrote:
> 
> If every things go normally, I will realese fvwm-themes-0.5.1
> the 25th between 6:00 and 10:00 (UTC).
> 
> IMHO this version is "a major version" (it is the first time
> that I am happy with the theme switching speed). So maybe,
> this version can be call 0.6.0. Any opinion?

You may choose any number from 0.5.1 to 0.9.0 including.

> I get one problem to build the rpm: the manpages are bzip2ed
> (mdk feature). I hope that I will be able to fix this today
> (by editing the good file), but I am not sure to succed.
> If I fail, Mikheal, can you release the rpm's?

Actually now (I hope) Glen creates rpms for fvwm, so I or you may ask him.

> I any case I would like to announce this version to the world.
> The world is fvwm-announce, freashmeat and fcola.

And fvwm-themes-users.

There is a problem with colors in modules@cde with colors@luthien.
The date field has its own gradient rectangle (say, 54x54 instead of
64x64). And font for weekday and month is cut from the top (it is seen
well in large button bar, in "Oct"). I thought these are simple problems,
but I didn't manage to solve them from the first try. Not very critical.

Regards,
Mikhael.

Re: Debian packages

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

On Sat, Oct 20, 2001 at 09:51:11PM +0000, Mikhael Goikhman wrote:
> I spoke with the maintainer of fvwm on Debian and he said he will not
> package fvwm-themes, because he does not use it, but he may help if
> someone needs to understand his package.
> 
> What should we do?
> 
> 1) Do nothing. If Debian users want to solve this problem they should
> worry, not us.
> 
> 2) Find someone to package fvwm-themes to be compatible with the existing
> fvwm package.
> 
> 3) Add an automatic procedure in fvwm, fvwm-themes, wm-icons similarly to
> rpm, so that debain packages would be easily created when needed.
> 
> I would go for (3), but I don't have Debian. There is Debian on
> SourceForge, but it is a bit problematic, and it does not have some needed
> packages installed (I think even X).

Yes (3) will be good. Let us try alien ...

Olivier

0.5.1

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

Hello,
If every things go normally, I will realese fvwm-themes-0.5.1
the 25th between 6:00 and 10:00 (UTC).

IMHO this version is "a major version" (it is the first time
that I am happy with the theme switching speed). So maybe,
this version can be call 0.6.0. Any opinion?

I get one problem to build the rpm: the manpages are bzip2ed
(mdk feature). I hope that I will be able to fix this today
(by editing the good file), but I am not sure to succed.
If I fail, Mikheal, can you release the rpm's?
 
I any case I would like to announce this version to the world.
The world is fvwm-announce, freashmeat and fcola.

Here a draft for fvwm-announce and fcola:

--
Subject: FVWM Themes version 0.5.1 [or 0.6.0]

We are pleased to announce FVWM Themes version 0.5.1.

FVWM Themes is a powerful configurational framework for the latest FVWM,
designed to be easily extendible and configurable.

All info about FVWM Themes and sources are available at the Home Page:

  http://fvwm-themes.sourceforge.net/

fvwm-themes 0.5.1 requires fvwm 2.4.3, so you may first upgrade your fvwm
before fvwm-themes.

There are rpm packages for both fvwm 2.4.3 and fvwm-themes 0.5.1 at:

  ftp://fvwm-themes.sourceforge.net/rpm/

Currently both fvwm and fvwm-themes are stable/production software.

New features in fvwm-themes 0.5.1 as compared to fvwm-themes 0.5.0:

* Improvements in the theme switching (really faster in the average).
* The Themes Center GUI is much faster now.
* Added ewmh and ksmserver support (requires fvwm-ewmh).
* Added Xinerama support (see the faq).
* Added Debian menu system support.
* New themes: Metal, Minimal (in extra).
* And much more...


The FVWM Themes developers, 25 October 2001
--

Any comments/corrections welcome

Regards, Olivier

Re: Debian packages

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

Mikhael Goikhman wrote:
> 
> I spoke with the maintainer of fvwm on Debian and he said he will not
> package fvwm-themes, because he does not use it, but he may help if
> someone needs to understand his package.
> 
> What should we do?
> 
> 1) Do nothing. If Debian users want to solve this problem they should
> worry, not us.
> 
> 2) Find someone to package fvwm-themes to be compatible with the existing
> fvwm package.
> 
> 3) Add an automatic procedure in fvwm, fvwm-themes, wm-icons similarly to
> rpm, so that debain packages would be easily created when needed.
> 
> I would go for (3), but I don't have Debian. There is Debian on
> SourceForge, but it is a bit problematic, and it does not have some needed
> packages installed (I think even X).
> 
> Alex did something on http://dove.net.au/~awol/fvwm/ (hmm, new look)
> about debian. Alex, may you explain what did you do and how?
>

Since my isp's site is quota limited, and I don't believe many people
are even aware of it, I restricted my uploads to just basically rpm's of
latest cvs of fvwm and fvwm-themes without all the extras which stay on
my own dyn hosted machine. Of course this means I have to be online to
access everything.
As far as debian goes all I did was install alien for redhat7.1 and I
just use that to create .deb's from both .rpm sources or tarball. I have
no one to test them though, I'm still looking for a volunteer.

My personal feeling is that although having a wide range of package
selection is fine, it's also confusing. The entire package tree of all
possible package choices and options is quite extensive. I'm thinking
that just releasing tarballs is the way to go as that format can be
universally installed on almost any distribution and/or architecture and
rpm's and deb's only make sense for dependancy checking. Since nothing
else, except its own themes, actually depends on having fvwm-themes
installed, it makes sense to concentrate on universally acceptable
package systems rather than getting distracted by problems with certain
distributions. Having said that, is it possible to compromise between
package choice alternatives to ensure some kind of version checking?
Is it possible to utilise each theme's theme.cfg for this purpose?

Perhaps fvwm's default install config gui (FvwmScript-Setup95 is it?),
could include a button/choice to install fvwm-themes if the path to the
tarball is given. I'm already working on a gui to --install, and
--create-pack for theme management but have been distracted a little by
real life. I will post something soon I hope.

Do these thoughts help?

Alex

Debian packages

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

I spoke with the maintainer of fvwm on Debian and he said he will not
package fvwm-themes, because he does not use it, but he may help if
someone needs to understand his package.

What should we do?

1) Do nothing. If Debian users want to solve this problem they should
worry, not us.

2) Find someone to package fvwm-themes to be compatible with the existing
fvwm package.

3) Add an automatic procedure in fvwm, fvwm-themes, wm-icons similarly to
rpm, so that debain packages would be easily created when needed.

I would go for (3), but I don't have Debian. There is Debian on
SourceForge, but it is a bit problematic, and it does not have some needed
packages installed (I think even X).

Alex did something on http://dove.net.au/~awol/fvwm/ (hmm, new look)
about debian. Alex, may you explain what did you do and how?

Regards,
Mikhael.

Re: Help! I modified my awol theme and ran into unforseen difficulties! :)

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

Olivier Chapuis wrote:
> 
> On Sun, Oct 14, 2001 at 04:32:25AM +0930, Alex Wallis wrote:
> >
> > To beautify my FvwmButtons a little, I've added a few pixmaps, and menu
> > routines, as well as added a few more sounds. The theme is over 500Kb's
> > now so it's approaching the bloatware stage, but I'll soon be
> > redesigning the sounds again to allow for a minimal install with easy
> > addition of different soundscapes.
> >
> > However, in order to get the Soundscapes menu onto the
> > MenuFvwmStartThemeModules I had to use a routine to create
> > MenuFvwmStartThemeModules so that any AddToMenu for the Soundscapes
> > would not create duplicate entries upon switching sounds. This
> > unfortunately would require all themes to use a similar routine for the
> > creation of the Modules menu to be consistant. I would appreciate an
> > alternative suggestion if there is one. Although using a Func for this
> > menu does have certain advantages.
> >
> 
> I do not really understand the question. 

O.K. Simply put, I've used a new func called
FuncMenuFvwmStartThemeModules which when called it then creates the
MenuFvwmStartThemeModules afresh. This allows changing the menu by
switching to other theme modules and still add to it my soundscape menu.
The func's routine can be viewed under the # Theme module menus section
at
http://dove.net.au/~awol/fvwm/testing/modified-ft-awol-0.5.1/awol/modules/main

This func would need to be added to, and called by every theme and
reloading sequence to be consistant.

>I will download your new
> version of the awol theme so maybe I can answer your question.
> But, it seems that you use experimental reloading (that I will
> rename "partial reloading") and that your sound component needs
> a module reloading (which seems strange for me). So, you may try
> to create a sound.cfg file which contains:
> 
> [component]
> file=sound
> depends+=modules
> 
> [component]
> file=modules
> stronglydepends+=sound
> 
> be award that the names "depends" and stronglydepends may change
> soon.
> 
Thanks for the tip! I'll try to pay attention to the Changelog. :)

Alex

Re: fvwm-themes-0.5.1 release plan

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

On Wed, Oct 17, 2001 at 12:04:29AM +0000, Mikhael Goikhman wrote:
> On 07 Sep 2001 08:09:02 +0200, Olivier Chapuis wrote:
> > 
> [...]
> 
> Olivier, I am not quoting this message, because I don't have yet time to
> come to good answers. Maybe sometime later...
>

No problems. Because I lost some times with FvwmScript and I want
to fix some problems I delay the release of one week.
 
> I don't very like that buttons component (and some others) became more
> complex, but since I can't suggest something better I can't complain.
>

Things are complex already before the introduction of the
buttons@{nanogui,mech,brushedmetal}. Now there are more complex,
and fvwm-themes is complex!
But to solve this we should think about a full documentation
which contains a component by component doc.

> About names, we may leave your *depends names for now.

I will see. Since I delay the release of one week if I found
good names I will use it.

> I think FuncFvwmReloadColorsModules should be FuncFvwmReloadModuleColors.
> 
> Something is wrong with modules@migo, when colors are changed swalowed
> apps has previous colors. This is not related to "experimental reloading".
>

I will take a look at the problem.
 
> Please decide yourself whether to use "experimental reloading" as the
> default and what to do with buttons@ in @nanogui and @mech.
>

Ok.

Regards, Olivier

PS: In your mail headers there is

Mail-Followup-To: Mikhael Goikhman <mi...@ho...>,
        FVWM Themes devel <fvw...@li...>

I am not a mail expert but this means that you want a copy
of a reply to mi...@ho.... Is this really the case?
If the answer is no adding fvw...@li...
to your mutt "subscribe" group (in addition to the mutt "lists")
should remove the mi...@ho... followup-To.

Re: Help! I modified my awol theme and ran into unforseen difficulties! :)

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

On Sun, Oct 14, 2001 at 04:32:25AM +0930, Alex Wallis wrote:
> 
> To beautify my FvwmButtons a little, I've added a few pixmaps, and menu
> routines, as well as added a few more sounds. The theme is over 500Kb's
> now so it's approaching the bloatware stage, but I'll soon be
> redesigning the sounds again to allow for a minimal install with easy
> addition of different soundscapes.
> 
> However, in order to get the Soundscapes menu onto the
> MenuFvwmStartThemeModules I had to use a routine to create
> MenuFvwmStartThemeModules so that any AddToMenu for the Soundscapes
> would not create duplicate entries upon switching sounds. This
> unfortunately would require all themes to use a similar routine for the
> creation of the Modules menu to be consistant. I would appreciate an
> alternative suggestion if there is one. Although using a Func for this
> menu does have certain advantages.
>

I do not really understand the question. I will download your new
version of the awol theme so maybe I can answer your question.
But, it seems that you use experimental reloading (that I will
rename "partial reloading") and that your sound component needs
a module reloading (which seems strange for me). So, you may try
to create a sound.cfg file which contains:

[component]
file=sound
depends+=modules

[component]
file=modules
stronglydepends+=sound

be award that the names "depends" and stronglydepends may change
soon.

Olivier

Re: Help!

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

On 18 Oct 2001 09:33:04 -0400, patricia lynn wrote:
> 
> In my search for better Windows icons, I found your site and downloaded the files you've made available. But the file path flashed by too fast for me to tell where they went! I've looked in the System file and tried to browse from the new icon function but I'm getting nowhere -- none of the files preview what image they are. Do I have to move them in order to get them to come up in the new icon display? How can I tell which ones they are? And if I can't readily access them, how do I delete them? Are they in a folder?
> 
> I'm using Windows ME -- and though I have been using computers for some time, I'm not good at accessing files through their "path." 

I don't think you will be able to use xpm icons on Windows without
converting to some other format. We don't support Windows, only UNIX.
Anyway, the folder name is wm-icons-0.3.0 .

Regards,
Mikhael.

Help!

[patricia l. <pl...@ro...>]

HI there -

In my search for better Windows icons, I found your site and downloaded =
the files you've made available. But the file path flashed by too fast =
for me to tell where they went! I've looked in the System file and tried =
to browse from the new icon function but I'm getting nowhere -- none of =
the files preview what image they are. Do I have to move them in order =
to get them to come up in the new icon display? How can I tell which =
ones they are? And if I can't readily access them, how do I delete them? =
Are they in a folder?

I'm using Windows ME -- and though I have been using computers for some =
time, I'm not good at accessing files through their "path."=20

Thanks for your help --

Tricia

Re: Icons

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

On 18 Oct 2001 04:46:42 -0400, ERIC TANEFO wrote:
> 
> My name is Eric Tanefo and I am very interested in using a few icons included in the 32*32 kde icon set.
> I plan to use them for a software solution that will be commercialized in the US and overseas.
> I would appreciate if you could let me know how to get these icons in a GIF or JPEG format.
> This is an urgent request.
> Thank you very much in advance.

These icons are from the KDE project (www.kde.org) and I believe they are
licensed under GNU GPL. You are free to use these or slightly modified
icons in GPL'd project. We are not the authors, so can't relicense them.

There are no KDE icons in GIF or JPG format as far as I know (only XPM and
PNG), you may use any image converting program to convert to another format.
If you use UNIX, I may suggest such programs as gimp, xv, ImageMagick.

Regards,
Mikhael.

Icons

[ERIC T. <MAR...@ms...>]

Hello,
 =20
My name is Eric Tanefo and I am very interested in using a few icons incl=
uded in the 32*32 kde icon set.
I plan to use them for a software solution that will be commercialized in=
 the US and overseas.
I would appreciate if you could let me know how to get these icons in a G=
IF or JPEG format.
This is an urgent request.
Thank you very much in advance.
 =20
Eric

Re: fvwm-themes-0.5.1 release plan

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

On 07 Sep 2001 08:09:02 +0200, Olivier Chapuis wrote:
> 
[...]

Olivier, I am not quoting this message, because I don't have yet time to
come to good answers. Maybe sometime later...

I don't very like that buttons component (and some others) became more
complex, but since I can't suggest something better I can't complain.

About names, we may leave your *depends names for now.
I think FuncFvwmReloadColorsModules should be FuncFvwmReloadModuleColors.

Something is wrong with modules@migo, when colors are changed swalowed
apps has previous colors. This is not related to "experimental reloading".

Please decide yourself whether to use "experimental reloading" as the
default and what to do with buttons@ in @nanogui and @mech.

Regards,
Mikhael.

Help! I modified my awol theme and ran into unforseen difficulties! :)

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

Since I switched to redhat7.1 I've found my favourite mixer app(kLo_mix)
is not viable as it doesn't want to build on redhat. Must be the QT
stuff suse uses.
Anyway, I've redesigned my button bar with my xinerama display in mind
and replaced kLo_mix with XtMix which is much more user friendly. Rpm's
for XtMix are available at
http://www.unix-ag.uni-kl.de/~mdenn/xtmix/xtmix_en.html

To beautify my FvwmButtons a little, I've added a few pixmaps, and menu
routines, as well as added a few more sounds. The theme is over 500Kb's
now so it's approaching the bloatware stage, but I'll soon be
redesigning the sounds again to allow for a minimal install with easy
addition of different soundscapes.

However, in order to get the Soundscapes menu onto the
MenuFvwmStartThemeModules I had to use a routine to create
MenuFvwmStartThemeModules so that any AddToMenu for the Soundscapes
would not create duplicate entries upon switching sounds. This
unfortunately would require all themes to use a similar routine for the
creation of the Modules menu to be consistant. I would appreciate an
alternative suggestion if there is one. Although using a Func for this
menu does have certain advantages.

The modified theme is available at
http://dove.net.au/~awol/fvwm/testing/modified-ft-awol-0.5.1.tar.gz
and can be easily installed with fvwm-themes-config --site --install
modified-ft-awol-0.5.1.tar.gz

Using play(sox) with sound@awol and changing between the soundscapes
then popping up Start Theme Modules menu, quickly demonstrates the
biggest problem I'm having. Using a different sound player demonstrates
another. No doubt my Func and Menu name choices are also problematic.

I was having some problems with sounds not playing at the correct sample
rate and found that certain sound players like sox allow for not only
rates but also volume and other settings. For example the current
package contains a sox sample rate entry for the robot and homer startup
sounds which will be silent using esdplay or rplay. Remove the sample
rate entry if desired.

Hope you had a good holiday Mikhael! Maybe not long enough?  ;)


Alex

Re: Hello back

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

On Wed, Oct 10, 2001 at 10:29:23PM +0000, Mikhael Goikhman wrote:
> I still does not have enough time to learn and comment on the latest
> dependency work of Olivier. Actually I though you will release 0.5.1
> without me. I will try to find a time soon.
>

There are a lot of change in 0.5.1 and few remaining problems.
I plan to release 0.5.1 the 18th. Mikhael, can you answer my
mail with subject: "fvwm-themes-0.5.1 release plan".

> I got 6 very nice "themes" from Suzanne that use MultiPixmap.
> I will try to force integration of MultiPixmap patch into fvwm.
>

Yes, this will be fine. But, I am a bit "lost" with fvwm release
plan. If we go to build 2.6 or 3.0 we will have to wait to use
MultiPixmap. Or, we should find a way to build fvwm-themes
against 2.4.x or 2.5.x. Maybe all files should be preprocessed
by or own fvwm-themes-pp at installation.
 
> We also should release rpms of fvwm-2.4.3 (hopefully tomorrow).
> 

Yep

Regards, Olivier

Hello back

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

I still does not have enough time to learn and comment on the latest
dependency work of Olivier. Actually I though you will release 0.5.1
without me. I will try to find a time soon.

I got 6 very nice "themes" from Suzanne that use MultiPixmap.
I will try to force integration of MultiPixmap patch into fvwm.

We also should release rpms of fvwm-2.4.3 (hopefully tomorrow).

Regards,
Mikhael.

Re: Some quirky things with xinerama.

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

On Mon, Oct 08, 2001 at 12:48:38AM +0930, Alex Wallis wrote:
> Olivier Chapuis wrote:
> > The WindowList should work now, 
> 
> Works fine! However on either screen it produces 2 errors each time.....
> 
> [FVWM][get_menu_option]:<<ERROR>> invalid position arguments
> [FVWM][WindowList]: <<ERROR>> Unknown option `Mouse`
> 

Ooops ... Fixed I hope now.
BTW, the fact the menus no longer cross between screens
is a fix by Dominik after I report this bug. I hope you
prefer this behavior.

Reagards, Olivier

Re: Some quirky things with xinerama.

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

Olivier Chapuis wrote:
> 
> 
> Can you test again? Also can you test the icons placement in two
> or three themes? 

Yeah I'd noticed some disappearing icons before but this now appears to
be fixed.  :)


> There was some changes in fvwm and fvwm-themes
> regarding Xinerama.

All seems working fine for me. :)

> The WindowList should work now, 

Works fine! However on either screen it produces 2 errors each time.....

[FVWM][get_menu_option]:<<ERROR>> invalid position arguments
[FVWM][WindowList]: <<ERROR>> Unknown option `Mouse`

> but I've
> no idea about your osx colours problems

The OSX colors are still playing up. Using any other colors works ok.
It's only the menus that show that problem though, and it's only on my
primary screen, so it must be something to do with them. The hilight
color works as expected, but the first menu shows up ok until mouse-over
where it turns all items black. All sub-menus are black too. No errors
are produced to help. I've noticed if I leave a sub-menu and go back to
its parent over a normal menu item its proper color is restored upon
leaving that item until I mouse over it again. Then it turns black once
more. This does not happen to menu items.

I'll try and investigate further.

> 
> Regards, Olivier
> 

Alex

Re: Some quirky things with xinerama.

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

On Wed, Sep 26, 2001 at 09:51:43PM +0930, Alex Wallis wrote:
> Olivier Chapuis wrote:
> > 
> > 
> > I think that now fvwm-themes (cvs) is Xinerama compliant.
> > You should read question 3.1.3 of the FAQ. WindowList is
> > still buggy but I hope that this will be fixed in fvwm
> > 2.4.3 (if not we will found a workaround).
> > 
> > Alex can you make some tests (specialy blackbox, cde and
> > osx modules with primary screen 0 and 1).
> > 
>

Can you test again? Also can you test the icons placement in two
or three themes? There was some changes in fvwm and fvwm-themes
regarding Xinerama. The WindowList should work now, but I've
no idea about your osx colours problems

Regards, Olivier

Re: Some quirky things with xinerama.

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

On Wed, Sep 26, 2001 at 09:51:43PM +0930, Alex Wallis wrote:
> Olivier Chapuis wrote:
> > 
> > 
> > I think that now fvwm-themes (cvs) is Xinerama compliant.
> > You should read question 3.1.3 of the FAQ. WindowList is
> > still buggy but I hope that this will be fixed in fvwm
> > 2.4.3 (if not we will found a workaround).
> > 
> > Alex can you make some tests (specialy blackbox, cde and
> > osx modules with primary screen 0 and 1).
> > 
> 
> The blackbox and CDE themes appear to work great!  :)
> 
> I've noticed some problems with OSX menu bar at the top of the screens.
> It's correctly placed across both screens. But with
> XineramaPrimaryScreen 1 (at least) the menus do not behave as desired.
> The icon/WinList, Shells, Programs, Help, and System menus are fine.
> However the Personal menu just produces a beep! (no errors)
> The menus on the other screen on the other hand all appear at the
> extreme right edge of the screen. That is the Themes, Modules, Config,
> WinOps, Xscreensaver and exit menus.
>

Of course ... I hope that now this is fixed
Olivier

Re: Some quirky things with xinerama.

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

Olivier Chapuis wrote:
> 
> 
> I think that now fvwm-themes (cvs) is Xinerama compliant.
> You should read question 3.1.3 of the FAQ. WindowList is
> still buggy but I hope that this will be fixed in fvwm
> 2.4.3 (if not we will found a workaround).
> 
> Alex can you make some tests (specialy blackbox, cde and
> osx modules with primary screen 0 and 1).
> 

The blackbox and CDE themes appear to work great!  :)

I've noticed some problems with OSX menu bar at the top of the screens.
It's correctly placed across both screens. But with
XineramaPrimaryScreen 1 (at least) the menus do not behave as desired.
The icon/WinList, Shells, Programs, Help, and System menus are fine.
However the Personal menu just produces a beep! (no errors)
The menus on the other screen on the other hand all appear at the
extreme right edge of the screen. That is the Themes, Modules, Config,
WinOps, Xscreensaver and exit menus.

I'll try changing my setup to a more conventional config arrangement and
see if that changes the symptoms at all.

Alex