fvwm-themes-devel — Developing FVWM Themes

Re: [FVWM-Themes] Theme names and packaging

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

"Thomas A. Gardiner" wrote:
> 
<snip>
> not sure, however, that this is the same case.  I hate to say this, but I
> think I would suggest mixed case for theme names and lower case for theme
> components.

I agree with this idea.

> 
> > 2) Currently we have one package for the core and all themes. Do you think
> > it makes sence to divide it to several ones. If yes, which packages to
> > have, fvwm-themes-base, fvwm-themes-extra? Or maybe only the base package,
> > and distribute all other themes using .tar.gz from themes.org?
> >
> > In other words, which method do you prefer, to install one fvwm-themes
> > tarball (or rpm), which is getting bigger (since it includes more themes),
> > or you are not interesting in more themes to be included and prefer to
> > find other themes on internet yourself?
> 
> I think the real issue is size.  I would suggest spliting the core from
> the themes when the sum becomes too large.  My biggest concern is having
> an rpm or tar ball and spec file from which to make one.  I find that I
> use rpm a LOT to find all of the pieces of a package, the documentation,
> etc.
> 
> Tom
> 
I raised this subject some time back. I think a lot of people will
prefer not to clutter up their hard disk with unwanted themes. However,
there aren't many themes at the moment so that will only be issue some
time in the future.
However to stimulate more interest in this project, the themes
themselves must be seen as being readily transportable and easily
reproducible.
I personally think it would be an advantage to have several easy install
options. 

Either the FULL package containing all themes.

OR

A basic package with additional themes available for individual
download.

I have no idea of the difficulties involved, but I once suggested that
perhaps the make rpm-dist could possibly have an option added to either
make a basic or full package. In this manner the decision is then the
users, whilst allowing uninterupted development in the complete source
tree.

Another idea is themes.org is prepared to contribute facilities allowing
individual theme creators to maintain cvs sources for their themes with
provisions for packaging and posting of new releases and updates.


Alex

P.S. The new themes.org site has been imminent for several months now,
but there's still no news on a definite announcement. If anyone has
ideas they wish to integrate into fvwm.themes.org please submit them now
by email to fv...@th....

Re: [FVWM-Themes] Theme names and packaging

[Thomas A. G. <gar...@pa...>]

Hi,

Not sure if I should bombard the lists with this, but maybe it'll help
promote an open discussion.

On Sat, 28 Apr 2001, Mikhael Goikhman wrote:

> 1) Which names to use for themes, lower-cased as it is now or mix-cased?
> I am very compfortable with lower-cased ones (cde, afterstep), just
> like with lower-cased components (background, colors) and I think we
> should use this as theme id for consistency, but it is not very hard to
> display mix-cased names (CDE, AfterStep).

I used to prefer mixed case, specificly in my code.  Lately I find the
mixed case to be just more detail when I'm looking for simplicity.  I'm
not sure, however, that this is the same case.  I hate to say this, but I
think I would suggest mixed case for theme names and lower case for theme
components.

> 2) Currently we have one package for the core and all themes. Do you think
> it makes sence to divide it to several ones. If yes, which packages to
> have, fvwm-themes-base, fvwm-themes-extra? Or maybe only the base package,
> and distribute all other themes using .tar.gz from themes.org?
> 
> In other words, which method do you prefer, to install one fvwm-themes
> tarball (or rpm), which is getting bigger (since it includes more themes),
> or you are not interesting in more themes to be included and prefer to
> find other themes on internet yourself?

I think the real issue is size.  I would suggest spliting the core from
the themes when the sum becomes too large.  My biggest concern is having
an rpm or tar ball and spec file from which to make one.  I find that I
use rpm a LOT to find all of the pieces of a package, the documentation,
etc.


Tom

Theme names and packaging

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

I would like to know an opinion of everyone here about these 2 questions
regarding fvwm-themes.

1) Which names to use for themes, lower-cased as it is now or mix-cased?
I am very compfortable with lower-cased ones (cde, afterstep), just
like with lower-cased components (background, colors) and I think we
should use this as theme id for consistency, but it is not very hard to
display mix-cased names (CDE, AfterStep).

2) Currently we have one package for the core and all themes. Do you think
it makes sence to divide it to several ones. If yes, which packages to
have, fvwm-themes-base, fvwm-themes-extra? Or maybe only the base package,
and distribute all other themes using .tar.gz from themes.org?

In other words, which method do you prefer, to install one fvwm-themes
tarball (or rpm), which is getting bigger (since it includes more themes),
or you are not interesting in more themes to be included and prefer to
find other themes on internet yourself?

The current packaging method seems to me easier for developers and users,
but I am not sure about users, this is why I am asking.

Regards,
Mikhael.

Re: fvwm-themes: patches to use fontsets instead of single fonts

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

Le Samedi 28 Avril 2001 01:44, vous avez écrit :
> On 26 Apr 2001 18:43:46 +0200, Mike Fabian wrote:
> > Attached are patches for fvwm-themes to use fontsets instead of single
> > fonts.
>
> Thank you for contributing!
>
> Which X Servers on different unices support fontsets?
>
> I thought about having component "fonts" for similar and other purposes.
> So if fontsets is not a portable option, support for Japanese (or Korean,
> Chinese, Russian whatever) would be possible by adding one file.
>

Yes, I think that a fonts component is a good idea. But, we will have a
the same problems that with colors. If a theme want a specific font in one
component it should define fonts for all component that needs one.

> > For European languages, nothing should be changed by these patches.
> >
> > Here is a screenshot showing Japanese in the window titles, the icon
> > manager and the window list:
> >
> > http://www.suse.de/~mfabian/fvwm-themes-japanese.png
>
> Very nice. We will support Japanese (with your help) in one of the
> upcoming versions once we decide with Olivier which method to use.
>
> If Japanese is left-to-right (I know, it is up-to-down), you may try to
> translate some of the locale/* to Japanese.
>

Here the problem is that I do not know if FvwmScript work with
multibyte text. A few time a go FvwmScript core dump at once when
compiled with multibyte enabled. Now It does not core dump any more
with unibyte text and I never try FvwmScript with Japanese.
Mike do you try FvwmScript with Japanese? It will be great if
you can translate one local/ file set say FvwmScript-ColorSelector.html
and FvwmScript-ColorSelector.msg so that I can make tests.

Mike, Thanks a lot for helping!

Regards, Olivier

Re: fvwm-themes: patches to use fontsets instead of single fonts

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

On 26 Apr 2001 18:43:46 +0200, Mike Fabian wrote:
> 
> Attached are patches for fvwm-themes to use fontsets instead of single
> fonts.

Thank you for contributing!

Which X Servers on different unices support fontsets?

I thought about having component "fonts" for similar and other purposes.
So if fontsets is not a portable option, support for Japanese (or Korean,
Chinese, Russian whatever) would be possible by adding one file.

> For European languages, nothing should be changed by these patches.
> 
> Here is a screenshot showing Japanese in the window titles, the icon
> manager and the window list:
> 
> http://www.suse.de/~mfabian/fvwm-themes-japanese.png

Very nice. We will support Japanese (with your help) in one of the
upcoming versions once we decide with Olivier which method to use.

If Japanese is left-to-right (I know, it is up-to-down), you may try to
translate some of the locale/* to Japanese.

Regards,
Mikhael.

fvwm-themes: patches to use fontsets instead of single fonts

[Mike F. <mf...@su...>]

Attached are patches for fvwm-themes to use fontsets instead of single
fonts.

For example, something like

    MenuStyle * Font -b&h-lucida-medium-r-*-*-12-*-*-*-*-*-*-*

will not work for Japanese, Korean or other exotic languages, because
the specified XLFD doesn't match any Japanese or Korean fonts. This
can be fixed by using a fontset instead:

    MenuStyle * Font "-b&h-lucida-medium-r-*-*-12-*-*-*-*-*-*-*,-*-*-medium-r-*--14-*,*"

For languages using iso8859-1, nothing will change, because the first
entry in the fontset still matches:

    mfabian@gregory:~$ xlsfonts -fn "-b&h-lucida-medium-r-*-*-12-*-*-*-*-*-*-*" | grep iso8859-1
    -b&h-lucida-medium-r-normal-sans-12-116-75-75-p-0-iso8859-1
    -b&h-lucida-medium-r-normal-sans-12-116-75-75-p-0-iso8859-1
    -b&h-lucida-medium-r-normal-sans-12-116-75-75-p-0-iso8859-1
    -b&h-lucida-medium-r-normal-sans-12-116-75-75-p-0-iso8859-1
    -b&h-lucida-medium-r-normal-sans-12-120-75-75-p-71-iso8859-1
    -b&h-lucida-medium-r-normal-sans-12-120-75-75-p-71-iso8859-1
    -b&h-lucida-medium-r-normal-sans-12-120-75-75-p-71-iso8859-1
    -b&h-lucida-medium-r-normal-sans-12-120-75-75-p-71-iso8859-1
    mfabian@gregory:~$ 

For Japanese, the first entry doesn't match, but the second does:

    mfabian@gregory:~$ xlsfonts -fn "-b&h-lucida-medium-r-*-*-12-*-*-*-*-*-*-*" | grep jisx0208
    mfabian@gregory:~$ xlsfonts -fn "-*-*-medium-r-*--14-*" | grep jisx0208-alias-fixed-medium-r-normal--14-140-75-75-c-140-jisx0208.1983-0
    -misc-fixed-medium-r-normal--14-130-75-75-c-140-jisx0208.1983-0
    -misc-fixed-medium-r-normal--14-130-75-75-c-140-jisx0208.1983-0
    -misc-fixed-medium-r-normal--14-130-75-75-c-140-jisx0208.1983-0
    -misc-fixed-medium-r-normal--14-130-75-75-c-140-jisx0208.1983-0
    -misc-fixed-medium-r-normal--14-130-75-75-c-140-jisx0208.1983-0
    -misc-fixed-medium-r-normal--14-130-75-75-c-140-jisx0208.1983-0
    -misc-fixed-medium-r-normal--14-130-75-75-c-140-jisx0208.1983-0
    -misc-fixed-medium-r-normal--14-130-75-75-c-140-jisx0208.1983-0
    -misc-fixed-medium-r-normal--14-130-75-75-c-140-jisx0208.1983-0
    -misc-fixed-medium-r-normal--14-140-75-75-c-140-jisx0208.1983-0
    -misc-gothic-medium-r-normal--14-130-75-75-c-140-jisx0208.1983-0
    -misc-gothic-medium-r-normal--14-130-75-75-c-140-jisx0208.1990-0
    -misc-gothic-medium-r-normal--14-130-75-75-c-140-jisx0208.1990-0
    -misc-gothic-medium-r-normal--14-130-75-75-c-140-jisx0208.1990-0
    -misc-marumoji-medium-r-normal--14-130-75-75-c-140-jisx0208.1983-0
    -misc-marumoji-medium-r-normal--14-130-75-75-c-140-jisx0208.1983-0
    mfabian@gregory:~$ 

Thus this fontset gives a slightly bigger font for Japanese, which
improves readability, Japanese in 12 pixel is difficult to read
because the characters are complicated. 

For Korean, the second entry matches as well:

    mfabian@gregory:~$ xlsfonts -fn "-*-*-medium-r-*--14-*" | grep ksc     
    -alias-fixed-medium-r-normal--14-140-75-75-c-140-ksc5601.1987-0
    -alias-variable-medium-r-normal--14-140-75-75-p-140-ksc5601.1987-0
    -baekmuk-batang-medium-r-normal--14-140-75-75-m-140-ksc5601.1987-0
    -baekmuk-dotum-medium-r-normal--14-140-75-75-m-140-ksc5601.1987-0
    -baekmuk-gulim-medium-r-normal--14-140-75-75-m-140-ksc5601.1987-0
    -baekmuk-headline-medium-r-normal--14-140-75-75-m-140-ksc5601.1987-0
    -hanyang-kodig-medium-r-normal--14-140-72-72-c-140-ksc5601.1987-0
    -hanyang-kodig-medium-r-normal--14-140-72-72-c-140-ksc5601.1987-0
    -hanyang-kodig-medium-r-normal--14-140-72-72-c-140-ksc5601.1987-0
    -hanyang-kodig-medium-r-normal--14-140-72-72-c-140-ksc5601.1987-0
    -hanyang-kodig-medium-r-normal--14-140-72-72-c-140-ksc5601.1987-0
    -hanyang-myeongjo-medium-r-normal--14-140-72-72-c-140-ksc5601.1987-0
    -hanyang-myeongjo-medium-r-normal--14-140-72-72-c-140-ksc5601.1987-0
    -hanyang-myeongjo-medium-r-normal--14-140-72-72-c-140-ksc5601.1987-0
    -hanyang-myeongjo-medium-r-normal--14-140-72-72-c-140-ksc5601.1987-0
    -hanyang-myeongjo-medium-r-normal--14-140-72-72-c-140-ksc5601.1987-0
    -misc-fixed-medium-r-normal--14-140-75-75-m-140-ksc5601.1987-0
    -narae-pinetree.precomposed-medium-r-normal--14-140-75-75-p-100-ksc5601.1987-0
    -narae-pinetree.precomposed-medium-r-normal--14-140-75-75-p-100-ksc5601.1987-0
    -narae-pinetree.precomposed-medium-r-normal--14-140-75-75-p-100-ksc5601.1987-0
    -narae-pinetree.precomposed-medium-r-normal--14-140-75-75-p-100-ksc5601.1987-0
    -narae-pinetree.precomposed-medium-r-normal--14-140-75-75-p-100-ksc5601.1987-0
    mfabian@gregory:~$ 

For simplified and traditonal Chinese, the second entry doesn't match either

    mfabian@gregory:~$ xlsfonts -fn "-*-*-medium-r-*--14-*" | grep gb2312
    mfabian@gregory:~$ xlsfonts -fn "-*-*-medium-r-*--14-*" | grep big5  

But the final "*" assures that at least some Font will match:

    mfabian@gregory:~$ xlsfonts -fn "*" | grep big5
    -eten-fixed-medium-r-normal--0-0-75-75-c-0-big5.eten-0
    -eten-fixed-medium-r-normal--0-0-75-75-c-0-big5.eten-0
    -eten-fixed-medium-r-normal--16-150-75-75-c-160-big5-0
    -eten-fixed-medium-r-normal--16-150-75-75-c-160-big5-0
    -eten-fixed-medium-r-normal--16-150-75-75-c-160-big5.eten-0
    -eten-fixed-medium-r-normal--16-150-75-75-c-160-big5.eten-0
    -eten-fixed-medium-r-normal--16-150-75-75-c-160-big5.eten-0
    -eten-fixed-medium-r-normal--16-150-75-75-c-160-big5.eten-0
    -eten-fixed-medium-r-normal--16-150-75-75-c-160-big5.eten-0
    -eten-fixed-medium-r-normal--16-150-75-75-c-160-big5.eten-0
    -eten-fixed-medium-r-normal--16-150-75-75-c-160-big5.eten-0
    -eten-fixed-medium-r-normal--16-150-75-75-c-160-big5.eten-0
    -eten-fixed-medium-r-normal--24-230-75-75-c-240-big5-0
    -eten-fixed-medium-r-normal--24-230-75-75-c-240-big5-0
    -eten-fixed-medium-r-normal--24-230-75-75-c-240-big5.eten-0
    -eten-fixed-medium-r-normal--24-230-75-75-c-240-big5.eten-0
    -eten-fixed-medium-r-normal--24-230-75-75-c-240-big5.eten-0
    -eten-fixed-medium-r-normal--24-230-75-75-c-240-big5.eten-0
    -eten-fixed-medium-r-normal--24-230-75-75-c-240-big5.eten-0
    -eten-fixed-medium-r-normal--24-230-75-75-c-240-big5.eten-0
    -eten-fixed-medium-r-normal--24-230-75-75-c-240-big5.eten-0
    -eten-fixed-medium-r-normal--24-230-75-75-c-240-big5.eten-0
    [... other big5 fonts ...]

    mfabian@gregory:~$ xlsfonts -fn "*" | grep gb2312
    -isas-song ti-medium-r-normal--0-0-72-72-c-0-gb2312.1980-0
    -isas-song ti-medium-r-normal--0-0-72-72-c-0-gb2312.1980-0
    -isas-song ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0
    -isas-song ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0
    -isas-song ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0
    -isas-song ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0
    -isas-song ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0
    -isas-song ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0
    -isas-song ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0
    -isas-song ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0
    -isas-song ti-medium-r-normal--24-240-72-72-c-240-gb2312.1980-0
    -isas-song ti-medium-r-normal--24-240-72-72-c-240-gb2312.1980-0
    -isas-song ti-medium-r-normal--24-240-72-72-c-240-gb2312.1980-0
    -isas-song ti-medium-r-normal--24-240-72-72-c-240-gb2312.1980-0
    -isas-song ti-medium-r-normal--24-240-72-72-c-240-gb2312.1980-0
    -isas-song ti-medium-r-normal--24-240-72-72-c-240-gb2312.1980-0
    -isas-song ti-medium-r-normal--24-240-72-72-c-240-gb2312.1980-0
    -isas-song ti-medium-r-normal--24-240-72-72-c-240-gb2312.1980-0
    [... other gb2312 fonts ...]

Here are the patches:

Re: Great!

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

On 20 Apr 2001 08:03:06 -0400, Larry Gensch wrote:
> 
> On 20 Apr, Olivier Chapuis wrote:
> 
> > Mikhael I found your change to osx and the new theme really great.
> 
> Can you shed some more light on this?  I wrote an OSX "theme" for
> fvwm2 (I sent my code out on this list about six months ago).  Dan
> Espen modified it to work with his own "themes" using decor hooks.
> 
> I'd be very interested in any other work that has gone into making
> fvwm2 look/act more like Aqua/OSX.
> 
> Or am I completely misunderstanding your message?

We usually discuss these topics on fvwm-themes-devel list.
Olivier refers to the latest changes in the fvwm-themes cvs, pre-0.4.3.
Here are screenshots of some of the changes:

  http://fvwm-themes.sourceforge.net/screenshots/full/osx.gif
  http://fvwm-themes.sourceforge.net/screenshots/full/brushedmetal.gif
  http://fvwm-themes.sourceforge.net/screenshots/full/nanogui.gif

I used your configuration posted more than year ago to initially create
theme osx in fvwm-themes-0.0.5, Olivier and me almost fully rewrote it
since then. Recently I changed buttons to look more like the original.

You may either get cvs version or wait for fvwm-themes-0.4.3 (preferable,
you will be able to define window buttons used and their order too).

Regards,
Mikhael.

MetaLab action notice from the `keeper' program

[Serena F. <fe...@me...>]

At about 2001-04-11 17:50:34 UCT, `keeper' moved the following files from
Incoming to X11/icons (various icons, bitmaps, and pixmaps):

wm-icons-0.3.0.tar.gz    window manager icons
wm-icons.lsm             

These replaced the following files:

wm-icons-0.2.6.tar.gz    window manager icons
wm-icons.lsm             

Thank you for your contribution of time, effort, and creativity.

This message was a form letter generated by keeper 1.54, but replying to
it will reach the human who told keeper what to do.  You got this note
because you're listed as a maintainer or author in the archive part involved.
If your package was actually uploaded by someone else, and you know who that
person is, please try to get that person to list him or herself in the LSM.  
--
			fents (MetaLab co-maintainer)

Re: wm-icons

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

On 02 Apr 2001 14:58:15 +0200, Kristian wrote:
> 
> I'm very sorry, but I have a lot of work and I can not do anything
> extensive work. So I would send you my four themes and you should
> convert them to a fvwmthemes-compatible mode.

Ok, I placed this tarball (slightly changed, and repackaged) to:

  http://fvwm-themes.sourceforge.net/data/samples/kristian/

If you send me screenshots of these 4 themes I will place them too.

I have created one more or less ready theme nanogui:

  http://fvwm-themes.sourceforge.net/data/themes/nanogui.tar.bz2

To install it run: fvwm-themes-config --install nanogui.tar.bz2
To uninstall it execute: rm -r ~/.fvwm/themes/nanogui
In both cases use "Theme Management" menu or GUI to load/drop this theme.

I used a not very standard component colors-extra, see README.
Olivier, it seems that there are many themes where only decorations
need to be defined (colorsets 1-4), but not other colors. Do you think
it is a bad idea to split colors@ component to colors@ and decorations@?

I will add this theme (and 3 others) to cvs when we decide about this.

Regards,
Mikhael.

FVWM Themes runs on NetBSD/sparc

[Adrian B. <bu...@fs...>]

Hi,

I want to tell you that the following setups of FVWM Themes run fine for
me (FVWM Themes is now my standard window manager) after a simple
"./configure; make; make install":

fvwm-2.3.27 + fvwm-themes-0.4.1:
NetBSD/sparc-1.4.2 (a.out)
NetBSD/sparc-1.5 (ELF)

fvwm-2.3.30 + fvwm-themes-0.4.2:
NetBSD/sparc-1.5 (ELF)


Thanks for your good work!
Adrian

-- 

Nicht weil die Dinge schwierig sind wagen wir sie nicht,
sondern weil wir sie nicht wagen sind sie schwierig.

fvwm-themes-web

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

I have created fvwm-themes-web cvs repository in parallel to fvwm-themes.
I also configured htdocs directory to be updated every 4 hours from cvs.
So, now it is possible to change web using cvs.

I have replaced 4 screenshots - default, luthien, migo and olicha.
I have no time now to replace (or add) others. Olivier, Alex, feel free.

Regards,
Mikhael.

Re: fvwm-themes-0.4.2

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

Ok, fvwm-themes-0.4.2 (wm-icons-0.3.0 compatible) is finally released. :)
Try 16x16-kde (or 16x16-gnome) icon sets if you don't like 16x16-general.

On 29 Mar 2001 06:49:09 +0200, Olivier Chapuis wrote:
> 
> > I think I will release it tomorrow. We need fvwm-2.3.30 rpms too.
> 
> I've uploaded some mdk rpm. However, I think that 2.3.29 should
> work with fvwm-themes-0.4.2

Even 2.3.22 should work with it, but with many glitches (changes in
fvwm-menu-* scripts, modules), I don't want unneeded glitches.

There is a problem with the old rpm place, so I currently use the new one.
But we may continue with the usual place, just don't forget g+w for files.

Regards,
Mikhael.

Re: fvwm-themes-0.4.2

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

Le Jeudi 29 Mars 2001 03:51, vous avez écrit :
> I didn't learn yet this Minimal stuff, this does not seem to be very
> optimal (dumplication of all functions); FuncFvwmThemesSetMinimalReload
> looks strange.
>

I do not remember exactly! Any way, as I say in the change log the
minimal stuff is not good (in general) because the dependencies
are not enough fine. However, you can try to change for
example the background or the menustyle (or lock a component)
and you will see a big difference.

> I think I will release it tomorrow. We need fvwm-2.3.30 rpms too.
>

I've uploaded some mdk rpm. However, I think that 2.3.29 should
work with fvwm-themes-0.4.2

Olivier

Re: wm-icons

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

On 28 Mar 2001 10:17:16 +0200, Kristian wrote:
> 
> Maybe you should try this link. Our provider is a cheap one, but we must
> safe money..
> 
> ftp://ftp.metalab.unc.edu/pub/Linux/X11/icons/KorsebyIcons-2.0.png.tar.gz
> ftp://ftp.metalab.unc.edu/pub/Linux/X11/icons/KorsebyIcons-2.0.xpm.tar.gz

Ok, I see 113 * 4 icons. Nice.

> There's a little world even in the internet. Since days I have contact
> to one of the fvwm-developers cause the window-movement is very slow
> with XFree 4.

I use XFree 4 on a not very modern machine and it is not slow for me.
Please describe the exact problem, which version do you use (I use the
latest cvs-2.3.30), the parts of your configuration (like decorations
used, OpaqueMoveSize), and send your report to fvw...@fv....

> I know your themes-package. But I didn't like it so much. ;-) Because it
> will replace my old settings.. By the way.. I have built two very nice
> themes called BrushedMetal and MineGui. Maybe I could send the files to
> you that you'll include them ?

Yes, only a general configuration is shipped, because it should work for
everyone, but there are also good ways to define your personal contents.
Everyone should customize his needs by adding files to the personal theme.
This is explained in FAQ; if you have a time you may try fvwm-themes again.

You may send fvwm2rc files to me or to list and we may decide what to do.
But it would be better if you create themes in the fvwm-themes format
yourself, it is not very hard and we will help.

-==-

But let return to wm-icons. In 0.3.x series we use 84 icon names per set.
In later series we may extend this list.

Your icon pack is partially concept-named, partially subject-named.
This is normal, most of icon packs are these (say, original icons in KDE,
GNOME, penguins and so on). But wm-icons is fully concept-named, i.e.
it does not include icons named "pencil" or "pen", but instead has icon
names represented concepts, like "editor", "viewer", "word-processor".

I think it is a good idea to compose a wm-icons icon set from your icons,
Can you do this? What is needed is to compose 84 icons (or less, in this
case _symlinks.lst file is needed too). To keep a track it would be nice
also to specify an origin for every icon (like it is done in doc/icons.lst).

You may choose how you want to do the work. You may just send us a ready
tarball, or work using CVS, by opening a SourceForge account.
You should also decide whether to create 4 icons sets: 48x48-korsebyred,
or maybe just one icon set and have others to be created from it by script.

Keep a good work. :)

Regards,
Mikhael.

Re: wm-icons

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

On 27 Mar 2001 12:53:55 +0200, Kristian wrote:
> 
> Hi !
> 
> I've also made a lots of icons and it is a good idea that we could
> combine our ideas. So I'd like to show you my icon-package in several
> formats. If you're interested, visit
> http://www.korseby.net/visuell/icons/ . Some elements also exists in
> raw-format (without the background).
> If you like my icons (especially the Korseby-Icons-Package) I would like
> to participate in your project.

Hello, Kristian!

Your server seems to have some technical problems, but I am sure I will
like your icons. :) You are of course welcome to wm-icons project.
We (I and Olivier) use CVS to develop wm-icons. We are also FVWM Themes
and FVWM developers, and not quite artists...

I hope you are not against cc-ing our conversation to this mailing list.
We use it ( http://lists.sourceforge.net/lists/listinfo/fvwm-themes-devel )
to discuss wm-icons issues. A separate list may be started if needed.

Currently wm-icons is a bit tied to FVWM. For example, window operation
icon names represent FVWM's window operations and some more things. But we
try to keep wm-icons window manager independent. What WM do you use? :)
You may wait a day or so for fvwm-themes-0.4.2 to see wm-icons in action.

You may also read the March mail archives and ChangeLog's if you like.
And we want to see your icons. :)

Regards,
Mikhael.

Re: releasing 0.4.2

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

Le Jeudi 22 Mars 2001 01:08, vous avez écrit :
> Olivier, do you have a time to release 0.4.2?

I can release 0.4.2 on the 28th (I will get a permanent fast
link to the internet).
Olivier

releasing 0.4.2

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

Olivier, do you have a time to release 0.4.2?
If not, I will do this later.

Regards,
Mikhael.

Re: Animated Root Cursors

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

Mikhael Goikhman wrote:
> 
> 
> You yourself said it does not work with happy2 animation well for you.
> It probably core dumps like for me.

I think the core dumps are an internal xancur issue. It can be resolved
by ensuring the absolute path to the xancur Script file (and the
bitmaps) is within a certain limit including the bitmap file's name. I
will fix this.

> 
> So just add killall to StartAllHooks too.

Yeah, I did that too. But that leaves an unwanted No Process Killed
message in all situations except restart.

> But as I said, pidof/killall is not portable, it does not work on Solaris.

I think I may have found a reasonable compromise using only fvwm
functions. I will investigate further.

Alex

Re: Animated Root Cursors

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

On 21 Mar 2001 13:01:12 +1030, Alex Wallis wrote:
> 
> Mikhael Goikhman wrote:
> > 
> > On 21 Mar 2001 04:54:45 +1030, Alex Wallis wrote:
> > >
> > > I know you guys are mostly busy with other stuff, but I've been
> > > rethinking my cursors ideas.
> > >
> > > I think the animated root cursors are best inserted into the multichoice
> > > theme not awol. If you include the attached tarball and modify
> > > multichoice/themes.cfg like so....
> > 
> > Ok. Some random notes.
> > 
> > xancur is buggy, it core dumps for me on some animations (both from SuSE
> > rpm and compiled from sources). Also there are no xancur rpms for other
> > distributions.
> 
> No bugs here! All animations work great for me. But I use SuSE linux.

You yourself said it does not work with happy2 animation well for you.
It probably core dumps like for me.

> > > Is it possible to modify the Exec command in the function
> > > that starts xancur to test if it's running first?
> > 
> > Exec pidof xancur >/dev/null && killall xancur; xancur ...
> > 
> > But this is not portable.
> 
> I was thinking something like...
> Exec if test -x /usr/X11R6/bin/xancur ; then exec xancur -blah

test -x only verifies the executable existence, not whether it runs.

> It runs a second instance of xancur when restarting because the function
> that starts it is added to Stop/StartAllHooks which works when switching
> components or options as the StopAllHooks makes sure xancur is killed
> first.
> During a restart it just calls for another Exec of xancur.

So just add killall to StartAllHooks too.
But as I said, pidof/killall is not portable, it does not work on Solaris.

Regards,
Mikhael.

Re: Animated Root Cursors

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

Mikhael Goikhman wrote:
> 
> On 21 Mar 2001 04:54:45 +1030, Alex Wallis wrote:
> >
> > I know you guys are mostly busy with other stuff, but I've been
> > rethinking my cursors ideas.
> >
> > I think the animated root cursors are best inserted into the multichoice
> > theme not awol. If you include the attached tarball and modify
> > multichoice/themes.cfg like so....
> 
> Ok. Some random notes.
> 
> xancur is buggy, it core dumps for me on some animations (both from SuSE
> rpm and compiled from sources). Also there are no xancur rpms for other
> distributions.

No bugs here! All animations work great for me. But I use SuSE linux.

> 
> Cursor colors for animations may be used from the existing colors option,
> I am not sure whether using colorset 10 is good.

I used that colorset because it's the main one used for modules, but as
I indicated the colorset choice could become another multichoice too.

> 
> In non-module lines it is better to use $. (current dir) not $FT_DATADIR/..
> 
> There are many image files, they are usually already installed with
> xancur, so I am not sure whether they should be included in fvwm-themes
> especially when most of users don't have xancur...

The image files are very tiny, and 3 of the animations (notable arrow,
eye, and the waving penguin) are not part of the distributed xancur
package as they come from another cursor package I downloaded years ago
and just found on an old floppy. The spinning X is also similar to but
not part of the original package.
We could however cut the images for the standard xancur cursors easily
and just use the files that come already installed with xancur.

> 
> But overall the idea is good for ones who wants toys.
> 
> > Is it possible to modify the Exec command in the function
> > that starts xancur to test if it's running first?
> 
> Exec pidof xancur >/dev/null && killall xancur; xancur ...
> 
> But this is not portable.

I was thinking something like...
Exec if test -x /usr/X11R6/bin/xancur ; then exec xancur -blah

> 
> I don't know why it is run for the second time for you (you didn't include
> your cursor/main file), but it would be better if it is only run once.

There is no cursor/main file. 
It runs a second instance of xancur when restarting because the function
that starts it is added to Stop/StartAllHooks which works when switching
components or options as the StopAllHooks makes sure xancur is killed
first.
During a restart it just calls for another Exec of xancur.



Alex

wm-icons-0.3.0

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

On 21 Mar 2001 04:54:45 +1030, Alex Wallis wrote:
> 
> On another note I've just updated my cvs twice now after installing the
> wm-icons-0.3.0-1.noarch.rpm and now I have a whole heap of new icons
> appearing all over. Looks _very_nice_! :) There needs to be a wm-config
> GUI somewhere imho. But the menu choices appear to be working great so
> far and very impressive indeed! I finally see why you guys have put so
> much effort into this and agree it's not only worthwhile, it's
> sensational.

Thank you. I like our work too. More improvements to come.

But sensational? fvwm-themes was always wm-icons compatible. :-)

> I'm assuming now theme designers can just issue the
> appropriate wm-icons-config command at the appropriate time in the
> configuration? 

Yes, this is possible if a user has wm-icons (it is still optional).
But is not it better if icon sets are changed by a user, not automatically?

> I'll write a news review article and post it on themes.org ASAP.

Maybe at least wait for fvwm-themes-0.4.2? :)

Regards,
Mikhael.

Re: Animated Root Cursors

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

On 21 Mar 2001 04:54:45 +1030, Alex Wallis wrote:
> 
> I know you guys are mostly busy with other stuff, but I've been
> rethinking my cursors ideas.
> 
> I think the animated root cursors are best inserted into the multichoice
> theme not awol. If you include the attached tarball and modify
> multichoice/themes.cfg like so....

Ok. Some random notes.

xancur is buggy, it core dumps for me on some animations (both from SuSE
rpm and compiled from sources). Also there are no xancur rpms for other
distributions.

Cursor colors for animations may be used from the existing colors option,
I am not sure whether using colorset 10 is good.

In non-module lines it is better to use $. (current dir) not $FT_DATADIR/..

There are many image files, they are usually already installed with
xancur, so I am not sure whether they should be included in fvwm-themes
especially when most of users don't have xancur...

But overall the idea is good for ones who wants toys.

> Is it possible to modify the Exec command in the function
> that starts xancur to test if it's running first?

Exec pidof xancur >/dev/null && killall xancur; xancur ...

But this is not portable.

I don't know why it is run for the second time for you (you didn't include
your cursor/main file), but it would be better if it is only run once.

Regards,
Mikhael.

Animated Root Cursors

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

I know you guys are mostly busy with other stuff, but I've been
rethinking my cursors ideas.

I think the animated root cursors are best inserted into the multichoice
theme not awol. If you include the attached tarball and modify
multichoice/themes.cfg like so....

 
option+file=animation
option.name=Animate root cursor?
option.default=1
option.value+file=none
option.value.name=None
option.value+file=arrow
option.value.name=Arrow
option.value+file=eye
option.value.name=Eye
option.value+file=happy2
option.value.name=Happy Face :)
option.value+file=penguin
option.value.name=Penguin waving!
option.value+file=pulse
option.value.name=Rythmic pulse
option.value+file=terra
option.value.name=The world turns.
option.value+file=x
option.value.name=X Spinning
option+file=themeroot
option.name=Theme root cursor?
option.default=1
option.value+file=no
option.value.name=No
option.value+file=yes
option.value.name=Yes

You then can choose from 7 different animations with colors matching
colorset 10, or the default colors. Providing of course the xancur
program is installed. It may be possible to add other modify color
options too.

This will not of course preclude a theme from having it's own cursors,
but I think this cursors option might best be inserted into fvwm-themes
in multichoice.
So don't bother with the cursor changes to my awol theme as previously
suggested.

It works everytime like a charm for me. I had a problem with the file
path for the happy2 cursor being too long if the happy2 Script was in
multichoice/cursors/images/happy2, which is why it's now in the
directory above. I think it's a problem with xancur possibly due to long
bitmap names, or the substitution of $FT_DATADIR?

Unpacking the attached tarball and adding the above lines to
multichoice/themes.cfg makes it all work for me perfectly even with the
Themes Center GUI, except for restarts. I've optimised the selection
functions and added them to Stop/StartAllHooks but another instance of
xancur is started on each restart. Refreshing the theme resets it to a
single xancur. Is it possible to modify the Exec command in the function
that starts xancur to test if it's running first?
 
My only other concern is that there possibly should be an extra menu or
option around MenuFvwmConfiguration and + "Restore Theme
&Cursors%menu/display.xpm%" for the new animated root cursors?

I'll prepare a new set of changes to awol theme. More themes coming
soon.

On another note I've just updated my cvs twice now after installing the
wm-icons-0.3.0-1.noarch.rpm and now I have a whole heap of new icons
appearing all over. Looks _very_nice_! :) There needs to be a wm-config
GUI somewhere imho. But the menu choices appear to be working great so
far and very impressive indeed! I finally see why you guys have put so
much effort into this and agree it's not only worthwhile, it's
sensational. I'm assuming now theme designers can just issue the
appropriate wm-icons-config command at the appropriate time in the
configuration? 

I'll write a news review article and post it on themes.org ASAP.

Cheers!

Alex

Broken MenuFvwmStartRegularModules

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

It seems I'm getting some kind of syntax error at the line....

+ "&ScrollBar (75%% scr)%menu/window-resize.xpm%" Module FvwmScroll 75p
75p

All I get in the menu is "&Scrollbar (75

The rest of the menu works ok.


Alex

Re: Modifications to awol theme.

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

Mikhael Goikhman wrote:
> 
> On 17 Mar 2001 16:57:06 +1030, Alex Wallis wrote:
> >
> > On another point the sounds themselves take up much more room than the
> > configuration files. I'd suggest the sound files for all themes could be
<snip>

I've got a complete working awol theme with all my changes included.
It can be viewed at http://dove.net.au/~awol/fvwm/testing/awol

The config files alone are available in the testing directory along with
the soundpack of just the .wav files in both .gz and bz2 form. This
rather modest demonstration of soundscaping clearly indicates the danger
of bloating fvwm-themes unnecessarily with the actual sounds themselves.

The only files I've NOT changed are background, buttons, colors and
menustyle.
Nor have I touched the images directory.
I've fiddled with just about everything else and added an animated root
cursors option using 4 examples from the xancur program which is easily
found at rpmfind.net
The cursor options could require some discussion, but I have plans for
this too.

I think it all works for me, even with the Fvwm Themes Center GUI. :)
Perhaps someone could find the time to merge this stuff into the cvs as
a patch might be too complicated.
 
> I hope you understand it better now. Also see multichoice/theme.cfg.
> 

I hope I do too. It still seems a little like magic.  ;)

Alex