Re: API for backends unification

2003-11-03 Thread Andre Poenitz
On Mon, Nov 03, 2003 at 02:25:38PM +, Jose' Matos wrote: > On Monday 03 November 2003 13:02, Andre Poenitz wrote: > > On Fri, Oct 31, 2003 at 04:21:55PM +, Jose' Matos wrote: > > > The attached patch unifies the API used for the different backends in > > > insets. > > > > > > In inset.h we

Re: API for backends unification

2003-11-03 Thread Jose' Matos
On Monday 03 November 2003 13:02, Andre Poenitz wrote: > On Fri, Oct 31, 2003 at 04:21:55PM +, Jose' Matos wrote: > > The attached patch unifies the API used for the different backends in > > insets. > > > > In inset.h we have: > > > > int latex(Buffer const &, std::ostream &,LatexRunParams con

Re: API for backends unification

2003-11-03 Thread Andre Poenitz
On Mon, Nov 03, 2003 at 02:04:33PM +0100, Lars Gullik Bjønnes wrote: > Andre Poenitz <[EMAIL PROTECTED]> writes: > > | The approach is fine with me. And as this is more or less the same > | scheme as used in src/m* this would be a major step forward on inset > | unification. > > I must admit that

Re: API for backends unification

2003-11-03 Thread Lars Gullik Bjønnes
Andre Poenitz <[EMAIL PROTECTED]> writes: | The approach is fine with me. And as this is more or less the same | scheme as used in src/m* this would be a major step forward on inset | unification. I must admit that I am not a fan of hiding _all_ arguments inside a huge object (a we-might-need-thi

Re: API for backends unification

2003-11-03 Thread Andre Poenitz
On Fri, Oct 31, 2003 at 04:59:27PM +, Angus Leeming wrote: > Jose' Matos wrote: > > One  of  the  goals  of  this  work  is  to  simply  the  > > creation of  new backends.  It would be cool if LyX was > > able to produce its own man page without any external > > help. The same applies to htm

Re: API for backends unification

2003-11-03 Thread Andre Poenitz
On Fri, Oct 31, 2003 at 04:21:55PM +, Jose' Matos wrote: > The attached patch unifies the API used for the different backends in insets. > > In inset.h we have: > > int latex(Buffer const &, std::ostream &,LatexRunParams const &); > int ascii(Buffer const &, std::ostream &,LatexRunParams cons

Re: API for backends unification

2003-10-31 Thread Jose' Matos
On Friday 31 October 2003 16:56, Jean-Marc Lasgouttes wrote: > > Jose'> Jean-Marc what do you think? > > This is fine, as is OutputParams Ok, OutputParams it will be. > Jose'> And now that we are discussing name is ascii acurate? > Jose'> Shouldn't it be text? > > Yes, text or plaintext wou

Re: API for backends unification

2003-10-31 Thread Jose' Matos
On Friday 31 October 2003 16:59, Angus Leeming wrote: > > Hmmm. I thought that one of the goals of an LyX xml file format was > to be able to move all these manipulators out of LyX and into > stand-alone programs lyx2latex, lyx2ascii, lyx2xhtml, lyx2man etc, > etc, etc. That will be possible, s

Re: API for backends unification

2003-10-31 Thread Angus Leeming
Jose' Matos wrote: > * create one for each backend: > output_latex.[Ch] > output_text.[Ch] > output_linuxdoc.[Ch] > output_docbook.[Ch] Yes please. -- Angus

Re: API for backends unification

2003-10-31 Thread Jean-Marc Lasgouttes
> "Jose'" == Jose' Matos <[EMAIL PROTECTED]> writes: >> You should rename LatexRunParams though. ExportParams? Jose'> Jean-Marc what do you think? This is fine, as is OutputParams Jose'> And now that we are discussing name is ascii acurate? Jose'> Shouldn't it be text? Yes, text or pla

Re: API for backends unification

2003-10-31 Thread Angus Leeming
Jose' Matos wrote: > One  of  the  goals  of  this  work  is  to  simply  the  > creation of  new backends.  It would be cool if LyX was > able to produce its own man page without any external > help. The same applies to html and xhtml + mathml. Hmmm. I thought that one of the goals of an LyX xm

Re: API for backends unification

2003-10-31 Thread Jose' Matos
On Friday 31 October 2003 16:35, Angus Leeming wrote: > Jose' Matos wrote: > > > Comments? > > Good! Especially the getting rid of 'nice'. Could you see if you can > can constify the non-const buffer member functions that alter 'nice' > too. Maybe in a separate iteration of course... After thi

Re: API for backends unification

2003-10-31 Thread Lars Gullik Bjønnes
Angus Leeming <[EMAIL PROTECTED]> writes: | Good! Especially the getting rid of 'nice'. Could you see if you can | can constify the non-const buffer member functions that alter 'nice' | too. Maybe in a separate iteration of course... > | You should rename LatexRunParams though. ExportParams? yo

Re: API for backends unification

2003-10-31 Thread Jose' Matos
On Friday 31 October 2003 16:28, Jean-Marc Lasgouttes wrote: > > "Jose'" == Jose' Matos <[EMAIL PROTECTED]> writes: > > Jose'> The attached patch unifies the API used for the different > Jose'> backends in insets. In inset.h we have: > > This looks good. Of course, the name LatexRunParams looks

Re: API for backends unification

2003-10-31 Thread Lars Gullik Bjønnes
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: >> "Jose'" == Jose' Matos <[EMAIL PROTECTED]> writes: > | Jose'> The attached patch unifies the API used for the different | Jose'> backends in insets. In inset.h we have: > | This looks good. Of course, the name LatexRunParams looks stupid now

Re: API for backends unification

2003-10-31 Thread Angus Leeming
Jose' Matos wrote: > The attached patch unifies the API used for the different backends > in insets. > > In inset.h we have: > > int latex(Buffer const &, std::ostream &,LatexRunParams const &); > int ascii(Buffer const &, std::ostream &,LatexRunParams const &); > int linuxdoc(Buffer const &, st

Re: API for backends unification

2003-10-31 Thread Jean-Marc Lasgouttes
> "Jose'" == Jose' Matos <[EMAIL PROTECTED]> writes: Jose'> The attached patch unifies the API used for the different Jose'> backends in insets. In inset.h we have: This looks good. Of course, the name LatexRunParams looks stupid now (because it is not for latex and not related to running eit

API for backends unification

2003-10-31 Thread Jose' Matos
The attached patch unifies the API used for the different backends in insets. In inset.h we have: int latex(Buffer const &, std::ostream &,LatexRunParams const &); int ascii(Buffer const &, std::ostream &,LatexRunParams const &); int linuxdoc(Buffer const &, std::ostream &,LatexRunParams const &)