>>>>> "Edwin" == Edwin Leuven <[EMAIL PROTECTED]> writes:
Edwin> what i haven't done: implement a lyxfunc Edwin> the main reason is that it is not clear to me that we would Edwin> want to introduce special casing in the core in order to avoid Edwin> it in the frontend... What you can do is create a special casing in ToobarBackend.C for your popup widget. Edwin> second, we are inserting a non-standard widget and i am not Edwin> sure we want a new lyxfunc for every deviation from a Edwin> toolbutton: we will want to have "iconpallete's" popups on some Edwin> buttons in a math toolbar, do we want lyxfuncs for these as Edwin> well? There are three kind of sub-things we may want to insert in a toolbar: combox, icon palette and menu. Combox is already hardcoded for layouts now, but I am not sure we have other needs. icon palette and menu are syntactically the same thing, only the display differs (icons vs. labels). These things should be implemented in toolbarbackend with new tags modelled after SubMenu in MenuBackend. And then, of course, we need a good implementation in the frontends. It seems to me that the icon palettes and menus that we need for a math toolbar are static, am I wrong? In this case, supporting them is as simple as enumerating in the .ui file. JMarc
