Eric Hanson [mailto:[EMAIL PROTECTED]] wrote:
> > Simple, you want some feature such as a graphical pager, you get
> > that app and run it. In almost all aspects BB allows you to add
> > what you want (the slit being the only exception I'm aware of).
>
> That is not modular. Having seperate applications able to run isn't
> modular. Or is Microsoft office modular because you can isntall Word,
> Excel, or Access.
Since when is this not modular? Linux is built around this philosophy and
is quite modular because of it. Small applications that do one thing and do
it well. These small applications can then be used together in a variety of
differing ways to create a custom fit to any problem. Again, how is this
not modular?
> > I'm not aware of the current version of BB grabbing any
> > keystrokes of any kind. Please elaborate on this.
>
> Try holding down the alt button and left or right click on a window.
> You will see the icon change and you can now resize/move the window
> while holding down the alt button. If you look at the blackbox.cc file
> you will notice several key and button grabs. Have you looked at the
> source code much? It doens't have any comments but it is a good place
> for finding undocumented "features".
No, I haven't looked over the BB code. I haven't had the need. I apologize
for my not reviewing the code leading to my lack of awareness regarding BB
and some key captures. IMHO, these key captures should be removed from BB's
native code. Not used as a reason for yet more key captures to be added.
> I agree that blackbox should grab keys, it has to, to be able
> to pop up menus, interact with them, provide interaction with the
> built-in pager, tasklist, etc. I don't think it should stop short.
> If it didn't handle any key clicks it wouldn't work. You would be
> trapped in a single workspace. So, since it needs to see key and
> button events it should go all the way and absorb bbkeys, perhaps
> adding options for those who don't want to customize anything.
There is no need to have BB natively capture key presses. Having BB not
capture key presses would in no way lock you to one Workspace. It is not
key presses that pop up the menus or interact with them, the built-in pager
or the tasklist. Rather, it is the mouse that interacts with these things.
Thus, there is a need to have BB native capture mouse input. The two are
seperate items. I realize that there have been many requests to have the BB
menus keyboard navigable. However it is not necessary to have BB capture
the key presses to do so. Key presses can be captured via another
application and in turn register events with BB to accomplish the desired
result.
> P.S. It still looks like simple resistance to change. If bbkeys, etc.
> are made compile time options, that in no way affects people who don't
> want to use those programs (especially if the default is to not include
> them, which I am sure it will be). The code isn't even compiled into
> the binary.
Again, how is the applications functionality hindered by not being a native
part of BB?
