show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Uwe Brauer


This is a long-standing request. You can find it on trac, if you
look. Unfortunately, it is not at all easy to do.

Well why not instead of displaying the latex source display
directly the LyX source and allow it to be edited and then to be
reloaded. Would such a solution be easier to implement?

Uwe 





Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Pavel Sanda
Uwe Brauer wrote:
 
 
 This is a long-standing request. You can find it on trac, if you
 look. Unfortunately, it is not at all easy to do.
 
 Well why not instead of displaying the latex source display
 directly the LyX source and allow it to be edited and then to be
 reloaded. Would such a solution be easier to implement?

i dont think so. parser of .lyx file supposes correct input, once
you allow user to directly change it (and thus making errs) you
will completely new error checking.

what looks much easier is to allow mutating math environment into ERT
and back.

pavel


Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Vincent van Ravesteijn
 Well why not instead of displaying the latex source display
 directly the LyX source and allow it to be edited and then to be
 reloaded. Would such a solution be easier to implement?


Why would anyone want to edit the LyX source (in LyX) ?

Vincent


Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Vincent van Ravesteijn
 what looks much easier is to allow mutating math environment into ERT
 and back.

 pavel


This is already possible. It needs some copy-pasting but it works. I
once implemented this, but then disregarded it because it was
essentially already possible.

Vincent


Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Pavel Sanda
Vincent van Ravesteijn wrote:
  what looks much easier is to allow mutating math environment into ERT
  and back.
 
  pavel
 
 
 This is already possible. It needs some copy-pasting but it works. I
 once implemented this, but then disregarded it because it was
 essentially already possible.

i know, but that needs some understanding how our math insets works and its
uncomfortable to do. i was talking about something like Switch to ERT/Math
item in context menu so even normal users get the idea...

pavel


Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Guenter Milde
On 2010-06-07, Pavel Sanda wrote:
 Vincent van Ravesteijn wrote:
  what looks much easier is to allow mutating math environment into ERT
  and back.
 
  pavel
 

 This is already possible. It needs some copy-pasting but it works. I
 once implemented this, but then disregarded it because it was
 essentially already possible.

 i know, but that needs some understanding how our math insets works and its
 uncomfortable to do.

It is quite simple and in line with other insets:

* Backspace at the first position in the inset converts it to normal
  text (in this case LaTeX code (without beeing marked as ERT))
  
Now edit ...
  
* Highlight and Ctrl-M converts it back to a Math inset.

If all you want is simple editing, there is no urgent need to have it as ERT
in the meantime.

 i was talking about something like Switch to ERT/Math
 item in context menu so even normal users get the idea...

OK, I see 2 advantages:

1. no need to place the cursor or highlight

2. you can compile while the Math is editible (as ERT)

that might offset the cost of added complexity.

Günter




Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Pavel Sanda
Guenter Milde wrote:
 * Backspace at the first position in the inset converts it to normal
   text (in this case LaTeX code (without beeing marked as ERT))

not in math inset.

 OK, I see 2 advantages:
 
 1. no need to place the cursor or highlight

thats what i call uncomfortable.

pavel


Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Vincent van Ravesteijn
On Mon, Jun 7, 2010 at 3:08 PM, Pavel Sanda sa...@lyx.org wrote:
 Guenter Milde wrote:
 * Backspace at the first position in the inset converts it to normal
   text (in this case LaTeX code (without beeing marked as ERT))

 not in math inset.

 OK, I see 2 advantages:

 1. no need to place the cursor or highlight

 thats what i call uncomfortable.

 pavel


If you're such a power-user that you use it so often that this becomes
uncomfortable, you probably should start to learn how to use the math
inset to do the things you want.

Vincent


Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Pavel Sanda
Vincent van Ravesteijn wrote:
 If you're such a power-user that you use it so often that this becomes
 uncomfortable, you probably should start to learn how to use the math
 inset to do the things you want.

frankly i dont use it at all and the main point was about discoverability
for normal users who ask for this again and again.

pavel


Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Guenter Milde
On 2010-06-07, Pavel Sanda wrote:
 Guenter Milde wrote:
 * Backspace at the first position in the inset converts it to normal
   text (in this case LaTeX code (without beeing marked as ERT))

 not in math inset.

Sorry, then this is a feature request.

 OK, I see 2 advantages:

 1. no need to place the cursor or highlight

 thats what i call uncomfortable.

Agreed.

Günter



show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Uwe Brauer
   >> 
   >> 
   > This is a long-standing request. You can find it on trac, if you
   > look. Unfortunately, it is not at all easy to do.

Well why not instead of displaying the "latex source" display
directly the LyX source and allow it to be edited and then to be
reloaded. Would such a solution be easier to implement?

Uwe 





Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Pavel Sanda
Uwe Brauer wrote:
>>> 
>>> 
>> This is a long-standing request. You can find it on trac, if you
>> look. Unfortunately, it is not at all easy to do.
> 
> Well why not instead of displaying the "latex source" display
> directly the LyX source and allow it to be edited and then to be
> reloaded. Would such a solution be easier to implement?

i dont think so. parser of .lyx file supposes correct input, once
you allow user to directly change it (and thus making errs) you
will completely new error checking.

what looks much easier is to allow mutating math environment into ERT
and back.

pavel


Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Vincent van Ravesteijn
> Well why not instead of displaying the "latex source" display
> directly the LyX source and allow it to be edited and then to be
> reloaded. Would such a solution be easier to implement?
>

Why would anyone want to edit the LyX source (in LyX) ?

Vincent


Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Vincent van Ravesteijn
> what looks much easier is to allow mutating math environment into ERT
> and back.
>
> pavel
>

This is already possible. It needs some copy-pasting but it works. I
once implemented this, but then disregarded it because it was
essentially already possible.

Vincent


Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Pavel Sanda
Vincent van Ravesteijn wrote:
> > what looks much easier is to allow mutating math environment into ERT
> > and back.
> >
> > pavel
> >
> 
> This is already possible. It needs some copy-pasting but it works. I
> once implemented this, but then disregarded it because it was
> essentially already possible.

i know, but that needs some understanding how our math insets works and its
uncomfortable to do. i was talking about something like "Switch to ERT/Math"
item in context menu so even normal users get the idea...

pavel


Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Guenter Milde
On 2010-06-07, Pavel Sanda wrote:
> Vincent van Ravesteijn wrote:
>> > what looks much easier is to allow mutating math environment into ERT
>> > and back.
>> >
>> > pavel
>> >

>> This is already possible. It needs some copy-pasting but it works. I
>> once implemented this, but then disregarded it because it was
>> essentially already possible.

> i know, but that needs some understanding how our math insets works and its
> uncomfortable to do.

It is quite simple and in line with other insets:

* Backspace at the first position in the inset converts it to normal
  text (in this case LaTeX code (without beeing marked as ERT))
  
Now edit ...
  
* Highlight and Ctrl-M converts it back to a Math inset.

If all you want is simple editing, there is no urgent need to have it as ERT
in the meantime.

> i was talking about something like "Switch to ERT/Math"
> item in context menu so even normal users get the idea...

OK, I see 2 advantages:

1. no need to place the cursor or highlight

2. you can compile while the Math is editible (as ERT)

that might offset the cost of added complexity.

Günter




Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Pavel Sanda
Guenter Milde wrote:
> * Backspace at the first position in the inset converts it to normal
>   text (in this case LaTeX code (without beeing marked as ERT))

not in math inset.

> OK, I see 2 advantages:
> 
> 1. no need to place the cursor or highlight

thats what i call uncomfortable.

pavel


Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Vincent van Ravesteijn
On Mon, Jun 7, 2010 at 3:08 PM, Pavel Sanda  wrote:
> Guenter Milde wrote:
>> * Backspace at the first position in the inset converts it to normal
>>   text (in this case LaTeX code (without beeing marked as ERT))
>
> not in math inset.
>
>> OK, I see 2 advantages:
>>
>> 1. no need to place the cursor or highlight
>
> thats what i call uncomfortable.
>
> pavel
>

If you're such a power-user that you use it so often that this becomes
uncomfortable, you probably should start to learn how to use the math
inset to do the things you want.

Vincent


Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Pavel Sanda
Vincent van Ravesteijn wrote:
> If you're such a power-user that you use it so often that this becomes
> uncomfortable, you probably should start to learn how to use the math
> inset to do the things you want.

frankly i dont use it at all and the main point was about discoverability
for normal users who ask for this again and again.

pavel


Re: show the lyx code (was: feature proposal: show latex code: allow to manipulate the latex code: reveal code)

2010-06-07 Thread Guenter Milde
On 2010-06-07, Pavel Sanda wrote:
> Guenter Milde wrote:
>> * Backspace at the first position in the inset converts it to normal
>>   text (in this case LaTeX code (without beeing marked as ERT))

> not in math inset.

Sorry, then this is a feature request.

>> OK, I see 2 advantages:

>> 1. no need to place the cursor or highlight

> thats what i call uncomfortable.

Agreed.

Günter



feature proposal: show latex code: allow to manipulate the latex code: reveal code

2010-05-28 Thread Uwe Brauer
Hello

One of the things I like in LyX is that the source code is
shown. It is a little like reveal code in wordperfect, which
I recently discovered.


However sometimes lyx is doing things I don't want
like inserting  a new line. 

Would it be possible to manipulate directly the source code
window, that would to obtain even better control about the
final document.


Uwe Brauer 



Re: feature proposal: show latex code: allow to manipulate the latex code: reveal code

2010-05-28 Thread Richard Heck

On 05/28/2010 06:13 AM, Uwe Brauer wrote:

Hello

One of the things I like in LyX is that the source code is
shown. It is a little like reveal code in wordperfect, which
I recently discovered.

However sometimes lyx is doing things I don't want
like inserting  a new line.

Would it be possible to manipulate directly the source code
window, that would to obtain even better control about the
final document.

   
This is a long-standing request. You can find it on trac, if you look. 
Unfortunately, it is not at all easy to do.


Richard



feature proposal: show latex code: allow to manipulate the latex code: reveal code

2010-05-28 Thread Uwe Brauer
Hello

One of the things I like in LyX is that the source code is
shown. It is a little like reveal code in wordperfect, which
I recently discovered.


However sometimes lyx is doing things I don't want
like inserting  a new line. 

Would it be possible to manipulate directly the source code
window, that would to obtain even better control about the
final document.


Uwe Brauer 



Re: feature proposal: show latex code: allow to manipulate the latex code: reveal code

2010-05-28 Thread Richard Heck

On 05/28/2010 06:13 AM, Uwe Brauer wrote:

Hello

One of the things I like in LyX is that the source code is
shown. It is a little like reveal code in wordperfect, which
I recently discovered.

However sometimes lyx is doing things I don't want
like inserting  a new line.

Would it be possible to manipulate directly the source code
window, that would to obtain even better control about the
final document.

   
This is a long-standing request. You can find it on trac, if you look. 
Unfortunately, it is not at all easy to do.


Richard