Here's an update. I added a couple of comments this time.
OptSubMenu isn't too useful yet because something is going awry in the
getStatus() stuff (perhaps mathed lfuns ?). We also need getStatus for
increase/decrease depth etc.
Any way, all comments gratefully received. JMarc, the ellipsisation
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> Here's an update. I added a couple of comments this time.
I like it. It will rwquire a lot of docs updates, though.
John> OptSubMenu isn't too useful yet because something is going awry
John> in the getStatus() stuff (perhaps mathed lf
On Tue, Feb 18, 2003 at 03:24:34PM +0100, Jean-Marc Lasgouttes wrote:
> John> Here's an update. I added a couple of comments this time.
>
> I like it. It will rwquire a lot of docs updates, though.
I am prepared to do this grunt work. If only to show off change tracking :)
> John> We also need
> "Jean-Marc" == Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
John> We also need getStatus for increase/decrease depth etc.
Jean-Marc> Should be easy.
I probably have to retract this statement. the incDepth/decDepth code
is ugly.
JMarc
> "John" == John Levon <[EMAIL PROTECTED]> writes:
>> Should be easy.
John> Perhaps you have some idea how. My 3-minute look didn't help me.
No, I have no idea anymore :(
John> The problems we need to solve :
John> 1) Toolbars. We've seen a little discussion on how to proceed
John> here,
On Tue, Feb 18, 2003 at 03:48:56PM +0100, Jean-Marc Lasgouttes wrote:
> 1/ name toobars, like menubars are named. For example, we would have a
> "literate_programming" toolbar.
Yes.
> 2/ Any toolbar can be on/off/auto (this is in qt land, not backend);
> if it is auto, show the toolbar only if a
> "John" == John Levon <[EMAIL PROTECTED]> writes:
>> I tend to think it is the best solution. Note that it could be
>> "edit-properties tabular", where edit-properties searches the
>> nearest inset with name "tabular" around. This means there will not
>> be much lfun duplication.
John> Ah ok
On Tue, Feb 18, 2003 at 04:09:23PM +0100, Jean-Marc Lasgouttes wrote:
> If only getStatus was not implemented as a big ugly switch, it would
> be great stuff...
getStatus should get locallized as localDispatch is...
This is not hard in theory but probably will take a while to get right...
Andre
Jean-Marc Lasgouttes wrote:
>> "John" == John Levon <[EMAIL PROTECTED]> writes:
>
>>> I tend to think it is the best solution. Note that it could be
>>> "edit-properties tabular", where edit-properties searches the
>>> nearest inset with name "tabular" around. This means there will not
>>> be
On Tue, Feb 18, 2003 at 03:19:42PM +, Angus Leeming wrote:
> Could we not have a heirarchy of FuncRequest-derived classes as a one
> to one replacement for each LFUN?
And dispatch on those how?
What would that buy us?
[The main problem _I_ have with current dispatch is the limited scope of
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> Here's an update. I added a couple of comments this time.
John> OptSubMenu isn't too useful yet because something is going awry
John> in the getStatus() stuff (perhaps mathed lfuns ?).
It is because math matrices and tabulars share th
On Thu, Feb 20, 2003 at 03:26:26PM +0100, Jean-Marc Lasgouttes wrote:
> John> OptSubMenu isn't too useful yet because something is going awry
> John> in the getStatus() stuff (perhaps mathed lfuns ?).
>
> It is because math matrices and tabulars share the same lfun. I
> thought you threatened to
12 matches
Mail list logo
