ec304c9e43
YOUR THEMES ARE NOW OFFICIALLY BROKEN. Openbox has just moved it's theme format to an XML based one. The details of this format can be found in data/themerc.xsd (and http://openbox.org/themerc.xsd ALSO! This is very good and important and stuff! In the tools directory you will find THEMETOXML ! This tool takes a themerc on stdin, and spits out the same theme in theme.xml format. So this is all you need to do to update your themes. PLEASE NOTE: This themetoxml does _not_ install itself anywhere. It simply builds and then lives out in its tools/themetoxml directory, and that's it. So if you want to use it, that is where to find it. In moving to the new XML format, a number of additions/changes to the theme engine have been made. Themetoxml takes these into account and will set all the new things appropriately to make your theme look the same as it always has. New additions include.. * padding now has an horizontal and vertical component, instead of being one number * menus can have different borders than windows (color and size) * menu offset can now be negative. it's a little weird, but someone will want it no doubt * fonts are no longer controled by the theme at all, however font shadowing is, and on that note.. * font shadows are now any color you want, not just black and white * you can now set the shadow anywhere you can set the text's color, so you have more control, i.e. you can set shadow on active menu items but not inactive, or disabled, etc. * every color now has an alpha channel. at the moment they don't do anything, besides the font shadow one, but it leaves room for future explorations. it is REALLY HIGHLY RECOMMENDED that you set the alpha to 255 all the time, until such time as it could be useful. otherwise one day your theme may turn awful for people. * font colors are in the range 0-255, in case you were wondering, and they have to be specified in decimal * if you'd like to change you font's you can do so in your configuration file. this is how it is going to stay. changing the font in the theme assumes too much about peoples eye sight and locality and stuff. it doesn't belong there, sorry. the system-wide default rc.xml includes the new font settings for your viewing pleasure, and ill drop an example of it below. * shadows can now be positioned in any direction, they have both an x and a y offset which can be negative and positive. and offset of 0,0 will disable the shadow This isn't a release or anything. If someone had some good ideas about the xml theme format, I'd like to hear them. But I don't think it will be changing much right now beyond where it is. I don't even know how the new functionality will play out for themers, so we'll see. Whew.. I guess that's it. I'm not sure if I mentioned every little change or not, but oh well. Mileage may vary.. Please send any feedback. Here's the font configuration example. Hopefully ObConf will let you set this real soon. <theme> ... <font place="ActiveWindow"> <name>arial,sans</name> <size>7</size> <weight>bold</weight> <slant>normal</slant> </font> <font place="InactiveWindow"> <name>arial,sans</name> <size>7</size> <weight>bold</weight> <slant>normal</slant> </font> <font place="MenuTitle"> <name>arial,sans</name> <size>8</size> <weight>bold</weight> <slant>normal</slant> </font> <font place="MenuItem"> <name>arial,sans</name> <size>8</size> <weight>bold</weight> <slant>normal</slant> </font> </theme>
93 lines
2.4 KiB
Text
93 lines
2.4 KiB
Text
# OB_DEBUG()
|
|
#
|
|
# Check if the user has requested a debug build.
|
|
# Sets the DEBUG or NDEBUG variables as appropriate
|
|
# Sets the CVS environment variable when building CVS sources.
|
|
AC_DEFUN([OB_DEBUG],
|
|
[
|
|
AC_MSG_CHECKING([build type])
|
|
|
|
AC_ARG_ENABLE([strict-ansi],
|
|
AC_HELP_STRING([--enable-strict-ansi],[Enable strict ANSI compliance build [[default=no]]]),
|
|
[STRICT=$enableval], [STRICT="no"])
|
|
if test "$GCC" = "yes" && test "$STRICT" = "yes"; then
|
|
CFLAGS="$CFLAGS -ansi -pedantic -D_XOPEN_SOURCE"
|
|
fi
|
|
|
|
AC_ARG_ENABLE([debug],
|
|
AC_HELP_STRING([--enable-debug],[build a debug version [[default=no]]]),
|
|
[DEBUG=$enableval], [DEBUG="no"])
|
|
|
|
TEST=""
|
|
test "${PACKAGE_VERSION%*alpha*}" != "$PACKAGE_VERSION" && TEST="yes"
|
|
test "${PACKAGE_VERSION%*beta*}" != "$PACKAGE_VERSION" && TEST="yes"
|
|
test "$TEST" = "yes" && DEBUG="yes"
|
|
|
|
if test "$DEBUG" = "yes"; then
|
|
MSG="DEBUG"
|
|
else
|
|
MSG="RELEASE"
|
|
fi
|
|
if test "$TEST" = "yes"; then
|
|
MSG="$MSG (test release)"
|
|
fi
|
|
if test "$STRICT" = "yes"; then
|
|
MSG="$MSG with strict ANSI compliance"
|
|
fi
|
|
AC_MSG_RESULT([$MSG])
|
|
|
|
test "$DEBUG" = "yes" && \
|
|
AC_DEFINE([DEBUG], [1], [Creating a debug build])
|
|
])
|
|
|
|
|
|
# OB_COMPILER_FLAGS()
|
|
#
|
|
# Check what compiler is being used for compilation.
|
|
# It sets the CFLAGS variable appropriately for the compiler, including flags
|
|
# for debug builds.
|
|
AC_DEFUN([OB_COMPILER_FLAGS],
|
|
[
|
|
AC_REQUIRE([AC_PROG_CPP])
|
|
AC_REQUIRE([AC_PROG_CC])
|
|
|
|
FLAGS=""
|
|
|
|
if test "$DEBUG" = "yes"; then
|
|
FLAGS="-DDEBUG"
|
|
else
|
|
FLAGS="-DNDEBUG -DG_DISABLE_ASSERT"
|
|
fi
|
|
|
|
# Check what compiler we are using
|
|
AC_MSG_CHECKING([for GNU CC])
|
|
if test "$GCC" = "yes"; then
|
|
AC_MSG_RESULT([yes])
|
|
if test "$DEBUG" = "yes"; then
|
|
FLAGS="$FLAGS -O0 -g -fno-inline"
|
|
FLAGS="$FLAGS -Wall -Wsign-compare -Waggregate-return"
|
|
FLAGS="$FLAGS -Wcast-qual -Wbad-function-cast -Wpointer-arith"
|
|
# for Python.h
|
|
#FLAGS="$FLAGS -Wno-long-long"
|
|
fi
|
|
if test "$STRICT" = "yes"; then
|
|
FLAGS="$FLAGS -ansi -pedantic -D_XOPEN_SOURCE"
|
|
fi
|
|
FLAGS="$FLAGS -fno-strict-aliasing"
|
|
fi
|
|
AC_MSG_CHECKING([for compiler specific flags])
|
|
AC_MSG_RESULT([$FLAGS])
|
|
CFLAGS="$CFLAGS $FLAGS"
|
|
])
|
|
|
|
AC_DEFUN([OB_NLS],
|
|
[
|
|
AC_ARG_ENABLE([nls],
|
|
AC_HELP_STRING([--enable-nls],[Enable NLS translations [[default=yes]]]),
|
|
[NLS=$enableval], [NLS="yes"])
|
|
|
|
if test "$NLS" = yes; then
|
|
DEFS="$DEFS -DENABLE_NLS"
|
|
fi
|
|
])
|
|
|