Yeah vooshy, you are correct. I migrated xoblite over to a bblean machine and it's system bar took on a majority of bbleans systembar settings. I believe alot of the blackbox.*.whatevers in the rc's are pretty much universal.

I wonder if the idea of font shadow custom colorization will be impllimented. I do like the ability to get an embosed look on some styles.

Perhaps some type of override feature where we can define a color.

I like Xoblite, why it is given me a C++ Runtime problem, various alert boxes about this? What is the problem? somthing I don`t have? maybe a msvcr...dll? I have 60 70 80

Please correct me if i am wrong...

xoblite's systembar and toolbar are actually part of xoblite's core. you can only hide them (or hide one and achieve a single bar configuration ala bbLean and bbLeanBar) but they are still loaded in the memory (?).. now, if that is the case, i don't think that is lite... again, please correct me if i'm wrong..

Im not sure about the memory resident thing.. but bbleanbar is s plugin that's why it's totally removed when toggling it from the plugin list. BBLean's toolbar however acts the same as all the other branches of blackbox. i.e. it toggles the same way as xoblites toolbar.

that's exactly what I like in bbLeanBar.. now, i hope someone would clear us about xoblite's SystemBar and Toolbar... cause i don't like the idea of just hiding one to achieve a configuration similar to bbLeanBar and yet the other one stays in memory although hidden, if that is the case. (?)

yeah, but... bblean's own toolbar is hidden in the same fashion as xoblite's is. There is no difference there. The only difference between xoblite and bblean is that bblean has more choices of toolbar addons.

All box shells has their toolbar integrated into them, I believe it performs a much needed task, that's why it's not permantly removed. Linux branches are the same in this.

bbleanbar could probably be made to work with xoblite if someone took a look at it. Or create a toolbar from xoblites exsisting one and just build around that.

awkay, that's sounds crystal clear to me..

To make a long story somewhat short, this is how it works:

bb4win and bbLean perform task and systray handling internally, and provide APIs (i.e. ways of accessing functions and data) to external plugins such as BBSystembar(Ex)/bbLeanBar and BBTray which act as display elements. In other words, you need either an integrated taskbar/systray plugin or separate taskbar and systray plugins to "see" something on screen.

xoblite features equivalent internal task and systray handling, but has taskbar+systray display functionality (toolbar+systembar) built in. It still provides the systray APIs, so you can load e.g. BBTray, but it only supports some of the taskbar APIs, which is why you (currently at least) can not load plugins such as BBSystembar(Ex)/bbLeanBar.

The reasoning behind xoblite's integrated taskbar/systray, again to make a long story short, is that such functionality is essential in a Windows environment, and should therefore always be accessible, whether you have the skills to load plugins or not (i.e. newbie friendly). It should also never get lost (e.g. screwing up settings), and it should be easy to find and configure. Having the different elements in the same executable also makes it possible to integrate them better, and they can potentially access each other's functionality. For example, I think I added 20 lines of code or so to make it possible to display the taskbar on the toolbar instead of on the systembar...

Due to the now very different code bases and feature sets of xoblite/bb4win/bbLean, it is not possible to compare file sizes anymore, but back in the days when (what was to become) xoblite was still fairly close to bb4win, its file size was always smaller than the equivalent core+plugin combinations. That doesn't necessarily mean it was "lighter" or "leaner" in every sense, but you could perhaps say that while the modular approach has certain benefits, so does the integrated approach. Finally, due to the fact that the difference lies mainly in the choice of display functionality and not the backend, the memory overhead of a hidden integrated element should be minimal or non-existent, especially when you consider that plugins need a certain overhead as well.

I'm not sure if that made things more clear, if not do not hesitate to ask!

BR//Karl -> qwilk

PS. In case you're interrested, you'll find the headers for the taskbar/systray APIs at the bottom of http://xoblite.net/source/BBApi.h.html.

now, if that is not clear, i don't know what is clear...

i understand it now.. it's really good to have the developer around..

so how do i fix the duplicate directories in the start menu? aside from modifying my directory structure itself.. i tried removing either "$StartMenu$" or "$CommonStartMenu$", but, of course, it won't show all my available menus...

The problem with the visual c++ runtime problem is with Xoblite and BBSeekBar, when begins a new song with Winamp or Foobar2000, happen this. For me.

I don't wish use bbLean etc...
I always use only Blackbox! Is this probably or very old the shell ?
What You say about Blackbox vs bbLean ?


some problem I have with styles "win borders" not be aplyed... but I now know it's need bbLeanSkin plugin.
I try use it
sorry, I'm newbie and ago not use any addons over!

Yes my favorites things is xoblite bb3 RC1 !

what is what this:
bbleanskinengmod116y1.zip
bbleanskinmod116m.zip
bbleanskinmod116u.zip - I see this 2008 year and I put it to plugins. Cool work!

I thinking more try to use bluebox... But i used to my blackboxy!

How I may to disable a dialog -
[reboot]
Are You Sure? [Y/N]
I wish reboot without any replys faster!
PS Always I had using:
[exec] (start) {shutdown.exe -r -f -t 00}
but now it's comes probably with somes other crazy my software.