On Wed, Mar 24, 2004 at 08:55:19AM +0100, Alfredo Braunstein wrote:
> Andre Poenitz wrote:
>
> > On Mon, Mar 22, 2004 at 11:34:06AM +0100, Alfredo Braunstein wrote:
> >> 2) row-driven cursor up and down get confused by it.
> >
> > This is sort of dead. We use mathed style up/down now, i.e. go to
Andre Poenitz wrote:
> On Mon, Mar 22, 2004 at 11:34:06AM +0100, Alfredo Braunstein wrote:
>> 2) row-driven cursor up and down get confused by it.
>
> This is sort of dead. We use mathed style up/down now, i.e. go to the
> closed position with a smaller y coordinate on 'up'.
We should use you me
Andre Poenitz wrote:
>> Funny, I proposed the same thing and got accused of boycotting your
>> cleanup. :-)
>
> By me?
No. Oh, nevermind.
Alfredo
On Sun, Mar 21, 2004 at 03:50:21PM +0100, Alfredo Braunstein wrote:
> > We could ignore the intend in paragraphs with a text inset as first item
> > in all three solutions as well...
>
> Funny, I proposed the same thing and got accused of boycotting your
> cleanup. :-)
By me?
This must have happ
On Mon, Mar 22, 2004 at 11:34:06AM +0100, Alfredo Braunstein wrote:
> 2) row-driven cursor up and down get confused by it.
This is sort of dead. We use mathed style up/down now, i.e. go to the
closed position with a smaller y coordinate on 'up'.
See LCursor::goUpDown (or however it is called...)
Alfredo Braunstein wrote:
> Angus Leeming wrote:
>
>> Cute, but doesn't scale well if you have multiple insets on one line.
>
> True.
>
>>> Otherwise (snapshot7) ,
>>
>> Yes please!
>
> There are still a number of problems, mainly due to the fact that the
> inset doesn't have his own row but
On Sun, Mar 21, 2004 at 02:18:59PM +0100, Alfredo Braunstein wrote:
> Angus Leeming wrote:
>
> > Most important comment is that all these solutions are temporary hacks
> > if the ultimate goal is "an inset is three boxes". IOW, I don't think
> > we should be t worried about which ever choice i
> "Alfredo" == Alfredo Braunstein <[EMAIL PROTECTED]> writes:
Alfredo> which is more compact (and simpler to code), but it's a bit
Alfredo> disconcerting that text that comes before (the footnote)
Alfredo> shown actually after (weell, it not so uncommon for
Alfredo> footnotes). This could be m
Angus Leeming wrote:
> Cute, but doesn't scale well if you have multiple insets on one line.
True.
>> Otherwise (snapshot7) ,
>
> Yes please!
There are still a number of problems, mainly due to the fact that the inset
doesn't have his own row but just vertically enlarges the row it's in:
1) it
Alfredo Braunstein wrote:
> There are two possibilities: either (snapshot6) we allow text after
> the inset button:
>
> blah blah blah blah [foot] blah blah
> ++
> ||
> ||
> +---
Andre Poenitz wrote:
>> option 2) he uses only w -> we get current cvs behaviour
>> option 3) use a mixture of the two, choosing the one that spans less
>> vertical space (the inlined version uses a line less, but then has less
>> horizontal space to accomodate the remaining rows and so there will
Am Samstag, 20. März 2004 21:14 schrieb Andre Poenitz:
> On Sat, Mar 20, 2004 at 12:29:09PM +0100, Alfredo Braunstein wrote:
> > Now what happens if we have the inset in the first char of an indented
line?
> >
> ><--- s --->
> >[open inset] blah blah blah
>
On Sat, Mar 20, 2004 at 12:29:09PM +0100, Alfredo Braunstein wrote:
> < s ->
> blah blah blah blah [open inset]
> ++
> ||
> ||
>
> |
Angus Leeming wrote:
> Most important comment is that all these solutions are temporary hacks
> if the ultimate goal is "an inset is three boxes". IOW, I don't think
> we should be t worried about which ever choice is implemented.
Is not clear to me if this is the general consensus. I may be
Alfredo Braunstein wrote:
> I've tried to make some sense on the last discussions on rebreaking,
> did some experimaentations with 1.3.x, and still I don't see a clear
> path.
[Compelling discussion snipped.]
> Any /constructive/ comment is welcomed.
Most important comment is that all these sol
15 matches
Mail list logo
