fvwm-themes-devel — Developing FVWM Themes

Re: Modifications to awol theme.

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

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
> best stored at fvwm.themes.org and keep them out of the fvwm-themes
> package. I'm thinking we could use standardised naming schemes for sound
> events and have a GUI to allow user selection of the particular sound to
> be symlinked to each event.
> Further thought is required. I'd imagine either you or Olivier might
> even have plans on this but time is the component in shortest supply.

Anything that you come with about a sound, is fine by me.
So, suggest and even implement your plan.

> > The problem is that the standard component is "sound", while you define
> > "sounds", and this new component is not included in the default [theme].

Ok, I will try to explain this again.
Take a look at the default or awol theme. The component name is "sound".
So, the component definition (including any options) should be either in
the file "sound" or in the directory "sound". You have this in directory
"sounds", this is why it is not recognized.

It does not matter where resources (images, sounds) are, they may be in
any other directory. Just specify a path to them.

> > The solution is either to use "sound" (preferable)

So, the first (the best) solution is to create directory "sound" and move
your four rc files to it. Now fix your sound.cfg (s/sounds/sound/). Easy?

> > or redefine [theme]
> > definition in theme.cfg (see @default, you may skip unexisting components).

The second possible solution (theoretical) would be to say "I don't want
to move any files, I like them in directory sounds, so I will just create
a new component called sounds." Thus create this testawol/theme.cfg file:

-----------------------------------------------------------------------
!include ../default/theme.cfg

[theme]
component+=background
component+=buttons
component+=colors
component+=menustyle
component+=modules
component+=sounds
component+=windowlook

!include-quiet sounds.cfg
=======================================================================

Now your theme contains one non-standard component. Easy? :)

> I've played about with the theme.cfg but quite frankly I  don't
> understand it.

I hope you understand it better now. Also see multichoice/theme.cfg.

> I'll try and investigate this further. Any thoughts on a $FT_SOUNDPATH ?

This should be solved in FvwmEvent, I think.

If you have any problem with soundpath, put temporarily all your wav's in
/home/awol/.fvwm/sounds and even hardcode this directory if needed.

Regards,
Mikhael.

Re: Modifications to awol theme.

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

Mikhael Goikhman wrote:
> 
> Alex, sorry for not answering, but we are really busy.
> I had some minutes to take a look at your files, but didn't run them.

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
best stored at fvwm.themes.org and keep them out of the fvwm-themes
package. I'm thinking we could use standardised naming schemes for sound
events and have a GUI to allow user selection of the particular sound to
be symlinked to each event.
Further thought is required. I'd imagine either you or Olivier might
even have plans on this but time is the component in shortest supply.

> 
> The problem is that the standard component is "sound", while you define
> "sounds", and this new component is not included in the default [theme].
> The solution is either to use "sound" (preferable) or redefine [theme]
> definition in theme.cfg (see @default, you may skip unexisting components).

I've played about with the theme.cfg but quite frankly I  don't
understand it.
The only way I can get this to work is to use file=sounds as this sets
the file/path/ to the configuration files. The file sound.cfg should get
included anyway as part of sound-extra? But it will not unload upon
changing themes to default/sound. I do not know the answer. I'm not even
sure I understand the question? I'll keep trying though.

I'm planning to have some new themes available for when fvwm.themes.org
finally goes "live", and sounds can be a large part of the fun in
theming. I'd like to eventually have a much more complex level of
soundscaping.

> 
> I don't know why $FT_DATADIR works, but $FVWM_USERDIR does not for you.
> I hope it is not critical for 0.4.2.

I'll try and investigate this further. Any thoughts on a $FT_SOUNDPATH ?

Alex

Re: Empty labels in ColorSelector

[Dan E. <da...@mk...>]

Mikhael Goikhman <mi...@ho...> writes:
> On 13 Mar 2001 22:28:09 -0500, Dan Espen wrote:
> > In the CDE menu, calendar is not spelled right.
> 
> I am not sure what does this mean. I can't find any calendar in our menus.

I think it was spelled calandar.

--
Dan Espen
444 Hoes Lane  Room RRC 1C-214           E-mail: da...@mk...
Piscataway, NJ 08854                     Phone: (732) 699-5570

Re: Modifications to awol theme.

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

Alex, sorry for not answering, but we are really busy.
I had some minutes to take a look at your files, but didn't run them.

The problem is that the standard component is "sound", while you define
"sounds", and this new component is not included in the default [theme].
The solution is either to use "sound" (preferable) or redefine [theme]
definition in theme.cfg (see @default, you may skip unexisting components).

I don't know why $FT_DATADIR works, but $FVWM_USERDIR does not for you.
I hope it is not critical for 0.4.2.

Regards,
Mikhael.

Re: Empty labels in ColorSelector

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

On 13 Mar 2001 22:28:09 -0500, Dan Espen wrote:
> 
> The menus are impressive,  I like the mini icons.

Wait for a few days then.

> The stone backgrounds are nice too.

A background from FVWM Home Page modified on fly by fvwm-themes-images.

> In the CDE menu, calendar is not spelled right.

I am not sure what does this mean. I can't find any calendar in our menus.

> On the README file on the default theme menu, the last line:
> 
> "If you really need, provide all components or create additional components."
> 
> I'm not sure what that means.

s/provide/implement/, I reworded and updated this file.

> Reloading the whole theme for every change is too slow.

Yes, a new research of where the time is spent is needed.

Regards,
Mikhael.

Re: [WM-ICONS]

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

On 14 Mar 2001 11:29:22 +0100, Olivier Chapuis wrote:
>=20
> Le Mardi 13 Mars 2001 20:24, Mikhael Goikhman a  =E9crit :
> >
> > Ok, 2 questions.
> >
> > 1) We have 83 icons. What will be 84-th? gimp, game-strategy?
>=20
> Really I will prefer gimp than game-strategy (we already have a
> lot of game icons).

I think I asked you to add gimp previously. :) Can you do this?

> > 2) Do we need to rename penguin to linux?
>=20
> I do not think so, but I've no objection.

Having a link from penguin to system (your idea) is a bit strange. :)
I probably prefer linux, but I let you to do (or not to do) the renaming.

> I've a question too: do you think that we have to use
> gnu for emacs (mini)icon style?

We can.

Regards,
Mikhael.

Re: Empty labels in ColorSelector

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

Le Mercredi 14 Mars 2001 13:35, Dan Espen a  écrit :
> Olivier Chapuis <oli...@fr...> writes:
> >
> > Yes, this is the main fvwm-themes problem. We work on minimal
> > reloading and you can try it via the Themes Management menu:
> >      Refresh and Reload -> Use experimental reloading
> > This can, under certain situation, speed up the switching, but
> > the method is not yet fully implemented.
> > You can also use the Themes Center GUI (Fvwm Configuration) which
> > allows to do several change and then apply it (Does this
> > FvwmScript work fpr you?).
>
> I think so.
>
> Whenever I click on anything in a list, it  turns all black so I can't
> read it.
>

Seems to me that it is a FvwmScript bug. When you select an item in a
list it change the item background colors. It seems that on your hardware
this color do not give a good result. I will take a look to this problem
in FvwmScript, but I am afraid that I will not found a good solution
(how to compute this color?).

Regards, Olivier

Re: Empty labels in ColorSelector

[Dan E. <da...@mk...>]

Olivier Chapuis <oli...@fr...> writes:
> Le Mercredi 14 Mars 2001 04:28, Dan Espen a  =E9crit :
> > Mikhael Goikhman <mi...@ho...> writes:
> > > On 09 Mar 2001 06:48:50 -0500, Dan Espen wrote:
> > > > Olivier Chapuis <oli...@fr...> writes:
> > > > > Le Vendredi  9 Mars 2001 00:10, vous avez =E9crit :
> > > > > > The color bars at the top of the selector are very pretty but=
 I
> > > > > > couldn'
> > > > > > figure out what they did.  Clicking in various places didn't =
do
> > > > > > anythin
> > >
> > > > I don't see any messages on my console.
> > >
> > > I hope you have installed the latest cvs. And still empty labels?
> >
> > Yes, from a few days ago.
> >
> > The labels are OK now.
> > The help window is OK now.
> >
> > Too bad the main window disappears when I press help.
> >
> =

> Do you mean you will prefer that the help appear in a separated
> window?

Yes.

> Does the color selector work normal or a click on the first 3
> palette does not change the last one as before?

Yes.

> > Maybe the selectors should have labels.
> >
> =

> What do you mean?

Some text above each color bar indicating what it does.

> >
> > The menus are impressive,  I like the mini icons.
> > There is also a lot of good stuff in the menus, unfortunately,
> > I don't have a lot of it installed.
> >
> =

> This is not normal. Only the applications which is on your path
> should appear in the "Program", "System" and "Shells" menu.
> Can you login as the user whose type "make install" and type:

My mistake.

> > Reloading the whole theme for every change is too slow.
> >
> =

> Yes, this is the main fvwm-themes problem. We work on minimal
> reloading and you can try it via the Themes Management menu:
>      Refresh and Reload -> Use experimental reloading
> This can, under certain situation, speed up the switching, but
> the method is not yet fully implemented.
> You can also use the Themes Center GUI (Fvwm Configuration) which
> allows to do several change and then apply it (Does this
> FvwmScript work fpr you?).

I think so.

Whenever I click on anything in a list, it  turns all black so I can't
read it.

--
Dan Espen
444 Hoes Lane  Room RRC 1C-214           E-mail: da...@mk...
Piscataway, NJ 08854                     Phone: (732) 699-5570

Re: [WM-ICONS]

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

Le Mardi 13 Mars 2001 20:24, Mikhael Goikhman a  écrit :
>
> Ok, 2 questions.
>
> 1) We have 83 icons. What will be 84-th? gimp, game-strategy?

Really I will prefer gimp than game-strategy (we already have a
lot of game icons).

> 2) Do we need to rename penguin to linux?
>

I do not think so, but I've no objection.

I've a question too: do you think that we have to use
gnu for emacs (mini)icon style?

Olivier

Re: Empty labels in ColorSelector

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

Le Mercredi 14 Mars 2001 04:28, Dan Espen a  écrit :
> Mikhael Goikhman <mi...@ho...> writes:
> > On 09 Mar 2001 06:48:50 -0500, Dan Espen wrote:
> > > Olivier Chapuis <oli...@fr...> writes:
> > > > Le Vendredi  9 Mars 2001 00:10, vous avez écrit :
> > > > > The color bars at the top of the selector are very pretty but I
> > > > > couldn'
> >
> > t
> >
> > > > > figure out what they did.  Clicking in various places didn't do
> > > > > anythin
> >
> > g.
> >
> > > I don't see any messages on my console.
> >
> > I hope you have installed the latest cvs. And still empty labels?
>
> Yes, from a few days ago.
>
> The labels are OK now.
> The help window is OK now.
>
> Too bad the main window disappears when I press help.
>

Do you mean you will prefer that the help appear in a separated
window?
Does the color selector work normal or a click on the first 3
palette does not change the last one as before?
 
> Maybe the selectors should have labels.
>

What do you mean?

>
> The menus are impressive,  I like the mini icons.
> There is also a lot of good stuff in the menus, unfortunately,
> I don't have a lot of it installed.
>

This is not normal. Only the applications which is on your path
should appear in the "Program", "System" and "Shells" menu.
Can you login as the user whose type "make install" and type:

fvwm-themes-menuapp --site --build-menus --remove-popup

Do you have strange message around when you make install 

if test "yes" = "yes"; then \
        a_path/fvwm-themes-menuapp --site --build-menus --remove-popup; \
fi

when you make install? Is the above sh test ok?

> The stone backgrounds are nice too.
>
> In the CDE menu, calendar is not spelled right.
>

This will be fixed when we will update fvwm-themes for
wm-icons-0.3.0 (which will be not needed, but if you like
mini-icons I think you will like it).

> On the README file on the default theme menu, the last line:
>
> "If you really need, provide all components or create additional
> components."
>
> I'm not sure what that means.
>
> Reloading the whole theme for every change is too slow.
>

Yes, this is the main fvwm-themes problem. We work on minimal
reloading and you can try it via the Themes Management menu:
     Refresh and Reload -> Use experimental reloading
This can, under certain situation, speed up the switching, but
the method is not yet fully implemented.
You can also use the Themes Center GUI (Fvwm Configuration) which
allows to do several change and then apply it (Does this
FvwmScript work fpr you?).
 

Thanks, Olivier

Re: Empty labels in ColorSelector

[Dan E. <da...@mk...>]

Mikhael Goikhman <mi...@ho...> writes:
> On 09 Mar 2001 06:48:50 -0500, Dan Espen wrote:
> > =

> > Olivier Chapuis <oli...@fr...> writes:
> > > Le Vendredi  9 Mars 2001 00:10, vous avez =E9crit :
> > > >
> > > > The color bars at the top of the selector are very pretty but I c=
ouldn'
> t
> > > > figure out what they did.  Clicking in various places didn't do a=
nythin
> g.
> > =

> > I don't see any messages on my console.
> =

> I hope you have installed the latest cvs. And still empty labels?

Yes, from a few days ago.

The labels are OK now.
The help window is OK now.

Too bad the main window disappears when I press help.

Maybe the selectors should have labels.

> Does this happen with other FvwmScript theme tools too?
> =

> Please run (the result is not a much readable text):
> =

>   fvwm-themes-script --get-msg FvwmScript-ColorSelector

If you meant to run it from a command prompt, I get:

fork> fvwm-themes-script --get-msg FvwmScript-ColorSelector
Use of uninitialized value at /opt/pub/fvwm/2.3.30/fvwm-themes-script lin=
e 646.
Title       0032Select a Color using the PalletesSelColor    0014Selected=
 Color:Help        0003HelpOk          0001OKCancel      0005CancelEND   =
      0003end

>   fvwm-themes-script --in-line-doc FvwmScript-ColorSelector
> =

> If you get something like "Documentation is not found", please try to
> add some print's in buildMsg() or buildDoc() to see what happens.

The menus are impressive,  I like the mini icons.
There is also a lot of good stuff in the menus, unfortunately,
I don't have a lot of it installed.

The stone backgrounds are nice too.

In the CDE menu, calendar is not spelled right.

On the README file on the default theme menu, the last line:

"If you really need, provide all components or create additional componen=
ts."

I'm not sure what that means.

Reloading the whole theme for every change is too slow.


--
Dan Espen
444 Hoes Lane  Room RRC 1C-214           E-mail: da...@mk...
Piscataway, NJ 08854                     Phone: (732) 699-5570

Empty labels in ColorSelector

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

On 09 Mar 2001 06:48:50 -0500, Dan Espen wrote:
>=20
> Olivier Chapuis <oli...@fr...> writes:
> > Le Vendredi  9 Mars 2001 00:10, vous avez =E9crit :
> > >
> > > The color bars at the top of the selector are very pretty but I cou=
ldn't
> > > figure out what they did.  Clicking in various places didn't do any=
thing.
>=20
> I don't see any messages on my console.

I hope you have installed the latest cvs. And still empty labels?
Does this happen with other FvwmScript theme tools too?

Please run (the result is not a much readable text):

  fvwm-themes-script --get-msg FvwmScript-ColorSelector
  fvwm-themes-script --in-line-doc FvwmScript-ColorSelector

If you get something like "Documentation is not found", please try to
add some print's in buildMsg() or buildDoc() to see what happens.

Regards,
Mikhael.

Re: [WM-ICONS]

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

On 13 Mar 2001 07:33:57 +0100, Olivier Chapuis wrote:
> 
> > Did you document all your changes in doc/icons.lst? I think no.
> 
> Yes, I plan to do this when I finish to add/change icons. But,
> do we really need so precise description of icons?

I find them useful when reworking icon sets. Usually a source icon name
and maybe the change (shrunk from 34x34, grown, converted) is enough.
These descriptions are needed if we want to prove our icons are free.

Ok, 2 questions.

1) We have 83 icons. What will be 84-th? gimp, game-strategy?
2) Do we need to rename penguin to linux?

I will work on configure and preview screenshots.

Regards,
Mikhael.

Re: [WM-ICONS]

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

Le Mardi 13 Mars 2001 01:39, Mikhael Goikhman a  écrit :
>
> There is one problem when you add new icon to, say, an icon set which uses
> 14 colors overall. It's not good to get some icon and "convert -colors 20"
> because you get 20 new unique colors. Only these 14 colors should be used.
>

Yes I know this problem, but it was impossible to add so much icons
and take this in account without palettes files and a script that
convert the icons vs these palettes.

>
> Did you document all your changes in doc/icons.lst? I think no.
>

Yes, I plan to do this when I finish to add/change icons. But,
do we really need so precise description of icons?

Olivier

Re: [WM-ICONS]

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

On 12 Mar 2001 18:39:26 +0100, Olivier Chapuis wrote:
> 
> Ok, I look at more. I think it is more prudent to do similar kde
> icon sets and then doing maybe kde3 when KDE2-2.2.x will be realesed.
> We may want to also add 16x16-kde2 and 48x48-kde but not for 0.3.0.

I didn't add 16x16-kde2 because they almost didn't change it (KDE 1.1.2),
I replaced 1-2 icons in 16x16-kde, instead.

> I think that all kde set are finished but 48x48-kde which I will finish
> this week.

I suppose you speak about 48x48-kde2. Ok, I will wait.

There is one problem when you add new icon to, say, an icon set which uses
14 colors overall. It's not good to get some icon and "convert -colors 20"
because you get 20 new unique colors. Only these 14 colors should be used.

> I think it will be good to finish the general icons sets as soon as
> possible so that we can update fvwm-themes and do the menu (partially
> done on my machine) and the icons styles files on both packages (good
> for testing the icons).

Ok, you will update menus after 0.3.0 is released.
Please do your style changes in wm-icons/devel/conf/style-icons.cfg,
then run "make create-wm-configs; make". After 0.3.0 we will copy
wm-icons/etc/fvwm2rc-wm-icons to fvwm-themes (as I usual do).

> What is your plan about 48x48-general?

I don't think I will touch it.

Did you document all your changes in doc/icons.lst? I think no.

Regards,
Mikhael.

Re: [WM-ICONS]

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

Le Vendredi  9 Mars 2001 23:08, vous avez écrit :
> On 09 Mar 2001 07:31:44 +0100, Olivier Chapuis wrote:
> > If I well understand the kde2 icons set are "hight" colors
> > KDE icons set.
>
> Not quite.
>
> 16x16-kde and 32x32-kde are from KDE 1.0.0 (low colors).
> 32x32-kde2 and 48x48-kde2 are from KDE 1.1.2 or similar (high color).
> All 4 these icons are original xpm icons (sometimes modified) from KDE.
>
> > With KDE2 there are a lot of new hight colors
> > icons, so for more themability I would like to change some (a lot)
> > of the icons of the kde2 wm-icons sets and also for consistancy
> > add a 16x16-kde2 icons set (and in the future a 48x48-kde set
> > but not for 0.3.0).
> > Any objection Mikhael?
>
> I don't have KDE2 for now, so I don't know yet whether it is better to
> rework kde2 icon sets or create kde3 icon sets (from png, I suppose).
>

Ok, I look at more. I think it is more prudent to do similar kde
icon sets and then doing maybe kde3 when KDE2-2.2.x will be realesed.
We may want to also add 16x16-kde2 and 48x48-kde but not for 0.3.0.
I think that all kde set are finished but 48x48-kde which I will finish
this week.

I think it will be good to finish the general icons sets as soon as
possible so that we can update fvwm-themes and do the menu (partially
done on my machine) and the icons styles files on both packages (good
for testing the icons).
16x16-general is finished for me, there are two problems cd-player.xpm
and multimedia.xpm. cd-player is ok for me and I am agree that 
multimedia is not very good. Do what you want!
What is your plan about 48x48-general?

Regards, Olivier

Re: Solaris make

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

On 09 Mar 2001 19:31:30 -0500, Dan Espen wrote:
> 
> If it meant to  change  the local  directories, "themes"  "images" and
> "sounds",  then I  think I  see the  problem.   The package contains a
> "themes" directory but for images and sounds there are these 2 files:
> 
> images.tar.gz
> sounds.tar.gz

Yes, because cvs and make do not like symlinks too much.
Permissions in these tarballs are already ok.

> > > What does the uppercase X in the permissions do?
> > 
> > Try the following (works well on Solaris):
> > 
> >   touch ttt; chmod a-x,g+x ttt; chmod +X ttt; ls -al ttt
> >   touch ttt; chmod a-x,g-x ttt; chmod +X ttt; ls -al ttt
> 
> Yes, it does seem to do something for files, but I tried it for
> directories like the makefile expects:

GNU chmod works like Solaris one, +X is always +x for directories.
Makefile expects exactly this.

So, I consider all known Solaris problems fixed. If no, please rereport.

I also consider all known FreeBSD problems fixed. If no, please rereport.

Regards,
Mikhael.

Re: Solaris make

[Dan E. <da...@mk...>]

Mikhael Goikhman <mi...@ho...> writes:
> On 08 Mar 2001 23:42:14 -0500, Dan Espen wrote:
> > 
> > Mikhael Goikhman <mi...@ho...> writes:
> > > On 08 Mar 2001 17:00:58 -0500, Dan Espen wrote:
> > > > 
> > > > make install gives me:
> > > > 
> > > > /bin/sh ./mkinstalldirs /opt/public/share/fvwm/2.3.30/fvwm
> > > > for dir in themes images sounds; do \
> > > > 	chmod -R o-w,go+rX $dir 2>/dev/null; \
> > > > 	rm -rf "/opt/public/share/fvwm/2.3.30/fvwm/$dir"; \
> > > > 	(if test -f $dir.tar.gz; then gzip -dc $dir.tar.gz; else \
> > > > 	tar cpf - $dir; fi) | (cd "/opt/public/share/fvwm/2.3.30/fvwm" 
> && tar x
> > > fBp -); \
> > > > 	find "/opt/public/share/fvwm/2.3.30/fvwm/$dir" -name CVS -exec 
> rm -r {}
> > >  \; 2>/dev/null ; \
> > > > done
> > > > *** Error code 1
> > > > make: Fatal error: Command failed for target `install-data-local'
...
> The idea is to change local directory permissions, not installed ones.
> These lines by Julian Gilbey are from old wm-icons, I have no time to
> rethink them.

If it meant to  change  the local  directories, "themes"  "images" and
"sounds",  then I  think I  see the  problem.   The package contains a
"themes" directory but for images and sounds there are these 2 files:

images.tar.gz
sounds.tar.gz

> > The Solaris shell requires that the "do" "done" block contain a list,
> > I needed to add an open paren after the do and a close paren before the
> > done.
> 
> But a list does not really require braces. :)
> We do have a shell access to Solaris on compilefarm.sourceforge.net, no X.
> The following works for /bin/sh on Solaris and other systems:
> 
>   for dir in a b c; do echo 1; echo 2; done
> 
> Does the following fix help (it is in cvs now):
> 
>   chmod -R o-w,go+rX $$dir 2>/dev/null || true; \

Yes, whats in cvs now works.
 
> > What does the uppercase X in the permissions do?
> 
> Try the following (works well on Solaris):
> 
>   touch ttt; chmod a-x,g+x ttt; chmod +X ttt; ls -al ttt
>   touch ttt; chmod a-x,g-x ttt; chmod +X ttt; ls -al ttt

Yes, it does seem to do something for files, but I tried it for
directories like the makefile expects:

File:

fork> touch ttt; chmod a-x,g+x ttt; chmod +X ttt; ls -al ttt
-rwxrwxr-x  1 dane  mk  0 Mar 09 19:24 ttt*
fork> touch ttt; chmod a-x,g-x ttt; chmod +X ttt; ls -al ttt
-rw-rw-r--  1 dane  mk  0 Mar 09 19:24 ttt

Directory:

fork> rm ttt
fork> mkdir ttt; chmod a-x,g+x ttt; chmod +X ttt; ls -al ttt
total 2
drwxrwxr-x   2 dane  mk   512 Mar 09 19:25 ./
drwxrwxr-x  12 dane  mk  1024 Mar 09 19:25 ../
fork> touch ttt; chmod a-x,g-x ttt; chmod +X ttt; ls -al ttt
total 2
drwxrwxr-x   2 dane  mk   512 Mar 09 19:25 ./
drwxrwxr-x  12 dane  mk  1024 Mar 09 19:25 ../

--
Dan Espen
444 Hoes Lane  Room RRC 1C-214           E-mail: da...@mk...
Piscataway, NJ 08854                     Phone: (732) 699-5570

cvs complain

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

On 09 Mar 2001 12:19:05 -0500, Dan Espen wrote:
> 
> Mikhael Goikhman <mi...@ho...> writes:
> > 
> > I suggest you to set up cvs, it is the same as
> > with fvwm, and you can always update fvwm-themes by one shell command.
> 
> I set up cvs and I have a complaint.
> 
> After I did the checkout I cd'd into the directory and did an update.
> 
> I got this message:
> 
> fork> cvs update
> sh: expect: not found

Ahh, it took me several minutes to understand you speak about cvs wrapper.
This file was supposed to be an example of the script to put into
~/bin/ needed only for developers (developers use ssh, not rsh in cvs).

This file was not supposed to have +x. I don't know why it had.
You also should not have "." first in your $PATH if you worry about a
minimal security, put it to the end! :-)

> Then I looked around and found an executable copy of cvs in
> the distribution.  I don't have expect and I don't have the cvs
> command installed in /usr/bin/cvs.
> 
> More important, I don't like downloading things that get me to execute
> code from a foreign source unexpectedly.
> 
> I think you should rename that to something like fvwm-theme-cvs.

I moved it, it was really not supposed to be run by you.
Sorry for any inconvenience.

Regards,
Mikhael.

Re: Solaris make

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

On 08 Mar 2001 23:42:14 -0500, Dan Espen wrote:
> 
> Mikhael Goikhman <mi...@ho...> writes:
> > On 08 Mar 2001 17:00:58 -0500, Dan Espen wrote:
> > > 
> > > make install gives me:
> > > 
> > > /bin/sh ./mkinstalldirs /opt/public/share/fvwm/2.3.30/fvwm
> > > for dir in themes images sounds; do \
> > > 	chmod -R o-w,go+rX $dir 2>/dev/null; \
> > > 	rm -rf "/opt/public/share/fvwm/2.3.30/fvwm/$dir"; \
> > > 	(if test -f $dir.tar.gz; then gzip -dc $dir.tar.gz; else \
> > > 	tar cpf - $dir; fi) | (cd "/opt/public/share/fvwm/2.3.30/fvwm" && tar x
> > fBp -); \
> > > 	find "/opt/public/share/fvwm/2.3.30/fvwm/$dir" -name CVS -exec rm -r {}
> >  \; 2>/dev/null ; \
> > > done
> > > *** Error code 1
> > > make: Fatal error: Command failed for target `install-data-local'

> > > This is Solaris 8 with Suns make.  Gnumake works fine.
> > 
> > Can you please add some echo lines in this for loop, like:
> 
> Its not really a make vs. gnumake issue at all.
> I don't know why it seemed that way.
> 
> When it does:
> 
> for dir in themes images sounds; do \
>  	chmod -R o-w,go+rX $dir
> 
> it has no chance of succeeding it needs $(FT_DATADIR)/
> before $$dir.

The idea is to change local directory permissions, not installed ones.
These lines by Julian Gilbey are from old wm-icons, I have no much time to
rethink them.

> The Solaris shell requires that the "do" "done" block contain a list,
> I needed to add an open paren after the do and a close paren before the
> done.

But a list does not really require braces. :)
We do have a shell access to Solaris on compilefarm.sourceforge.net, no X.
The following works for /bin/sh on Solaris and other systems:

  for dir in a b c; do echo 1; echo 2; done

Does the following fix help (it is in cvs now):

  chmod -R o-w,go+rX $$dir 2>/dev/null || true; \

> What does the uppercase X in the permissions do?

Try the following (works well on Solaris):

  touch ttt; chmod a-x,g+x ttt; chmod +X ttt; ls -al ttt
  touch ttt; chmod a-x,g-x ttt; chmod +X ttt; ls -al ttt

Regards,
Mikhael.

Re: [WM-ICONS]

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

On 09 Mar 2001 07:31:44 +0100, Olivier Chapuis wrote:
> 
> If I well understand the kde2 icons set are "hight" colors
> KDE icons set.

Not quite.

16x16-kde and 32x32-kde are from KDE 1.0.0 (low colors).
32x32-kde2 and 48x48-kde2 are from KDE 1.1.2 or similar (high color).
All 4 these icons are original xpm icons (sometimes modified) from KDE.

> With KDE2 there are a lot of new hight colors
> icons, so for more themability I would like to change some (a lot)
> of the icons of the kde2 wm-icons sets and also for consistancy
> add a 16x16-kde2 icons set (and in the future a 48x48-kde set
> but not for 0.3.0).
> Any objection Mikhael?

I don't have KDE2 for now, so I don't know yet whether it is better to
rework kde2 icon sets or create kde3 icon sets (from png, I suppose).

Regards,
Mikhael.

Re: Maybe my last themes problem report for today

[Dan E. <da...@mk...>]

Mikhael Goikhman <mi...@ho...> writes:
> On 08 Mar 2001 18:10:46 -0500, Dan Espen wrote:
> > 
> > When I bring up the color selector, the OK button has a label, but
> > the other 2 buttons are blank.
> > 
> > The middle button must be Help since it brings up a window that says
> > it can't find the documenation.  The button on that window is also
> > blank.
> 
> These internationalization problems (empty translated labels) should be
> fixed in the current cvs. I suggest you to set up cvs, it is the same as
> with fvwm, and you can always update fvwm-themes by one shell command.

I set up cvs and I have a complaint.

After I did the checkout I cd'd into the directory and did an update.

I got this message:

fork> cvs update
sh: expect: not found

Then I looked around and found an executable copy of cvs in
the distribution.  I don't have expect and I don't have the cvs
command installed in /usr/bin/cvs.

More important, I don't like downloading things that get me to execute
code from a foreign source unexpectedly.

I think you should rename that to something like fvwm-theme-cvs.

--
Dan Espen
444 Hoes Lane  Room RRC 1C-214           E-mail: da...@mk...
Piscataway, NJ 08854                     Phone: (732) 699-5570

Re: Maybe my last themes problem report for today

[Dan E. <da...@mk...>]

Olivier Chapuis <oli...@fr...> writes:
> Le Vendredi  9 Mars 2001 00:10, vous avez =E9crit :
> >
> > The color bars at the top of the selector are very pretty but I could=
n't
> > figure out what they did.  Clicking in various places didn't do anyth=
ing.
> >
> =

> It should change the forth palette: you populate the color you
> select by using black-color-white gradient.
> This is explained in the doc that I hope you should see if
> you use cvs. (you can also find it in the source:
> locale/en/FvwmScript-ColorSelector.html).
> =

> There are a lot of reason for that to does not work (The ColorSelector
> is not very important but ...): =

> - $FT_DATADIR should be set to install $datadir (fvwm-themes-start
> do this)
> - the fvwm-themes bin dir should be in the path and this is probably
> the problem with Dan.

I changed this a few months back, now
the shell that I use to start fvwm puts fvwm in my path.
Things started from my .xinitrc don't have fvwm in the path,
things started by fvwm do.

> - Some grep (and sh) commands are executed, so maybe I do not
> use universal sh.

I don't see any messages on my console.

> Olivier

--
Dan Espen
444 Hoes Lane  Room RRC 1C-214           E-mail: da...@mk...
Piscataway, NJ 08854                     Phone: (732) 699-5570

Re: Solaris make

[Dan E. <da...@mk...>]

David Koo <ko...@is...> writes:
> ::: What does the uppercase X in the permissions do?
> 
>     From "man chmod" ...
> 
>     <snip>
> 
>     The  letters `rwxXstugo' select the new permissions for the
>     affected users: read (r), write (w), execute (or access for
>     directories) (x),
> --> execute only if the file is a directory or already has execute
>     permission for some user (X)
>     
>     </snip>

That doesn't appear on my Solaris man page.

Solaris seems to accept the uppercase, but I don't think its doing
anything special with it:

/u/tools/dane/fvwm/fvwm-themes-0.4.1> mkdir /tmp/t
/u/tools/dane/fvwm/fvwm-themes-0.4.1> ls -la /tmp/t
total 32
drwxrwxr-x   2 dane     mk           117 Mar  9 06:36 .
drwxrwxrwt  10 root     sys         1750 Mar  9 06:36 ..
/u/tools/dane/fvwm/fvwm-themes-0.4.1> chmod a-x /tmp/t
/u/tools/dane/fvwm/fvwm-themes-0.4.1> ls -la /tmp/t
/tmp/t/.: Permission denied
/tmp/t/..: Permission denied
total 0
/u/tools/dane/fvwm/fvwm-themes-0.4.1> chmod +X /tmp/t
/u/tools/dane/fvwm/fvwm-themes-0.4.1> ls -la /tmp/t
total 32
drwxrwxr-x   2 dane     mk           117 Mar  9 06:36 .
drwxrwxrwt  10 root     sys         1750 Mar  9 06:36 ..

--
Dan Espen
444 Hoes Lane  Room RRC 1C-214           E-mail: da...@mk...
Piscataway, NJ 08854                     Phone: (732) 699-5570

Re: Maybe my last themes problem report for today

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

Le Vendredi  9 Mars 2001 00:10, vous avez écrit :
>
> The color bars at the top of the selector are very pretty but I couldn't
> figure out what they did.  Clicking in various places didn't do anything.
>

It should change the forth palette: you populate the color you
select by using black-color-white gradient.
This is explained in the doc that I hope you should see if
you use cvs. (you can also find it in the source:
locale/en/FvwmScript-ColorSelector.html).

There are a lot of reason for that to does not work (The ColorSelector
is not very important but ...): 
- $FT_DATADIR should be set to install $datadir (fvwm-themes-start
do this)
- the fvwm-themes bin dir should be in the path and this is probably
the problem with Dan.
- Some grep (and sh) commands are executed, so maybe I do not
use universal sh.

Olivier