"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:

| On Mon, Jul 09, 2001 at 09:45:18AM +0200, Lars Gullik Bjønnes wrote:
| > "Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
| > 
| > | On Mon, Jul 09, 2001 at 09:34:22AM +0200, Lars Gullik Bjønnes wrote:
| > | > | Great. How about the Scraps that use TeX mode? Where's the solution
| > | > | for that?
| > | > 
| > | > I am thinking about it...
| > | > 
| > | > - easiest solution is to map all scrap envirs to '666', but that is not
| > | > a nice solution.
| > | >  
| > | > - second option is to enhance the layout format a bit so that scrap
| > | > automatically inserts a '666' box with a 'scrap' label.
| > | 
| > | I like the second solution better.
| > 
| > Ok, so then InsetERT need to be able to take one additional paramters:
| > the label name.
| > In the layout format we need to be able to give a lfun to run when
| > selected (you won't easily be able to move away from this envir
| > though).
| > 
| > "ert-insert scrap" 
| > 
| > and when called from the layout dropdown the 'scrap' will be in a
| > paragraph of its own. (the surrounding layout will be standard)
| 
| What do you mean? I won't be able to just mark a paragraph as a scrap?

exactly.
 
| > Also in the lyx file the 'scrap' will not be stored as a layout but as
| > an inset.
| 
| Okay... This last point is going to break lots of literate code.

Why? How can it break any existing literate code?
 
| I think we should make 1.2.0 read old lyx code (with scrap layouts) and write
| new code (with scrap insets).

sure, of course we will.
when reading old code, everything that uses the old tex-mode will
automatically be rewritten during the parsing to the new style.

-- 
        Lgb

Reply via email to