"Marko" == Marko Vendelin [EMAIL PROTECTED] writes:
Marko Another possibility is to use exactly the same interface for
Marko toolbar and menubar. Then the set of toolbars will be presented
Marko by first level submenus, buttons in the toolbars --- by
Marko commands in submenus, and comboboxen
On 9 Feb 2001, Jean-Marc Lasgouttes wrote:
It's not me who wanted toolbars to appear depending on cursor position
:)
hey, it's not me either ! I just wanted the possibility of context-sensitive stuff.
Note that the frontend would be free to ignore that, or condition
it on some config
On Fri, 9 Feb 2001, John Levon wrote:
On 9 Feb 2001, Jean-Marc Lasgouttes wrote:
It's not me who wanted toolbars to appear depending on cursor position
:)
hey, it's not me either ! I just wanted the possibility of
context-sensitive stuff.
It would seem none of you have ever used Lotus
> "Marko" == Marko Vendelin <[EMAIL PROTECTED]> writes:
Marko> Another possibility is to use exactly the same interface for
Marko> toolbar and menubar. Then the set of toolbars will be presented
Marko> by first level submenus, buttons in the toolbars --- by
Marko> commands in submenus, and
On 9 Feb 2001, Jean-Marc Lasgouttes wrote:
> It's not me who wanted toolbars to appear depending on cursor position
> :)
hey, it's not me either ! I just wanted the possibility of context-sensitive stuff.
> Note that the frontend would be free to ignore that, or condition
> it on some config
On Fri, 9 Feb 2001, John Levon wrote:
> On 9 Feb 2001, Jean-Marc Lasgouttes wrote:
>
> > It's not me who wanted toolbars to appear depending on cursor position
> > :)
>
> hey, it's not me either ! I just wanted the possibility of
> context-sensitive stuff.
It would seem none of you have ever
"Marko" == Marko Vendelin [EMAIL PROTECTED] writes:
Marko There is another silly example when this signal is needed ---
Marko one might have TOC in the toolbar with chapters showing up as a
Marko buttons. I am not sure who would like to have this feature, but
Marko the point is that kernel has
On 8 Feb 2001, Jean-Marc Lasgouttes wrote:
"Marko" == Marko Vendelin [EMAIL PROTECTED] writes:
Marko There is another silly example when this signal is needed ---
Marko one might have TOC in the toolbar with chapters showing up as a
Marko buttons. I am not sure who would like to have this
On Thu, 8 Feb 2001, Allan Rae wrote:
Maybe TOC, LOF, LOT, ... need a new signal (updateLists)?
Why all lists? If a figure inset is changed then an LOF-signal could be
sent and so on.
As far as I can tell this kind of "document mutated" medium-grained signal is what
I've been arguing for
> "Marko" == Marko Vendelin <[EMAIL PROTECTED]> writes:
Marko> There is another silly example when this signal is needed ---
Marko> one might have TOC in the toolbar with chapters showing up as a
Marko> buttons. I am not sure who would like to have this feature, but
Marko> the point is that
On 8 Feb 2001, Jean-Marc Lasgouttes wrote:
> > "Marko" == Marko Vendelin <[EMAIL PROTECTED]> writes:
>
> Marko> There is another silly example when this signal is needed ---
> Marko> one might have TOC in the toolbar with chapters showing up as a
> Marko> buttons. I am not sure who would
On Thu, 8 Feb 2001, Allan Rae wrote:
> > Maybe TOC, LOF, LOT, ... need a new signal (updateLists)?
>
> Why all lists? If a figure inset is changed then an LOF-signal could be
> sent and so on.
As far as I can tell this kind of "document mutated" medium-grained signal is what
I've been arguing
"John" == John Levon [EMAIL PROTECTED] writes:
John So I must update every dynamic menu/toolbar item on every
John update(). OK, I suppose that's not too bad. But what is it
John you're actually informing the frontend of ? It seems that the
John current examples are just about buffer
On 7 Feb 2001, Jean-Marc Lasgouttes wrote:
Finally, my main problem is that I do not have time to work on this
right now, so if I cannot convince you to work from the current
scheme, I'll have to give up :(
I only happened to mention it in passing really. I really need to sit down and
think
John Levon [EMAIL PROTECTED] writes:
| [1] Lars, there would only be one file auto-generated now after our
| tete-a-tete, and
| that's the initialiser for the lyxfuncs ... does that change your
| opinion on the auto-gen
| at all :))
Slightly :-)
Lgb
Hi!
On 7 Feb 2001, Jean-Marc Lasgouttes wrote:
"John" == John Levon [EMAIL PROTECTED] writes:
John So I must update every dynamic menu/toolbar item on every
John update(). OK, I suppose that's not too bad. But what is it
John you're actually informing the frontend of ? It seems that the
Still to read the full thread but skimming a couple I can add these
comments:
On Wed, 7 Feb 2001, Marko Vendelin wrote:
[...]
John How would your method cope with a number of different toolbars
John for different things ? Do you call update() on each one ? Why
John not just let the
On Thu, 8 Feb 2001, Allan Rae wrote:
On Wed, 7 Feb 2001, Marko Vendelin wrote:
[...]
John How would your method cope with a number of different toolbars
John for different things ? Do you call update() on each one ? Why
John not just let the frontend decide what needs updating - why
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> So I must update every dynamic menu/toolbar item on every
John> update(). OK, I suppose that's not too bad. But what is it
John> you're actually informing the frontend of ? It seems that the
John> current examples are just about buffer
On 7 Feb 2001, Jean-Marc Lasgouttes wrote:
> Finally, my main problem is that I do not have time to work on this
> right now, so if I cannot convince you to work from the current
> scheme, I'll have to give up :(
I only happened to mention it in passing really. I really need to sit down and
John Levon <[EMAIL PROTECTED]> writes:
| [1] Lars, there would only be one file auto-generated now after our
| tete-a-tete, and
| that's the initialiser for the lyxfuncs ... does that change your
| opinion on the auto-gen
| at all :))
Slightly :-)
Lgb
Hi!
On 7 Feb 2001, Jean-Marc Lasgouttes wrote:
> > "John" == John Levon <[EMAIL PROTECTED]> writes:
> John> So I must update every dynamic menu/toolbar item on every
> John> update(). OK, I suppose that's not too bad. But what is it
> John> you're actually informing the frontend of ? It
Still to read the full thread but skimming a couple I can add these
comments:
On Wed, 7 Feb 2001, Marko Vendelin wrote:
[...]
> > John> How would your method cope with a number of different toolbars
> > John> for different things ? Do you call update() on each one ? Why
> > John> not just let
On Thu, 8 Feb 2001, Allan Rae wrote:
> On Wed, 7 Feb 2001, Marko Vendelin wrote:
> [...]
> > > John> How would your method cope with a number of different toolbars
> > > John> for different things ? Do you call update() on each one ? Why
> > > John> not just let the frontend decide what needs
The subject says it all. Removing this code would simplify things,
really.
JMarc
On 6 Feb 2001, Jean-Marc Lasgouttes wrote:
The subject says it all. Removing this code would simplify things,
really.
JMarc
Simplify what exactly ? The core code ? If it's just the menu code, well
that needs totally reworking anyway...
john
--
"Do you mean to tell me that "The Prince"
"John" == John Levon [EMAIL PROTECTED] writes:
John Simplify what exactly ? The core code ? If it's just the menu
John code, well that needs totally reworking anyway...
It would give us (at least me) a better view of the code. Removing it
is as simple as doing a big cut in the xforms code and
On 6 Feb 2001, Jean-Marc Lasgouttes wrote:
"John" == John Levon [EMAIL PROTECTED] writes:
John Simplify what exactly ? The core code ? If it's just the menu
John code, well that needs totally reworking anyway...
It would give us (at least me) a better view of the code.
OK
in the
"John" == John Levon [EMAIL PROTECTED] writes:
John I've spent some time thinking about the menu stuff a couple of
John months ago. It is an icky problem really; I'm definitely leaning
John towards having all item-creation / default.ui parsing in each
John frontend, and only having meaningful
On 6 Feb 2001, Jean-Marc Lasgouttes wrote:
"John" == John Levon [EMAIL PROTECTED] writes:
John I've spent some time thinking about the menu stuff a couple of
John months ago. It is an icky problem really; I'm definitely leaning
John towards having all item-creation / default.ui parsing in
On 6 Feb 2001, Jean-Marc Lasgouttes wrote:
"John" == John Levon [EMAIL PROTECTED] writes:
John Not generate a dynamic menu every time it's called
John (theoretically, the hookes needed in kernel are simple in some
John cases, more complicated in others)
You can generate the menus at
The subject says it all. Removing this code would simplify things,
really.
JMarc
On 6 Feb 2001, Jean-Marc Lasgouttes wrote:
>
> The subject says it all. Removing this code would simplify things,
> really.
>
> JMarc
Simplify what exactly ? The core code ? If it's just the menu code, well
that needs totally reworking anyway...
john
--
"Do you mean to tell me that "The
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> Simplify what exactly ? The core code ? If it's just the menu
John> code, well that needs totally reworking anyway...
It would give us (at least me) a better view of the code. Removing it
is as simple as doing a big cut in the xforms
On 6 Feb 2001, Jean-Marc Lasgouttes wrote:
> > "John" == John Levon <[EMAIL PROTECTED]> writes:
>
> John> Simplify what exactly ? The core code ? If it's just the menu
> John> code, well that needs totally reworking anyway...
>
> It would give us (at least me) a better view of the code.
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> I've spent some time thinking about the menu stuff a couple of
John> months ago. It is an icky problem really; I'm definitely leaning
John> towards having all item-creation / default.ui parsing in each
John> frontend, and only having
On 6 Feb 2001, Jean-Marc Lasgouttes wrote:
> > "John" == John Levon <[EMAIL PROTECTED]> writes:
>
> John> I've spent some time thinking about the menu stuff a couple of
> John> months ago. It is an icky problem really; I'm definitely leaning
> John> towards having all item-creation /
On 6 Feb 2001, Jean-Marc Lasgouttes wrote:
> > "John" == John Levon <[EMAIL PROTECTED]> writes:
>
> John> Not generate a dynamic menu every time it's called
> John> (theoretically, the hookes needed in kernel are simple in some
> John> cases, more complicated in others)
>
> You can
38 matches
Mail list logo
