The bbBroam project is discontinued by the author. bbBroam was a basic blackbox-style plugin with minimal functionality (send broams), which purpose was to develop a text input interface (also a console output was considered) with solid functional Slit and no-Slit modes. Some additional hacks have been done in order to work (more or less successfully) with bbRun (0.0.7 or less) through a broam.

Quoted from the original first post:


The new bbRunBar (bbRun) plugin project started using bbBroam 0.0.4 (still buggy and unoptimized) for its interface. Since then, all the bug fixes and improvements are done in bbRunBar and will not be updated anymore in bbBroam by the author. bbBroam contributors are free to update it and keep the project alive, though. The console output idea is still around, but as an option for bbRunBar instead.

New bbRunBar plugin is here.

Version 0.0.3 was the last verified by the community, for bbLean. Included sources for compatible version by unkamunka (unchecked, may need to uncomment a couple of #includes), with partially fixed styling, autohide & toggle problems in the slit & outside too.

You can download the last version 0.0.4 with a couple of changes over the previous one (still with problems) and compatibility unverified.

Old Plugins Forum Threads

• bbBroam (0.0.2) stylized broamer project

Up to bbBroam 0.2, the input area shows black when the Style for toolbar.label.appearence is parentrelative. Adding two lines to the beginning of GetStyleSettings(void) can fix this. After the second line (style_info.Edit = *(StyleItem *)GetSettingPtr(SN_TOOLBARLABEL);), the following can be added:

you may set "bbBroam.editborder:" to a negative number to give bbBroam a flat panel kind of look

In the continuing absence of the-r-, here is an update

• Replaced: conditional xoblite compile with reference to an "xoblite library" (as used in bbCore.dll)
• Fixed: text display issue where toolbar.label is parentrelative

The plugin (which requires bbRun) now performs identically under all flavours of bb4win.

A bro@ms list is now usable for xoblite folks. Source code is in the zip file.

Would anyone be so kind as to write a mini tut just to get started with bbBroam and bbRun? I don't understand there relation.

bbBroam gives you a simple interface so that bbRun functionality (as described in the dox bbRun zip file) can be available all the time. You can set the menu of your choice to appear when you RightClick on the bb logo on bbBroam. All the command line functionality in bbBroam depends on having bbRun loaded at the same time.

There is also "MRU" functionality. The MRU list works basically the same as the RightClick menu - but the command line text appears in the bbBroam interface. Since the *.mru file has to be updated by hand, "MRU" - as in MostRecentlyUsed - is somewhat of a misnomer.

Thanks unkamunka. So is bbBroam suppose to sit on the desktop? Or is there a way to call it like win+R?

IIRC there's a bro@m for bbRun that does that. AFAICS bbBroam is for folks that want to see the command line 24|7.

I see. Well I'm new to the broam functionality of bblean. Never had a use for it in the past. But my workflow is starting to get messy.

I found the bbkey command that calls bbrun, but that only brings the bbrun ui, not the bbBroam ui. I may have to read more about the slit feature, or build a bbi for it.

It seems that when you type into bbBroam that it disappears. How do you call it back? That's really all I needed to know. Thanks.

Do you mean the text - or the entire interface?

The entire interface.

I like the fact that it disappears, just like windows run. But I would like to invoke the interface with a keystroke.

abelmiah, the problem you mentioned is fixed in v0.0.3.

AutoHide mode makes the interface disappear when you hit <Escape> to cancel or <Enter> to run something, or with @bbBroam.focus again (toggle).
HiddenSlit was a hack intended to make bbBroam visible (in slit) when the slit is hidden, but was removed in the new version because i think the slit is a more mouse-oriented interface.

The new version is here.

hi people! well, I've updated the main post with an update (the last one by me) and some bad and good news. See you soon.