blackhome-0.3.4.2
28 June 2007
Display lines using the 'bsetroot' command get commented out; fixed.
Problem with failure to restore original blackbox behaviour when
blackhome is removed (with ~/.blackhome/config/destroy). Fixed.
Blackhome obliterates default styles menu; changed from
/usr/local/share/Blackbox/styles to the default
/usr/X11R6/share/blackbox/styles. See the 'menu' file. Note: if your styles
directory is in another location you need to alter this line in the supplied
menu files for the default theme customisations as well as the default
blackhome menu file '.blackhome/menus/menu'. New themes installed will
automatically use this latter file.

blackhome-0.3.4.1
7 Sept. 2006
Problem with themes whose styles contain additional lines after the initial
'rootCommand' at the end of the style file: lines partially overwritten.
Fixed. Now the 'LemonSpace' theme image loads correctly.

blackhome-0.3.4
2 Sept. 2006
Non-compliancy with current ISO c++ standards fixed. Built and tested 
under Slackware 10.2. Other distributions: keep a copy of your WM start-up 
files somewhere safe - I've had reports the install script has lost user's 
previous setup and failed to reinstate it. No details supplied so I can't 
be specific.

blackhome-0.3.2.1
A long-standing problem with text entry boxes not accepting keyboard input
re-surfaced when testing blackhome on blackbox-0.65.0. Turned out to be a
mis-specification of the popup text widget shell type.

Default resource files have been reorganised so resources are specified
both alphabetically and by widget tree where possible, enabling separation
of general and specific resources and also ease of search.


blackhome-0.3.2

Fixed another problem with non-image-file backgrounds (sigh). Hopefully
they're all trapped now.

A problem with some themes' backgrounds remains: where a style specifies more
than one rootCommand to do background handling - the last specified one takes
precedence but it confuses blackhome. Theme 'LemonSpace' is an example: one
rootCommand specifies a plain background, a second a jpeg image file. Black-
home chooses the first rootCommand it comes across (the plain background one)
and ignores the other. If you want the image file, simply comment out the un-
wanted rootCommand in the style file by preceding it with a '!' before
installing the theme.

GTK theme handling is now incorporated. If you have gnome, then you get a
GTK themes menu. These can be either pre- or post-merged with the blackhome
GTK resource files, allowing for some interesting effects...


blackhome-0.3.1

Fixed problem with rootCommand in styles relating to non-image-file backgrounds.
Background now sets correctly in such cases (e.g. themes 'AlfredIsDead',
'Blacky4').


blackhome-0.3

Various default resource file changes, mostly cosmetic to improve appearance of
default themes (and not set outlandish colours).

Complete overhaul of ResourceFileEditor code in response to skar@hacktick.de who
alerted me to the fact that rfe does not run. Indeed it didn't and probably
hasn't since the orginal libc5 version. Also it had some bugs; those which I
have found have been fixed.
Not all combinations of rfe options have been tested. More bug reports welcome.
It is still slow and non-event oriented, which means its windows don't get
refreshed on a long operation :(

New feature: resourceFileEditor now attempts to cope with gnome-style colour
resources, so harmonisation of gtk-based apps is now possible (e.g. gimp).

Support for Bashish has been removed :(
Keeping track of the changes and re-integrating it has proved too much for now...


blackhome-060302

Style generation fixed to cope with blackbox releases to 0.61.1.
ResourceFileEditor is extremely buggy, needs a total rewrite and will
probably hang your machine. If it builds or runs.

However - the utility 'ColourSpecConvertTest' has been patched to
build and run correctly on 2.4.x kernels. This can be used to do colour
format conversions via the command line, 'colourSpecConvertTest "#0a0b8f"',
for example.


blackhome-0.2.4

Bugfixed 0.2.3. 'Undo/last' now functions correctly giving complete
restoration without having to resort to 'Undo/<undoFilename>' Some text
files edited to improve legibility.

.Xdefaults changed for theme alpha so netscape uses more legible link
colours to match the theme; 

Acrobat reader base defaults file 'AcroRead-color' fixed so it responds to
foreground and background colour changes

Added 'killall -e blackbox' to cleanup.sh' in .blackhome/control, in
addition to the 'kill -a blackbox'; quits one way or another, variation in
requirements between my Slackware 3.4 and 7.0 Linux distributions.

Colour component deviation code rewritten so that the fuzzy search option
produces predictable results...

Blackhome now supports the Bashish terminal theme manager. You can enable
or disable bashish under blackhome, depending on whether you prefer your
term themes in blackbox managed by blackhome or bashish. Bashish theme
selection is also supported, via blackhome's resource file editor. See
blackhome.HOWTO, 'Bashish and blackhome'.


blackhome-0.2.3

The blackhome.HOWTO has been updated; additions include 'using themes with
supplied fonts', such as Case#Obscene, 'using themes which don't have
images', such as Blacky4, and tips on how to automatically execute applications
on a per-theme basis.

New documentation added to support the blackhome resourceFileEditor, an
application to assist you in harmonising colours in your apps with those in your
themes. No messy hand-editing of blackhome resource files necessary. Find things
vaguely dark red and replace effortlessly with shades of lime green!


Modifications to 0.2.2

Support for Adobe Acrobat customisation.
If your acrobat reader isn't installed in /usr/local then you'll have to edit
.blackhome/menus/menu when you have unpacked the tar.gz and change the entry for
the Acrobat reader path _before_ running the 'blackhome' install script (this
way all your installed themes pick up the new path since they copy the base
menu file).

Tidied up installtheme.c and installImage.c instructions doing nothing; more
usefully, ensured that all files written by these routines have terminating
newlines (decimal 10, hex 0A) at the end of the files. The new resource file
editor relies on these being here; if you write blackhome configure scripts by
hand, be aware of this requirement.

Style and menu files particularly should have an ending newline; these are
automatically inserted if installTheme is used, but manual editing again could
cause problems. Lack of a terminating newline at the end of a line and the end
of the file means that line will not be read (or subsequently written ) by the
install routines or by the resource file editor.

The most common evidence of a lacking newline at the end of a file is a
core dump from RFE; if you have any hand-built files, check they have a newline
as the last character.


0.2.2 bugfixes

Acroread base app defs file now included by acroread-color (looked in homedir
instead of .blackhome/app-defaults)

XWave-color app defaults file typos corrected and default dir (left
pointing at my home dir) changed to /tmp.

Theme omega - menu didn't work due to my personal version somehow finding its
way into the distribution. Theme alpha worked, the error was pretty obvious,
nobody complained, probably nobody cares...

