Re: Ninja mode

2010-02-25 Thread Manveru
2010/2/22 Jose Quesada ques...@gmail.com

 +1, definitely the most important thing for me is good latex integration.
 That use case (cols use plain latex, you use lyx) is very common

 But LyX was not designed to reverse engineer LaTeX documents, so lot of
sophisticated solutions are problematic for LyX import.

-- 
Manveru
jabber: manv...@manveru.pl
gg: 1624001
  http://www.manveru.pl


Re: Ninja mode

2010-02-25 Thread Niko Schwarz
Well, yea. So what? It doesn't need to work all the time. If the Lyx
compile button doesn't work anymore, but the make script still runs,
that's good enough for me.

By the way, the lyx importer is great. I imported several docuents
which I consider quite complex,  and sometimes after a few
adaptations, often right away, they compile in lyx. Export is great,
too. So what's the problem? :)

Niko

On Thu, Feb 25, 2010 at 1:16 PM, Manveru manv...@manveru.pl wrote:


 2010/2/22 Jose Quesada ques...@gmail.com

 +1, definitely the most important thing for me is good latex integration.
 That use case (cols use plain latex, you use lyx) is very common

 But LyX was not designed to reverse engineer LaTeX documents, so lot of
 sophisticated solutions are problematic for LyX import.

 --
 Manveru
 jabber: manv...@manveru.pl
     gg: 1624001
   http://www.manveru.pl




-- 
http://scg.unibe.ch/staff/Schwarz
twitter.com/nes1983
Tel: +41 076 235 8683


Re: Ninja mode

2010-02-25 Thread Manveru
2010/2/22 Jose Quesada ques...@gmail.com

 +1, definitely the most important thing for me is good latex integration.
 That use case (cols use plain latex, you use lyx) is very common

 But LyX was not designed to reverse engineer LaTeX documents, so lot of
sophisticated solutions are problematic for LyX import.

-- 
Manveru
jabber: manv...@manveru.pl
gg: 1624001
  http://www.manveru.pl


Re: Ninja mode

2010-02-25 Thread Niko Schwarz
Well, yea. So what? It doesn't need to work all the time. If the Lyx
compile button doesn't work anymore, but the make script still runs,
that's good enough for me.

By the way, the lyx importer is great. I imported several docuents
which I consider quite complex,  and sometimes after a few
adaptations, often right away, they compile in lyx. Export is great,
too. So what's the problem? :)

Niko

On Thu, Feb 25, 2010 at 1:16 PM, Manveru manv...@manveru.pl wrote:


 2010/2/22 Jose Quesada ques...@gmail.com

 +1, definitely the most important thing for me is good latex integration.
 That use case (cols use plain latex, you use lyx) is very common

 But LyX was not designed to reverse engineer LaTeX documents, so lot of
 sophisticated solutions are problematic for LyX import.

 --
 Manveru
 jabber: manv...@manveru.pl
     gg: 1624001
   http://www.manveru.pl




-- 
http://scg.unibe.ch/staff/Schwarz
twitter.com/nes1983
Tel: +41 076 235 8683


Re: Ninja mode

2010-02-25 Thread Manveru
2010/2/22 Jose Quesada 

> +1, definitely the most important thing for me is good latex integration.
> That use case (cols use plain latex, you use lyx) is very common
>
> But LyX was not designed to "reverse engineer" LaTeX documents, so lot of
sophisticated solutions are problematic for LyX import.

-- 
Manveru
jabber: manv...@manveru.pl
gg: 1624001
  http://www.manveru.pl


Re: Ninja mode

2010-02-25 Thread Niko Schwarz
Well, yea. So what? It doesn't need to work all the time. If the Lyx
compile button doesn't work anymore, but the make script still runs,
that's good enough for me.

By the way, the lyx importer is great. I imported several docuents
which I consider quite complex,  and sometimes after a few
adaptations, often right away, they compile in lyx. Export is great,
too. So what's the problem? :)

Niko

On Thu, Feb 25, 2010 at 1:16 PM, Manveru  wrote:
>
>
> 2010/2/22 Jose Quesada 
>>
>> +1, definitely the most important thing for me is good latex integration.
>> That use case (cols use plain latex, you use lyx) is very common
>>
> But LyX was not designed to "reverse engineer" LaTeX documents, so lot of
> sophisticated solutions are problematic for LyX import.
>
> --
> Manveru
> jabber: manv...@manveru.pl
>     gg: 1624001
>   http://www.manveru.pl
>



-- 
http://scg.unibe.ch/staff/Schwarz
twitter.com/nes1983
Tel: +41 076 235 8683


Ninja mode

2010-02-22 Thread Niko Schwarz
Hi y'all,

what helped popularize git in my research group was undoubtably to
ninja into git using git-svn, that is: people like I could switch from
svn to git, and it wouldn't force others to change their workflows.

I find it quite a pity that lyx has no ninja mode. That is: a mode of
lyx that would allow me to change a versioned latex document from
within lyx, which stores its meta information in a separate .lyxextra
file, but exports itself constantly to the shared .tex file, such that
the .tex file and lyx are always in sync.

I know I could import and export manually all the time, and
conceptually, that would (seriously!) be good enough for me. But it's
too much pressing buttons  to be productive. Does anyone do it that
way?

How do you ninja lyx into your research groups?

Cheers,

Niko

-- 
twitter.com/nes1983


Re: Ninja mode

2010-02-22 Thread Thomas Steffen
On Mon, Feb 22, 2010 at 8:10 AM, Niko Schwarz
niko.schw...@googlemail.comwrote:

 How do you ninja lyx into your research groups?


I agree this is a problem. Some lossless round trip collaboration between
LyX and pure LaTeX would be very useful. I tried doing this with export -
import - merge, but it did not produce the best results.

Maybe the issue to address is that export - import is a very loss operation,
and it should not be. Of course certain parts are not required in the export
(LyX macros, disabled branches, LyX comments, and even LyX styles). But they
could be hidden in comments and restored during the import.

But I am sure there is more than one solution to this problem.

Regards,
Thomas


Re: Ninja mode

2010-02-22 Thread Jose Quesada
+1, definitely the most important thing for me is good latex integration.
That use case (cols use plain latex, you use lyx) is very common

On Mon, Feb 22, 2010 at 10:41 PM, Thomas Steffen 
steffen.list.acco...@gmail.com wrote:

 On Mon, Feb 22, 2010 at 8:10 AM, Niko Schwarz
 niko.schw...@googlemail.comwrote:

  How do you ninja lyx into your research groups?
 

 I agree this is a problem. Some lossless round trip collaboration between
 LyX and pure LaTeX would be very useful. I tried doing this with export -
 import - merge, but it did not produce the best results.

 Maybe the issue to address is that export - import is a very loss
 operation,
 and it should not be. Of course certain parts are not required in the
 export
 (LyX macros, disabled branches, LyX comments, and even LyX styles). But
 they
 could be hidden in comments and restored during the import.

 But I am sure there is more than one solution to this problem.

 Regards,
 Thomas




-- 
Best,
-Jose

Jose Quesada, PhD.
Max Planck Institute,
Center for Adaptive Behavior and Cognition,
Berlin
http://www.josequesada.name/
http://twitter.com/Quesada


Ninja mode

2010-02-22 Thread Niko Schwarz
Hi y'all,

what helped popularize git in my research group was undoubtably to
ninja into git using git-svn, that is: people like I could switch from
svn to git, and it wouldn't force others to change their workflows.

I find it quite a pity that lyx has no ninja mode. That is: a mode of
lyx that would allow me to change a versioned latex document from
within lyx, which stores its meta information in a separate .lyxextra
file, but exports itself constantly to the shared .tex file, such that
the .tex file and lyx are always in sync.

I know I could import and export manually all the time, and
conceptually, that would (seriously!) be good enough for me. But it's
too much pressing buttons  to be productive. Does anyone do it that
way?

How do you ninja lyx into your research groups?

Cheers,

Niko

-- 
twitter.com/nes1983


Re: Ninja mode

2010-02-22 Thread Thomas Steffen
On Mon, Feb 22, 2010 at 8:10 AM, Niko Schwarz
niko.schw...@googlemail.comwrote:

 How do you ninja lyx into your research groups?


I agree this is a problem. Some lossless round trip collaboration between
LyX and pure LaTeX would be very useful. I tried doing this with export -
import - merge, but it did not produce the best results.

Maybe the issue to address is that export - import is a very loss operation,
and it should not be. Of course certain parts are not required in the export
(LyX macros, disabled branches, LyX comments, and even LyX styles). But they
could be hidden in comments and restored during the import.

But I am sure there is more than one solution to this problem.

Regards,
Thomas


Re: Ninja mode

2010-02-22 Thread Jose Quesada
+1, definitely the most important thing for me is good latex integration.
That use case (cols use plain latex, you use lyx) is very common

On Mon, Feb 22, 2010 at 10:41 PM, Thomas Steffen 
steffen.list.acco...@gmail.com wrote:

 On Mon, Feb 22, 2010 at 8:10 AM, Niko Schwarz
 niko.schw...@googlemail.comwrote:

  How do you ninja lyx into your research groups?
 

 I agree this is a problem. Some lossless round trip collaboration between
 LyX and pure LaTeX would be very useful. I tried doing this with export -
 import - merge, but it did not produce the best results.

 Maybe the issue to address is that export - import is a very loss
 operation,
 and it should not be. Of course certain parts are not required in the
 export
 (LyX macros, disabled branches, LyX comments, and even LyX styles). But
 they
 could be hidden in comments and restored during the import.

 But I am sure there is more than one solution to this problem.

 Regards,
 Thomas




-- 
Best,
-Jose

Jose Quesada, PhD.
Max Planck Institute,
Center for Adaptive Behavior and Cognition,
Berlin
http://www.josequesada.name/
http://twitter.com/Quesada


Ninja mode

2010-02-22 Thread Niko Schwarz
Hi y'all,

what helped popularize git in my research group was undoubtably to
ninja into git using git-svn, that is: people like I could switch from
svn to git, and it wouldn't force others to change their workflows.

I find it quite a pity that lyx has no ninja mode. That is: a mode of
lyx that would allow me to change a versioned latex document from
within lyx, which stores its meta information in a separate .lyxextra
file, but exports itself constantly to the shared .tex file, such that
the .tex file and lyx are always in sync.

I know I could import and export manually all the time, and
conceptually, that would (seriously!) be good enough for me. But it's
too much pressing buttons  to be productive. Does anyone do it that
way?

How do you ninja lyx into your research groups?

Cheers,

Niko

-- 
twitter.com/nes1983


Re: Ninja mode

2010-02-22 Thread Thomas Steffen
On Mon, Feb 22, 2010 at 8:10 AM, Niko Schwarz
wrote:

> How do you ninja lyx into your research groups?
>

I agree this is a problem. Some lossless round trip collaboration between
LyX and pure LaTeX would be very useful. I tried doing this with export -
import - merge, but it did not produce the best results.

Maybe the issue to address is that export - import is a very loss operation,
and it should not be. Of course certain parts are not required in the export
(LyX macros, disabled branches, LyX comments, and even LyX styles). But they
could be hidden in comments and restored during the import.

But I am sure there is more than one solution to this problem.

Regards,
Thomas


Re: Ninja mode

2010-02-22 Thread Jose Quesada
+1, definitely the most important thing for me is good latex integration.
That use case (cols use plain latex, you use lyx) is very common

On Mon, Feb 22, 2010 at 10:41 PM, Thomas Steffen <
steffen.list.acco...@gmail.com> wrote:

> On Mon, Feb 22, 2010 at 8:10 AM, Niko Schwarz
> wrote:
>
> > How do you ninja lyx into your research groups?
> >
>
> I agree this is a problem. Some lossless round trip collaboration between
> LyX and pure LaTeX would be very useful. I tried doing this with export -
> import - merge, but it did not produce the best results.
>
> Maybe the issue to address is that export - import is a very loss
> operation,
> and it should not be. Of course certain parts are not required in the
> export
> (LyX macros, disabled branches, LyX comments, and even LyX styles). But
> they
> could be hidden in comments and restored during the import.
>
> But I am sure there is more than one solution to this problem.
>
> Regards,
> Thomas
>



-- 
Best,
-Jose

Jose Quesada, PhD.
Max Planck Institute,
Center for Adaptive Behavior and Cognition,
Berlin
http://www.josequesada.name/
http://twitter.com/Quesada