dockapps/libdockapp
Doug Torrance fa7743bc58 libdockapp: Do not include pathnames in Window Name and Class Properties
Patch by Corin-EU from GitHub [1].

In libdockapps file wmgeneral.c, wname is set from argv[0] and is then used
to set the window name and class resource. Often applications are called with
their full path which then means that the window name has a path in it,
thereby requiring an unwieldy path specific string for "Name" in WMState if
the applet is to be captured in the WM dock.

The simple solution is that wname should be the basename of argv[0] to
ensure that the window name for the applet is the simple and obvious one.
Thus the inclusion of header file libgen.h is required.

Just say "no" to path slashes "/" in window name/class resources ....

[1] https://github.com/d-torrance/dockapps/issues/5
2017-04-26 23:27:19 +01:00
..
examples libdockapp: Update header location in examples. 2015-10-18 00:20:33 -04:00
fonts libdockapp: Recompress fonts without timestamp. 2015-10-21 09:07:01 -04:00
src libdockapp: Do not include pathnames in Window Name and Class Properties 2017-04-26 23:27:19 +01:00
AUTHORS libdockapp: Add version 0.6.3 to repository. 2014-11-28 16:30:06 +00:00
BUGS libdockapp: Add version 0.6.3 to repository. 2014-11-28 16:30:06 +00:00
ChangeLog libdockapp: Bump to version 0.7.2. 2015-10-21 09:07:01 -04:00
configure.ac libdockapp: Bump to version 0.7.2. 2015-10-21 09:07:01 -04:00
COPYING libdockapp: Add version 0.6.3 to repository. 2014-11-28 16:30:06 +00:00
Makefile.am libdockapp: Clean generated file dockapp.pc. 2015-10-21 09:07:01 -04:00
NEWS libdockapp: Release version 0.6.4. 2014-11-28 16:39:20 +00:00
README libdockapp: Simplify instructions to generate a ./configure script. 2015-10-09 17:43:38 -04:00

DockApp Development Standard Library

Alban G. Hertroys <dalroi@solfertje.student.utwente.nl>
Alfredo K. Kojima <kojima@windowmaker.org>
Pascal G. Hofstee <daeron@windowmaker.org>

...............................................................................

You must have libXpm library installed and the shape extension supported
by your X server to be able to build and install libdockapp.

If you received this file in a tarball then you probably need to generate the
configuration environment yourself. You need libtool and autotools for this
purpose.
To compile libDockApp enter the libdockapp directory and type:

autoreconf -if
./configure
make install

You can choose to not install the examples or the fonts with configure
options:
  --with-font             install the dockapp font (default=yes)
  --with-examples         install the examples (default=yes)


The API is described in dockapp.h
There are some examples in the examples directory. These aren't build by
default.
You can compile them like:

    cd examples/basic
    make

Optionally you can "make install" if you really like the example application.


License:

Copyright (c) 1999-2003 Alfredo K. Kojima, Pascal Hofstee, Alban G. Hertroys
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
   notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
   notice, this list of conditions and the following disclaimer in the
   documentation and/or other materials provided with the distribution.
3. The name of the author may not be used to endorse or promote products
   derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.