Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> the inset you are speaking of have no need f.ex. for the
| Lars> multiparagraph support in InsetText.
|
| Yes, I agree. However, when this wonderful insetmbox exists, it
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> the inset you are speaking of have no need f.ex. for the
Lars> multiparagraph support in InsetText.
Yes, I agree. However, when this wonderful insetmbox exists, it will
be very easy to switch to that :)
JMarc
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> No but we should perhaps create one...
|
| And what would that be exactly? More to the point, what is the problem
| with subclassing insettext? Just that you feel it is n
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> No but we should perhaps create one...
And what would that be exactly? More to the point, what is the problem
with subclassing insettext? Just that you feel it is not right? I do
not see speed or memeory problems happen due to
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> I still think InsetText is too complex for that use. We should
| Lars> rather create a InsetMbox variant...
|
| Do we have an InsetMBox?
No but we should perhaps create
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> I still think InsetText is too complex for that use. We should
Lars> rather create a InsetMbox variant...
Do we have an InsetMBox?
JMarc
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> Won't InsetText be a bit overkill for this?
|
| Lars> This is closer to InsetLabel...
|
| For the case of a key binding, insettext is not needed (and I did not
| plan to
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Won't InsetText be a bit overkill for this?
Lars> This is closer to InsetLabel...
For the case of a key binding, insettext is not needed (and I did not
plan to use it). But if I want to do some formatting, it seems to me
that
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes:
|
| Juergen> Well yes this should be possible, but I still don't get what
| Juergen> you really want to do with it!
|
| The idea would be, in the docs, to do an
| M-x menuinset-inse
> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes:
Juergen> Well yes this should be possible, but I still don't get what
Juergen> you really want to do with it!
The idea would be, in the docs, to do an
M-x menuinset-insert lyx-quit
and have a nice box on the screen showing "_File>_Qu
On 30-May-2001 Jean-Marc Lasgouttes wrote:
>> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes:
>
> Juergen> I don't get to what exactly you need, but surely one can make
> Juergen> a MenuInset based on InsetText and not Editable.
>
> Doing an inset for key bindings is easy, since it w
> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes:
Juergen> I don't get to what exactly you need, but surely one can make
Juergen> a MenuInset based on InsetText and not Editable.
Doing an inset for key bindings is easy, since it will just contain
plain text. For a menu, it will be mor
On 30-May-2001 Jean-Marc Lasgouttes wrote:
> The idea I had for menus was to subclass a non-editable version of
> insettext (does this exist) so that a small insettext (with underlines
> at the right place and nice menu separators and maybe even the sans
> serif font) would be created on the fly
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Sure menus are for _loosers_!
The idea I had for menus was to subclass a non-editable version of
insettext (does this exist) so that a small insettext (with underlines
at the right place and nice menu separators and maybe even
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
|
| Lars> Even if this inset would seemingly make things easier I do not
| Lars> quite agree with it. IMO the bindings are not athorative, the
| Lars> lyxfuns are. So the bindings c
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Even if this inset would seemingly make things easier I do not
Lars> quite agree with it. IMO the bindings are not athorative, the
Lars> lyxfuns are. So the bindings can be referenced in the main text,
Lars> but the main focus
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| I also had a few ideas on how to simplify somewhat the documenter's
| work, like an inset that displays the keybinding of a given function,
| or even the menu entry corresponding to this lyxfunc. I guess this
| could help getting the doc up to da
On 29-May-2001 [EMAIL PROTECTED] wrote:
> Perhaps it's time for an Errata page on the Web. Anyone with Web CVS
> access willing to lead the charge?
Good we have the doc-team working again ;) IMO we should really try to
update the documentation a bit regarding all the new and changed stuff
from
> "Mike" == <[EMAIL PROTECTED]> writes:
Mike> This brought up the idea of an Errata section on
Mike> the Web. At least we can collect the current inconsistencies and
Mike> make them known there, so the Users don't get totally frustrated
Mike> with the current situation.
Note also that a go
> I'm hoping that 1.2.0pre0 will freeze
> the basic interface/keybindings/commandline for at least a few versions;
Don't trust math key bindings yet...
Andre'
--
André Pönitz . [EMAIL PROTECTED]
> "Mike" == <[EMAIL PROTECTED]> writes:
Mike> I'm not criticizing the decision to change these bindings -
Mike> improving the UI is always good, but having just seen another
Mike> message about needing to update the docs about --export, I need
Mike> to vent.
In the second case, it is rathe
21 matches
Mail list logo