fvwm-themes-devel — Developing FVWM Themes

Re: [FVWM-Themes] CDE-Theme

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

On 12 Dec 2000 18:15:23 +0100, Olivier Chapuis wrote:
> 
> It seems that the awk line is POSIX. However, the m4 esyscmd is a GNU
> extension and I do not see how to fix it without changing the logic. 
> We can transform all the .db file to m4 file  (using awk or by adding
> a new sub option to fvwm-themes-image) and use include. Or we can change
> the read command by something like:
> 
> PipeRead 'a one line program in perl or in awk/sed'
> 
> Any other suggestions?

If esyscmd does not exist in non-GNU m4, it probably can be emulated by
maketemp + syscmd + include.

It may be put into ifelse(defn({{__gnu__}}, ...) to use the current
solution without temporary files for GNU users.

Anyway I don't have non-GNU m4 to test this suggestion.

Regards,
Mikhael.

Re: Missing fonts in GUI's

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

Alex Wallis wrote:
> 
> For some time since Olivier began the locale languages thing, I have
> been missing the writing on the FvwmScript GUI's buttons. See attached
> images.
> 

Outch!
I cannot reproduce this.
Can you:
 - update to the last cvs code (I'm image that you already do this).
 - Try again and send me any errors output.
 - what is the value of your $LANG variable? en I imagine.
 - See if fvwm-themes-config run when the ConfigCenter run.
 - See if fvwm-themes-script run when the ThemesCenter run.
 - Try the help button in the ThemesCenter (2nd button from the right).
 - do you have the folowing files:
  where_fvwm-themes_is_installed/locale/en/FvwScript-ThemesCenter.msg
  where_fvwm-themes_is_installed/locale/en/FvwScript-ConfigCenter.msg

Many thanks, Olivier

Missing fonts in GUI's

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

For some time since Olivier began the locale languages thing, I have
been missing the writing on the FvwmScript GUI's buttons. See attached
images.

It makes no difference which theme/colors component I use.

Any clues?

Alex

Re: New version

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

Mikhael Goikhman wrote:
> 
> On 09 Dec 2000 16:36:34 +0100, Olivier Chapuis wrote:
> >
> > Do you think I've to do some announcemenst? Maybe just a simple
> > freshmeat announce?
> 
> I myself would not announce minor versions. Maybe just increment a version
> number in freshmeat without announcing.
> 
Regular casual announcements of minor version releases are what the
freshmeat lists are for IMO.

Alex

Re: New version

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

On 09 Dec 2000 16:36:34 +0100, Olivier Chapuis wrote:
> 
> Do you think I've to do some announcemenst? Maybe just a simple 
> freshmeat announce?

I myself would not announce minor versions. Maybe just increment a version
number in freshmeat without announcing.

Regards,
Mikhael.

Re: New version

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

Mikhael Goikhman wrote:
> 
> I don't have enough free time for some period, but I hope to have it soon.
> 
> Olivier, can you release a new fvwm-themes version?

Yes, I will release a new version the 12 or the 13 of december (I will
have a fast internet connection).
Do you think I've to do some announcemenst? Maybe just a simple 
freshmeat announce?

Olivier

Re: ConfigCenter: problems when loading themes config!

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

On 09 Dec 2000 09:26:16 +0100, Andre Goeree wrote:
> 
> I ran into this, running Configuration Center on my FreeBSD-4.2-STABLE
> box:
> 
> usage: mknod name [b | c] major minor [owner:group]
> script-32502: cannot read fifo .tmp-com-lock-script-32502

> Seems there is a difference between the Linux? and the FreeBSD mknod(8)
> command ;-).

Yes, GNU mknod includes a functionality of mkfifo (there is p option).

> Changing mknod(8) in the fvwm-themes-* scripts to mkfifo(1) seems
> to make things work.. although i'm not sure this is a proper fix..

I think, the next version of fvwm-themes will use mkfifo.
Thank you!

Regards,
Mikhael.

Re: The new Official fvwm.themes.org site

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

Mikhael Goikhman wrote:
> 
> On 07 Dec 2000 14:09:51 +1030, Alex Wallis wrote:
> >
<snip>
> > Let me know ASAP if you think any changes are necessary.
> 
> Is "Coming Soon!" page much better than 404 Error page? :) I don't know.

I think it's better than implying themes for fvwm don't exist.

> The documentation you want to put at awol.themes.org has nothing new that
> fvwm-themes-sourceforge.net does not have now. Having the same things in 2
> different places leads to a problem that it will be updated in one place
> and not in other place.  Anyway, you decide about fvwm.themes.org.

Understood, however themes.org demands at least minimal instructions for 
creating and installing themes must be somewhere on the site. I'll just
have to try to keep it all updated.

> 
> Please don't refer to FVWM as FVWM2. There is only one FVWM not two.
> Refereing to it as, say, FVWM 2.4 would be ok as well.

OK.
> 
<snip>
> 
> We may think about dividing fvwm-themes to more than one package when
> this will be more actual. wm-icons has the same problem (16 icon sets).
> 
> Still it is probably much easier to download one full package, that
> several small ones for most of peoples.

At the moment this is true, but may change.

> 
> > At this stage I realise the themes themselves are dictating the design
> > of the overall structure of the project, but eventually they should be
> > separated anyway.
> > Of course there's no reason why there can't be a minimum required number
> > of themes. I just think 12 is too many.
> >
> > IMO the "basic" fvwm-themes package could contain only say
> > default/afterstep/blackbox/cde/redmond98 and all the other themes could
> > be add-ons or contained in the FULL version.
> >
> > Just an idea.
> 
> We may remove any theme from fvwm-themes if there is an enthusiast who
> wants to maintain this theme himself. For example we may remove awol theme
> if you ask us. As for other themes there are no other than me and Olivier
> maintainers, and we prefer to have them in one place in cvs. Having all
> these themes in cvs does not contradict with releasing of several packages.
> 

I wasn't suggesting to remove themes from the project, quite the
opposite in fact.
My point was you could have dozens or even hundreds of themes in cvs IF
there was a way to make an rpm package with only chosen themes. A
compromise would be a flagged option for an rpm with only a few default
themes or ALL.

In this way new themes can enter the project or be d/l'd separately. As
it stands
now fvwm-themes is actually inappropriate for themes.org which dedicates
itself
as a repository of themes and not necessarily the theme engines.

Much of the initial audience once fvwm.themes.org pages are world
viewable, will
come from regular visitors of other themes.org pages, and most will be
unfamiliar
with the history and progress of fvwm. With a notable lack of suitable
material
for the site, I deemed it appropriate to introduce fvwm-themes as the
new "standard" for fvwm theme configurations.

As more material becomes available, the fvwm.themes.org site will evolve
and change often, reflecting the interests of the users.

Alex

ConfigCenter: problems when loading themes config!

[Andre G. <abg...@uw...>]

Hello,

I ran into this, running Configuration Center on my FreeBSD-4.2-STABLE
box:

usage: mknod name [b | c] major minor [owner:group]
script-32502: cannot read fifo .tmp-com-lock-script-32502
com: No lock Fifo .tmp-com-lock-menuapp-32391 for menuapp-32391 communication
X connection to :0.0 broken (explicit kill or server shutdown).
com: No lock Fifo .tmp-com-lock-script-32502 for script-32502 communication
cannot open .tmp-com-buf-script-32502 at /home/ago/fvwm2b/bin/fvwm-themes-com
+line 62.
[FVWM][Echo]:  ConfigCenter: problems when loading themes config!
[FVWM][Echo]:  ConfigCenter: can you send a bug report to:
[FVWM][Echo]:  ConfigCenter: <fvw...@li...>

Versions:
Fvwm-2.3.22
fvwm-themes-0.4.0

Seems there is a difference between the Linux? and the FreeBSD mknod(8)
command ;-).

Changing mknod(8) in the fvwm-themes-* scripts to mkfifo(1) seems
to make things work.. although i'm not sure this is a proper fix..
(and i have not really tested this!)

If you need more information, just ask (i'm not on this list).

Regards,

Andre.

New version

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

I don't have enough free time for some period, but I hope to have it soon.

Olivier, can you release a new fvwm-themes version?

Regards,
Mikhael.

Re: The new Official fvwm.themes.org site

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

On 07 Dec 2000 14:09:51 +1030, Alex Wallis wrote:
> 
> It was decided to put up a temporary "Coming Soon!" page with a link to
> awol.themes.org which will be just a shell account with webspace, where
> I'll put the pages I've cobbled together by stealing and rearranging
> snippets from fvwm-themes.sourceforge.net pages and some docs from the
> package.
> 
> At the moment the new pages are simply just a bunch of text files with
> no graphics, but they spell out the main details of where/how/what/why
> of fvwm-themes imho. :)
> 
> I've attached them as a small 13k tarball for any comments before I
> upload them.
> 
> Let me know ASAP if you think any changes are necessary.

Is "Coming Soon!" page much better than 404 Error page? :) I don't know.
The documentation you want to put at awol.themes.org has nothing new that
fvwm-themes-sourceforge.net does not have now. Having the same things in 2
different places leads to a problem that it will be updated in one place
and not in other place.  Anyway, you decide about fvwm.themes.org.

Please don't refer to FVWM as FVWM2. There is only one FVWM not two.
Refereing to it as, say, FVWM 2.4 would be ok as well.

> Perhaps I should start a separate thread for this.....
> On the subject of themes and themes.org, I've given some thought to the
> needs of users generally. There are those users who are minimalists, and
> possibly wouldn't necessarily like to install ALL the themes available.
> Perhaps they might like to only install one or two themes, or even just
> write their own.
> 
> Can I suggest a feature request, although I've no idea how difficult it
> may be. Can another option be added to the make rpm-dist cparams(or
> other) to only include certain themes? Or none at all except default?
> Then all the other themes we have can be packaged separately for d/l
> from the fvwm.themes.org site when it's running.

We may think about dividing fvwm-themes to more than one package when
this will be more actual. wm-icons has the same problem (16 icon sets).

Still it is probably much easier to download one full package, that
several small ones for most of peoples.

> At this stage I realise the themes themselves are dictating the design
> of the overall structure of the project, but eventually they should be
> separated anyway.
> Of course there's no reason why there can't be a minimum required number
> of themes. I just think 12 is too many.
> 
> IMO the "basic" fvwm-themes package could contain only say
> default/afterstep/blackbox/cde/redmond98 and all the other themes could
> be add-ons or contained in the FULL version.
> 
> Just an idea.

We may remove any theme from fvwm-themes if there is an enthusiast who
wants to maintain this theme himself. For example we may remove awol theme
if you ask us. As for other themes there are no other than me and Olivier
maintainers, and we prefer to have them in one place in cvs. Having all
these themes in cvs does not contradict with releasing of several packages.

Regards,
Mikhael.

The new Official fvwm.themes.org site

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

After many discussions on irc.openprojects.net #themes.org a simple
compromise has been agreed upon.

Since themes.org is about to undergo extensive upgrades and
modifications to their site, it was deemed unsuitable to try to setup
fvwm.themes.org pages with the old PHP sytem which is due to be replaced
with hopefully a more user friendly version. So....

It was decided to put up a temporary "Coming Soon!" page with a link to
awol.themes.org which will be just a shell account with webspace, where
I'll put the pages I've cobbled together by stealing and rearranging
snippets from fvwm-themes.sourceforge.net pages and some docs from the
package.

At the moment the new pages are simply just a bunch of text files with
no graphics, but they spell out the main details of where/how/what/why
of fvwm-themes imho. :)

I've attached them as a small 13k tarball for any comments before I
upload them.

Let me know ASAP if you think any changes are necessary.

Perhaps I should start a separate thread for this.....
On the subject of themes and themes.org, I've given some thought to the
needs of users generally. There are those users who are minimalists, and
possibly wouldn't necessarily like to install ALL the themes available.
Perhaps they might like to only install one or two themes, or even just
write their own.

Can I suggest a feature request, although I've no idea how difficult it
may be. Can another option be added to the make rpm-dist cparams(or
other) to only include certain themes? Or none at all except default?
Then all the other themes we have can be packaged separately for d/l
from the fvwm.themes.org site when it's running.

At this stage I realise the themes themselves are dictating the design
of the overall structure of the project, but eventually they should be
separated anyway.
Of course there's no reason why there can't be a minimum required number
of themes. I just think 12 is too many.

IMO the "basic" fvwm-themes package could contain only say
default/afterstep/blackbox/cde/redmond98 and all the other themes could
be add-ons or contained in the FULL version.

Just an idea.


Alex

Re: menus & icons styles

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

On 03 Dec 2000 21:39:04 +0100, Olivier Chapuis wrote:
> 
> It seems that there are no warning with the Style command if no
> icons are found.

I get many warnings (ok, maybe 10). They are from menu icons. I think,
titlebar mini-icons would produce a warning too (I can't test now).

> In my opinion the fact that fvwm2 remove an icon by an non existing
> one which leads to no icon image is a bug.

What should it do in case of unexisting menu icons or title icons or icons
in modules, when there are no default icon? I think a warning and an empty
icon is ok.

> One reason is that I've installed KDE2 to see the problems vs KDE1
> and now I would like to uninstall it.

You may wish to leave icons before uninstalling. They are probably a bit
more updated than ones included in the wm-icons kde2 icon sets.

Regards,
Mikhael.

Re: menus & icons styles

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

Mikhael Goikhman wrote:
> 
> On 01 Dec 2000 16:43:24 +0100, Olivier Chapuis wrote:
> >
> > I would like to do at least the following now:
> >
> > Split the (mini)icons styles in more files:
> >
> > + One under settings/iconstyle/ as the current but without the
> > GNOME and KDE applications (of course this file need some works
> > but we may wait for wm-icons 0.3)
> 
> This will not be ready without your help. I will start a new thread about
> wm-icons when I will have more time start to work on it.
>

I am ready to help with this. 
 
> > + New options under KDE for icons styles:
> >       - disabled (default?)
> >       - wm/ft-icons (maybe default?)
> 
> Depends on the number of the KDE icon style patterns in wm-icons.
> We may start with the second as a default and see if it takes time.
>

ok
 
> >       - KDE2 mini-icons (tr-images)
> >       - KDE1 mini-icons (native kde1 icons)
> >
> > Note that only mini-icons styles is needed for the last two options
> > because KDE apps give icons.
> 
> Are these normal icons defined by apps globally resize-able?
>

Yes, with kde 1.2 you can chose between 2 size (32 or 48) and more size
with kde2.
 
> The problem with KDE (or GNOME) application definitions (the icon section)
> is that it is almost guaranteed that some .desktop file lists an icon,
> which does not actually exist on the user's disk, and a user gets a lot of
> warnings and no icons in some places.
>

It seems that there are no warning with the Style command if no
icons are found.
In my opinion the fact that fvwm2 remove an icon by an non existing
one which leads to no icon image is a bug. But, if this not changed 
we need to (re)generate the GNOME/KDE icons styles files with the 
GNOME/KDE and, you are true, cannot use the intermediate above
solutions.


> > + "As above" for GNOME.
> 
> Except that GNOME applications do not set normal icons (when iconified).
> 
> > Of course this imply some changes (simplifications) in the menu
> > KDE/GNOME options but it seems to me that such menu must be
> > generated each time and that its not reasonable to generate
> > the styles fvwm-menu-desktop ...
> 
> As I understand you, these icon options will be global for all GNOME or
> KDE menus, and there will be variants for each menu (system, user..) "on"
> and "off". This is ok.
> 
> But I don't understand the second part of your paragraph.
>

fvwm-menu-desktop  can generate the icon styles but the result is not
very clean and there are various problems, one is that theme switching
is very slow if fvwm-menu-desktop is runned during a theme switching.
This is not a problem with menu because we can use DynamicPopupAction,
but we cannot do that with the styles.

> > I do not think that this logic can be bad for the future.
> 
> I don't know. I would solve this together with wm-icons, but if you see a
> reason to do it now, do it.
>

One reason is that I've installed KDE2 to see the problems vs KDE1
and now I would like to uninstall it. KDE2 applications use to much
memory in my opinion 10Mb for a simple GUI is crazy, also KDE2 is slow
on my machine. Any way I can wait, because now I use no more KDE
applications ...

I think we have to work on wm-icons and on a new version of
fvwm-themes-menuapp to solve these problems.

Olivier

Olivier

Re: menus & icons styles

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

On 01 Dec 2000 16:43:24 +0100, Olivier Chapuis wrote:
> 
> I would like to do at least the following now:
> 
> Split the (mini)icons styles in more files:
> 
> + One under settings/iconstyle/ as the current but without the
> GNOME and KDE applications (of course this file need some works
> but we may wait for wm-icons 0.3)

This will not be ready without your help. I will start a new thread about
wm-icons when I will have more time start to work on it.

> + New options under KDE for icons styles:
> 	- disabled (default?)
> 	- wm/ft-icons (maybe default?)

Depends on the number of the KDE icon style patterns in wm-icons.
We may start with the second as a default and see if it takes time.

> 	- KDE2 mini-icons (tr-images)
> 	- KDE1 mini-icons (native kde1 icons)
> 
> Note that only mini-icons styles is needed for the last two options
> because KDE apps give icons.

Are these normal icons defined by apps globally resize-able?

The problem with KDE (or GNOME) application definitions (the icon section)
is that it is almost guaranteed that some .desktop file lists an icon,
which does not actually exist on the user's disk, and a user gets a lot of
warnings and no icons in some places.

> + "As above" for GNOME.

Except that GNOME applications do not set normal icons (when iconified).

> Of course this imply some changes (simplifications) in the menu 
> KDE/GNOME options but it seems to me that such menu must be 
> generated each time and that its not reasonable to generate 
> the styles fvwm-menu-desktop ...

As I understand you, these icon options will be global for all GNOME or
KDE menus, and there will be variants for each menu (system, user..) "on"
and "off". This is ok.

But I don't understand the second part of your paragraph.

> I do not think that this logic can be bad for the future.

I don't know. I would solve this together with wm-icons, but if you see a
reason to do it now, do it.

Regards,
Mikhael.

Re: menus & icons styles

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

Mikhael Goikhman wrote:
> 
> On 26 Nov 2000 22:34:40 +0100, Olivier Chapuis wrote:
> >
> > Our menus and mini icons styles "files" need some work I think.
> >
> > Here, a proposition:
> 
> [skipped]
> 
> > I will try to start this, so I need comments ...
> 
> I think this is a complex issue. I should think well before making any
> comments. We probably can postpone this issue a bit.
> 
> BTW, rc files in wm-icons are generated from devel/conf/style-icons.cfg
> (I have a more updated version locally) and using other files in devel/.
> 

Hello,

I would like to do at least the following now:

Split the (mini)icons styles in more files:

+ One under settings/iconstyle/ as the current but without the
GNOME and KDE applications (of course this file need some works
but we may wait for wm-icons 0.3)

+ New options under KDE for icons styles:
	- disabled (default?)
	- wm/ft-icons (maybe default?)
	- KDE2 mini-icons (tr-images)
	- KDE1 mini-icons (native kde1 icons)

Note that only mini-icons styles is needed for the last two options
because KDE apps give icons.

+ "As above" for GNOME.

Of course this imply some changes (simplifications) in the menu 
KDE/GNOME options but it seems to me that such menu must be 
generated each time and that its not reasonable to generate 
the styles fvwm-menu-desktop ...

I do not think that this logic can be bad for the future.

Olivier

Re: What would be involved in fvwm.themes.org

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

On 01 Dec 2000 02:56:52 +1030, Alex Wallis wrote:
> 
> It seems I've had an avid interest in this project since before it
> began, and I obviously have more time than Mikhael or Olivier, so I'm
> willing to volunteer myself as the fvwm.themes.org Project
> Leader(whatever that means), unless anyone objects.

Good. I suggest you to start to recruit peoples to help you with this.
You don't need to do everything yourself. In fact, teoretically, a leader
only needs to handle organizational questions and manage others. :)

> At this stage I'm merely preparing some of the excellent documentation
> we have for installation etc, to make it suitable for the website.
> The graphics will be done mostly by artwiz I believe, but we can decide
> the layout. It might be nice to decide on some sort of logo or general
> icon relating to fvwm. I would suggest a tiger which should appeal to
> cat lovers everywhere!  ;-)

Tiger is ok, but probably any striped cat (calico, tabi? my english is bad)
would probably be better by me.

Get ftp://sunsite.unc.edu/pub/Linux/X11/demos/oneko-1.1b.tar.gz

And then: xv bitmaps/tora/*right2_tora.xbm

Seems nice as a prototype. :)

> If anyone has any comments or input, or is willing to help in any way,
> please let me know asap.

I suggest you not to hurry. Just think what will be on the site?
Documentation only, or some themes too? Seems we don't have any theme
except for the 12 ones included with fvwm-themes.

There are old fvwm.t.o themes at http://kfc.themes.org/old/fvwm_themes/
They are almost all the same and not so good IMHO, but there are 2-3,
which may be reimplemented (like @cheese, just replace background, @blues,
@mars, maybe @stone).

It is preferable to ask more artistic peoples (than me or you, Alex),
say Jos, or others mentioned in the HP Links section, to create themes.

Creating "look" themes in fvwm-themes format is simple.
windowlook@ and buttons@ components are not hard if you know which fvwm
command go to each one. colors@ is easy, but may be time consuming.
Optional menustyle@ and background@ are copy-and-replace ones.
All 3 or 5 files are placed into a theme directory, say stone/, and packed
to stone.tar.gz or stone.tar.bz2. Others may apply the distributed theme:

  fvwm-themes-config --install stone.tar.gz metal.tar.bz2

I may ocationally help with fvwm.themes.org, but not on a regular basis.

Regards,
Mikhael.

Re: What would be involed in...

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

Charlie Schmidt wrote:
> 
> -
> 
> fvwm.t.o will need (at a minimum) a Project Lead, and a Maintainer (although,
> extra people are always welcome and needed).  I believe we still want to keep
> all the graphics work internal (by artwiz), but the layout is up to the Project
> Lead.
> 
> So, anyone interested in working at fvwm.themes.org should get together and
> talk to us at t.o about getting it up and running.
> 
I had a quick chat on the #themes.org at irc.openprojects.net

Subsequently I've written an email to ar...@th... requesting his
assistance.

It seems I've had an avid interest in this project since before it
began, and I obviously have more time than Mikhael or Olivier, so I'm
willing to volunteer myself as the fvwm.themes.org Project
Leader(whatever that means), unless anyone objects.
At this stage I'm merely preparing some of the excellent documentation
we have for installation etc, to make it suitable for the website.
The graphics will be done mostly by artwiz I believe, but we can decide
the layout. It might be nice to decide on some sort of logo or general
icon relating to fvwm. I would suggest a tiger which should appeal to
cat lovers everywhere!  ;-)

If anyone has any comments or input, or is willing to help in any way,
please let me know asap.

Preparing a new fvwm section for themes.org

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

Hi,

I've been told you are the wizard of artistry at themes.org, and that
your assistance would be invaluable in creating a suitable set of pages
for inclusion of fvwm into the themes.org repository.

I'm not sure what exactly is involved, but I have begun preparing the
documentation I feel is pertinent to both fvwm and fvwm-themes, for
inclusion on the site. We probably have too much.

Please inform us if you can, of any requirements you may have, and the
necessary steps we must take.

At this stage I have volunteered to undertake the Project Leadership,
subject to no objections from others.

If you could reply to our mailing list at
fvw...@li...  all points raised by you could
then be discussed by all involved.

Regards

Alex Wallis

Re: What would be involed in...

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

On 29 Nov 2000 09:56:56 -0600, An Thi-Nguyen Le wrote:
> 
> ... reviving the old themes.org site for fvwm2? 

Hi, An.

FVWM fans and their time would be involved.

If you want to help, it is a good idea to be subscribed to this list and
be familar with fvwm-themes at http://fvwm-themes.sourceforge.net/ .

Regards,
Mikhael.

Re: What would be involed in...

[Charlie S. <ish...@th...>]

-

I work at t.o, and want to do everything possible to get fvwm.themes.org
up and running again.

However, I don't have a huge amoutn of time on my hands at the moment,
so the best thing would be to pop in #themes.org on irc.openprojects.net
or email fee...@th..., and express an interest in working there
or getting it set up.

fvwm.t.o will need (at a minimum) a Project Lead, and a Maintainer (although,
extra people are always welcome and needed).  I believe we still want to keep
all the graphics work internal (by artwiz), but the layout is up to the Project
Lead.

So, anyone interested in working at fvwm.themes.org should get together and
talk to us at t.o about getting it up and running.


[Wed, 29 Nov 2000 09:56:56 -0600] <An Thi-Nguyen Le> 

> .... reviving the old themes.org site for fvwm2? 


-- 
Charlie Schmidt - ish...@th...

What would be involed in...

[An Thi-N. Le <an...@ew...>]

... reviving the old themes.org site for fvwm2? 


-- 
An Thi-Nguyen Le
|You will be a winner today.  Pick a fight with a four-year-old.

Re: Error in last commit?

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

Olivier Chapuis wrote:
> 
> Alex Wallis wrote:
> >
> > Olivier Chapuis wrote:
> > >
> > > Alex Wallis wrote:
> > > >
> > >
> > > Ooops, hope this is fixed now.
> > > Thanks, Olivier
> > > --
> >
> > Um....now I get.....
> 
> Ok ..., I do not understand what happen, but it is my fault ...
> Anyawy I hope that now this is really fixed.
> Thanks, Olivier

It is. Merci beaucoup!  :)

Alex

Re: Error in last commit?

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

Alex Wallis wrote:
> 
> Olivier Chapuis wrote:
> >
> > Alex Wallis wrote:
> > >
> >
> > Ooops, hope this is fixed now.
> > Thanks, Olivier
> > --
> 
> Um....now I get.....
> Making all in ru
> make[2]: Entering directory `/home/awol/cvs/fvwm-themes/locale/ru'
> make[2]: *** No rule to make target `FvwmScript-ThemeOption.msg', needed
> by `all-am'.  Stop.
> make[2]: Leaving directory `/home/awol/cvs/fvwm-themes/locale/ru'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/awol/cvs/fvwm-themes/locale'
> make: *** [all-recursive] Error 1
> awol@as1-38:~/cvs/fvwm-themes >
> 

Ok ..., I do not understand what happen, but it is my fault ...
Anyawy I hope that now this is really fixed.
Thanks, Olivier

Re: Error in last commit?

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

Olivier Chapuis wrote:
> 
> Alex Wallis wrote:
> >
> 
> Ooops, hope this is fixed now.
> Thanks, Olivier
> --

Um....now I get.....
Making all in ru
make[2]: Entering directory `/home/awol/cvs/fvwm-themes/locale/ru'
make[2]: *** No rule to make target `FvwmScript-ThemeOption.msg', needed
by `all-am'.  Stop.
make[2]: Leaving directory `/home/awol/cvs/fvwm-themes/locale/ru'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/awol/cvs/fvwm-themes/locale'
make: *** [all-recursive] Error 1
awol@as1-38:~/cvs/fvwm-themes >


Alex