Menu
▾
▴
fvwm-themes-devel — Developing FVWM Themes
You can subscribe to this list here.
| 2000 |
Jan
(40) |
Feb
(57) |
Mar
(31) |
Apr
(62) |
May
(15) |
Jun
(38) |
Jul
(46) |
Aug
(50) |
Sep
(13) |
Oct
(41) |
Nov
(65) |
Dec
(36) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(15) |
Feb
(50) |
Mar
(57) |
Apr
(10) |
May
(24) |
Jun
(10) |
Jul
(14) |
Aug
(20) |
Sep
(9) |
Oct
(32) |
Nov
(4) |
Dec
(3) |
| 2002 |
Jan
|
Feb
(8) |
Mar
(3) |
Apr
(3) |
May
(15) |
Jun
(23) |
Jul
(11) |
Aug
|
Sep
(6) |
Oct
(7) |
Nov
|
Dec
(30) |
| 2003 |
Jan
(8) |
Feb
(5) |
Mar
(4) |
Apr
(9) |
May
(11) |
Jun
|
Jul
(5) |
Aug
|
Sep
(22) |
Oct
(30) |
Nov
(13) |
Dec
|
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
(6) |
May
(2) |
Jun
|
Jul
|
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
(1) |
Dec
(2) |
| 2008 |
Jan
(1) |
Feb
|
Mar
(12) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
(10) |
Oct
|
Nov
|
Dec
(4) |
|
From: Mikhael G. <mi...@ho...> - 2002-09-02 20:15:50
|
I have added several new themes in cvs. Here are screenshots (the first 4) at: http://fvwm-themes.sf.net/windowdecors/ As usual if you use the latest fvwm-themes cvs, you should first upgrade to the latest fvwm cvs (currently 2.5.4-devel). Regards, Mikhael. |
|
From: TAIWO A. <tai...@en...> - 2002-07-18 16:51:25
|
Dear Sir, REQUEST FOR YOUR UNRESERVED ASSISTANCE Firstly, I must solicit your confidence in this transaction, this is by virtue of its nature as being utterly confidential and top secret. Though I know that a transaction of this magnitude will make any one apprehensive and worried, but I am assuring you that all will be well at the end of the day.We have decided to contact you due to the urgency of this transaction, as we have been reliably informed of it's swiftness and confidentiality. Let me start by first introducing myself properly to you. I am Engr. Taiwo Ajayi, a Manager at the Union Bank Nigeria PLC, Lagos. I came to know of you in my private search for a reliable and reputable person to handle a very confidential transaction, which involves the transfer of a huge sum of money to a foreign account requiring maximum confidence. A foreigner, Late Engineer William Adams, an oil Merchant /contractor with the federal Government of Nigeria, until his death three years ago in a ghastly air crash, banked with us here at the Union Bank PLC,Lagos, and had a closing balance of USD$22.2M (Twenty-Two Million, Two Hundred Thousand United States Dollars) which the bank now unquestionably expects to be claimed by any of his available foreign next of kin or alternatively be donated to a discredited trust fund for arms and ammunition at a military war collage here in Nigeria. Fervent valuable efforts are being made by the Union Bank to get in touch with any of late Engr. William Adams's next of kin (he had no known wife and children) that the management under the influence of our chairman, board of directors, Retired Major General Kalu Uke Kalu, that an arrangement for the fund to be declared "UNCLAIMABLE " and then be subsequently donated to the trust fund for Arms and Ammunition, which will further enhance the course of war in Africa and the world in general. In order to avert this negative development, myself and some of my trusted colleagues in the bank now seek for your permission to have you stand as late Engr.WILLIAMS ADAMSs next of kin so that the fund, USD$22.2M, would be subsequently transferred and paid into your bank account as the beneficiary next of kin. All documents and proves to enable you get this fund have been carefully worked out and we are assuring you a 100% risk free involvement. Your share would be 30% of the total amount. 10% has been set aside for expenses, while the rest would be for myself and my colleagues for purposes in your country. If this proposal is OK by you and you do not wish to take advantage of the trust we hope to bestow on you and your company, then kindly get to me immediately via my e-mail address furnishing me with your most confidential telephone, fax and e-mail, so that I can forward to you the relevant details of this transaction. Thank you in advance for your anticipated co-operation. Regards. Engr. Taiwo Ajayi Tel:+234-90-505561 Email: tai...@en... |
|
From: Alexis R. <ri...@ne...> - 2002-07-16 15:02:29
|
Mikhael Goikhman <mi...@ho...> writes: > On 15 Jul 2002 21:37:06 +0200, Alexis Rimbaud wrote: >> >> There is a line in menu-system/fvwm_themes.in which causes the >> following error when I run update-menus (Debian): >> >> --- >> alexis@cliff:~$ update-menus >> In file "/etc/menu-methods//fvwm_themes", at (or in the definition at >> that ends at) line 355: >> function ltitle()=translate(lang(),title()) >> >> Unknown function: "lang" >> /etc/menu-methods//fvwm_themes: Aborting >> Update-menus[32350]: Script /etc/menu-methods//fvwm_themes returned >> error status 1. >> --- >> >> The line number here is not the real line number you have. In fact, I >> merged the fvwm_themes*.h.in a unique fvwm_themes.in file because the >> Debian Policy doesn't allow non-executable extra files in >> /etc/menu-methods. > > Can you try to patch this yourself? I don't think anyone else has > Debian. I could try but I'm not skilled enough for this. > If you can't fix this, my common sence says you may replace that line > with: function ltitle()=title() This is what I use for now. :-) Cheers, Alexis |
|
From: Mikhael G. <mi...@ho...> - 2002-07-16 13:10:27
|
On 15 Jul 2002 21:37:06 +0200, Alexis Rimbaud wrote: > > There is a line in menu-system/fvwm_themes.in which causes the > following error when I run update-menus (Debian): > > --- > alexis@cliff:~$ update-menus > In file "/etc/menu-methods//fvwm_themes", at (or in the definition at > that ends at) line 355: > function ltitle()=translate(lang(),title()) > > Unknown function: "lang" > /etc/menu-methods//fvwm_themes: Aborting > Update-menus[32350]: Script /etc/menu-methods//fvwm_themes returned > error status 1. > --- > > The line number here is not the real line number you have. In fact, I > merged the fvwm_themes*.h.in a unique fvwm_themes.in file because the > Debian Policy doesn't allow non-executable extra files in > /etc/menu-methods. Can you try to patch this yourself? I don't think anyone else has Debian. If you can't fix this, my common sence says you may replace that line with: function ltitle()=title() Regards, Mikhael. |
|
From: Alexis R. <ri...@ne...> - 2002-07-15 19:35:12
|
Hi, There is a line in menu-system/fvwm_themes.in which causes the following error when I run update-menus (Debian): --- alexis@cliff:~$ update-menus In file "/etc/menu-methods//fvwm_themes", at (or in the definition at that ends at) line 355: function ltitle()=translate(lang(),title()) Unknown function: "lang" /etc/menu-methods//fvwm_themes: Aborting Update-menus[32350]: Script /etc/menu-methods//fvwm_themes returned error status 1. --- The line number here is not the real line number you have. In fact, I merged the fvwm_themes*.h.in a unique fvwm_themes.in file because the Debian Policy doesn't allow non-executable extra files in /etc/menu-methods. Cheers, Alexis |
|
From: Mikhael G. <mi...@ho...> - 2002-07-15 17:46:39
|
On 15 Jul 2002 13:39:10 +0200, Alexis Rimbaud wrote:
>
> With that:
>
> ./configure --prefix=/usr \
> --mandir=/usr/share/man \
> --disable-build-menus \
> --disable-run-updatemenu \
> --disable-run-ft-config
>
> and:
>
> $(MAKE) install ROOT_PREFIX=$(CURDIR)/debian/fvwm-themes \
> prefix=$(CURDIR)/debian/fvwm-themes/usr
>
>
> I get:
> ---
> [...]
> /bin/sh ../mkinstalldirs /usr/share/man/man1
> [...]
> ---
>
> instead of:
> ---
> /bin/sh ../mkinstalldirs $(CURDIR)/debian/fvwm-themes/usr/share/man
> ---
It works just like you requested. You should use:
./configure --prefix=/usr \
--mandir='/${prefix}/share/man' \
^^^^^^^^^^
--disable-build-menus \
--disable-run-updatemenu \
--disable-run-ft-config
and:
$(MAKE) install ROOT_PREFIX=$(CURDIR)/debian/fvwm-themes \
prefix=$(CURDIR)/debian/fvwm-themes/usr
Yes, there should be a leading slash, otherwise /usr/man will be used
instead of /usr/share/man that you want. This is an fvwm-themes artifact.
Maybe sometimes I will make the leading slash not needed, but not now.
Regards,
Mikhael.
|
|
From: Alexis R. <ri...@ne...> - 2002-07-15 11:37:20
|
Mikhael Goikhman <mi...@ho...> writes:
> On 15 Jul 2002 02:51:24 +0200, Alexis Rimbaud wrote:
>>
>> The standard way to build a package is to run dpkg-buildpackage in the
>> source directory. You just need a debian/ directory and the files set
>> to build the package.
>
> Yes, but someone should just submit a patch for this deb/ directory (I do
> not want it to conflict with the debian/ one) and add "make deb-dist" for
> inclusion in the mainstream. It could be as general as possible; just
> creating a deb package that is equivalent to a pure "make install" from a
> tarball is good enough.
Frankly, I don't if it is feasible.
>> > Well, neither fvwm nor fvwm-themes do not have configuration that is not
>> > data. There is no division between two in fvwm.
>>
>> The "static data" are data which aren't modified after installation.
>> The theme-rc* files may be modified by fvwm-themes-config when it is
>> run by root for global settings. So these files should be in /etc
>> just like /etc/X11/fvwm/system.fvwm2rc since themes-rc* files
>> substitute for fvwm2rc.
>
> I have a feeling that either we don't interpret a Debian policy correctly
> or it is bad. /usr/share should be used for share-able data that is
> 1) global for all users, 2) may be shared between different machines even
> on different architectures, so it should be arch-independent. Whether
> /usr/share files are modified after an instalation or not is up to the
> system administrator. He may modify the global data, why not? For example,
> someone posted fvwm.vim to the fv...@fv... list. I installed it as
> /usr/share/vim/vim61/syntax/fvwm.vim in place of the old one. If I would
> like to add a complitely new perl2.vim, I would install it to the same
> directory, not /etc. Similarly, I would modify a global emacs config by
> changing files in /usr/share/emacs/20.5/lisp, not /etc.
Yes but these vim and elisp files are add-on. They aren't global
configuration. We don't want to see /usr/share/fvwm/themes go to /etc
even if you can add, remove or modify the themes. But the themes-rc*
files are for global user configuration. However, if you think that
these files must stay in /usr/share, so OK--I'll make symlink in /etc.
> fvwm-themes by default does not write to FVWM_DATADIR, it only writes to
> FVWM_USERDIR even if run as root. But it may help with modifying the
> global data, for example - install, uninstall new themes, change the
^^^^^^^^^^
> default current theme configuration.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
That's just the point! :-)
[...]
>> >> Another problem is that if I specify
>> >> --with-ft-datadir=/etc/X11/fvwm-themes, it tries to install it
>> >> directly to /etc/... instead of ROOT_DIR/etc/.... So it also should
>> >> be fixed. I've joined a little patch which add some functionality.
>> >> The --with-ft-confdir is not completely implemented and it also has
>> >> the same problem as --with-ft-datadir explained above.
>> >
>> > I don't quite understand the problem and what is ROOT_DIR. Please explain
>> > what you try to achieve. Does "make ROOT_PREFIX=/tmp/bubu install" help?
>>
>> Sorry, I wanted to write `ROOT_PREFIX'. Concerning ROOT_PREFIX, it
>> work for most of the directory created during the installation but
>> when I specify a directory with configure, it ignores ROOT_PREFIX and
>> tries to install the files (concerned by the passed option) directly
>> in /. In fact, if you want to build a .deb, you need to put all the
>> installed files (/bin/*, /usr/share/* etc.) in
>> debian/temporary_directory (reconstituing the whole tree).
>
> ROOT_PREFIX works for rpms, this line is used:
>
> make prefix=$RPM_BUILD_ROOT/usr ROOT_PREFIX=$RPM_BUILD_ROOT install
With that:
./configure --prefix=/usr \
--mandir=/usr/share/man \
--disable-build-menus \
--disable-run-updatemenu \
--disable-run-ft-config
and:
$(MAKE) install ROOT_PREFIX=$(CURDIR)/debian/fvwm-themes \
prefix=$(CURDIR)/debian/fvwm-themes/usr
I get:
---
[...]
/bin/sh ../mkinstalldirs /usr/share/man/man1
[...]
---
instead of:
---
/bin/sh ../mkinstalldirs $(CURDIR)/debian/fvwm-themes/usr/share/man
---
I can avoid the problem by adding something like:
$(MAKE) install ROOT_PREFIX=$(CURDIR)/debian/fvwm-themes \
prefix=$(CURDIR)/debian/fvwm-themes/usr
man1dir=$(CURDIR)/debian/fvwm-themes/usr/share/man/man1
but this is ugly... I have _not_ this problem if I do _not_ specify
--mandir to configure. And the problem is the same for
--with-ft-datadir so this might be a bug...
>> > I don't think a patch for confdir is needed (and you don't really use it
>> > except for creating a difectory on install). If you feel strongly about
>> > it, try to convince me that the current solution is not good.
>>
>> If there are files which may be modified after installation for global
>> configuration, so these files shall go to /etc.
>
> If you really want to have /etc, you should symlink themes-rc* files to
> it, but I don't think /etc is needed.
OK, I will do it that way.
Cheers,
Alexis
|
|
From: Mikhael G. <mi...@ho...> - 2002-07-15 03:28:20
|
On 15 Jul 2002 02:51:24 +0200, Alexis Rimbaud wrote:
>
> The standard way to build a package is to run dpkg-buildpackage in the
> source directory. You just need a debian/ directory and the files set
> to build the package.
Yes, but someone should just submit a patch for this deb/ directory (I do
not want it to conflict with the debian/ one) and add "make deb-dist" for
inclusion in the mainstream. It could be as general as possible; just
creating a deb package that is equivalent to a pure "make install" from a
tarball is good enough.
> > Well, neither fvwm nor fvwm-themes do not have configuration that is not
> > data. There is no division between two in fvwm.
>
> The "static data" are data which aren't modified after installation.
> The theme-rc* files may be modified by fvwm-themes-config when it is
> run by root for global settings. So these files should be in /etc
> just like /etc/X11/fvwm/system.fvwm2rc since themes-rc* files
> substitute for fvwm2rc.
I have a feeling that either we don't interpret a Debian policy correctly
or it is bad. /usr/share should be used for share-able data that is
1) global for all users, 2) may be shared between different machines even
on different architectures, so it should be arch-independent. Whether
/usr/share files are modified after an instalation or not is up to the
system administrator. He may modify the global data, why not? For example,
someone posted fvwm.vim to the fv...@fv... list. I installed it as
/usr/share/vim/vim61/syntax/fvwm.vim in place of the old one. If I would
like to add a complitely new perl2.vim, I would install it to the same
directory, not /etc. Similarly, I would modify a global emacs config by
changing files in /usr/share/emacs/20.5/lisp, not /etc.
fvwm-themes by default does not write to FVWM_DATADIR, it only writes to
FVWM_USERDIR even if run as root. But it may help with modifying the
global data, for example - install, uninstall new themes, change the
default current theme configuration. Actually it is currently overridden
anyway on the first user's run, so although it is possible to modify
global themes-rc files after installation, it is pointless.
> > The old confdir (for one file system.fvwm2rc only) is still
> > supported in fvwm, but deprecated. I think you may safely pass this
> > policy, the global themes-rc files are only changed by a sysadmin on
> > installation time, they need not be changed otherwise, so may be
> > considered static.
>
> Why needn't they changed after installation? I thought these files
> were for global configuration.
"fvwm-themes-start" creates all needed files in the user home directory,
so these themes-rc* files may be excluded from the package. They provide
some defence. For example a user may still run "fvwm-themes-start" or
"fvwm -f themes-rc" even if he has no home directory at all (wrong $HOME,
wrong $FVWM_USERDIR or simply home directories are not mounted).
> > I would like if fvwm.deb stops to use confdir as well. There are 2 data
> > directories, FVWM_DATADIR and FVWM_USERDIR, I don't see a need in the
> > third one, this only needlessly complicates things.
>
> The official fvwm Debian package sources provide a FVWM_CONFDIR:
You may see the Debian specific patch in the same sources.
> -- configure.in --
> FVWM_CONFDIR='${sysconfdir}'dnl used _only_ to search for system.fvwm2rc
>
> But I don't know if the official sources have it...
Yes, I added this comment, but I hoped to remove FVWM_CONFDIR somewhen...
> >> Another problem is that if I specify
> >> --with-ft-datadir=/etc/X11/fvwm-themes, it tries to install it
> >> directly to /etc/... instead of ROOT_DIR/etc/.... So it also should
> >> be fixed. I've joined a little patch which add some functionality.
> >> The --with-ft-confdir is not completely implemented and it also has
> >> the same problem as --with-ft-datadir explained above.
> >
> > I don't quite understand the problem and what is ROOT_DIR. Please explain
> > what you try to achieve. Does "make ROOT_PREFIX=/tmp/bubu install" help?
>
> Sorry, I wanted to write `ROOT_PREFIX'. Concerning ROOT_PREFIX, it
> work for most of the directory created during the installation but
> when I specify a directory with configure, it ignores ROOT_PREFIX and
> tries to install the files (concerned by the passed option) directly
> in /. In fact, if you want to build a .deb, you need to put all the
> installed files (/bin/*, /usr/share/* etc.) in
> debian/temporary_directory (reconstituing the whole tree).
ROOT_PREFIX works for rpms, this line is used:
make prefix=$RPM_BUILD_ROOT/usr ROOT_PREFIX=$RPM_BUILD_ROOT install
> > I don't think a patch for confdir is needed (and you don't really use it
> > except for creating a difectory on install). If you feel strongly about
> > it, try to convince me that the current solution is not good.
>
> If there are files which may be modified after installation for global
> configuration, so these files shall go to /etc.
If you really want to have /etc, you should symlink themes-rc* files to
it, but I don't think /etc is needed. Without symlinks you should patch
fvwm to search files in 3 directories instead of the current 2.
Regards,
Mikhael.
|
|
From: Alexis R. <ri...@ne...> - 2002-07-15 00:49:29
|
Mikhael Goikhman <mi...@ho...> writes:
> On 15 Jul 2002 00:13:23 +0200, Alexis Rimbaud wrote:
>>
>> I plan to create a package of fvwm-themes for Debian and include it in
>> the archive shortly.
>
> Nice.
>
> I have some wishes too. We have a common procedure for creating rpms using
> "make rpm-dist" in fvwm, fvwm-themes and wm-icons. This is pretty useful
> for 2 purposes, any user may build an rpm from the tarball (for example,
> from a daily snapshot) for his home usage; and creating rpms from the
> official releases is easy: "./configure; make rpm-dist release=1". I would
> like to have a directory deb and "make deb-dist" in these packages. This
> is mostly for an easy creation of unofficial pure debs from a tarball.
The standard way to build a package is to run dpkg-buildpackage in the
source directory. You just need a debian/ directory and the files set
to build the package.
[...]
> Well, neither fvwm nor fvwm-themes do not have configuration that is not
> data. There is no division between two in fvwm.
The "static data" are data which aren't modified after installation.
The theme-rc* files may be modified by fvwm-themes-config when it is
run by root for global settings. So these files should be in /etc
just like /etc/X11/fvwm/system.fvwm2rc since themes-rc* files
substitute for fvwm2rc.
> The old confdir (for one file system.fvwm2rc only) is still
> supported in fvwm, but deprecated. I think you may safely pass this
> policy, the global themes-rc files are only changed by a sysadmin on
> installation time, they need not be changed otherwise, so may be
> considered static.
Why needn't they changed after installation? I thought these files
were for global configuration.
> I would like if fvwm.deb stops to use confdir as well. There are 2 data
> directories, FVWM_DATADIR and FVWM_USERDIR, I don't see a need in the
> third one, this only needlessly complicates things.
The official fvwm Debian package sources provide a FVWM_CONFDIR:
-- configure.in --
FVWM_CONFDIR='${sysconfdir}'dnl used _only_ to search for system.fvwm2rc
But I don't know if the official sources have it...
>> Another problem is that if I specify
>> --with-ft-datadir=/etc/X11/fvwm-themes, it tries to install it
>> directly to /etc/... instead of ROOT_DIR/etc/.... So it also should
>> be fixed. I've joined a little patch which add some functionality.
>> The --with-ft-confdir is not completely implemented and it also has
>> the same problem as --with-ft-datadir explained above.
>
> I don't quite understand the problem and what is ROOT_DIR. Please explain
> what you try to achieve. Does "make ROOT_PREFIX=/tmp/bubu install" help?
Sorry, I wanted to write `ROOT_PREFIX'. Concerning ROOT_PREFIX, it
work for most of the directory created during the installation but
when I specify a directory with configure, it ignores ROOT_PREFIX and
tries to install the files (concerned by the passed option) directly
in /. In fact, if you want to build a .deb, you need to put all the
installed files (/bin/*, /usr/share/* etc.) in
debian/temporary_directory (reconstituing the whole tree).
>> Content-Description: patch
>
> I may apply a patch for --disable-run-ft-config.
OK.
> I don't think a patch for confdir is needed (and you don't really use it
> except for creating a difectory on install). If you feel strongly about
> it, try to convince me that the current solution is not good.
If there are files which may be modified after installation for global
configuration, so these files shall go to /etc.
> Changing names of menus (for Mdk and Debian) is Debian specific and should
> not be applied to the mainstream.
Sure.
Cheers,
Alexis
|
|
From: Mikhael G. <mi...@ho...> - 2002-07-14 23:51:05
|
On 15 Jul 2002 00:13:23 +0200, Alexis Rimbaud wrote: > > I plan to create a package of fvwm-themes for Debian and include it in > the archive shortly. Nice. I have some wishes too. We have a common procedure for creating rpms using "make rpm-dist" in fvwm, fvwm-themes and wm-icons. This is pretty useful for 2 purposes, any user may build an rpm from the tarball (for example, from a daily snapshot) for his home usage; and creating rpms from the official releases is easy: "./configure; make rpm-dist release=1". I would like to have a directory deb and "make deb-dist" in these packages. This is mostly for an easy creation of unofficial pure debs from a tarball. > I've run into some problems: I want the global > configuration files to reside in /etc as mandated by the Debian > Policy--/usr/share is for static data (like the theme data itself). > However, the configure and Makefile scripts in their current form > doesn't seem to support any other configuration than that the global > themes-rc files resides in another place than FT_DATADIR. Do you > think it would be possible to add a --with-ft-confdir to the configure > script (with FT_DATADIR as the default) to specify a location for the > themes-rc* files where output global operations (fvwm-themes-config > --site) will be stored. Well, neither fvwm nor fvwm-themes do not have configuration that is not data. There is no division between two in fvwm. The old confdir (for one file system.fvwm2rc only) is still supported in fvwm, but deprecated. I think you may safely pass this policy, the global themes-rc files are only changed by a sysadmin on installation time, they need not be changed otherwise, so may be considered static. Actually themes themselves may be added and removed (not changed) after instalation, I hope this matches the Debian policy. I would like if fvwm.deb stops to use confdir as well. There are 2 data directories, FVWM_DATADIR and FVWM_USERDIR, I don't see a need in the third one, this only needlessly complicates things. > Another problem is that if I specify > --with-ft-datadir=/etc/X11/fvwm-themes, it tries to install it > directly to /etc/... instead of ROOT_DIR/etc/.... So it also should > be fixed. I've joined a little patch which add some functionality. > The --with-ft-confdir is not completely implemented and it also has > the same problem as --with-ft-datadir explained above. I don't quite understand the problem and what is ROOT_DIR. Please explain what you try to achieve. Does "make ROOT_PREFIX=/tmp/bubu install" help? > Content-Description: patch I may apply a patch for --disable-run-ft-config. I don't think a patch for confdir is needed (and you don't really use it except for creating a difectory on install). If you feel strongly about it, try to convince me that the current solution is not good. Changing names of menus (for Mdk and Debian) is Debian specific and should not be applied to the mainstream. Regards, Mikhael. |
|
From: Jeff M. <JM...@se...> - 2002-07-10 22:12:01
|
The updates in 0.6.1 to remove colons (:) from the file names now gets
fvwm-themes almost working on cygwin. You can start up fvwm themes, and
pick a theme.
But the cygwin.dll (latests 1.3.12-2) does not support fifos, but
fvwm-themes appears to use them for the "configuration" menu options. You
get errors like these:
==================
mkfifo: cannot create fifo ``.tmp-com-lock-script-1764'': Function not
implemented
script-1764: cannot read fifo .tmp-com-out-script-1764
fvwm-themes-script: internal error 1
OS error: No such file or directory
killing FvwmScript-ConfigCenter
fvwm-themes[com]: fail to create fifo .tmp-com-out-script-1764
Can you send a bug report to fvw...@li...com:
No lock Fifo .tmp-com-lock-script-1764 for script-1764 communication
===================
It looks like the lack of fifo's in cygwin is a known issue with the cygwin
devs. I found these threads on the cygwin mailing list from July 2001 and
September 2001:
http://sources.redhat.com/ml/cygwin/2001-07/msg00772.html
http://sources.redhat.com/ml/cygwin/2001-09/msg01714.html
No discussions since, so I'm not sure if anybody within cygwin is actively
working on adding fifos.
Until cygwin gets support for fifos, fvwm-themes may want to indicate that
it only partially works with cygwin -- you can pick which theme you want to
use, but the theme customization tools may not work. If support for cygwin
is a big enough deal, fvwm-themes could use something other then fifos. I'm
sure that would not be easy...
Jeff
|
|
From: Mikhael G. <mi...@ho...> - 2002-06-30 10:38:51
|
On 30 Jun 2002 16:08:02 +0930, Alex Wallis wrote: > > > I think that having 2 packages is good. We may just rename fvwm-themes-base > > to fvwm-themes. > > I agree with all of Olivier's comments, but would we also then need an > fvwm-themes-all package? With all the themes included? Or perhaps a > permanently separated package set? I also agree with Olivier, but is this the best thing to do now? I don't think having 3 packages is better then 1 or 2. I also think we should have one src rpm and thus maybe one src tarball. > I also have found issues/problems with the fvwm-themes-extra.rpm and new > users. I'd make the extras package as a .tar.gz ONLY, and add the > instructions to use fvwm-themes-config --site -install command to > install it. This would then clearly demonstrate how easy theme > installation actually is, and perhaps encourage new users, and make it > easier for distributions to decide to include the updated fvwm-themes > packages. What is the problem with the extra rpm? Rpms are less problematic than tarballs, installing/uninstalling is clean because of package dependences. Having the extra tarball only makes it harder for an rpm user to upgrade if he already uses some component from the extra themes. With the current rpms if there is only one base rpm, he should even first uninstall extra themes, otherwise he may end up with old themes or components. > So my vote is for the base package to be called simply fvwm-themes-0.x.x > and the extras package permanently made into a tarball only release. What about this solution? We distribute one fvwm-themes tarball with everything we have in the cvs. We distribute one fvwm-themes rpm and one src.rpm. I.e. the current "make dist" and "make rpm-dist". By default, only base themes are installed just like in wm-icons by default only general icon sets are installed. We may also additionally distrubute fvwm-themes-base and fvwm-themes-extra rpms, this is not a problem, just another "make rpm-dist3". I would make a default to be to install all themes and only have one full rpm, but the solution above is also acceptable. Regards, Mikhael. |
|
From: Alex W. <aw...@pr...> - 2002-06-30 06:42:06
|
Olivier Chapuis wrote: > > On Sat, Jun 29, 2002 at 10:55:31PM +0000, Mikhael Goikhman wrote: > > I thought a lot about the packaging, it is not an easy decision. > > > > I think having 2 packages fvwm-themes-base and fvwm-themes-extra did not > > bring any advantage to us. The original plan was to have more theme > > submissions, but this is failed. Alex wanted such division to submit > > all extra themes to themes.org or freshmeat, but I don't see that. > > So the good side of such division is questionable. > > > > Some avantages to have 2 packages. If you just install fvwm-themes-base > then: > - you save download time and disk space (~2.5 Mb) > - fvwm-themes-config is faster > So for a weak machine installing just fvwm-themes-base is not a > so bad idea. > > > The bad sides are that it is harder for users to install and uninstall > > fvwm-themes with all themes. It is also not very clear what is the main > > package; fvwm-themes-x.y.z.tar.gz is expected or "fvwm-themes" when typed > > in the rpm search. It seems that distributors did not like this division > > as well. SuSE, FreeBSD and GNU-Darwin all did not upgrade the old 0.4.x, > > probably because 0.5.0+ is divided to 2 packages. But I may be wrong. > > > > Maybe, the error we made is to name the base package fvwm-themes-base > and not just fvwm-themes. > > > I think we should have fvwm-themes package. The question is whether to > > have or not fvwm-themes-extra. Unless someone wants to support his theme > > (i.e. update it to work with the latest fvwm-themes) we may just > > distribute what we have in the fvwm-themes cvs in one package. > > > > Any thoughts against or for this decision? > > > > I think that having 2 packages is good. We may just rename fvwm-themes-base > to fvwm-themes. > > Olivier > I agree with all of Olivier's comments, but would we also then need an fvwm-themes-all package? With all the themes included? Or perhaps a permanently separated package set? I also have found issues/problems with the fvwm-themes-extra.rpm and new users. I'd make the extras package as a .tar.gz ONLY, and add the instructions to use fvwm-themes-config --site -install command to install it. This would then clearly demonstrate how easy theme installation actually is, and perhaps encourage new users, and make it easier for distributions to decide to include the updated fvwm-themes packages. So my vote is for the base package to be called simply fvwm-themes-0.x.x and the extras package permanently made into a tarball only release. Alex |
|
From: Olivier C. <oli...@fr...> - 2002-06-30 05:48:46
|
On Sat, Jun 29, 2002 at 10:55:31PM +0000, Mikhael Goikhman wrote: > I thought a lot about the packaging, it is not an easy decision. > > I think having 2 packages fvwm-themes-base and fvwm-themes-extra did not > bring any advantage to us. The original plan was to have more theme > submissions, but this is failed. Alex wanted such division to submit > all extra themes to themes.org or freshmeat, but I don't see that. > So the good side of such division is questionable. > Some avantages to have 2 packages. If you just install fvwm-themes-base then: - you save download time and disk space (~2.5 Mb) - fvwm-themes-config is faster So for a weak machine installing just fvwm-themes-base is not a so bad idea. > The bad sides are that it is harder for users to install and uninstall > fvwm-themes with all themes. It is also not very clear what is the main > package; fvwm-themes-x.y.z.tar.gz is expected or "fvwm-themes" when typed > in the rpm search. It seems that distributors did not like this division > as well. SuSE, FreeBSD and GNU-Darwin all did not upgrade the old 0.4.x, > probably because 0.5.0+ is divided to 2 packages. But I may be wrong. > Maybe, the error we made is to name the base package fvwm-themes-base and not just fvwm-themes. > I think we should have fvwm-themes package. The question is whether to > have or not fvwm-themes-extra. Unless someone wants to support his theme > (i.e. update it to work with the latest fvwm-themes) we may just > distribute what we have in the fvwm-themes cvs in one package. > > Any thoughts against or for this decision? > I think that having 2 packages is good. We may just rename fvwm-themes-base to fvwm-themes. Olivier |
|
From: Mikhael G. <mi...@ho...> - 2002-06-29 22:56:15
|
I thought a lot about the packaging, it is not an easy decision. I think having 2 packages fvwm-themes-base and fvwm-themes-extra did not bring any advantage to us. The original plan was to have more theme submissions, but this is failed. Alex wanted such division to submit all extra themes to themes.org or freshmeat, but I don't see that. So the good side of such division is questionable. The bad sides are that it is harder for users to install and uninstall fvwm-themes with all themes. It is also not very clear what is the main package; fvwm-themes-x.y.z.tar.gz is expected or "fvwm-themes" when typed in the rpm search. It seems that distributors did not like this division as well. SuSE, FreeBSD and GNU-Darwin all did not upgrade the old 0.4.x, probably because 0.5.0+ is divided to 2 packages. But I may be wrong. I think we should have fvwm-themes package. The question is whether to have or not fvwm-themes-extra. Unless someone wants to support his theme (i.e. update it to work with the latest fvwm-themes) we may just distribute what we have in the fvwm-themes cvs in one package. Any thoughts against or for this decision? Regards, Mikhael. |
|
From: Mikhael G. <mi...@ho...> - 2002-06-25 22:38:43
|
Jos, I like what I see here: http://www.xs4all.nl/~josvanr/cdemu.png I hope you will submit something that is more or less may be included into fvwm-themes. All buttons should call fvwm-themes-config with correct parameters (to change color scheme, background, fonts). There should be a boolean option (like 4 vus 8 colors) to automatically apply colors to all aplications by calling fvwm-themes-xrdb if chosen. Other changes should be done to properties of cde components as well. I think some new component functionality is needed too. I see these problems with fvwm-themes-xrdb that should be solved somehow. It should not override the user's ~/.Xdefaults or ~/.gtkrc, but modify resources on the fly when called. And more important, it should be able to store all original application colors and then restore them. How? Several questions. 1) How many different fonts CDE uses? One, two? 2) Does CDE active item in menus look pressed as in screenshot? 3) Is wait cursor so big? Can you create cursors@cde component? 4) The old question. Does CDE ever use black foreground? P.S. I filtered out "Content-Type: text/html" messages. Regards, Mikhael. |
|
From: Wireless T. <mai...@wi...> - 2002-06-25 20:38:19
|
<html> <head> <meta name="generator" content="HTML Tidy, see www.w3.org"> <title>Wireless Team: Outdoor Wireless Equipment</title> <meta name="description" content= "Wireless Team is specialized in producing wireless network equipment. Find out more information about our award winning products at www.wirelessteam.net"> <meta name="keywords" content= "wireless, outdoor, router, equipment, power injector, technical, support, ethernet, fast, network, hubs, switches, adapters, NIC, servers"> <meta http-equiv="Content-Type" content= "text/html; charset=iso-8859-1"> <link href="http://www.wirelessteam.net/stylesheet.css" rel= "stylesheet" type="text/css"> </head> <body bgcolor="#FFFFFF" text="#000000" leftmargin="0" topmargin="0" marginwidth="0" marginheight="0"> <table width="100%" border="0" cellspacing="1" cellpadding="0" bgcolor="#FFFFFF" align="center"> <tr> <td colspan="2"> <table width="100%" border="0" cellspacing="0" cellpadding="0"> <tr> <td background="http://www.wirelessteam.net/images/bkgrnd.gif"><img src="http://www.wirelessteam.net/images/shim.gif" width="100" height="20"> </td> <td align="right" width="300"><img src= "http://www.wirelessteam.net/images/logo.gif" width="300" height= "43" border="0"></td> </tr> </table> </td> </tr> <tr> <td colspan="2"> <table border="0" cellpadding="1" cellspacing="0" width="100%" background="http://www.wirelessteam.net/images/bkgrnd_nav.gif" height="30"> <tr> <td align="right" valign="middle"> <table border="0" cellspacing="0" cellpadding="0"> <tr valign="bottom"> <td><a href="http://www.wirelessteam.net/index.html"><img src= "http://www.wirelessteam.net/images/home.gif" width="90" height= "14" border="0"></a></td> <td><a href="http://www.wirelessteam.net/aboutus.html"><img src= "http://www.wirelessteam.net/images/aboutus.gif" width="100" height="14" border="0"></a></td> <td><a href="http://www.wirelessteam.net/contactus.html"><img src= "http://www.wirelessteam.net/images/contactus.gif" width="110" height="14" border="0"></a></td> <td><a href="http://www.wirelessteam.net/faq.html"><img src= "http://www.wirelessteam.net/images/faq.gif" width="100" height= "14" border="0"></a></td> </tr> </table> </td> </tr> </table> </td> </tr> <tr> <td colspan="2"> <table width="100%" border="0" cellspacing="1" cellpadding="0"> <tr> <td valign="top"> <table width="100%" border="0" cellspacing="0" cellpadding="0"> <tr> <td colspan="2"></td> </tr> <tr> <td bgcolor="#F5F5F5" valign="top"> </td> <td align="center"> <table width="100%" border="0"> <tr> <td> <ul> <li><font color="#990000"><b>Low Cost One Stop Solution</b></font></li> <li><font color="#990000"><b>True Easy To Use Device.</b></font></li> <li><font color="#990000"><b>Superior Range And Throughput</b></font></li> <li><font color="#990000"><b>Built-In Antenna</b></font></li> <li><font color="#990000"><b>No Additional Equipment Needed</b></font></li> <li><font color="#990000"><b>Multiple Configuration Tools</b></font></li> <li><font color="#990000"><b>Based On Linux Firmware</b></font></li> <li><font color="#990000"><b>Full Network Address Translation (NAT).</b></font></li> <li><font color="#990000"><b>Bandwidth Shaping Support Included.</b></font></li> <li><font color="#990000"><b>Linux Shell For Custom Configurations</b></font></li> </ul> </td> <td colspan="2"><img src= "http://www.wirelessteam.net/images/img-new.jpg" width="500" height="300"></td> </tr> <tr> <td> </td> <td><img src="http://www.wirelessteam.net/images/price.gif" width= "150" height="23"></td> <td><a href="http://www.wirelessteam.net/orders.html"> <img src="http://www.wirelessteam.net/images/ordernow.gif" width="150" height="23"></a></td> </tr> </table> </td> </tr> <tr> <td bgcolor="#f5f5f5"> </td> <td align="left" valign="top"> <table width="99%" border="0" cellspacing="5" cellpadding="5" align="right"> <tr> <td colspan="2"> <p><b>The Outdoor Wireless Router</b> is a flexible network solution designed to provide a new high-speed alternative for delivering broadband connections. The Wireless Router helps to bypass telecommunications charges for expensive local loops and costly equipment usually needed to establish a T1 (1.5 Mbps) or faster connections. The Wireless Router helps you take advantage of the rapidly changing Internet, and to enhance your company's productivity at a very reasonable price.</p> <p><b>The Outdoor Wireless Router</b> is totally adapted for outdoor mounting and the base system includes integrated antenna. It is equipped with power injector as well. Thus prevents you from having problems with power supplies at open areas and gives you the possibility to have the device at a distance of 100-140 m from your switch or hub.</p> <p><b>With a full 100mW of transmit power</b> and the best receive sensitivity in the industry it has the longest range and best reliability available for wireless clients. Advanced signal processing helps manage the multi-path propagation often found in office environments. Intelligent filtering addresses ambient noise and interference that can decrease network performance. Building upon Cisco leadership in wireless LAN (WLAN) performance, it provides the greatest throughput available so users can enjoy virtually the same connectivity they gain from wired connections. Based on direct sequence spread spectrum (DSSS) technology and operating in the 2.4-GHz band, the device complies with the IEEE 802.11b standard-ensuring interoperability with all other compliant WLAN products.</p> <p><br> </p> </td> </tr> <tr> <td colspan="2"> </td> </tr> </table> </td> </tr> <tr> <td bgcolor="#f5f5f5" rowspan="3"> </td> <td align="left" valign="top"> </td> </tr> <tr> <td align="left" valign="top"> <table width="100%" border="0"> <tr> <td align="left" valign="top"> <table width="99%" border="0" cellspacing="5" cellpadding="5" align="right"> <tr> <td bordercolor="#CCCC99" valign="top"><font class= "bottomtxt">This mailing is done only to people who have requested info from one of our sites, or downloaded our Software. If you have recieved this email in error and you wish to be removed from future mailings, please reply with the subject "<b>Remove</b>" and our software will automatically block you from their future mailings.<br> <br> </font> </td> </tr> </table> </td> </tr> <tr> <td> </td> </tr> </table> </td> </tr> </table> </td> </tr> </table> </td> </tr> </table> </body> </html> |
|
From: Mikhael G. <mi...@ho...> - 2002-06-20 10:48:18
|
On 20 Jun 2002 12:07:11 +0200, Riswick, J.G.A. van wrote: > > I was wondering if in fvwm-themes there is somewhere a > function that in some magic way finds an icon for a given > application, maybe through some kind of an icon-database > or something. I'm working on an application launching > panel, and one of the problems i face is to always find > an icon for a given application. It is possible by using > the gnome libraries, but I'd prefer not to... Well, yes, there is an application-matching-pattern-to-icon database. But it will not help you. There is a need in a wider application database including name, resource strings and category. This should be enough to assign an icon (using wm-icons categories), to automatically create application menus and to implement application choosers for bindings and panels like yours. You may use GNOME or KDE *.desktop database for now, I think. Or maybe even query FreshMeat online to get a category, I don't know. Regards, Mikhael. |
|
From: Riswick, J.G.A. v. <J.G...@tu...> - 2002-06-20 10:07:35
|
Hi! I like the 'flat' look of this icon set. I was wondering if in fvwm-themes there is somewhere a function that in some magic way finds an icon for a given application, maybe through some kind of an icon-database or something. I'm working on an application launching panel, and one of the problems i face is to always find an icon for a given application. It is possible by using the gnome libraries, but I'd prefer not to... best regards jos -----Original Message----- For your info, here is a preview of the new icon set by Maciej Szymanski: http://wm-icons.sf.net/preview/48x48-infox.html |
|
From: Mikhael G. <mi...@ho...> - 2002-06-20 09:45:17
|
For your info, here is a preview of the new icon set by Maciej Szymanski: http://wm-icons.sf.net/preview/48x48-infox.html BTW, fvwm-themes-0.6.1 was released yesterday. Besides the other things it includes now an updated 16x16-kde icon set instead of 16x16-general: http://wm-icons.sf.net/preview/16x16-kde.html All these updates will be included in the next wm-icons release. Regards, Mikhael. |
|
From: Staff <Hea...@om...> - 2002-06-18 00:54:17
|
SGkNCg0KPGh0bWw+DQoNCjxoZWFkPg0KDQo8bWV0YSBodHRwLWVxdWl2PSJD b250ZW50LVR5cGUiIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD13aW5k b3dzLTEyNTIiPg0KDQo8bWV0YSBuYW1lPSJHRU5FUkFUT1IiIGNvbnRlbnQ9 Ik1pY3Jvc29mdCBGcm9udFBhZ2UgNC4wIj4NCg0KPG1ldGEgbmFtZT0iUHJv Z0lkIiBjb250ZW50PSJGcm9udFBhZ2UuRWRpdG9yLkRvY3VtZW50Ij4NCg0K PHRpdGxlPlRoZXJlIGFyZSB0aHJlZSBkaWZmZXJlbnQgdHlwZXMgb2YgSEdI IHByb2R1Y3RzPC90aXRsZT4NCg0KPC9oZWFkPg0KDQo8Ym9keSBiYWNrZ3Jv dW5kPSJjbG91ZHMuanBnIj4NCg0KPHA+PGZvbnQgc2l6ZT0iNCI+PGZvbnQg Y29sb3I9IiM4MDAwMDAiPjxiPlRoZXJlIGFyZSB0aHJlZSBkaWZmZXJlbnQg dHlwZXMgb2YNCg0KSEdIIHByb2R1Y3RzLjwvYj48L2ZvbnQ+PGJyPg0KDQpU aGUgY29uZnVzaW9uIGlzIHRoYXQgYWxsIHRocmVlIGFyZTxicj4NCg0KYWR2 ZXJ0aXNlZCBhcyBpZiB0aGV5IHdlcmUgdGhlIHNhbWUuPC9mb250Pjxicj4N Cg0KJm5ic3A7PGJyPg0KDQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsgPHU+VGhlIHRocmVlIHR5cGVzIGFyZTo8L3U+PGJy Pg0KDQombmJzcDs8YnI+DQoNCjxiPjEpPC9iPiAtLS0gPGZvbnQgY29sb3I9 IiMwMDAwRkYiPjxiPkhvbWVvcGF0aGljIEhHSDwvYj48L2ZvbnQ+PGJyPg0K DQo8Yj4yKTwvYj4gLS0tIDxmb250IGNvbG9yPSIjMDAwMEZGIj48Yj5QcmUt Y3Vyc29yIEhHSDwvYj48L2ZvbnQ+PGJyPg0KDQo8Yj4zKTwvYj4gLS0tIDxm b250IGNvbG9yPSIjMDAwMEZGIj48Yj5SZWFsIG9yIHN5bnRoZXRpYyBIR0g8 L2I+PC9mb250Pg0KDQooZGVsaXZlcmVkIGJ5IGluamVjdGlvbjxicj4NCg0K Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IG9y LCBieSBhbiBvcmFsIHNwcmF5IG1ldGhvZCkuPGJyPg0KDQombmJzcDs8YnI+ DQoNCkRvIHlvdSBrbm93IGRpZmZlcmVuY2VzPzxicj4NCg0KJm5ic3A7PGJy Pg0KDQpDYWxsIHVzIGFuZCB3ZSdsbCBleHBsYWluIHRoZW0gdG8geW91Ljxi cj4NCg0KJm5ic3A7PGJyPg0KDQpPdXIgdG9sbCBmcmVlIG51bWJlciBpcyA8 Zm9udCBjb2xvcj0iIzAwMDA4MCI+PGI+MS04ODgtNjIxLTczMDA8L2I+PC9m b250Pjxicj4NCg0KQW4gSEdIIHN0YWZmIG1lbWJlciBpcyBhdmFpbGFibGU8 YnI+DQoNCjkgdG8gNSBQYWNpZmljIFRpbWUuPGJyPg0KDQpJZiBhZnRlciBo b3VycywgcGxlYXNlIGxlYXZlIHlvdSBuYW1lPGJyPg0KDQphbmQgZGF5IGFu ZCBldmVuaW5nIHBob25lIG51bWJlcnMuPGJyPg0KDQpXZSB3aWxsIGNhbGwg eW91IGJhY2sgaW4gYSBubyBwcmVzc3VyZSw8YnI+DQoNCmVkdWNhdGlvbmFs IG1hbm5lci48YnI+DQoNCklmIHlvdSBhcmUgb3ZlcnNlYXMgY2FsbCB5b3Vy IGxvbmcgZGlzdGFuY2U8YnI+DQoNCm9wZXJhdG9yIGFuZCBhc2sgdG8gYmUg Y29ubmVjdGVkIHRvIG91cjxicj4NCg0KcGhvbmUgbnVtYmVyLiZuYnNwOyBX ZSB3aWxsIGNhbGwgeW91IGJhY2sgc288YnI+DQoNCndlIGNhbiBwYXkgZm9y IHRoZSBsb25nIGRpc3RhbmNlIGNoYXJnZXMuPGJyPg0KDQombmJzcDs8YnI+ DQoNCjxmb250IGNvbG9yPSIjRkYwMDAwIj5Gb3IgbW9yZSBpbmZvcm1hdGlv biBvbiBIR0ggcmVhZCBvbi4uLi4uLi4uLi4uLjwvZm9udD48YnI+DQoNCiZu YnNwOzxicj4NCg0KSEFWRSBZT1UgSEVBUkQgT0Y8YnI+DQoNCkhVTUFOIEdS T1dUSCBIT1JNT05FIChIR0gpPz8/PGJyPg0KDQombmJzcDs8YnI+DQoNCiZu YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBSZWxlYXNlZCBieSB5b3VyIG93biBw aXR1aXRhcnkgZ2xhbmQsIEhHSCBzdGFydHMNCg0KZGVjbGluaW5nPGJyPg0K DQppbiB5b3VyIDIwcywgZXZlbiBtb3JlIGluIHlvdXIgMzBzIGFuZCA0MHMs IGV2ZW50dWFsbHkgcmVzdWx0aW5nPGJyPg0KDQppbiB0aGUgc2hyaW5rYWdl IG9mIG1ham9yIG9yZ2FucyAtLSBwbHVzLCBhbGw8YnI+DQoNCm90aGVyIHN5 bXB0b21zIHJlbGF0ZWQgdG8gb2xkIGFnZS48YnI+DQoNCiZuYnNwOzxicj4N Cg0KJm5ic3A7PGJyPg0KDQpJTiBUSE9VU0FORFMgT0YgQ0xJTklDQUwgU1RV RElFUyw8YnI+DQoNCkhHSCBIQVMgQkVFTiBTSE9XTiBUTyBBQ0NPTVBMSVNI IFRIRSBGT0xMT1dJTkc6PGJyPg0KDQombmJzcDs8YnI+DQoNCiogUmVkdWNl IEJvZHkgRmF0IGFuZCBCdWlsZCBMZWFuIE11c2NsZTxicj4NCg0KJm5ic3A7 Jm5ic3A7IFdJVEhPVVQgRVhFUkNJU0UhPGJyPg0KDQombmJzcDs8YnI+DQoN CiogRW5oYW5jZSBTZXh1YWwgUGVyZm9ybWFuY2U8YnI+DQoNCiZuYnNwOzxi cj4NCg0KKiBSZW1vdmUgV3JpbmtsZXMgYW5kIENlbGx1bGl0ZTxicj4NCg0K Jm5ic3A7PGJyPg0KDQoqIExvd2VyIEJsb29kIFByZXNzdXJlIGFuZCBJbXBy b3ZlIENob2xlc3Rlcm9sIFByb2ZpbGU8YnI+DQoNCiZuYnNwOzxicj4NCg0K KiBJbXByb3ZlIFNsZWVwLCBWaXNpb24gYW5kIE1lbW9yeTxicj4NCg0KJm5i c3A7PGJyPg0KDQoqIFJlc3RvcmUgSGFpciBDb2xvciBhbmQgR3Jvd3RoPGJy Pg0KDQombmJzcDs8YnI+DQoNCiogU3RyZW5ndGhlbiB0aGUgSW1tdW5lIFN5 c3RlbTxicj4NCg0KJm5ic3A7PGJyPg0KDQoqIEluY3JlYXNlIEVuZXJneSBh bmQgQ2FyZGlhYyBPdXRwdXQ8YnI+DQoNCiZuYnNwOzxicj4NCg0KKiBUdXJu IGJhY2sgeW91ciBib2R5J3MgQmlvbG9naWNhbCBUaW1lIENsb2NrIDEwIC0g MjAgeWVhcnM8YnI+DQoNCiZuYnNwOzxicj4NCg0KKiBMaXZlIExvbmdlciBB TkQgU3Ryb25nZXI8YnI+DQoNCiZuYnNwOzxicj4NCg0KQWxsIG5hdHVyYWwg YW5kIG9yZ2FuaWMgcGxhbnQgYmFzZWQ8YnI+DQoNCiZuYnNwOzxicj4NCg0K PGZvbnQgY29sb3I9IiMwMDAwRkYiPjxiPkZFRUwgMTAgWUVBUlMgWU9VTkdF UiBXSVRIIE9SQUwgU1BSQVkgSEdILjxicj4NCg0KR1VBUkFOVEVFRDwvYj48 L2ZvbnQ+PGJyPg0KDQombmJzcDs8YnI+DQoNCiZuYnNwOyZuYnNwOyZuYnNw OyBXZSBhcmUgdGhlIG1hbnVmYWN0dXJlciBhbmQgd2Ugc2VsbCBkaXJlY3Rs eSB0byBEb2N0b3JzLDxicj4NCg0KQ2hpcm9wcmFjdG9ycywgYW5kIGNvbnN1 bWVycyB3b3JsZCB3aWRlIHRoZSBoaWdoZXN0IGdyYWRlPGJyPg0KDQombmJz cDtIR0ggT3JhbCBTcHJheSBhdmFpbGFibGUuJm5ic3A7PGJyPg0KDQombmJz cDs8YnI+DQoNCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBXaXRoIGludGVy bmV0IG1hcmtldGluZywgd2UgYXJlIGFibGUgdG8gc2F2ZQ0KDQphZHZlcnRp c2luZzxicj4NCg0KY29zdCBhbmQgcGFzcyB0aG9zZSBzYXZpbmdzIGFsb25n IHRvIHlvdS48YnI+DQoNCkJ1dCB5b3UgbXVzdCBhY3Qgbm93LiZuYnNwOzxi cj4NCg0KJm5ic3A7PGJyPg0KDQpUbyByZWNlaXZlIG1vcmUgaW5mb3JtYXRp b24gY2FsbCZuYnNwOyB1cyBub3cuPGJyPg0KDQombmJzcDs8YnI+DQoNCiZu YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw OyZuYnNwOyZuYnNwOyZuYnNwOyBUT0xMIEZSRUUgPGI+PGZvbnQgY29sb3I9 IiMwMDAwODAiPjEtODg4LTYyMS03MzAwPC9mb250PjwvYj48YnI+DQoNCiZu YnNwOzxicj4NCg0KV2UgbXVzdCBzcGVhayB0byB5b3UgaW4gcGVyc29uIHRv IHF1YWxpZnkgeW91ciB1c2FnZS48YnI+DQoNCiZuYnNwOzxicj4NCg0KJm5i c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IEFsbCBvZiB5b3VyIHF1ZXN0aW9ucyB3 aWxsIGJlIGFkZHJlc3NlZCBhbmQgYW5zd2VyZWQgaW4NCg0KYSBmcmllbmRs eSw8YnI+DQoNCm5vIHByZXNzdXJlIG1hbm5lci4mbmJzcDsgT3VyIG1haW4g cHVycG9zZSBpcyB0byBwcm92aWRlIHlvdSB3aXRoPGJyPg0KDQombmJzcDtp bmZvcm1hdGlvbiBzbyB5b3UgY2FuIG1ha2UgYW4gZWR1Y2F0ZWQgZGVjaXNp b24uPGJyPg0KDQombmJzcDs8YnI+DQoNCiZuYnNwOyZuYnNwOyZuYnNwOyZu YnNwOyBGb3IgbW9yZSBpbmZvcm1hdGlvbiBjYWxsPGJyPg0KDQombmJzcDs8 YnI+DQoNCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyA8Yj48Zm9udCBjb2xvcj0i IzAwMDA4MCI+MS04ODgtNjIxLTczMDA8L2ZvbnQ+PC9iPjxicj4NCg0KJm5i c3A7PGJyPg0KDQombmJzcDtJZiB5b3UgYXJlIG9uIGxpbmUgd3JpdGUgZG93 biBvdXI8YnI+DQoNCnBob25lIG51bWJlciBhbmQgY2FsbCB1cyB3aGVuIHlv dSBjYW4uPGJyPg0KDQombmJzcDs8YnI+DQoNClNvb24sIHlvdSBhbmQgeW91 ciBsb3ZlZCBvbmVzIHdpbGwgYmUgdmVyeSBnbGFkIHlvdSBkaWQuPGJyPg0K DQombmJzcDs8YnI+DQoNClJlYWQgd2hhdCBwZW9wbGUgYXJlIHNheWluZzo8 YnI+DQoNCiZuYnNwOzxicj4NCg0KJnF1b3Q7VGhlIGVmZmVjdHMgb2YgNiBt b250aHMgb2YgR0ggb248YnI+DQoNCmxlYW4gYm9keSBtYXNzIGFuZCBmYXQg d2VyZSBlcXVpdmFsZW50PGJyPg0KDQppbiBtYWduaXR1ZGUgdG8gdGhlIGNo YW5nZXMgaW5jdXJyZWQ8YnI+DQoNCmR1cmluZyAxMC0yMCB5ZWFycyBvZiBh Z2luZy4mcXVvdDs8YnI+DQoNCkRyLiBEYW5pZWwgUnVkbWFuLCBNRCw8YnI+ DQoNCk5ldyBFbmdsYW5kIEpvdXJuYWwgb2YgTWVkaWNpbmUuPGJyPg0KDQom bmJzcDs8YnI+DQoNCiZxdW90O1dpdGhpbiBmb3VyIG1vbnRocywgbXkgYm9k eSBmYXQgZGVjcmVhc2VkPGJyPg0KDQombmJzcDtmb3JtIDMwJSBkb3duIHRv IDIxJSEgSSBub3RpY2VkIG15IHNraW48YnI+DQoNCiZuYnNwO2lzIG1vcmUg c3VwcGxlIGFuZCBteSBvdmVyYWxsIG1lbnRhbDxicj4NCg0KJm5ic3A7b3V0 bG9vayBpbXByb3ZlZCBzaWduaWZpY2FudGx5LiZxdW90Ozxicj4NCg0KJm5i c3A7RC5XLiwgTmV3IEplcnNleTxicj4NCg0KJm5ic3A7PGJyPg0KDQomcXVv dDtXZSBoYXZlIGJlZW4gb24gdGhlIHNwcmF5IGZvciBqdXN0IDMgd2Vla3M8 YnI+DQoNCm5vdywgYW5kIGJlc2lkZXMgdGhlIHRyZW1lbmRvdXMgZW5lcmd5 IHdlPGJyPg0KDQpib3RoIGZlZWwsIG15IGh1c2JhbmRzIGFsbGVyZ2llcyBh bmQgc3BlbGxzPGJyPg0KDQpvZiBkZXByZXNzaW9uIGhhdmUgbGlmdGVkLiBJ IGFtIGhlYWxpbmc8YnI+DQoNCmV4dHJlbWVseSBmYXN0IGFmdGVyIGFuIGFj Y2lkZW50IGFuZCBoYXZlPGJyPg0KDQpsb3N0IDcgbGJzLiB3aXRob3V0IHRy eWluZyEmcXVvdDs8YnI+DQoNCkMuQi4sIEZsYWdzdGFmZi4gQVo8YnI+DQoN CiZuYnNwOzxicj4NCg0KVGhhbmtzIGZvciByZWFkaW5nIG91ciBsZXR0ZXIs PGJyPg0KDQpUaGUgSEdIIFN0YWZmPGJyPg0KDQpVU0EgRGl2aXNpb248YnI+ DQoNCiZuYnNwOzxicj4NCg0KUFM6Jm5ic3A7IFRoZSBIR0ggU3RhZmYgZ3Vh cmFudGVlcyB0aGU8YnI+DQoNCmhpZ2hlc3QgcXVhbGl0eSBhbmQgbG93ZXN0 IHByaWNlLjxicj4NCg0KJm5ic3A7PGJyPg0KDQombmJzcDtXZSBtYW51ZmFj dHVyZSBhbmQgc2hpcCBkaXJlY3RseSB0byB5b3VyIGRvb3IuPGJyPg0KDQom bmJzcDs8YnI+DQoNCkNhbGwgdXMgbm93IDxiPjxmb250IGNvbG9yPSIjMDAw MDgwIj4xLTg4OC02MjEtNzMwMDwvZm9udD48L2I+PGJyPg0KDQombmJzcDs8 YnI+DQoNCj09PT09PT0mbmJzcDsmbmJzcDsgRW5kIG9mIG1lc3NhZ2UgPT09 PT09PT0mbmJzcDs8YnI+DQoNCiZuYnNwOzxicj4NCg0KJm5ic3A7Jm5ic3A7 IFRoZSBmb2xsb3dpbmcgc3RhdGVtZW50IGlzIHByb3ZpZGVkIHRvIGJlPGJy Pg0KDQppbiBjb21wbGlhbmNlIHdpdGggY29tbWVyY2lhbCBlbWFpbCBsYXdz Ljxicj4NCg0KJm5ic3A7PGJyPg0KDQombmJzcDsmbmJzcDsgSWYgeW91IGRv IG5vdCB3aXNoIHRvIHJlY2VpdmUgZnVydGhlcjxicj4NCg0KbWFpbGluZ3Ms IHBsZWFzZSBjbGljayByZXBseSB0bzogIHRoZV9oZ2hfY2xpbmljQGJ0YW1h aWwubmV0LmNuICBhbmQgdHlwZSByZW1vdmUgaW4gdGhlIHN1YmplY3QgYm94 Ljxicj4NCg0KVGhlbiBjbGljayBzZW5kLjxicj4NCg0KJm5ic3A7PGJyPg0K DQombmJzcDsmbmJzcDsgVGhpcyBtZXNzYWdlIGlzIGluIGZ1bGwgY29tcGxp YW5jZSB3aXRoPGJyPg0KDQpVLlMuIEZlZGVyYWwgcmVxdWlyZW1lbnRzIGZv ciBjb21tZXJjaWFsPGJyPg0KDQplbWFpbCB1bmRlciBiaWxsIFMuMTYxOCBU aXRsZSBsbGwsIFNlY3Rpb24gMzAxLDxicj4NCg0KUGFyYWdyYXBoIChhKSgy KShDKSBwYXNzZWQgYnkgdGhlIDEwNXRoIFUuUy48YnI+DQoNCkNvbmdyZXNz IGFuZCBpcyBub3QgY29uc2lkZXJlZCBTUEFNPGJyPg0KDQpzaW5jZSBpdCBp bmNsdWRlcyBhIHJlbW92ZSBtZWNoYW5pc20uKjxicj4NCg0KVGhpcyBtZXNz YWdlIGlzIG5vdCBpbnRlbmRlZCBmb3IgcmVzaWRlbnRzIGluIHRoZTxicj4N Cg0Kc3RhdGVzIG9mIENBLCBOQywgTlYsIFJJLCBUTiwgVkEgJmFtcDsgV0Eu PGJyPg0KDQpTY3JlZW5pbmcgb2YgYWRkcmVzc2VzIGhhcyBiZWVuIGRvbmUg dG8gdGhlIGJlc3Q8YnI+DQoNCm9mIG91ciB0ZWNobmljYWwgYWJpbGl0eS48 YnI+DQoNCiZuYnNwOzxicj4NCg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i c3A7IENhbGwgdXMNCg0Kbm93IDxiPjxmb250IGNvbG9yPSIjMDAwMDgwIj4x LTg4OC02MjEtNzMwMDwvZm9udD48L2I+IGZvciB5b3VyPGJyPg0KDQombmJz cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgZnJlZQ0KDQpIR0ggY29uc3VsdGF0 aW9uLjwvcD4NCg0KPHA+PGJyPg0KDQpUaGFuayB5b3U8L3A+DQoNCjwvYm9k eT4NCg0KPC9odG1sPg0KDQogDQogDQogDQogDQogDQogDQogDQogDQogDQog DQogDQogDQogDQogDQogDQogDQogDQogDQogDQogDQogDQogDQogDQogDQog DQogDQogDQogDQogDQogDQogDQogDQogDQogDQogDQogDQogDQogDQogDQog DQogDQogDQogDQogDQogDQoNCi0tDQoNCjA0MDJ5d3NEOC0yMDlzbHRDOTQy Nm1lcXEwLTAwNVBFSEIzMzgzZWd1azktMzY3cEJJczcwMzhReUpMNS02MzR0 UU9nNDY3M3FsNjk= |
|
From: Mikhael G. <mi...@ho...> - 2002-06-13 05:47:27
|
I added .*ADV.* to spam filter. Regards, Mikhael. |
|
From: <ind...@ya...> - 2002-06-13 05:38:58
|
<HTML>
<HEAD>
<TITLE>Untitled Document</TITLE>
</HEAD>
<BODY BGCOLOR=3D"#ffffff">
<P><CENTER><TABLE WIDTH=3D"593" BORDER=3D"1" CELLSPACING=3D"2" CELLPADDING=3D"0">
<TR>
<TD WIDTH=3D"100%" BGCOLOR=3D"#0000ff">
<P><CENTER><FONT SIZE=3D"+4"> </FONT><FONT COLOR=3D"#cccccc"
SIZE=3D"+4" FACE=3D"Times New Roman">The Wall Street =
Stockwatch</FONT></CENTER></TD>
</TR>
</TABLE><TABLE WIDTH=3D"450" BORDER=3D"0" CELLSPACING=3D"0" CELLPADDING=3D"0"
HEIGHT=3D"30">
<TR>
<TD WIDTH=3D"100%">
<P><CENTER> <B>THE COMPANY: XENICENT INC. (OTCBB: =
XCNT)</B></CENTER></TD>
</TR>
</TABLE><TABLE WIDTH=3D"518" BORDER=3D"0" CELLSPACING=3D"0" CELLPADDING=3D"0"
HEIGHT=3D"149">
<TR>
<TD WIDTH=3D"40%" BGCOLOR=3D"#00ffff">
<B>SYMBOL:XCNT</B></TD>
<TD WIDTH=3D"60%">
</TD>
</TR>
<TR>
<TD WIDTH=3D"40%" BGCOLOR=3D"#00ffff">
52 WEEK HIGH: $2.50</TD>
<TD WIDTH=3D"60%">
*INNOVATIVE TECHNOLOGY COMPANY</TD>
</TR>
<TR>
<TD WIDTH=3D"40%" BGCOLOR=3D"#00ffff">
52 WEEK LOW: $0.15</TD>
<TD WIDTH=3D"60%">
*LED DISPLAY SYSTEMS</TD>
</TR>
<TR>
<TD WIDTH=3D"40%" BGCOLOR=3D"#00ffff">
MARKET CAP: $7.5M</TD>
<TD WIDTH=3D"60%">
*STRATEGIC MERGERS & ACQUISITIONS</TD>
</TR>
<TR>
<TD WIDTH=3D"40%" BGCOLOR=3D"#00ffff">
APPROX. FLOAT: $.4M</TD>
<TD WIDTH=3D"60%">
</TD>
</TR>
<TR>
<TD WIDTH=3D"40%" BGCOLOR=3D"#00ffff">
RECENT PRICE: $0.50</TD>
<TD WIDTH=3D"60%">
</TD>
</TR>
</TABLE><TABLE WIDTH=3D"576" BORDER=3D"1" CELLSPACING=3D"0" CELLPADDING=3D"0"
HEIGHT=3D"410">
<TR>
<TD WIDTH=3D"100%" HEIGHT=3D"42" BGCOLOR=3D"#0000ff">
<P><CENTER><FONT COLOR=3D"#cccccc"> </FONT><FONT COLOR=3D"#ffffff"
SIZE=3D"+2">Company Background</FONT></CENTER></TD>
</TR>
<TR>
<TD WIDTH=3D"100%" HEIGHT=3D"365" BGCOLOR=3D"#c8c8c8">
<P> Dear Investors, Traders, and Speculators:</P>
<P><BR>
<B>XENICENT INC.</B> <B>(OTCBB: XCNT) IS UNDER OUR RADAR THIS
WEEK</B>. The Company, develops, invests in, and operates technology
and land development related companies within the US, China,
and Taiwan. XCNT's <B>immediate strategy</B> is to accelerate
the success of its technology division by acquisitions and development.=
</P>
<P><BR>
<B>XCNT </B>recently announced the signing of a definitive agreement
under which the Company will <B>acquire a 60% interest in Giantek</B>,
a Taiwanese corporation for U.S. distribution of Giantek's LED
Display Systems and additional Giantek proprietary technologies.
"By joining forces with Giantek, we will <B>accelerate our
entry</B> <B>into attractive new technology markets</B>, and
add critical breadth to our line of innovative products,"
Said CEO Duane Bennett of Xenicent. <U>As a result of this important
acquisition, XCNT will receive exclusive rights to market Giantek's
products within the United States</U>. Giantek reported over
$2 million in revenues for 2001, has approximately $3 million
in assets and currently employs a workforce of 30 employees.</TD>
</TR>
</TABLE><TABLE WIDTH=3D"575" BORDER=3D"1" CELLSPACING=3D"0" CELLPADDING=3D"0"
HEIGHT=3D"331">
<TR>
<TD WIDTH=3D"100%" BGCOLOR=3D"#0000ff" HEIGHT=3D"39">
<P><CENTER><B><FONT SIZE=3D"+2"> </FONT></B><FONT COLOR=3D"#ffffff"
SIZE=3D"+2">XCNT Growth Strategy</FONT></CENTER></TD>
</TR>
<TR>
<TD WIDTH=3D"100%" BGCOLOR=3D"#c8c8c8" HEIGHT=3D"289">
<P> <B>IN THE NEAR FUTURE</B>, management will announce
its new strategy to capitalize on the growing technology sector
exploding in Asia. Xenicent has assembled an outstanding team
of management personnel, all with proven leadership and management
skills in working with larger "hyper-growth" companies.
The Company's strategy includes the <B>internal development and
operation of subsidiaries</B> within the XCNT family, as well
as investment in additional technology companies directly, and
through other venture capital arrangements.</P>
<P><BR>
<B>THE MOST EXTRAORDINARY ASPECT OF XCNT IS THE OPPORTUNITY IT
PROVIDES </B>by the limited amount of shares within the public
float now available for individual investors. It has been our
experience, that as word gets around the street of new technologies
being acquired by Xenicent Inc., limited shares, (presently under
1M), <B>USUALLY </B><U>causes rapid price increase as increased
buying occurs in these type of smallcap bulletin board companies</U>.=
</TD>
</TR>
</TABLE><TABLE WIDTH=3D"574" BORDER=3D"1" CELLSPACING=3D"0" CELLPADDING=3D"0"
HEIGHT=3D"124">
<TR>
<TD WIDTH=3D"100%" BGCOLOR=3D"#0000ff" HEIGHT=3D"38">
<P><CENTER><FONT SIZE=3D"+2"> </FONT><FONT COLOR=3D"#ffffff"
SIZE=3D"+2">Conclusion</FONT></CENTER></TD>
</TR>
<TR>
<TD WIDTH=3D"100%" BGCOLOR=3D"#c8c8c8" HEIGHT=3D"80">
<B>IN MANAGEMENT'S OPINION, XCNT</B> at a present price
of .50 cents a share, will in the short term increase its per
market share by its current strategic objective of acquisition
targets within the technology field. <B>The Xenicent Technology
family of companies is expected to increase dramatically</B>…hence
greater revenues equals price appreciation.</TD>
</TR>
</TABLE><TABLE WIDTH=3D"573" BORDER=3D"0" CELLSPACING=3D"0" CELLPADDING=3D"0"
HEIGHT=3D"318">
<TR>
<TD WIDTH=3D"100%" HEIGHT=3D"264" BGCOLOR=3D"#0000ff">
<P> </P>
<P><FONT COLOR=3D"#ffffff" SIZE=3D"-1">DISCLAIMER:<BR>
The Wallstreetalerts.com Equity Report and Wall Street Strategies,
Inc. is an independent research and investor relations firm paid
for electronic dissemination of company information, and in some
cases, for consulting services. All statements and expressions
are meant to be an independent analysis and relies on information
supplied by sources believed to be reliable and are not meant
to be a solicitation or recommendation to buy, sell, or hold
securities. Wwallstreetalerts.com or Wall Street Strategies,
Inc. are not registered investment advisors or a broker dealer.
While it is our goal to feature equity investments in micro or
small capitalization companies that have the potential for long-term
appreciation, investments in the companies reviewed are considered
to be a high risk and use of the information provided is at the
investor's sole risk. Wallstreetalerts.com and Wall Street Strategies,
Inc. has been retained as a consultant to Xenicent Inc. and has
been remunerated by XCNT or its shareholders for investor relation
services in the amount of 50,000 shares to date. Wall Street
Strategies, Inc., or its affiliates, agents and/or relatives
thereof may have interests or positions in equity securities
of the companies reviewed in this bulletin, some or all of which
may have been acquired prior to the dissemination of this report,
and may increase or decrease these positions at any time. Investments
in smallcap companies are generally deemed to be highly speculative
and to involve substantial risk, making it appropriate for readers
to consult with professional investment advisors and to make
independent investigation</FONT></TD>
</TR>
<TR>
<TD WIDTH=3D"100%" HEIGHT=3D"42" BGCOLOR=3D"#0000ff">
<P><CENTER><B><FONT COLOR=3D"#ffffff" SIZE=3D"+1">If you wish to
unsubscribe from our mailing list, please Click <mailto:remove@nounce1.=
com?subject=3DREMOVE>
Here or call us at 1-866-667-5399, or write to us at: NOUNCE1,
6822 22nd Ave. N, St. Petersburg, FL 33710-3918</FONT></B></CENTER></TD>
</TR>
</TABLE><TABLE WIDTH=3D"450" BORDER=3D"0" CELLSPACING=3D"0" CELLPADDING=3D"0"
HEIGHT=3D"26">
<TR>
<TD WIDTH=3D"100%">
<P><CENTER> OTCBB: XCNT</CENTER></TD>
</TR>
</TABLE></CENTER>
</BODY>
</HTML>
|
|
From: Alex W. <aw...@pr...> - 2002-06-11 01:47:35
|
Mikhael Goikhman wrote: > > On 10 Jun 2002 13:32:25 +0930, Alex Wallis wrote: > > > > I think default/menus should have this minor change added in > > MenuFvwmWindowStyle before the next release. > > > > + "%menu/window.xpm%TitleAtLeft" Pick (CirculateHit) Style $n TitleAtLeft > > + "%menu/window.xpm%TitleAtRight" Pick (CirculateHit) Style $n TitleAtRight > > Not in 0.6.1, because fvwm-2.4.8 does not support these. > > > I'm also trying to prepare some other things if I can submit a patch in > > time. > > Hmm, if you think they should be included in 0.6.1, tell me now. > Since I'm not completely sure what's in and what's not in 2.4.8, then no matter. Alex |
|
From: Mikhael G. <mi...@ho...> - 2002-06-10 19:50:02
|
On 10 Jun 2002 13:32:25 +0930, Alex Wallis wrote: > > I think default/menus should have this minor change added in > MenuFvwmWindowStyle before the next release. > > + "%menu/window.xpm%TitleAtLeft" Pick (CirculateHit) Style $n TitleAtLeft > + "%menu/window.xpm%TitleAtRight" Pick (CirculateHit) Style $n TitleAtRight Not in 0.6.1, because fvwm-2.4.8 does not support these. > I'm also trying to prepare some other things if I can submit a patch in > time. Hmm, if you think they should be included in 0.6.1, tell me now. Regards, Mikhael. |
6 messages has been excluded from this view by a project administrator.
![http://www.wirelessteam.net/images/bkgrnd.gif"><img](http://www.wirelessteam.net/images/bkgrnd.gif"><img){kind=link}
![http://www.wirelessteam.net/images/shim.gif"](http://www.wirelessteam.net/images/shim.gif"){kind=link}
![http://www.wirelessteam.net/images/logo.gif"](http://www.wirelessteam.net/images/logo.gif"){kind=link}
![http://www.wirelessteam.net/images/bkgrnd_nav.gif"](http://www.wirelessteam.net/images/bkgrnd_nav.gif"){kind=link}
![http://www.wirelessteam.net/images/home.gif"](http://www.wirelessteam.net/images/home.gif"){kind=link}
![http://www.wirelessteam.net/images/aboutus.gif"](http://www.wirelessteam.net/images/aboutus.gif"){kind=link}
![http://www.wirelessteam.net/images/contactus.gif"](http://www.wirelessteam.net/images/contactus.gif"){kind=link}
![http://www.wirelessteam.net/images/faq.gif"](http://www.wirelessteam.net/images/faq.gif"){kind=link}
![http://www.wirelessteam.net/images/img-new.jpg"](http://www.wirelessteam.net/images/img-new.jpg"){kind=link}
![http://www.wirelessteam.net/images/price.gif"](http://www.wirelessteam.net/images/price.gif"){kind=link}
![http://www.wirelessteam.net/images/ordernow.gif"](http://www.wirelessteam.net/images/ordernow.gif"){kind=link}