On Fri, Dec 05, 2003 at 10:29:03AM +0200, Martin Vermeer wrote:
> Interesting. It feels like direct manipulation to me.
>
> I am using it all the time in math. Discovered it by accident but
> grasped it straightaway, and now it is second nature. Delete the whole
> by trying to delete a part, or '
On Tue, Dec 09, 2003 at 10:31:51AM +0100, Andre Poenitz spake thusly:
> > BTW should we have symmetric behaviour? I.e. pressing 'delete' on the
> > inside of the right of a parentheses pair would 'melt' the pair. But
> > it seems this is already bound...
>
> bound? What?
To deleting a matrix ro
On Tue, Dec 09, 2003 at 11:04:41AM +0200, Martin Vermeer wrote:
> On Mon, Dec 08, 2003 at 11:40:48AM +0100, Andre Poenitz spake thusly:
>
> > Index: math_cursor.C
> > ===
> > RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/math_
On Mon, Dec 08, 2003 at 11:40:48AM +0100, Andre Poenitz spake thusly:
> Index: math_cursor.C
> ===
> RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/mathed/math_cursor.C,v
> retrieving revision 1.368
> diff -u -p -r1.368 math_cursor.C
On Mon, 8 Dec 2003, Andre Poenitz wrote:
> On Mon, Dec 08, 2003 at 12:12:51PM +0200, Martin Vermeer wrote:
> > > Straight-forward. Five lines at most.
> >
> > Which five lines?
> >
> > :-)
>
> Attached.
>
> Actually, I even think this feature is usable.
Not bad... I think this should be appli
On Mon, Dec 08, 2003 at 11:28:30AM +0100, Helge Hafting wrote:
> * Help->about lyx says Lyx 1.4.0cvs Thu, Jan 30, 2003. This made me suspect
> a cvs setup error, or doesn't the date reflect the latest change?
That's "ok".
> So, is "lyx-devel" development or stable?
The former with the general
On Mon, Dec 08, 2003 at 12:12:51PM +0200, Martin Vermeer wrote:
> > Straight-forward. Five lines at most.
>
> Which five lines?
>
> :-)
Attached.
Actually, I even think this feature is usable.
Andre'
? .math_cursor.C.swp
? 1.diff
? cursor.diff
Index: math_cursor.C
=
Andre Poenitz wrote:
On Fri, Dec 05, 2003 at 02:06:10PM +0100, Helge Hafting wrote:
[...]
gave me a src/lyx that don't want keyboard input. I can't type,
only move around and/or paste text.
I thought this just was the sort of things that might happen when
trying 1.4cvs versions.
It shouldn't. Is
On Mon, Dec 08, 2003 at 09:46:16AM +0100, Andre Poenitz spake thusly:
> > One could in the above situation make the first backspace invoke
> > selection of the previous bracketed expression. I don't know how hard
> > that is to implement.
>
> Straight-forward. Five lines at most.
Which five lin
On Sat, Dec 06, 2003 at 04:53:05PM +0100, Lars Gullik Bjønnes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> | If the overlapping stuff is out and physical position == locical
> | position is in, all-boxes is (a) natural, (b) simple.
>
> I am not convinced...
>
> OTOH what I am convinc
On Sat, Dec 06, 2003 at 04:45:23PM +0100, Lars Gullik Bjønnes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> >> What I'm telling you is that the problem goes completely away with
> >> ranges, because we then have a natural interface:
> >>
> >> Edit->Text_Style->Noun
> >>
On Sat, Dec 06, 2003 at 10:59:30AM +0200, Martin Vermeer wrote:
> This is actually not a bad idea. But we sort-of have this now already.
> In MathEd, I never delete anything but single characters straightaway.
> I don't dare to :-( If I want to delete a bracketed expression etc., I
> always select
On Fri, Dec 05, 2003 at 07:49:38PM +0100, Christian Ridderström wrote:
> I agree with Helge here, and it reminded me of a behaviour that's
> sometimes annoying in mathed. It happens quite often that I delete the
> previous 'box' without intending to when using the backspace key. An
> example (ju
On Sat, Dec 06, 2003 at 04:53:05PM +0100, Lars Gullik Bjønnes spake thusly:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> | If the overlapping stuff is out and physical position == locical
> | position is in, all-boxes is (a) natural, (b) simple.
>
> I am not convinced...
>
> OTOH what I a
Andre Poenitz <[EMAIL PROTECTED]> writes:
| If the overlapping stuff is out and physical position == locical
| position is in, all-boxes is (a) natural, (b) simple.
I am not convinced...
OTOH what I am convinced about is that we don't need to support
overlapping stuff/nested LCS.
--
Andre Poenitz <[EMAIL PROTECTED]> writes:
>> What I'm telling you is that the problem goes completely away with
>> ranges, because we then have a natural interface:
>>
>> Edit->Text_Style->Noun
>> Emphasis
>> Badger
>> Other...
>
| And? We jus
On Fri, Dec 05, 2003 at 07:49:38PM +0100, Christian Ridderström spake thusly:
> In case that was unclear, here's an example:
>
> a^2+\textrm{aFunction}+2|
>
> pressing backspace gives
>
> a^2+\textrm{aFunction}+|
>
> backspace again...
>
> a^2+\textrm{aFunction}|
>
> now w
On Fri, 5 Dec 2003, Helge Hafting wrote:
> Andre Poenitz wrote:
> > On Thu, Dec 04, 2003 at 11:43:16AM +0100, Helge Hafting wrote:
> I can't even unapply a change of some text to bold in mathed without
> running round the houses.
> >>>What's wrong with ?
> >>
> >>People don't think of t
On Fri, Dec 05, 2003 at 02:06:10PM +0100, Helge Hafting wrote:
> Another thing I worry about is on-screen appearance. The text gets too
> full of boxes in 1.3 due to index entries, having visible boxes for markup
> might make reading harder. Still, I have to try before complaining
> on this one t
Andre Poenitz wrote:
On Thu, Dec 04, 2003 at 11:43:16AM +0100, Helge Hafting wrote:
Andre Poenitz wrote:
I can't even unapply a change of some text to bold in mathed without
running round the houses.
What's wrong with ?
People don't think of text as formulas. In the text, I expect
backspace
On Fri, Dec 05, 2003 at 09:06:25AM +0100, Andre Poenitz spake thusly:
> On Thu, Dec 04, 2003 at 03:52:54PM +, John Levon wrote:
> > > Yes, box removing by is 'direct manipulation' according to
> > > this definition.
> >
> > It's clearly not :)
>
> Oha.
>
> Andre'
Interesting. It feels li
On Thu, Dec 04, 2003 at 03:52:54PM +, John Levon wrote:
> > Yes, box removing by is 'direct manipulation' according to
> > this definition.
>
> It's clearly not :)
Oha.
Andre'
On Thu, Dec 04, 2003 at 03:09:20AM +0100, Christian Ridderstr?m wrote:
> I recognise several of these from my personal experience with LyX, but
> let me add that on several occasions I've simply thought that:
>
> "ok, there's this little problem, but who cares, LyX is still so good"
people sho
On Thu, Dec 04, 2003 at 11:49:03AM +0100, Andre Poenitz wrote:
> Same argument as John's when he opposed equivalent changes in mathed.
> Nobody, not a single person! complained about this since 1.3.0 is out.
> I am really tempted to call this argument 'FUD'.
Oh come on.
john
--
Khendon's Law:
On Thu, Dec 04, 2003 at 10:43:34AM +0100, Andre Poenitz wrote:
> Having it in the menu would make it discoverable, describing it in the
> UserGuide is sufficient in my opinion.
Then we have reached a complete impasse, alas. At christmas.
> > http://www.usabilityfirst.com/glossary/main.cgi?functi
On Thu, Dec 04, 2003 at 11:43:16AM +0100, Helge Hafting wrote:
> Andre Poenitz wrote:
>
> >>I can't even unapply a change of some text to bold in mathed without
> >>running round the houses.
> >
> >
> >What's wrong with ?
> >
>
> People don't think of text as formulas. In the text, I expect
> b
On Wed, Dec 03, 2003 at 07:06:18PM +, John Levon wrote:
> On Wed, Dec 03, 2003 at 06:56:19PM +0100, Andre Poenitz wrote:
>
> > > > If you really want, you can add two or three generic items (undo inner
> > > > level, split inner box, merge adjacent boxes) but I doubt anybody ever
> > > > will
Andre Poenitz wrote:
I can't even unapply a change of some text to bold in mathed without
running round the houses.
What's wrong with ?
People don't think of text as formulas.
In the text, I expect backspace to erase the character (or other
object) to the left of the cursor. It has always bee
This is just an unimportant comment :-)
On Wed, 3 Dec 2003, John Levon wrote:
> There are a number of ways in which users can be negatively affected by
> a feature. Sometimes these are critical ("LyX crashed"), sometimes
> merely very annoying ("LyX has a stupid banner in the way"), and
> sometim
On Wed, Dec 03, 2003 at 06:56:19PM +0100, Andre Poenitz wrote:
> > > If you really want, you can add two or three generic items (undo inner
> > > level, split inner box, merge adjacent boxes) but I doubt anybody ever
> > > will use them as soon as he discovered the keyboaerd short cuts.
> >
> > I
On Wed, Dec 03, 2003 at 05:48:57PM +, John Levon wrote:
> On Wed, Dec 03, 2003 at 07:47:37PM +0200, Martin Vermeer wrote:
>
> > What I meant was that in light of the smallness (assuming good
> > authoring practices) of these style instances -- as rare(-ish)
> > exceptions to common rules -- th
On Wed, Dec 03, 2003 at 05:27:28PM +, John Levon wrote:
> > We get complaints on other issues
>
> So what ? The above is a list of some of the reasons why we might not
> get complaints. All of them occur. I know because I personally have both
> discovered these being used as reasons, AND done
On Wed, Dec 03, 2003 at 07:47:37PM +0200, Martin Vermeer wrote:
> What I meant was that in light of the smallness (assuming good
> authoring practices) of these style instances -- as rare(-ish)
> exceptions to common rules -- the balance of pros and cons looks more
> favourable for the insets/obje
On Wed, Dec 03, 2003 at 05:19:54PM +, John Levon spake thusly:
> > Forgive me for pointing out that we are living in a "finger painting
> > matrix" where people expect to be able to, and routinely practice,
> > painting large areas of text in whatever visual style they find
> > suitable, rathe
On Wed, Dec 03, 2003 at 06:22:39PM +0100, Andre Poenitz wrote:
> > > > * "the mailing list looks scary"
> > > > * "I'm too busy"
> > > > * "I suppose the designers know what they're doing, who am I to disagree?"
> > > > * "I'm not using the latest LyX, perhaps it's fixed"
> > > > "Sod this, I'm go
On Wed, Dec 03, 2003 at 05:03:36PM +, John Levon wrote:
> On Wed, Dec 03, 2003 at 06:02:14PM +0100, Andre Poenitz wrote:
>
> > All LyX output (.tex, .xml) won't use it, input (.tex) doesn't use it,
> > and it is not necessary to have them for editing.
>
> [ backend implementation ]
>
> > Now
On Wed, Dec 03, 2003 at 05:01:24PM +, John Levon wrote:
> On Wed, Dec 03, 2003 at 05:55:37PM +0100, Andre Poenitz wrote:
>
> > Inset splitting could be a new lfun bound to whatever key you want.
> >
> > \foo{|} + -> \foo{}|\foo{}
> >
> > or even
> >
> > \foo{xx[xx|]}
On Wed, Dec 03, 2003 at 07:29:27PM +0200, Martin Vermeer wrote:
> One thing not to forget here is the following question: how long
> typically, or even maximally, are the pieces of text you would paint
> "Noun" -- or any other logical charstyle for that matter?
>
> I think typically they are smal
On Wed, Dec 03, 2003 at 04:36:26PM +, John Levon spake thusly:
>
> Um, no. I, naturally, have heavily used physical character styles in the
> absence of LCS. The thing with Noun is just a testing thing because it's
> currently implemented both ways in CVS lyx. I am sure you must be aware
> of
On Wed, Dec 03, 2003 at 06:02:14PM +0100, Andre Poenitz wrote:
> All LyX output (.tex, .xml) won't use it, input (.tex) doesn't use it,
> and it is not necessary to have them for editing.
[ backend implementation ]
> Now, if implementation of ranges would be simpler than boxes one could
> try to
On Wed, Dec 03, 2003 at 05:55:37PM +0100, Andre Poenitz wrote:
> Inset splitting could be a new lfun bound to whatever key you want.
>
> \foo{|} + -> \foo{}|\foo{}
>
> or even
>
> \foo{xx[xx|]} + -> \foo{xx}[xx|]\foo{}
>
> where [xx] is the selection.
Sorry, I do
On Wed, Dec 03, 2003 at 04:40:03PM +, John Levon wrote:
> On Wed, Dec 03, 2003 at 05:15:52PM +0100, Andre Poenitz wrote:
>
> > You miss the point. I am arguing that users rarely need overlapping
> > styles and consequently all-boxes is sufficient. You are arguing that
> > you want to select ha
On Wed, Dec 03, 2003 at 04:36:26PM +, John Levon wrote:
> On Wed, Dec 03, 2003 at 05:09:28PM +0100, Andre Poenitz wrote:
>
> > Now, what's the exact difference between C-b and C-b?
> >
> > I can't follow you here?
>
> Um, we were comparing :
>
> > > > Cut, create new \emph inset, go there,
On Wed, Dec 03, 2003 at 05:15:52PM +0100, Andre Poenitz wrote:
> You miss the point. I am arguing that users rarely need overlapping
> styles and consequently all-boxes is sufficient. You are arguing that
> you want to select half of one range and half of an other.
You are (purposefully?) taking
On Wed, Dec 03, 2003 at 05:09:28PM +0100, Andre Poenitz wrote:
> Now, what's the exact difference between C-b and C-b?
>
> I can't follow you here?
Um, we were comparing :
> > > Cut, create new \emph inset, go there, paste.
> > > "select object, apply change"
i.e. inset splitting.
> That's in
On Wed, Dec 03, 2003 at 04:01:59PM +, John Levon wrote:
> On Wed, Dec 03, 2003 at 12:56:21PM -0300, Alfredo Braunstein wrote:
>
> > > o I can't select part of an inset and part outside of an inset and apply
> > > a change
> >
> > I think that implementing this type of selections (i.e. two P
On Wed, Dec 03, 2003 at 04:01:15PM +, John Levon wrote:
> On Wed, Dec 03, 2003 at 04:48:25PM +0100, Andre Poenitz wrote:
>
> > > > Given range style LCS
> > > >
> > > > aaasa dfas dfa ds fasd va sdcv asdv casd
> > > >
> > > >|- a --|
> > > >|
> > > > |-
On Wed, Dec 03, 2003 at 03:41:37PM +, John Levon wrote:
> > THis is the implementation. The user pressed C-b on a selction.
>
> We're not talking about mathed.
No, we are talking about 'selecting things and pressing C-b on them'.
Which happens to work in mathed and outside.
> > > It is *way*
On Wed, Dec 03, 2003 at 12:56:21PM -0300, Alfredo Braunstein wrote:
> > o I can't select part of an inset and part outside of an inset and apply
> > a change
>
> I think that implementing this type of selections (i.e. two PosIterators)
> can be useful for normal insets too. I think that it can
On Wed, Dec 03, 2003 at 04:48:25PM +0100, Andre Poenitz wrote:
> > > Given range style LCS
> > >
> > > aaasa dfas dfa ds fasd va sdcv asdv casd
> > >
> > >|- a --|
> > >|
> > > |- b -|
> > >
> > > what should be output to LaTeX/XML/whatever?
> >
> > T
On Wed, Dec 03, 2003 at 04:20:26PM +0100, Andre Poenitz wrote:
> Given range style LCS
>
> aaasa dfas dfa ds fasd va sdcv asdv casd
>|- a --|
> |- b -|
>
> what should be output to LaTeX/XML/whatever?
Um, same as we already do. Neither backend handles non-re
John Levon wrote:
> o I can't select part of an inset and part outside of an inset and apply
> a change
I think that implementing this type of selections (i.e. two PosIterators)
can be useful for normal insets too. I think that it can even simplify the
current code to some extent.
Alfredo
On Wednesday 03 December 2003 15:59, Martin Vermeer wrote:
>
> like is the case in XML: logically you could have
>
> .
>
> but you dont ;-)
That is not well formed XML. The standards are very clear on this point. :-)
> - Martin
--
José Abílio
On Wed, Dec 03, 2003 at 03:37:32PM +, Jose' Matos wrote:
> On Wednesday 03 December 2003 15:20, Andre Poenitz wrote:
> > >
> > > The latex backend could produce either form.
> >
> > How?
> >
> > Given range style LCS
> >
> > aaasa dfas dfa ds fasd va sdcv asdv casd
> >
> >|- a -
On Wed, Dec 03, 2003 at 03:37:32PM +, Jose' Matos spake thusly:
> On Wednesday 03 December 2003 15:20, Andre Poenitz wrote:
> > >
> > > The latex backend could produce either form.
> >
> > How?
> >
> > Given range style LCS
> >
> > aaasa dfas dfa ds fasd va sdcv asdv casd
> >
> >|
On Wed, Dec 03, 2003 at 04:18:18PM +0100, Andre Poenitz wrote:
> > > Cut, create new \emph inset, go there, paste. Pretty much what C-b does
> > > for 'mathbf in mathed.
> >
> > You really think this is acceptable ?
>
> THis is the implementation. The user pressed C-b on a selction.
We're not t
On Wednesday 03 December 2003 15:20, Andre Poenitz wrote:
> >
> > The latex backend could produce either form.
>
> How?
>
> Given range style LCS
>
> aaasa dfas dfa ds fasd va sdcv asdv casd
>
>|- a --|
>|
> |- b -|
>
> what should be output to LaTeX/XML/
On Wed, Dec 03, 2003 at 02:56:38PM +, John Levon wrote:
> On Wed, Dec 03, 2003 at 02:50:21PM +, Angus Leeming wrote:
>
> > >> > \normal{\foo{xxx\normal{nnn}xxx}}
> > >> > and
> > >> > \normal{\foo{xxx}nnn\foo{xxx}}
> > >> Let \foo be \small and you will see a difference.
> > > How ?
> >
>
On Wed, Dec 03, 2003 at 02:30:34PM +, John Levon wrote:
> > Cut, create new \emph inset, go there, paste. Pretty much what C-b does
> > for 'mathbf in mathed.
>
> You really think this is acceptable ?
THis is the implementation. The user pressed C-b on a selction.
> It is *way* more complex
On Wednesday 03 December 2003 2:56 pm, John Levon wrote:
> On Wed, Dec 03, 2003 at 02:50:21PM +, Angus Leeming wrote:
> > >> > \normal{\foo{xxx\normal{nnn}xxx}}
> > >> > and
> > >> > \normal{\foo{xxx}nnn\foo{xxx}}
> > >>
> > >> Let \foo be \small and you will see a difference.
> > >
> > > How ?
On Wed, Dec 03, 2003 at 02:50:21PM +, Angus Leeming wrote:
> >> > \normal{\foo{xxx\normal{nnn}xxx}}
> >> > and
> >> > \normal{\foo{xxx}nnn\foo{xxx}}
> >> Let \foo be \small and you will see a difference.
> > How ?
>
> By trying it out and seeing what the difference is, perchance?
We're not t
John Levon wrote:
>> > \normal{\foo{xxx\normal{nnn}xxx}}
>> > and
>> > \normal{\foo{xxx}nnn\foo{xxx}}
>> Let \foo be \small and you will see a difference.
> How ?
By trying it out and seeing what the difference is, perchance?
Actually, \large and \small aren't the best choices here as they work
On Wed, Dec 03, 2003 at 03:13:33PM +0100, Andre Poenitz wrote:
> > \normal{\foo{xxx\normal{nnn}xxx}}
> >
> > and
> >
> > \normal{\foo{xxx}nnn\foo{xxx}}
>
> Let \foo be \small and you will see a difference.
How ?
> > But, nonetheless, a non-inset-based UI can still handle both via a
> > "Res
On Wed, Dec 03, 2003 at 01:57:36PM +, John Levon wrote:
> On Wed, Dec 03, 2003 at 02:51:23PM +0100, Andre Poenitz wrote:
>
> > This is a problem inherent to structured editing.
> >
> > \foo{xxx\normal{nnn}xxx} _is_ different from \foo{xxx}nnn\foo{xxx}.
>
> That depends upon the surrounding c
On Wed, Dec 03, 2003 at 02:51:23PM +0100, Andre Poenitz wrote:
> This is a problem inherent to structured editing.
>
> \foo{xxx\normal{nnn}xxx} _is_ different from \foo{xxx}nnn\foo{xxx}.
That depends upon the surrounding context. I do not see a difference
between:
\normal{\foo{xxx\normal{nnn}xx
On Wed, Dec 03, 2003 at 01:34:10PM +, John Levon wrote:
> On Wed, Dec 03, 2003 at 01:19:13PM +0100, Andre Poenitz wrote:
>
> > I guess we really need two operations here:
> > - insert nested style
> > - split current inset
>
> Please, please, let's not. We'd be introducing complex half-solu
On Wed, Dec 03, 2003 at 01:19:13PM +0100, Andre Poenitz wrote:
> I guess we really need two operations here:
> - insert nested style
> - split current inset
Please, please, let's not. We'd be introducing complex half-solutions
to a problem of our own making.
I'd much rather leave the current c
On Wed, Dec 03, 2003 at 01:41:23PM +0100, Andre Poenitz spake thusly:
> On Wed, Dec 03, 2003 at 12:40:16PM +0200, Martin Vermeer wrote:
> > On Wed, Dec 03, 2003 at 11:15:56AM +0100, Jean-Marc Lasgouttes spake thusly:
> >
> > > It is not renamable, but 'cutable' in chunks, as in the example whic
On Wed, Dec 03, 2003 at 12:50:19PM +, Angus Leeming wrote:
> Andre Poenitz wrote:
> > Could the two of you please have a look at the new
> > math_colorinset.[Ch] and tell me whether this would be sufficient
> > UI-wise?
>
> Which reminds me: wouldn't it me more elegant to implement this in
>
Andre Poenitz wrote:
> Could the two of you please have a look at the new
> math_colorinset.[Ch] and tell me whether this would be sufficient
> UI-wise?
Which reminds me: wouldn't it me more elegant to implement this in
'math-macro' style? Nonetheless, I do like it a lot better than in
its origi
On Wed, Dec 03, 2003 at 10:40:42AM +, Jose' Matos wrote:
> On Wednesday 03 December 2003 10:27, Martin Vermeer wrote:
> >
> > Well, if you want charstyles to be renameable, that can be done
> > straightforwardly but requires an inset dialog, cf Note/Branch. I
> > wonder if it's worth it.
>
>
On Wed, Dec 03, 2003 at 12:40:16PM +0200, Martin Vermeer wrote:
> On Wed, Dec 03, 2003 at 11:15:56AM +0100, Jean-Marc Lasgouttes spake thusly:
>
> > It is not renamable, but 'cutable' in chunks, as in the example which
> > was given.
> >
> > JMarc
>
> Ah. I misread you. No, I have no easy solut
On Wed, Dec 03, 2003 at 10:31:33AM +0100, Jean-Marc Lasgouttes wrote:
> > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> Martin> On Tue, Dec 02, 2003 at 09:35:42PM +0100, Helge Hafting spake
> Martin> thusly:
> >> If this sort of thing won't be possible, how will the alternative
>
On Tue, Dec 02, 2003 at 09:35:42PM +0100, Helge Hafting wrote:
> On Tue, Dec 02, 2003 at 02:28:26PM +, John Levon wrote:
> > On Tue, Dec 02, 2003 at 10:46:35AM +0100, Andre Poenitz wrote:
> >
> > > On Tue, Dec 02, 2003 at 10:53:26AM +0100, Helge Hafting wrote:
> > > > At least latex lets me ch
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> Ah. I misread you. No, I have no easy solution for that.
Martin> Cutting up an inset in this way will require some very tricky
Martin> coding I think, which I would be reluctant to consider. Count
Martin> that as a restriction of
On Wednesday 03 December 2003 10:27, Martin Vermeer wrote:
>
> Well, if you want charstyles to be renameable, that can be done
> straightforwardly but requires an inset dialog, cf Note/Branch. I
> wonder if it's worth it.
Now that you talk about it, it seems a reasonable thing to do. ;-)
Seri
On Wed, Dec 03, 2003 at 11:15:56AM +0100, Jean-Marc Lasgouttes spake thusly:
> It is not renamable, but 'cutable' in chunks, as in the example which
> was given.
>
> JMarc
Ah. I misread you. No, I have no easy solution for that. Cutting up an
inset in this way will require some very tricky codi
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> Well, if you want charstyles to be renameable, that can be
Martin> done straightforwardly but requires an inset dialog, cf
Martin> Note/Branch. I wonder if it's worth it.
It is not renamable, but 'cutable' in chunks, as in the e
On Wed, Dec 03, 2003 at 10:31:33AM +0100, Jean-Marc Lasgouttes spake thusly:
> > "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
>
> Martin> On Tue, Dec 02, 2003 at 09:35:42PM +0100, Helge Hafting spake
> Martin> thusly:
> >> If this sort of thing won't be possible, how will the alter
> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> On Tue, Dec 02, 2003 at 09:35:42PM +0100, Helge Hafting spake
Martin> thusly:
>> If this sort of thing won't be possible, how will the alternative
>> way be to edit? How will a user remove wrong markup, for this will
>> be necess
On Tue, Dec 02, 2003 at 09:35:42PM +0100, Helge Hafting wrote:
> That is not how I think about editing or styles.
Absolutely, this is my point.
> What do you consider the natural UI?
Select-and-apply. Like current physical styles work.
john
--
Khendon's Law:
If the same point is made twice
On Tue, Dec 02, 2003 at 09:35:42PM +0100, Helge Hafting spake thusly:
> If this sort of thing won't be possible, how will the alternative
> way be to edit? How will a user remove wrong markup, for
> this will be necessary at times.
>
> What do you consider the natural UI?
> Delete & rewrite t
On Tue, Dec 02, 2003 at 02:28:26PM +, John Levon wrote:
> On Tue, Dec 02, 2003 at 10:46:35AM +0100, Andre Poenitz wrote:
>
> > On Tue, Dec 02, 2003 at 10:53:26AM +0100, Helge Hafting wrote:
> > > At least latex lets me change from "\emph{This is marked}" to
> > > "\emph{This} is \emph{marked}"
On Tue, Dec 02, 2003 at 10:46:35AM +0100, Andre Poenitz wrote:
> On Tue, Dec 02, 2003 at 10:53:26AM +0100, Helge Hafting wrote:
> > At least latex lets me change from "\emph{This is marked}" to
> > "\emph{This} is \emph{marked}" without retyping any text. :-)
>
> This is implementable with 'boxes
On Tue, Dec 02, 2003 at 10:53:26AM +0100, Helge Hafting wrote:
> At least latex lets me change from "\emph{This is marked}" to
> "\emph{This} is \emph{marked}" without retyping any text. :-)
This is implementable with 'boxes in boxes', too.
Andre'
--
Those who desire to give up Freedom in order
Martin Vermeer wrote:
On Mon, Dec 01, 2003 at 12:20:33PM +0100, Helge Hafting spake thusly:
Of course code for deleting or "unapplying" an inset (e.g., backspace
in pos 0, like in math) could be created as well. But what you will
never be able to do in this paradigm is "unapplying" a charstyle f
On Mon, Dec 01, 2003 at 04:03:57PM +, Angus Leeming wrote:
> Andre Poenitz wrote:
>
> > On Mon, Dec 01, 2003 at 03:34:35PM +, John Levon wrote:
> >> On Mon, Dec 01, 2003 at 03:21:23PM +, Angus Leeming wrote:
> >>
> >> > > Easy peasy !
> >> >
> >> > and if the inset is drawn over two
Andre Poenitz wrote:
> On Mon, Dec 01, 2003 at 03:34:35PM +, John Levon wrote:
>> On Mon, Dec 01, 2003 at 03:21:23PM +, Angus Leeming wrote:
>>
>> > > Easy peasy !
>> >
>> > and if the inset is drawn over two or more lines, does each row
>> > have a '|--- noun -|' centered un
On Mon, Dec 01, 2003 at 03:34:35PM +, John Levon wrote:
> On Mon, Dec 01, 2003 at 03:21:23PM +, Angus Leeming wrote:
>
> > > Easy peasy !
> >
> > and if the inset is drawn over two or more lines, does each row have
> > a '|--- noun -|' centered underneath that chunk of inset?
On Mon, Dec 01, 2003 at 03:21:23PM +, Angus Leeming wrote:
> > Easy peasy !
>
> and if the inset is drawn over two or more lines, does each row have
> a '|--- noun -|' centered underneath that chunk of inset?
No.
OK, maybe, but it's easier if it's not. And you could easily do
John Levon wrote:
> On Mon, Dec 01, 2003 at 02:51:40PM +0100, Juergen Spitzmueller
> wrote:
>
>> > Would you feel like coding it up? I can assure you it's well
>> > beyond my ability right now.
>>
>> No, I don't feel like coding it up (it's well beyond my ability
>> too). And I
>
> Come come gu
On Mon, Dec 01, 2003 at 05:20:20PM +0200, Martin Vermeer wrote:
> > http://marc.theaimsgroup.com/?l=lyx-devel&m=104974730920332&w=2
>
> Yes, it all comes back (fine write-up BTW). So basically we have that
> now, except the user editable part, don't we? Only, it's an inset, not
> a named combinat
On Mon, Dec 01, 2003 at 01:19:46PM +, John Levon spake thusly:
> On Mon, Dec 01, 2003 at 03:23:42PM +0200, Martin Vermeer wrote:
>
> > Now I have to read that. Do you happen to have a link handy?
>
> http://marc.theaimsgroup.com/?l=lyx-devel&m=104974730920332&w=2
>
> john
Yes, it all come
On Mon, Dec 01, 2003 at 02:51:40PM +0100, Juergen Spitzmueller wrote:
> > Would you feel like coding it up? I can assure you it's well beyond my
> > ability right now.
>
> No, I don't feel like coding it up (it's well beyond my ability too). And I
Come come guys, of course it's not beyond eithe
Martin Vermeer wrote:
> Would you feel like coding it up? I can assure you it's well beyond my
> ability right now.
No, I don't feel like coding it up (it's well beyond my ability too). And I
didn't say that you have to do it. And of course your efforts are a huge step
into the right direction.
On Mon, Dec 01, 2003 at 08:49:49AM +0100, Juergen Spitzmueller spake thusly:
> I think the
> conglomerate-like solution (where the content description can be switched
> off) would fit very much to LyX's philosophy and is user friendly.
Would you feel like coding it up? I can assure you it's we
On Mon, Dec 01, 2003 at 12:20:33PM +0100, Helge Hafting spake thusly:
> > Of course code for deleting or "unapplying" an inset (e.g., backspace
> > in pos 0, like in math) could be created as well. But what you will
> > never be able to do in this paradigm is "unapplying" a charstyle for a
> > pi
On Mon, Dec 01, 2003 at 03:23:42PM +0200, Martin Vermeer wrote:
> Now I have to read that. Do you happen to have a link handy?
http://marc.theaimsgroup.com/?l=lyx-devel&m=104974730920332&w=2
john
--
Khendon's Law:
If the same point is made twice by the same person, the thread is over.
On Mon, Dec 01, 2003 at 12:27:41PM +, John Levon spake thusly:
> On Mon, Dec 01, 2003 at 09:18:06AM +0200, Martin Vermeer wrote:
>
> > > > Hmmm perhaps. Did I point out already that I don't really like physical
> > > > character attributes? :-)
> > >
> > > They shouldn't exist at all, but tha
On Mon, Dec 01, 2003 at 11:07:55AM +0100, Andre Poenitz spake thusly:
> >
> > As I wrote earlier, one-box inlined is implementable right now but
> > won't work right for current CVS because of the width stuff.
>
> What width stuff?
>
> Andre'
Try and insert an inlined ERT into a text, any text.
1 - 100 of 110 matches
Mail list logo
