fvwm-themes-devel — Developing FVWM Themes

Re: Warning and Gnome problems

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

Mikhael Goikhman wrote:
> 
> On 16 Aug 2000 23:39:49 +0200, Olivier Chapuis wrote:
> >
> > My good you commit just betwenn I update the ChangeLog and
> > I commit. I've committed again I hope that I do not destroy
> > your fixes!
> 
> The last time I committed was a day ago. If you had a conflict, maybe this
> is because you didn't do 'update' before 'commit'?
>

Strange, I do cvs diff ChangeLog > diff and do not see your changes
so I send the above mail and go to commit but then the commit fail.
 
> BTW, I sometimes get 'pipe broken' errors during commit, I don't know why.
> I simply rerun the latest command until all files are actually commited.
> 
> > I will do not modify this file in the future!
> 
> Why not? :)

Because the shell is too difficult for me. What about using perl?
Moreover, it was understand "near future" :)
Olivier

Re: Comments about awol theme

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

Alex Wallis wrote:
> 
> Olivier Chapuis wrote:
> >
> > Alex Wallis wrote:
> > >
> > > Here's a couple of comments about awol theme.
> >
> > Ok I will commit this change soon.
> 
> Well I've found one or two other things I'd like to tweak just to make
> the theme a little more entertaining. I thought I'd get it all set
> before I made too much noise about it. But... no problems.  :)
> 
> >
> > > However, I'm also not entirely happy with the way other color schemes
> > > handle my IconMan colors but it may just be something I'll have to live
> > > with. I've spent some time looking at other themes but it's become
> > > rather a complex issue. I'll make some more comments later.
> 
> I'm now finding my IconMan is dying. Not sure if its the new buggy GUI
> or not, but something new seems to go wrong every time I try it! C'est
> la vie!
> 

If you speak about the "Themes Center" I do not think that it can cause
IconMan problems. See if you have a core file and send the gdb analyse
to the fvwm-devel mailing list if yes. Yes, the Themes Center is buggy
but I hope that it will be almost bug free in a near future. Any, bug
report is welcome. Also, some new things (fvwm-themes session) can
cause some problems (but not kill your IconMan).

> > >
> > > Now the "desker" also needs a little modification too.
> > > I've tried to change themes/awol/modules/pager/desker file but the
> > > module only produces 4 desks that rotate. I want to change it to more
> > > desks but it seems to only read the default desker.
> > >
> >
> > How many desk you need? I do the change because all others modules
> > themes have a 4 desks desker it is for me a kind a default but in
> > fact I've not real reasons for this.
> >
> In theory one could have up to desk +4000000000 or down to -4000000000
> or thereabouts. Plus or minus 4 billion.
> I can easily imagine someone wanting only 1 page per desk but wanting
> plenty of desks. Or vice versa, say 81 pages on just one desk.
> I was trying to make a desker for my theme that could stretch across all
> the pages on my desktop, and accurately reflect the desktop I was on.
> (Say desk -21)
> Purely for demonstration purposes basically, but also fully functional.
> I really need to spend more time delving into the wizardry you and
> Mikhael are putting together.
>

Yes, we need to add documentation to fvwm-themes. The FAQ is
out of date for example.
 
> Bottom line? I want desks -7 to +7 in awol/modules/pager/desker
> 
> Of course I actually very rarely use more than 2!  :)
>

Here I do not know what to do. Do we have to break this 4
desks default for all modules themes? Mikhael?

Olivier

Re: Warning and Gnome problems

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

On 16 Aug 2000 23:39:49 +0200, Olivier Chapuis wrote:
> 
> My good you commit just betwenn I update the ChangeLog and
> I commit. I've committed again I hope that I do not destroy
> your fixes!

The last time I committed was a day ago. If you had a conflict, maybe this
is because you didn't do 'update' before 'commit'?

BTW, I sometimes get 'pipe broken' errors during commit, I don't know why.
I simply rerun the latest command until all files are actually commited.

> I will do not modify this file in the future!

Why not? :)

Regards,
Mikhael.

Re: Warning and Gnome problems

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

Olivier Chapuis wrote:
> 
> Hello,
> 
> My first commit about the fvwm-themes session was not
> good, sorry. Now I think the stuff is ok (I use your last
> solution for themes-rc-2, Mikhael).
> Maybe you can rm all the files of the forms:
>         themes-rc* and themes/current*
> before really restart with fvwm-themes.
>

My good you commit just betwenn I update the ChangeLog and
I commit. I've committed again I hope that I do not destroy
your fixes!
I will do not modify this file in the future!
 
Olivier

Warning and Gnome problems

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

Hello,

My first commit about the fvwm-themes session was not
good, sorry. Now I think the stuff is ok (I use your last
solution for themes-rc-2, Mikhael).
Maybe you can rm all the files of the forms:
	themes-rc* and themes/current*
before really restart with fvwm-themes.

Unfortunately, it seems that fvwm-themes-start does not
work with gnome-session (at least with my "old" version of
GNOME:gnome-core-1.0.4-13rh) because GNOME is intelligent or
stupid I do not know but it retains only the windows manager
start command ...
The only solution I saw is to add an option to ft-start,
says --dummy which does not start fvwm2 and ask the user to
start fvwm as:

fvwm-themes-start -s gnome -d
gnome-session

and to use fvwm-themes-start -s gnome as wm command in the
GNOME control center.

Olivier

Re: Comments about awol theme

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

Olivier Chapuis wrote:
> 
> Alex Wallis wrote:
> >
> > Here's a couple of comments about awol theme.
> 
> Ok I will commit this change soon.

Well I've found one or two other things I'd like to tweak just to make
the theme a little more entertaining. I thought I'd get it all set
before I made too much noise about it. But... no problems.  :)

> 
> > However, I'm also not entirely happy with the way other color schemes
> > handle my IconMan colors but it may just be something I'll have to live
> > with. I've spent some time looking at other themes but it's become
> > rather a complex issue. I'll make some more comments later.

I'm now finding my IconMan is dying. Not sure if its the new buggy GUI
or not, but something new seems to go wrong every time I try it! C'est
la vie!

> >
> > Now the "desker" also needs a little modification too.
> > I've tried to change themes/awol/modules/pager/desker file but the
> > module only produces 4 desks that rotate. I want to change it to more
> > desks but it seems to only read the default desker.
> >
> 
> How many desk you need? I do the change because all others modules
> themes have a 4 desks desker it is for me a kind a default but in
> fact I've not real reasons for this.
> 
In theory one could have up to desk +4000000000 or down to -4000000000
or thereabouts. Plus or minus 4 billion. 
I can easily imagine someone wanting only 1 page per desk but wanting
plenty of desks. Or vice versa, say 81 pages on just one desk.
I was trying to make a desker for my theme that could stretch across all
the pages on my desktop, and accurately reflect the desktop I was on.
(Say desk -21)
Purely for demonstration purposes basically, but also fully functional.
I really need to spend more time delving into the wizardry you and
Mikhael are putting together.

Bottom line? I want desks -7 to +7 in awol/modules/pager/desker

Of course I actually very rarely use more than 2!  :)

Alex

Re: Session Support

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

On 15 Aug 2000 22:01:00 +0200, Olivier Chapuis wrote:
> 
> Mikhael Goikhman wrote:
> > 
> > On 14 Aug 2000 08:50:59 +0200, Olivier Chapuis wrote:
> > >
> > > Mikhael Goikhman wrote:
> > > >
> > > > Ok, but do we really need to have --session in both scripts? Probably
> > > > fvwm-themes-config needs not be aware of session, it can simply work with
> > > > themes/current and this can be symlinked (by fvwm-themes-start) to
> > > > current-default real directory. Just a though.
> > >
> > > Agree. But fvwm-themes-config have to ignore the current-* directory.
> > > I will try to implement this soon (with symlink themes-rc-2 -> themes-rc-2-*).
> > 
> > Maybe themes-rc-2 -> themes/current-*/themes-rc-2 would be less noisy
> > and more structured. I don't know.
> 
> I don't know too. But I think I will do your original idea
> (because this is already on my machine ...).

This is trivially to change. Let's try to be less noisy first.

> > Maybe a theme designer can have an option for top vus bottom layout.
> > Having default-situation= makes things more complex, which is not really
> > needed. This also requires fvwm-themes-config to be aware of sessions.
> 
> It is not really needed, but I think that this will be useful.
> Ok, you do not want these default-gnome ft config command :(

I don't like this solution, because having several defaults does not look
clean to me (when we use what, what default will show editors, all?). You
can try to improve the solution or convince me that it is not that bad.

> But now we need to have a special gnome-session support.
> 	1 - special key binding for gnome menu 
> 	2 - special Quit fvwm menu
> (I think that the components under the gnome setting  component
> are independent with "gnome-session"). So we need at least a component
> 
> settings/session-manager/
> 
> with choices: none, gnome, generic and may be other in the future

Instead of settings/session? Ok.

> Again I think that the good component have to be load (by default)
> automatically. I suggest that if a user start fvwm-themes-themes
> as
> 	fvwm-themes-start --session gnome*
> then the gnome component is load automatically (by default again!).
> We do not need to add an option to fvwm-themes-config we
> just have to look the name of the directory that is symlinked
> to themes/current .... and have a default-situation ft cfg cmd.
> Damn!

We can say that gnome support is special. In this case having a global
function like your old NosmOrGnomeOrGeneric should solve all problems, no?
For which other situations would you like to define their own defaults?

Regards,
Mikhael.

Re: fvwm-themes have a GUI Themes Selector

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

Mikhael Goikhman wrote:
> 
> I sometimes get "Too many messages sended (i.e. sent)", and "Warn: Option
> editors for <name> already out". I don't quite understand these errors.
>

The first message (in STDERR) is a bug both of FvwmScript and of the 
"Themes Center". The second message is a consequence of the first
message. I will try to fix this. The point for the second message is
that you do not have the right to popup two options editors for the
same opt/cho/sub (feature), but some SendToScript commands fail
("Too many messages sended" (not an olicha misprint :)) and
ThemesCenter does not know that ThemeOptions for a given option
is no more popup!
Olivier

Re: fvwm-themes have a GUI Themes Selector

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

On 15 Aug 2000 19:13:39 +0200, Olivier Chapuis wrote:
> 
> Mikhael Goikhman wrote:
> > 
> > On 14 Aug 2000 08:01:35 +0200, Olivier Chapuis wrote:
> > >
> > > > FvwmScript-ThemeOptions does not work for me yet.
> > 
> > com: No lock Fifo .tmp-com-lock-config- for config- communication
> > cannot open .tmp-com-buf-config- at /opt/fvwm/bin/fvwm-themes-com line 62.
> > cannot open .tmp-com-buf-config- at /opt/fvwm/bin/fvwm-themes-com line 62.
> > com: No lock Fifo .tmp-com-lock-config- for config- communication
> 
> Ok, I understand the errors (the first errors about line 105 has been 
> fixed in a previous commit), but this is strange.
> Sorry, but can you try again (Alex and Mikhael) with the current cvs
> (make install in scripts should be enough; Mikhael if you have made
> some changes in the scripts can you use the current original).
> Any others bugs report will be very helpful.

Ah, ok, now I understand. I ran FvwmScript FvwmScript-ThemeOptions
from FvwmConsole, I didn't use Opt/Cho/Sub button (it didn't work some
time ago because of syntax errors). Now it works well.

I sometimes get "Too many messages sended (i.e. sent)", and "Warn: Option
editors for <name> already out". I don't quite understand these errors.

Regards,
Mikhael.

Re: Comments about awol theme

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

Alex Wallis wrote:
> 
> Here's a couple of comments about awol theme.
> 
> Firstly, the IconMan highlighting for the button bar is _all_wrong_! :-P
> My intention was to have the writing change to green when mouse-over
> occurs, and red when the mouse is on top of the corresponding window
> with the button as depressed.
> 
> Making the folowing changes to themes/awol/colors file defines the
> module
> correctly.
> 
> # Window Lists Colorsets
> # standard item
> *FvwmThemeColorset 17 fg blue4, bg grey77, hi grey88, sh grey65, Plain,
> NoShape
> # active item
> *FvwmThemeColorset 18 fg red2, bg grey77, hi grey88, sh grey65, Plain,
> NoShape
> # iconified item
> *FvwmThemeColorset 19 fg yellow, bg grey77, hi grey88, sh grey65, Plain,
> NoShape
> # pointed item
> *FvwmThemeColorset 20 fg DarkGreen, bg grey77, hi grey88, sh grey65,
> Plain, NoShape
> 
> I also redefined/changed the iconified colors.
>

Ok I will commit this change soon.
 
> However, I'm also not entirely happy with the way other color schemes
> handle my IconMan colors but it may just be something I'll have to live
> with. I've spent some time looking at other themes but it's become
> rather a complex issue. I'll make some more comments later.
> 
> Now the "desker" also needs a little modification too.
> I've tried to change themes/awol/modules/pager/desker file but the
> module only produces 4 desks that rotate. I want to change it to more
> desks but it seems to only read the default desker.
>

How many desk you need? I do the change because all others modules
themes have a 4 desks desker it is for me a kind a default but in
fact I've not real reasons for this.

Olivier

Re: Session Support

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

Mikhael Goikhman wrote:
> 
> On 14 Aug 2000 08:50:59 +0200, Olivier Chapuis wrote:
> >
> > Mikhael Goikhman wrote:
> > >
> > > Ok, but do we really need to have --session in both scripts? Probably
> > > fvwm-themes-config needs not be aware of session, it can simply work with
> > > themes/current and this can be symlinked (by fvwm-themes-start) to
> > > current-default real directory. Just a though.
> >
> > Agree. But fvwm-themes-config have to ignore the current-* directory.
> > I will try to implement this soon (with symlink themes-rc-2 -> themes-rc-2-*).
> 
> Maybe themes-rc-2 -> themes/current-*/themes-rc-2 would be less noisy
> and more structured. I don't know.
>

I don't know too. But I think I will do your original idea
(because this is already on my machine ...).

> 
> Maybe a theme designer can have an option for top vus bottom layout.
> Having default-situation= makes things more complex, which is not really
> needed. This also requires fvwm-themes-config to be aware of sessions.

It is not really needed, but I think that this will be useful.
Ok, you do not want these default-gnome ft config command :(

But now we need to have a special gnome-session support.
	1 - special key binding for gnome menu 
	2 - special Quit fvwm menu
(I think that the components under the gnome setting  component
are independent with "gnome-session"). So we need at least a component

settings/session-manager/

with choices: none, gnome, generic and may be other in the future

Again I think that the good component have to be load (by default)
automatically. I suggest that if a user start fvwm-themes-themes
as
	fvwm-themes-start --session gnome*
then the gnome component is load automatically (by default again!).
We do not need to add an option to fvwm-themes-config we
just have to look the name of the directory that is symlinked
to themes/current .... and have a default-situation ft cfg cmd.
Damn!

Olivier

Re: fvwm-themes have a GUI Themes Selector

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

Mikhael Goikhman wrote:
> 
> On 14 Aug 2000 08:01:35 +0200, Olivier Chapuis wrote:
> >
> > > FvwmScript-ThemeOptions does not work for me yet.
> >
> > Damn! Do you have any error msg in STDERR? Which syntax error do you
> > have fixed?
> 
> One If was without Then, one - without Begin, and one more thing, which I
> don't remember now.
> 
> com: No lock Fifo .tmp-com-lock-config- for config- communication
> cannot open .tmp-com-buf-config- at /opt/fvwm/bin/fvwm-themes-com line 62.
> cannot open .tmp-com-buf-config- at /opt/fvwm/bin/fvwm-themes-com line 62.
> com: No lock Fifo .tmp-com-lock-config- for config- communication
> 
> At least now I see some widgets after some timeout, I remember yersturday
> there was only one empty window after a timeout.
>

Ok, I understand the errors (the first errors about line 105 has been 
fixed in a previous commit), but this is strange.
Sorry, but can you try again (Alex and Mikhael) with the current cvs
(make install in scripts should be enough; Mikhael if you have made
some changes in the scripts can you use the current original).
Any others bugs report will be very helpful.

> > > I don't think "FVWM Themes Center" belongs to the menu-driven interface,
> > > it belongs IMHO to "FVMW Configuration" or "FVWM Themes Configuration".
> > > It is not an essential part, although probably important for most people.
> >
> > Here I do not know, but FvwmScript-ThemesCenter will be able (I hope) to
> > do the same things that the theme management menu, it is directly
> > connected with fvwm-themes-config and its task is theme management.
> 
> Still I think we should have it in "FVMW Configuration" or "FVWM Themes
> Configuration" menu, and optionally (?) at the end of "Theme Management".

at the end of "Theme Management" seems more logic for me, for the
above reason (I've made the change).

Olivier

Re: Session Support

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

On 14 Aug 2000 08:50:59 +0200, Olivier Chapuis wrote:
> 
> Mikhael Goikhman wrote:
> > 
> > Ok, but do we really need to have --session in both scripts? Probably
> > fvwm-themes-config needs not be aware of session, it can simply work with
> > themes/current and this can be symlinked (by fvwm-themes-start) to
> > current-default real directory. Just a though.
> 
> Agree. But fvwm-themes-config have to ignore the current-* directory.
> I will try to implement this soon (with symlink themes-rc-2 -> themes-rc-2-*).

Maybe themes-rc-2 -> themes/current-*/themes-rc-2 would be less noisy
and more structured. I don't know.

> I have just some ideas for default-gnome: modules themes designer
> can start different modules by default for a default or a gnome
> session.

Some people like to have a duplication if it spead ups things (the same
stroke/keyboard/menu/buttons bindings). Say, I have a clock in FvwmButtons
and in the panel, native pager and in the panel (when I want to test gnome
support), some may prefer both native taskbar and in the panel and so on.

> > I don't like this idea very much, because it is not flexible enough,
> > i.e. if you want to add a "situation", you should change all relevent
> > theme.cfg files, i.e. a user can't do this strictly speaking, because he
> > has no write permissions for these files. 
> 
> Not a problem it is just a thing for themes designer, user will build
> its "session" theme. Any way this default-* stuff is not essential,
> I like it just because I would like that modules themes take in account
> automatically the gnome panel (with its default config).

Gnome panel default is distribution specific, I think. At least I saw
the panel at the top and bottom in default configurations.

Maybe a theme designer can have an option for top vus bottom layout.
Having default-situation= makes things more complex, which is not really
needed. This also requires fvwm-themes-config to be aware of sessions.

Regards,
Mikhael.

Re: fvwm-themes have a GUI Themes Selector

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

On 14 Aug 2000 08:01:35 +0200, Olivier Chapuis wrote:
> 
> > FvwmScript-ThemeOptions does not work for me yet.
> 
> Damn! Do you have any error msg in STDERR? Which syntax error do you
> have fixed?
  
One If was without Then, one - without Begin, and one more thing, which I
don't remember now.

com: No lock Fifo .tmp-com-lock-config- for config- communication
cannot open .tmp-com-buf-config- at /opt/fvwm/bin/fvwm-themes-com line 62.
cannot open .tmp-com-buf-config- at /opt/fvwm/bin/fvwm-themes-com line 62.
com: No lock Fifo .tmp-com-lock-config- for config- communication

At least now I see some widgets after some timeout, I remember yersturday
there was only one empty window after a timeout.

> > I don't think "FVWM Themes Center" belongs to the menu-driven interface,
> > it belongs IMHO to "FVMW Configuration" or "FVWM Themes Configuration".
> > It is not an essential part, although probably important for most people.
> 
> Here I do not know, but FvwmScript-ThemesCenter will be able (I hope) to
> do the same things that the theme management menu, it is directly
> connected with fvwm-themes-config and its task is theme management.

Still I think we should have it in "FVMW Configuration" or "FVWM Themes
Configuration" menu, and optionally (?) at the end of "Theme Management".

Regards,
Mikhael.

Comments about awol theme

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

Here's a couple of comments about awol theme.

Firstly, the IconMan highlighting for the button bar is _all_wrong_! :-P
My intention was to have the writing change to green when mouse-over
occurs, and red when the mouse is on top of the corresponding window
with the button as depressed.

Making the folowing changes to themes/awol/colors file defines the
module
correctly.

# Window Lists Colorsets
# standard item
*FvwmThemeColorset 17 fg blue4, bg grey77, hi grey88, sh grey65, Plain,
NoShape
# active item
*FvwmThemeColorset 18 fg red2, bg grey77, hi grey88, sh grey65, Plain,
NoShape
# iconified item
*FvwmThemeColorset 19 fg yellow, bg grey77, hi grey88, sh grey65, Plain,
NoShape
# pointed item
*FvwmThemeColorset 20 fg DarkGreen, bg grey77, hi grey88, sh grey65,
Plain, NoShape

I also redefined/changed the iconified colors.

However, I'm also not entirely happy with the way other color schemes
handle my IconMan colors but it may just be something I'll have to live
with. I've spent some time looking at other themes but it's become
rather a complex issue. I'll make some more comments later.

Now the "desker" also needs a little modification too.
I've tried to change themes/awol/modules/pager/desker file but the
module only produces 4 desks that rotate. I want to change it to more
desks but it seems to only read the default desker.

Some other "bugs" appear to have already been fixed! :)
More later.

Cheers.

Alex

Re: Session Support

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

Mikhael Goikhman wrote:
> 
> Let's speak about fvwm outside a session manager first.
> You suggest to implement our own sessions. This may be useful, although
> probably most of users don't need this, and in fact will never use more
> than one session. But this is ok by me. So, if I understand you correctly,
> a user will have ~/.fvwm/themes/current/ (for the default session),
> themes/current-bosshere/ and so on. New sessions start with a default
> config and a user "builds" them independandly from other ones.
> 
> > I think that the solution is easy: add a "--session name" option
> > to fvwm-themes-start and to fvwm-themes-config.
> >
> > If we start as: fvwm-themes-start --session name then
> > fvwm-themes-start will run fvwm-themes-config --session name
> > which will look at a personal/themes-name.cfg file (if not found
> > the site themes.cfg will be copied), and will build themes-rc2
> > accordingly to this themes cfg file. Moreover, we will have in
> > the Themes Management menu a popup which allows to switch between
> > these themes cfg.
> 
> Ok, but do we really need to have --session in both scripts? Probably
> fvwm-themes-config needs not be aware of session, it can simply work with
> themes/current and this can be symlinked (by fvwm-themes-start) to
> current-default real directory. Just a though.
>

Agree. But fvwm-themes-config have to ignore the current-* directory.
I will try to implement this soon (with symlink themes-rc-2 -> themes-rc-2-*).
 
> > These can be also used to reestablish the GNOME and the generic session
> > support: if the session name begin with gnome (respectively gsm (for
> > generic session manager)), then some special file can be loaded for
> > a GNOME (respectively, a session manager) support. Moreover, in this
> > way it will be easy to add support for xsm or an other session manager.
> > Finally, we can have different default for the options/settings with
> > a new theme config cmd. "default-name=" in this way we can start
> > by default different modules under a regular session or under a gnome
> > session.
> >
> > The only disadvantage that I saw with the above method is each time
> > we start fvwm-themes-start we have to rebuild themes-rc2.
> 
> Yes. Maybe we can have themes-rc-2 variants for all sessions, and
> fvwm-themes-start can manipulate them (resymlink or copy, not rebuild).
> 
> You suggest to have default-situation=, and situation is not always
> related to session. For example default-gnome=, will this be used when the
> session name starts from gnome- prefix? 

Yes if the session name start with gnome.

> How about default-laptoplow=.

I have just some ideas for default-gnome: modules themes designer
can start different modules by default for a default or a gnome
session.

> I don't like this idea very much, because it is not flexible enough,
> i.e. if you want to add a "situation", you should change all relevent
> theme.cfg files, i.e. a user can't do this strictly speaking, because he
> has no write permissions for these files. 

Not a problem it is just a thing for themes designer, user will build
its "session" theme. Any way this default-* stuff is not essential,
I like it just because I would like that modules themes take in account
automatically the gnome panel (with its default config).

> I would like only to add a new
> component (or theme if needed) 'gnome', 'laptop', without requiring
> to change existing theme configurations.
>

Agree, I think we really need a special gnome component and may be
a generic session one and maybe others (kde, cde). For laptop, I do
not think that we need a special component.

Olivier

Re: fvwm-themes have a GUI Themes Selector

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

Mikhael Goikhman wrote:
> 
> Ok, this even works. I did some syntax error fixes in your files, which I
> have found while using new scripts during several minutes. 

Yes there are still some bugs. I have just fixed one or two (maybe you
have to do a rm .tmp-com-buf* in fvwm user dir)

> Still
> FvwmScript-ThemeOptions does not work for me yet.
>

Damn! Do you have any error msg in STDERR? Which syntax error do you
have fixed?

> I don't think "FVWM Themes Center" belongs to the menu-driven interface,
> it belongs IMHO to "FVMW Configuration" or "FVWM Themes Configuration".
> It is not an essential part, although probably important for most people.
>

Here I do not know, but FvwmScript-ThemesCenter will be able (I hope) to
do the same things that the theme management menu, it is directly
connected with fvwm-themes-config and its task is theme management.

Regards, Olivier

Re: fvwm-themes have a GUI Themes Selector

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

Ok, this even works. I did some syntax error fixes in your files, which I
have found while using new scripts during several minutes. Still
FvwmScript-ThemeOptions does not work for me yet.

I don't think "FVWM Themes Center" belongs to the menu-driven interface,
it belongs IMHO to "FVMW Configuration" or "FVWM Themes Configuration".
It is not an essential part, although probably important for most people.

Regards,
Mikhael.

Re: Session Support

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

Sorry to answer only now (I just read the message).
I will think more with your cleaver suggestions and do
an other proposition.
Olivier

fvwm-themes have a GUI Themes Selector

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

:o)

More details in the ChangeLog!

Olivier

Re: Session Support

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

On 08 Aug 2000 09:32:03 +0200, Olivier Chapuis wrote:
> 
> I would like the reestablish the "session support". In fact,
> I would like to do a little bit more:
> 
> My main concern is to have the possibility to load different
> "fvwm-themes config" (i.e., personal/themes.cfg). Typically,
> on want to use different "fvwm-themes config" when running
> a regular fvwm session, a gnome session, an ac-off (laptop) 
> session, or a "my boss is in the same room" session ...etc.

Let's speak about fvwm outside a session manager first.
You suggest to implement our own sessions. This may be useful, although
probably most of users don't need this, and in fact will never use more
than one session. But this is ok by me. So, if I understand you correctly,
a user will have ~/.fvwm/themes/current/ (for the default session),
themes/current-bosshere/ and so on. New sessions start with a default
config and a user "builds" them independandly from other ones.

> I think that the solution is easy: add a "--session name" option 
> to fvwm-themes-start and to fvwm-themes-config.
> 
> If we start as: fvwm-themes-start --session name then 
> fvwm-themes-start will run fvwm-themes-config --session name
> which will look at a personal/themes-name.cfg file (if not found
> the site themes.cfg will be copied), and will build themes-rc2
> accordingly to this themes cfg file. Moreover, we will have in
> the Themes Management menu a popup which allows to switch between
> these themes cfg.

Ok, but do we really need to have --session in both scripts? Probably
fvwm-themes-config needs not be aware of session, it can simply work with
themes/current and this can be symlinked (by fvwm-themes-start) to
current-default real directory. Just a though.

> These can be also used to reestablish the GNOME and the generic session
> support: if the session name begin with gnome (respectively gsm (for
> generic session manager)), then some special file can be loaded for
> a GNOME (respectively, a session manager) support. Moreover, in this 
> way it will be easy to add support for xsm or an other session manager.
> Finally, we can have different default for the options/settings with
> a new theme config cmd. "default-name=" in this way we can start
> by default different modules under a regular session or under a gnome
> session.
> 
> The only disadvantage that I saw with the above method is each time
> we start fvwm-themes-start we have to rebuild themes-rc2. 

Yes. Maybe we can have themes-rc-2 variants for all sessions, and
fvwm-themes-start can manipulate them (resymlink or copy, not rebuild).

You suggest to have default-situation=, and situation is not always
related to session. For example default-gnome=, will this be used when the
session name starts from gnome- prefix? How about default-laptoplow=.
I don't like this idea very much, because it is not flexible enough,
i.e. if you want to add a "situation", you should change all relevent
theme.cfg files, i.e. a user can't do this strictly speaking, because he
has no write permissions for these files. I would like only to add a new
component (or theme if needed) 'gnome', 'laptop', without requiring
to change existing theme configurations.

Also defaults are probably subjective anyway, what exactly do you want to
have in default-gnome, default-laptoplow or default-bosshere?
Maybe it's possible to create a components or themes for these situations?

Regards,
Mikhael.

Re: About the CVS page on sourceforge

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

Mikhael Goikhman wrote:
> 
> On 07 Aug 2000 23:29:28 +0930, Alex Wallis wrote:
> >
> > I just noticed the "Anonymous FTP Space" directory contains an old
> > version (0.3.6) which obviously needs updating.
> 
> Join SF users and I will give you all permissions to do everything you
> think is needed yourself. There are 6 Wallis and even one AWOL already...
> 
Okay, I think I already did this before so one of those Wallis's could
already be me, but anyway I signed in as awol_  userID 61198

> I can also put the web pages into cvs if anybody wants to update them,
> add screenshots etc., just ask me.

You mean the project's homepage? or ALL the pages relating to the
project?
> 
> > As a further comment, I think occasional regular announcements to the
> > freshmeat list and/or fvwm-workers list might deserve consideration now,
> > to stimulate interest and input from new users. Perhaps even the wider
> > fvwm list and/or fvwm-announce?
> 
> I will do this for 0.4.0, we don't need to announce every minor release.

Okay, no problems. It's just that regular announcements are more likely
to get noticed than occasional ones. And I doubt that many fvwm users
are even aware of the existence of fvwm-themes......


Alex

Session Support

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

Hello,
I would like the reestablish the "session support". In fact,
I would like to do a little bit more:

My main concern is to have the possibility to load different
"fvwm-themes config" (i.e., personal/themes.cfg). Typically,
on want to use different "fvwm-themes config" when running
a regular fvwm session, a gnome session, an ac-off (laptop) 
session, or a "my boss is in the same room" session ...etc.

I think that the solution is easy: add a "--session name" option 
to fvwm-themes-start and to fvwm-themes-config.

If we start as: fvwm-themes-start --session name then 
fvwm-themes-start will run fvwm-themes-config --session name
which will look at a personal/themes-name.cfg file (if not found
the site themes.cfg will be copied), and will build themes-rc2
accordingly to this themes cfg file. Moreover, we will have in
the Themes Management menu a popup which allows to switch between
these themes cfg.
These can be also used to reestablish the GNOME and the generic session
support: if the session name begin with gnome (respectively gsm (for
generic session manager)), then some special file can be loaded for
a GNOME (respectively, a session manager) support. Moreover, in this 
way it will be easy to add support for xsm or an other session manager.
Finally, we can have different default for the options/settings with
a new theme config cmd. "default-name=" in this way we can start
by default different modules under a regular session or under a gnome
session.

The only disadvantage that I saw with the above method is each time
we start fvwm-themes-start we have to rebuild themes-rc2. 

Olivier

fvwm-themes and GTK

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

I have added an initial gtk GUI, very similar to FvwmForm-ThemeSettings.
This is intended to be an example only. There is Gtk-CRITICAL warning...
I didn't work on it more than an hour, including learning FvwmGtk.

I also had 2 days experience with Perl/GTK. There are some boring
screenshots I did for my work, in case you are interested:
  http://cortext.co.il/cortext/gtk-screenshots/

Perl/GTK is very good in all categories. But unfortunately we can't use
it, because, even thought many of users have GTK, they unlikely have
Perl/GTK installed, sadly.

We can use FvwmGtk, which became very clear for me, after I learned GTK
using perl. But FvwmGtk is FvwmForm like, i.e. has no real scripting
abilities, so you need to create it's config dynamically in perl anyway
for generic GUIs. And FvwmGtk should be an addition, not everyone has GTK.

These are just thoughts. We may want to write fvwm-themes-gtk after 0.4.0.

Regards,
Mikhael.

Re: About the CVS page on sourceforge

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

On 07 Aug 2000 23:29:28 +0930, Alex Wallis wrote:
> 
> I just noticed the "Anonymous FTP Space" directory contains an old
> version (0.3.6) which obviously needs updating.

Join SF users and I will give you all permissions to do everything you
think is needed yourself. There are 6 Wallis and even one AWOL already...

I can also put the web pages into cvs if anybody wants to update them,
add screenshots etc., just ask me.

> As a further comment, I think occasional regular announcements to the
> freshmeat list and/or fvwm-workers list might deserve consideration now,
> to stimulate interest and input from new users. Perhaps even the wider
> fvwm list and/or fvwm-announce?

I will do this for 0.4.0, we don't need to announce every minor release.

Regards,
Mikhael.