> > > etc, and then everybody places whatever combination he likes in one
> > > single "toolslit".
> >
> > this would imho cause way too much memory-load for this stuff.
>
> I don't believe the suggestion was for the creation of separate apps
> with the functions (least I hope not), but rather keep the code internal
> to Blackbox, as it already is, and allow the user to place the
> interfaces in the "toolslit" where and how they want.
>

I candidly admit to not know about C/C++ or Blackbox internals enough
to have an opinion on what the best implementation would be.

Mine are user's arguments: I am suggesting that *one* rectangle in the
root window is enough to host anybody's preferred combination of
functions, from workspace management to new email.

All deciding what gets loaded in RAM and what not from one rc file.
without all of us being *forced* to apply all possible combination of
patches (those who want to do it are welcome of course, that's what
the source is for).

This is what I would really like to have. Again, I have no idea whatsoever
if this is best done integrating the functions in the core code,
putting everything in the slit or anything else.

I was just pointing out that being able to patch anything this side
of the sun shouldn't always mean that everybody *must* do it, if there
is another more efficient and flexible way.

        You tell me.

                        Marco

Reply via email to