Robert Williams wrote:
Sounds cool. But why forget about KDE? You can use BlackBox with KDE...
Use BlackBox with KDE? only if you got XNest332 and thats not a KDE application. I never found any function in a KDE application just lack of. E on the other hand was and prob still is just for EYE Candy, for when your windows friends came over and ya wanted to make em drool a bit (specialy on the desktop with naky chicks and deamons) Anyways.. fvwm2 is great for stability, AS is not so fun configuring. WM is ok. CDE is kinda cool. icewm I do not like at all. You can what? Do you know how many system resources get eaten with KDE? 26+% I have not seen a KDE application that couldn't be beat by other applications for use/function/whatever. Blackbox is very useful/easy/neat looking/easy to configure/ you can add whatever programs you need to the blackbox.menu with ease. You just can't beat Blackbox. Steven Damn I hate when Netscape screws my posts up with line returns I didn't put there..looks awful.
Steven Udell wrote:
Forget E,fvwm,AS,icewm,WM,CDE,KDE
Check it out : and SuSE its OK to put it on SuSE-5.3 <A HREF="http://linux.wiw.org/blackbox"><A HREF="http://linux.wiw.org/blackbox</A">http://linux.wiw.org/blackbox</A</A>>
Subject: Blackbox 0.34.3 released. Date: Mon, 20 Jul 1998 02:44:12 -0500 (CDT)
This is a major bug fix release, also there is a new window styling... tell me how you like it...
from the Changelog:
Changes from 0.34.2 to 0.34.3: - this was a small change in the code... but a BIG change for the user base... the X error handler is now non fatal... yes... this means if blackbox encounters an X error (like a bad window or a bad match) it will fprintf() the error and continue running... the quick window bug has been mostly fixed... i have a small app that i wrote that quickly maps a window, calls XSync()... then destroys the window and exits...the first time i ran this little beauty... blackbox died a horrible death... blackbox now handles this app nicely... but does occasionally report an error (during the decoration creation... which is promptly destroyed from the destroy notify event placed in the queue by the X server... thus... no memory leaks... no memory corruption... blackbox just keeps chugging along nicely
Changes from 0.34.1 to 0.34.2 (unreleased): - fixed MSBFirst byte order image rendering at 32bpp (24bpp pending)(for machines better than this intel machine of mine) - changed BImage to allocate dithering space when the image is created and to delete it when the image is destroyed... instead of allocating the space and deleting the space each time the image is rendered to an XImage... hopefully this will provide a speed increase (albeit a small one) - changed blackbox to call XListPixmapFormats once at startup... instead of each time an image is rendered... this should afford some speed increase (a small one at best :) - fixed a bug in Window.cc that re-reads the window name... Jon Denardis discovered this bug while playing with netscape 4.5...the validation call is now directly before the XFetchName call... instead of before an if() { } block that calls strcmp and XFree() - edit Window.cc to change the way buttons are decorated and sized the associatedWindow.button.color(To) resources have been removed,but the associatedWindow.button texture resource is still there
regards!
Brad Hughes / nyztihke - 1998 -
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e