>>>>> "Allan" == Allan Rae <[EMAIL PROTECTED]> writes:
Allan> Allan's Rant Summary: We can use JMarc's and Asger's single
Allan> toolbar class (or hierarchy) just like I said in my last email.
Allan> The interface that the LyX core sees via the LyXView is a
Allan> couple of signals in a manner similar to that currently used by
Allan> the Popups class. The two ideas are not incompatible its just
Allan> a matter of how much the rest of LyX has to know about toolbars
Allan> in order to use them.
Absolutely true. My plan is to make the abstract toolbar part, and let
you do the signals ;)
Allan> If the user wants to have a bunch of different toolbars is it
Allan> really necessary to display them all at once? As I suggested
Allan> yesterday one at a time should be sufficient and then flip
Allan> through them to get to a different toolbar. If we have a few
Allan> standard names like MATH or TABLE for example we could provide
Allan> context sensitive toolbars via a very simple signal interface
Allan> (the same style of interface used in Popups and also described
Allan> yesterday).
Exactly.
Allan> Each Frame would have a similar format to the Popups class: a
Allan> bunch of simple signals that allow us full independence from
Allan> the gui implementations. This also masks the gui-backend stuff
Allan> from the rest of LyX.
I'm not sure I understand how signals work currently, but this looks
good.
Allan> I've said all along we should be using the one toolbar class
Allan> hierarchy that you and Asger have discussed and developed! I'm
Allan> only arguing about how the rest of LyX sees the toolbars!
Allan> toolbars should be seen the same way popups are: they're
Allan> aren't! they're invisible to the rest of LyX.
In fact, we agree on what to do, it is just that we did not know that :)
JMarc
