InsetOld::hasParagraphs->InsetOld::numParagraphs

2003-10-31 Thread Alfredo Braunstein
Can I do it? hasParagraphs is never used in the code, and we need numParagraphs for having PosIterator/Cursor::operator-- PS: should I drop PosIterator and try to make Cursor::operator++/-- operative? Alfredo

Re: InsetOld::hasParagraphs->InsetOld::numParagraphs

2003-10-31 Thread Angus Leeming
Alfredo Braunstein wrote: > Can I do it? > > hasParagraphs is never used in the code, and we need numParagraphs > for having PosIterator/Cursor::operator-- Who could possibly object? Go for it. > PS: should I drop PosIterator and try to make Cursor::operator++/-- > operative? Why not make PosIt

Re: InsetOld::hasParagraphs->InsetOld::numParagraphs

2003-10-31 Thread Alfredo Braunstein
Angus Leeming wrote: >> hasParagraphs is never used in the code, and we need numParagraphs >> for having PosIterator/Cursor::operator-- > > Who could possibly object? Go for it. The ways of objections are misterious... ;-) I'll do it then. >> PS: should I drop PosIterator and try to make Cursor

Re: InsetOld::hasParagraphs->InsetOld::numParagraphs

2003-10-31 Thread Angus Leeming
Alfredo Braunstein wrote: > [Btw, it should be super easy to implement regex searches right? It > [would > suffice to implement operator* that gives pit->getChar(pos) if pos < > size and some '\n' if pos == size. In that way one could also search > for newlines etc. Methink.] Great idea. ... it w

Re: new layout files for g-brief2

2003-10-31 Thread Felix Kurth
Sorry, the apache died. Please try again. Felix Jean-Marc Lasgouttes wrote: >> "Felix" == Felix Kurth <[EMAIL PROTECTED]> writes: > > Felix> Hello I just created layout files and examples for the g-brief2 > Felix> latex style. This style is the successor of g-brief. Its more > Felix> flexi

compier warning question

2003-10-31 Thread Angus Leeming
If I were to compile this function with -DNDEBUG, I'd get a compiler warning about 'control reaches the end of a non-void function'. It seems ugly to shove a 'return arbitrary_value;' after the assert. Is there Another Way? int const store[] = { 1, 2, 3, 4, 5 }; int const store_size = sizeof(s

Re: compier warning question

2003-10-31 Thread John Levon
On Fri, Oct 31, 2003 at 03:24:10PM +, Angus Leeming wrote: > If I were to compile this function with -DNDEBUG, I'd get a compiler > warning about 'control reaches the end of a non-void function'. It > seems ugly to shove a 'return arbitrary_value;' after the assert. Is > there Another Way?

Re: new layout files for g-brief2

2003-10-31 Thread Jean-Marc Lasgouttes
> "Felix" == Felix Kurth <[EMAIL PROTECTED]> writes: Felix> Sorry, the apache died. Please try again. Thanks. Could you provide a small text for LaTeXConfig.lyx.in (see Help>LaTeX Configuration) explaining the difference between the two classes? If g-brief is the obsolete version, should it

Re: PosIterator - design pattern discussion

2003-10-31 Thread Kuba Ober
On Thursday 30 October 2003 01:06 pm, Angus Leeming wrote: > Kuba Ober wrote: > > On Thursday 30 October 2003 11:26 am, Alfredo Braunstein wrote: > >> Angus Leeming wrote: > >> > Note that multiple BufferViews implies multiple Cursors. I'm sure > >> > that I would be pissed off if I replaced "brown

Re: compier warning question

2003-10-31 Thread Lars Gullik Bjønnes
Angus Leeming <[EMAIL PROTECTED]> writes: | If I were to compile this function with -DNDEBUG, I'd get a compiler | warning about 'control reaches the end of a non-void function'. It | seems ugly to shove a 'return arbitrary_value;' after the assert. Is | there Another Way? > > | int const store

Re: PosIterator - design pattern discussion

2003-10-31 Thread Lars Gullik Bjønnes
Kuba Ober <[EMAIL PROTECTED]> writes: | Why not make the tree structure explicit, with leaf and node base | classes from which insets can derive? Wouldn't it make life much | simpler? Moving towards that... slowly... -- Lgb

Re: PosIterator - design pattern discussion

2003-10-31 Thread Kuba Ober
> >> It's pseudo-rubbish in that the lyx data structure is a tree > >> in-concept only. It's actually a std::list where each > >> Paragraph contains a std::vector and an InsetList. Insets are > >> identified in the std::vector by chars with value > >> 'META_INSET' and a Buffer::inset_iterator class

Re: compier warning question

2003-10-31 Thread Angus Leeming
John Levon wrote: > On Fri, Oct 31, 2003 at 03:24:10PM +, Angus Leeming wrote: > >> If I were to compile this function with -DNDEBUG, I'd get a >> compiler warning about 'control reaches the end of a non-void >> function'. It seems ugly to shove a 'return arbitrary_value;' after >> the assert

Re: Stlport+gcc-2.96 builds but does not run

2003-10-31 Thread Lars Gullik Bjønnes
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | Index: src/debug.C | === | RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/debug.C,v | retrieving revision 1.39 | diff -u -p -r1.39 debug.C | --- src/debug.C 6 Oct 2003 15:42:13

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 &)

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

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 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 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
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: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 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 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: > * 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 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: Stlport+gcc-2.96 builds but does not run

2003-10-31 Thread Martin Vermeer
On Thu, Oct 30, 2003 at 04:22:50PM +0100, Jean-Marc Lasgouttes spake thusly: > > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: > Lars> Ok, try this: > > Lars> remove the rdbuf initialization from debug.C and put it in > Lars> main.C instead: > > This works. Great! I was w

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

[patch] more PosIterator

2003-10-31 Thread Alfredo Braunstein
Not tested througly, but seems to work normally on standard operations. (note that almost all the + are in the new files...) Comments please? BufferView_pimpl.C|2 Makefile.am |2 PosIterator.C | 151 ++ PosIterator.h | 66 +

Re: InsetOld::hasParagraphs->InsetOld::numParagraphs

2003-10-31 Thread Alfredo Braunstein
Angus Leeming wrote: > Alfredo Braunstein wrote: >> [Btw, it should be super easy to implement regex searches right? It >> [would >> suffice to implement operator* that gives pit->getChar(pos) if pos < >> size and some '\n' if pos == size. In that way one could also search >> for newlines etc. Met

Re: Stlport+gcc-2.96 builds but does not run

2003-10-31 Thread Lars Gullik Bjønnes
Martin Vermeer <[EMAIL PROTECTED]> writes: | On Thu, Oct 30, 2003 at 04:22:50PM +0100, Jean-Marc Lasgouttes spake thusly: | >> > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: > >> Lars> Ok, try this: >> >> Lars> remove the rdbuf initialization from debug.C and put it in >> L

Re: prosper.layout

2003-10-31 Thread John Weiss
On Wed, Oct 29, 2003 at 01:51:14PM +0100, Christian Ridderström wrote: > > Quoting myself: "... Weiss's layout seems to work best at the moment." > > That probably refers to this layout: > http://www.md.kth.se/~chr/lyx/examples/prosper/layouts/prosper-by-Weiss.layout > Aroo? I don't rec

Re: prosper.layout

2003-10-31 Thread John Weiss
On Wed, Oct 29, 2003 at 08:57:30AM +, Jose' Matos wrote: > On Wednesday 29 October 2003 08:55, Andre Poenitz wrote: > > There is a prosper.layout from Dekel. Is there a specific reason we do > > not distribute this? > > And also another from John Weiss. > Christian some more bits about thi

Re: prosper.layout

2003-10-31 Thread John Weiss
On Fri, Oct 31, 2003 at 11:55:48PM -0500, John Weiss wrote: > On Wed, Oct 29, 2003 at 01:51:14PM +0100, Christian Ridderström wrote: > > > > Quoting myself: "... Weiss's layout seems to work best at the moment." > > > > That probably refers to this layout: > > http://www.md.kth.se/~chr/lyx/e