Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

Sidharth Kshatriya wrote: > > I find the source code very lightly commented unfortunately. Even if every > > class had a 3-4 lines describing what it did, it would have been great. It > > would be wonderful if some more human commenting of each class were part of > > the goals of the 2.0 version.

Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

Thanks for your reply Richard. After reading your and Vincent's comments, I felt my questions relating to the DocIterator were well answered. Sure, I look forward to you suggesting enhancement features to implement. Thanks, Sidharth On Sun, Jun 13, 2010 at 11:16 PM, Richard Heck wrote: > On

Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

On 06/13/2010 01:22 PM, Sidharth Kshatriya wrote: On Sun, Jun 13, 2010 at 9:58 PM, Vincent van Ravesteijn >wrote: Are you interested in implementing a certain feature ? If it's not too difficult, we can guide you and explain you the things you'll find on your roa

Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

On Sun, Jun 13, 2010 at 9:58 PM, Vincent van Ravesteijn wrote: > Are you interested in implementing a certain feature ? If it's not too > difficult, we can guide you and explain you the things you'll find on your > road. It's indeed useful if you document it immediately. I myself have tried > to d

Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

On 06/13/2010 11:13 AM, Sidharth Kshatriya wrote: I want to understand * What is the use of the inset_ member in the DocIterator class? Each CursorSlice has a link to its corresponding inset so what is the use of inset_ in the DocIterator class? I don't know this code terribly well, but I thi

Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

Op 13-6-2010 17:13, Sidharth Kshatriya schreef: I want to understand * What is the use of the inset_ member in the DocIterator class? Each CursorSlice has a link to its corresponding inset so what is the use of inset_ in the DocIterator class? I don't have a good answer, but if you create a D

Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

Thanks for you reply Amir. How familiar are you with the source code? Would be great to get your help on this. My skype id is sid.kshatriya and I'd be happy to speak to you and others in bringing out a document on LyX internals. There are so many free resources on Linux kernel programming and it

Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

Basically I want to understand how the diagram of http://wiki.lyx.org/Devel/Diagrams corresponds to the implementation. I have figured out that each CursorSlice relates to one node in the stack of parents upto the root InsetText but can't understand the role of inset_ in DocIterator. On Sun, Jun

Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

Hi, I'm pretty much at the same position as you are right now and if you want to join forces on the documentations I can offer my help with it. Though as I said, I'm also a newbie to the code (but not LyX, I've been using it for some time). Thanks, - Amir Rachum On Sun, Jun 13, 2010 at 6:13 PM,

Re: wish: parallel build

"Mikhail T." writes: > Well, there is still lyx-1.5.7/src/frontends/qt4/ui/Makefile, which > means, the fix was, probably, never merged into 1.5.x (although back > then it was still a maintained branch). > Any hope for a fix now? Thanks! Yours, No, this will not happen now: the 1.5 branch is dead

Re: wish: parallel build

Jean-Marc Lasgouttes написав(ла): "Mikhail T." writes: That's a race condition... Any hope of seeing this fixed -- I'm fairly certain, 1.6.x has the same issue and that the fix will be applicable to 1.5.x as well. Thanks! Yours, I think this has been fixed with the following changeset

Re: wish: parallel build

"Mikhail T." writes: > That's a race condition... Any hope of seeing this fixed -- I'm fairly > certain, 1.6.x has the same issue and that the fix will be applicable > to 1.5.x as well. Thanks! Yours, I think this has been fixed with the following changeset, which removed ui/Makefile.am. I am not

Re: wish: parallel build

Mikhail T. wrote: Jean-Marc Lasgouttes wrote: LyX 1.5 and 1.6 can be built with -jx without problem. I do not know what is wrong with 1.4.5.1, but there is little (!) chance to see it fixed... JMarc I just had a report about failure of parallel build of LyX-1.5.7 -- the frontends/qt4/*.h fi

Re: wish: parallel build

Jean-Marc Lasgouttes wrote: LyX 1.5 and 1.6 can be built with -jx without problem. I do not know what is wrong with 1.4.5.1, but there is little (!) chance to see it fixed... JMarc I just had a report about failure of parallel build of LyX-1.5.7 -- the frontends/qt4/*.h files were being crea

Re: wish: parallel build

Mikhail Teterin <[EMAIL PROTECTED]> writes: > Hello! > > I tried to do a parallel build of lyx-1.4.5.1 with > > gmake -j4 > > but it failed due to some race condition. With more and more computers having > multiple processors, it would be extremely useful to have all dependencies > properl

Re: Wish: add newline after \begin{centering} and before \end{centering}

Juergen Spitzmueller <[EMAIL PROTECTED]> writes: > Gregor Gorjanc wrote: > > Gosh. I am surprised on license need for something so small. > > This is just our way to get you into the boat ;) > > Which 1.4.X will have this feature? > > The next one (1.4.4). Thank you again! Gregor

Re: Wish: add newline after \begin{centering} and before \end{centering}

Gregor Gorjanc wrote: > Gosh. I am surprised on license need for something so small. This is just our way to get you into the boat :-) > Which 1.4.X will have this feature? The next one (1.4.4). Jürgen

Re: Wish: add newline after \begin{centering} and before \end{centering}

On Sun, Dec 03, 2006 at 11:52:48PM +0100, Herbert Voss wrote: > Enrico Forestieri schrieb: > > On Sun, Dec 03, 2006 at 09:31:45PM +0100, Herbert Voss wrote: > > > >> no, do it without a caption ... There is no _correct_ way. > >> A command shouldn't be used as environemtn. That's correct. > >> In

Re: Wish: add newline after \begin{centering} and before \end{centering}

Enrico Forestieri schrieb: On Sun, Dec 03, 2006 at 09:31:45PM +0100, Herbert Voss wrote: no, do it without a caption ... There is no _correct_ way. A command shouldn't be used as environemtn. That's correct. Independant from that it works sometimes ... However, it is clearly documented in the

Re: Wish: add newline after \begin{centering} and before \end{centering}

On Sun, Dec 03, 2006 at 09:31:45PM +0100, Herbert Voss wrote: > no, do it without a caption ... There is no _correct_ way. > A command shouldn't be used as environemtn. That's correct. > Independant from that it works sometimes ... However, it is clearly documented in the LaTeX book by Lamport th

Re: Wish: add newline after \begin{centering} and before \end{centering}

Jean-Marc Lasgouttes schrieb: "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes: Herbert> Enrico Forestieri schrieb: Herbert, the two constructs are not equivalent. Herbert> I know, what I want to show is that it is not a good idea to Herbert> use a _command_ as an environment. The real

Re: Wish: add newline after \begin{centering} and before \end{centering}

> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes: Herbert> Enrico Forestieri schrieb: >> Herbert, the two constructs are not equivalent. Herbert> I know, what I want to show is that it is not a good idea to Herbert> use a _command_ as an environment. The real problem is that this comma

Re: Wish: add newline after \begin{centering} and before \end{centering}

Enrico Forestieri schrieb: Herbert, the two constructs are not equivalent. I know, what I want to show is that it is not a good idea to use a _command_ as an environment. This one: \begin{figure} \begin{centering} foo \end{centering} \caption{bar} \end{figure} corresponds to: \begin{figur

Re: Wish: add newline after \begin{centering} and before \end{centering}

> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes: Juergen> Jean-Marc Lasgouttes wrote: Adding a newline has no side Juergen> effects in this specific case AFAICS (and we already do that Juergen> for trivlist alignment), so I think this change could go in. >> Yes (in 1.4.X too)

Re: Wish: add newline after \begin{centering} and before \end{centering}

On Sun, Dec 03, 2006 at 08:04:40PM +0100, Herbert Voss wrote: > Jean-Marc Lasgouttes schrieb: > > > I guess Herbert is balking at the use of centering as an environment. > > In my view, using > > \begin{centering}...\end{centering} > > is equivalent to the more traditional > > {\centering ..

Re: Wish: add newline after \begin{centering} and before \end{centering}

Jean-Marc Lasgouttes schrieb: I guess Herbert is balking at the use of centering as an environment. In my view, using \begin{centering}...\end{centering} is equivalent to the more traditional {\centering ...} except that at least the first one is a proper markup. I agree nevertheless that

Re: Wish: add newline after \begin{centering} and before \end{centering}

Gregor Gorjanc <[EMAIL PROTECTED]> writes: > Juergen Spitzmueller wrote: > > Juergen Spitzmueller wrote: > >>> Yes (in 1.4.X too) Which 1.4.X will have this feature? Thanks. Gregor

Re: Wish: add newline after \begin{centering} and before \end{centering}

Juergen Spitzmueller wrote: > Juergen Spitzmueller wrote: >>> Yes (in 1.4.X too) >> I'll do that. > > However, after testing Gregor's patch, I noticed that it adds some unneeded > blank lines after \end tags (where a linebreak occurs anyway). So I'll apply > the attached patch instead. Thank yo

Re: Wish: add newline after \begin{centering} and before \end{centering}

Juergen Spitzmueller wrote: > > Yes (in 1.4.X too) > > I'll do that. However, after testing Gregor's patch, I noticed that it adds some unneeded blank lines after \end tags (where a linebreak occurs anyway). So I'll apply the attached patch instead. Before I do this: Gregor, can you please post

Re: Wish: add newline after \begin{centering} and before \end{centering}

Jean-Marc Lasgouttes wrote: > Juergen> Adding a newline has no side effects in this specific case > Juergen> AFAICS (and we already do that for trivlist alignment), so I > Juergen> think this change could go in. > > Yes (in 1.4.X too) I'll do that. Jürgen

Re: Wish: add newline after \begin{centering} and before \end{centering}

> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes: Juergen> Jean-Marc Lasgouttes wrote: >> I think it makes sense, but it needs careful checking. In >> particular, extra \n can create unwanted extra paragraphs in some >> cases. Juergen> Adding a newline has no side effects in thi

Re: Wish: add newline after \begin{centering} and before \end{centering}

Jean-Marc Lasgouttes wrote: > I think it makes sense, but it needs careful checking. In particular, > extra \n can create unwanted extra paragraphs in some cases. Adding a newline has no side effects in this specific case AFAICS (and we already do that for trivlist alignment), so I think this cha

Re: Wish: add newline after \begin{centering} and before \end{centering}

On Fri, Dec 01, 2006 at 05:05:55PM +0100, Jean-Marc Lasgouttes wrote: > Gregor> Sorry for ranting again. Can someone please "evaluate" my > Gregor> proposal. Should I file bug report, or, ... > > I think it makes sense, but it needs careful checking. In particular, > extra \n can create unwanted e

Re: Wish: add newline after \begin{centering} and before \end{centering}

Jean-Marc Lasgouttes wrote: >> "Gregor" == Gregor Gorjanc <[EMAIL PROTECTED]> writes: > > Gregor> Gregor Gorjanc <[EMAIL PROTECTED]> writes: >>> Jean-Marc Lasgouttes ...> writes: ... > >> stupid >>> code ... > >> I suppose you do not know the difference between >>> centering and > >> center >

Re: Wish: add newline after \begin{centering} and before \end{centering}

> "Gregor" == Gregor Gorjanc <[EMAIL PROTECTED]> writes: Gregor> Gregor Gorjanc <[EMAIL PROTECTED]> writes: >> Jean-Marc Lasgouttes ...> writes: ... > >> stupid >> code ... > >> I suppose you do not know the difference between >> centering and > >> center >> > >> > First, I want to point out

Re: Wish: add newline after \begin{centering} and before \end{centering}

Gregor Gorjanc <[EMAIL PROTECTED]> writes: > Jean-Marc Lasgouttes ...> writes: > ... > > >> stupid code ... > > >> I suppose you do not know the difference between centering and > > >> center > > > > First, I want to point out that this is the code output by LyX, not > > Gregor's doing. And I do

Re: Wish: add newline after \begin{centering} and before \end{centering}

On Fri, Dec 01, 2006 at 02:48:39PM +0100, Jean-Marc Lasgouttes wrote: > > "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes: > > Enrico> Now, when \csname is used to define a command for the first > Enrico> time, this command is made equivalent to \relax until it is > Enrico> redefined.

Re: Wish: add newline after \begin{centering} and before \end{centering}

> "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes: Enrico> Now, when \csname is used to define a command for the first Enrico> time, this command is made equivalent to \relax until it is Enrico> redefined. Ahh, I did not know that \csname...\endcsname could define the macro if it di

Re: Wish: add newline after \begin{centering} and before \end{centering}

On Fri, Dec 01, 2006 at 12:46:51PM +0100, Jean-Marc Lasgouttes wrote: > What I don't quite understand is that \endcentering does not exist (at > least I did not find its definition). This due to the way \begin and \end are defined: \def\begin#1{% [EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL

Re: Wish: add newline after \begin{centering} and before \end{centering}

> "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes: Enrico> On Fri, Dec 01, 2006 at 09:27:17AM +0100, Jean-Marc Lasgouttes Enrico> wrote: >> I guess Herbert is balking at the use of centering as an >> environment. In my view, using \begin{centering}...\end{centering} >> is equivalent t

Re: Wish: add newline after \begin{centering} and before \end{centering}

On Fri, Dec 01, 2006 at 09:27:17AM +0100, Jean-Marc Lasgouttes wrote: > I guess Herbert is balking at the use of centering as an environment. > In my view, using > \begin{centering}...\end{centering} > is equivalent to the more traditional > {\centering ...} > except that at least the first o

Re: Wish: add newline after \begin{centering} and before \end{centering}

Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: ... > >> stupid code ... > >> I suppose you do not know the difference between centering and > >> center > > First, I want to point out that this is the code output by LyX, not > Gregor's doing. And I do not think that his particular problem is > ab

Re: Wish: add newline after \begin{centering} and before \end{centering}

> "Gregor" == Gregor Gorjanc <[EMAIL PROTECTED]> writes: Gregor> Herbert Voss <[EMAIL PROTECTED]> writes: >> > That is the output if I center scrap (modified to allow that) >> environment: >> > >> > \begin{figure} > \begin{centering}<>= > >> boxplot(Sepal.Length~Species,data=iris) > \par\end

Re: Wish: add newline after \begin{centering} and before \end{centering}

Herbert Voss <[EMAIL PROTECTED]> writes: > > That is the output if I center scrap (modified to allow that) environment: > > > > \begin{figure} > > \begin{centering}<>= > > boxplot(Sepal.Length~Species,data=iris) > > \par\end{centering} > > > > > > \caption{bla bla} > > \end{figure} > > stupid

Re: Wish: add newline after \begin{centering} and before \end{centering}

Gregor Gorjanc schrieb: > Gregor Gorjanc <[EMAIL PROTECTED]> writes: > >> Herbert Voss ...> writes: >>> you mean center, not centering ... >>> \centering is a macro and center an environment. >>> >> Whatever. LyX sometimes outputs centering otherwise center. > > That is the output if I center sc

Re: Wish: add newline after \begin{centering} and before \end{centering}

Gregor Gorjanc <[EMAIL PROTECTED]> writes: > > Herbert Voss ...> writes: > > you mean center, not centering ... > > \centering is a macro and center an environment. > > > > Whatever. LyX sometimes outputs centering otherwise center. That is the output if I center scrap (modified to allow that

Re: Wish: add newline after \begin{centering} and before \end{centering}

Herbert Voss <[EMAIL PROTECTED]> writes: > you mean center, not centering ... > \centering is a macro and center an environment. > Whatever. LyX sometimes outputs centering otherwise center. Gregor

Re: Wish: add newline after \begin{centering} and before \end{centering}

Gregor Gorjanc schrieb: > Dear LyX team! > > I am trying to provide support for Sweave[1] (another literate programming > idea > based on noweb) in LyX. I have already contacted this list about Sweave [2] > and > got some respone from Andre. I have just responded in that thread. To have a > bit

RE: wish list: cross-referencing

>available in Lyx 1.4Certainly not. Ace! >Do you want everything labeled all the time? Suggestion. Referencing to the 'Cross reference' dialog box current in lyx 1.3.2... Below "Document" and above "Available references in selected document" have two radio options (one MUST be selected). S

Re: wish list: cross-referencing

On Mon, Jun 30, 2003 at 01:31:50PM +0100, Dan Owen wrote: > OK, now your on the hook!... *shrug* I already found this annoying myself. > I use a lot of ERT inserts which manual label verbatim, for these I > don't mind manually cross-referencing... > > But when I want to cross reference a sectio

RE: wish list: cross-referencing

tion*) in the list of reference points (figures, etc also). To late for 1.4? Cheers Dan. -Original Message- From: Andre Poenitz [mailto:[EMAIL PROTECTED] Sent: 30 June 2003 13:28 To: Dan Owen Cc: [EMAIL PROTECTED] Subject: Re: wish list: cross-referencing On Mon, Jun 30, 2003 at 01:19:0

Re: wish list: cross-referencing

On Mon, Jun 30, 2003 at 01:19:07PM +0100, Dan Owen wrote: > Guys, > > Am recently a convert (though use the win32 port from Ruurd Reitsma) > from word (to write my PhD thesis!!!) and have a wish... > > Why should I need to add labels to sections, subsections & > subsubsections (and even figures

Re: wish list

> "adi" == adi mailbox <[EMAIL PROTECTED]> writes: adi> c) Some of ERT commands do not work with lyx but work fine if the adi> file is converted first to latex [see b) above]. For example the adi> following lyx code: [...] adi> The output if viewed in lyx is different compared with the case ad

Re: footnotes (was Re: Wish)

> > Donald Knuth's wife used to say "Don, don't use footnotes". And he > > doesn't use them and it seems to work. I presume human science papers are > > very different from computer science papers. Thousands footnotes in a PhD > > thesis. WOW is all I can say. Okay, okay, let's not start a flamewar

Re: footnotes (was Re: Wish)

Kuba Ober wrote: > Donald Knuth's wife used to say "Don, don't use footnotes". And he doesn't > use them and it seems to work. I presume human science papers are very > different from computer science papers. Thousands footnotes in a PhD > thesis. WOW is all I can say. Okay, okay, let's not start a

Re: footnotes (was Re: Wish)

> However, my PhD has several thousand footnotes by now, which is not unusual > for a human science document. I'm just too lazy to open and close them > manually, and it also disturbs reading and concentration. Donald Knuth's wife used to say "Don, don't use footnotes". And he doesn't use them

Re: Wish

On Mon, Nov 18, 2002 at 02:18:22PM +0100, Juergen Spitzmueller wrote: > Why? When working on a text, sometimes I want to read only the main text, > sometimes I want to read the footnotes too. Having this two options easily > accessable is part of logical document processing IMO, since these are

Re: Wish

John Levon wrote: > Yes, it's possible, but first we should fix any bugs that corrupt the > open/close state (spellchecker, for example) /then/ see if people > /really/ still want such a feature (why ?) I can tell you already now that I will really still want this even if all bugs are fixed. Why

Re: Wish

On Mon, Nov 18, 2002 at 10:21:57AM +0100, Pascal Francq wrote: > In an old version of LyX, there was menu entries which enable to open or close > all the floats (or all those of a given type) directly. This was very > interesting, because sometimes after a command all the floats are open, for >

Re: wish list items

On Thu, Dec 20, 2001 at 01:59:42PM -0400, John Janmaat wrote: > More for the wish list, > > Integrate a bibtex reference manager. Why ? We already support the lyxserver so managers like gbib can insert references into lyx. I don't think we need to go beyond that level of integration ... regard

Re: Wish: Multiple Windows

> "Axel" == Axel Boldt <[EMAIL PROTECTED]> writes: Axel> First of all, thank you all very much for a wonderful product. Axel> My biggest wish for lyx is to be able to edit a document Axel> simultaneously in several windows, as is possible in emacs and Axel> word. This is something that will

Re: wish list

On Wed, May 10, 2000 at 02:08:08PM +0200, Jean-Marc Lasgouttes wrote: > > Dekel> 2. Sort the labels in the Insert Reference Dialog/Refs menu > > That's nice. Is it possible to make it optional (a check box in the > popup?) for people who prefer them in docuemnt order? Done. I've also added 1.

Re: wish list

> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes: Dekel> Content-Type: text/plain; charset=us-ascii On Tue, May 02, 2000 Dekel> at 05:02:23PM +0200, Jean-Marc Lasgouttes wrote: >> It would be useful if the menu were hierarchical, in which case the >> TOC browser should go away. Dekel> I've

Re: wish list

On Tue, May 02, 2000 at 05:02:23PM +0200, Jean-Marc Lasgouttes wrote: > It would be useful if the menu were hierarchical, in which case the > TOC browser should go away. I've changed the ToC menu to be hierarchical. Besides the new ToC & Refs menus, the patch does other things: 1. Editable labels

Re: wish list

On Wed, May 03, 2000 at 10:05:57AM +1000, Allan Rae wrote: > I'd rather we improved the integration of external programs than try to > duplicate their capabilities into LyX. It should be possible using XTL in > LyX and some corresponding externalization support in the external > programs to get/s

Re: wish list

> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Lars> Allan Rae <[EMAIL PROTECTED]> writes: | A different Lars> colour with the pretty 3d boxes that we had in the old tree. | Lars> (I know, the 3d boxes are dependent on the Painter so I'll have Lars> to wait | for those) Lars> Wh

Re: wish list

Allan Rae <[EMAIL PROTECTED]> writes: | I (one day) want to add the option of document scope selection of a | citation package (harvard.sty etc.) and then have a corresponding menu in | the citation dialog for the various forms of citation that package | provides (citeyear, citeauthor and so on).

Re: wish list

Allan Rae <[EMAIL PROTECTED]> writes: | A different colour with the pretty 3d boxes that we had in the old tree. | (I know, the 3d boxes are dependent on the Painter so I'll have to wait | for those) What do you mean? We have been using the Painter for some months now... Lgb

Re: wish list

On 3 May 2000, Jean-Marc Lasgouttes wrote: > Dekel> I put it on the left side in order to leave enough room for > Dekel> long lines in the menu. However, this can be changed easily. > > Yes. And then what about the TOC popup? Should it be removed? In a word: No. Maybe I'm the only one; but it'

Re: wish list

> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes: Dekel> I've already suggested this idea (however, I think that the ToC Dekel> should be "flat" if there is small enough). Yes, there may be some threshold (the same would hold for submenus). Currently, the menu for the UserGuide is not usab

Re: wish list

On Tue, 2 May 2000, Dekel Tsur wrote: > On Tue, May 02, 2000 at 06:06:55PM +1000, Allan Rae wrote: > > That's what pybliographer, barracuda and tkbib among others are all for. > > It would be nice if they could insert multiple references however I think > > they only insert one at a time at the m

Re: wish list

On Tue, May 02, 2000 at 10:54:40AM -0400, Amir Karger wrote: > IMO, there shouldn't be lots of different ways of looking at the TOC. Seems > like overkill and too many features. Why have a separate menu of the TOC > when you can get it with keys, mouseclick, or menu selection? Using my ToC menu i

Re: wish list

On Tue, May 02, 2000 at 04:28:21PM +0200, Jean-Marc Lasgouttes wrote: > > Hi Dekel. I really like the idea of this patch... > > Some comments: > > - could the TOC menu be hierarchical (with submenus)? I've already suggested this idea (however, I think that the ToC should be "flat" if there is

Re: wish list

On Tue, May 02, 2000 at 06:06:55PM +1000, Allan Rae wrote: > That's what pybliographer, barracuda and tkbib among others are all for. > It would be nice if they could insert multiple references however I think > they only insert one at a time at the moment. I'm aware of these programs, but I thin

Re: wish list

On Mon, May 01, 2000 at 07:11:33PM -0300, Garst R. Reese wrote: > > or by typing "M-e t". > Duh, > But in that case why not just have the TOC on the menu do the same > thing? > Are there key-bindings for TOC and REF? e.g., F10-T F10-R M-t and M-r

Re: wish list

Jean-Marc Lasgouttes wrote: > - Now that labels are editable, there should maybe be something like > 'label:' in their box, so that they are really different from refs. > Of course, a small icon would be nice, but it might be a bit > difficult. > > JMarc I just tested this great new featur

Re: wish list

> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: Amir> IMO, there shouldn't be lots of different ways of looking at the Amir> TOC. Seems like overkill and too many features. Why have a Amir> separate menu of the TOC when you can get it with keys, Amir> mouseclick, or menu selection? It wo

Re: wish list

IMO, there shouldn't be lots of different ways of looking at the TOC. Seems like overkill and too many features. Why have a separate menu of the TOC when you can get it with keys, mouseclick, or menu selection? -Amir

Re: wish list

> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes: Dekel> OK. I've changed my patch to (2). The attached patch contains Dekel> both ToC & Refs menus (and it also simplifies existing code). Hi Dekel. I really like the idea of this patch... Some comments: - could the TOC menu be hierarchica

Re: wish list

On Mon, 1 May 2000, Dekel Tsur wrote: > On Mon, May 01, 2000 at 12:41:03PM +1000, Allan Rae wrote: > > What did you have in mind for the citation popup? > [...] > > In addition one change I've been meaning to do for ages which should be > > extremely simple is to change the combox operation so th

Re: wish list

Dekel Tsur wrote: > > On Sun, Apr 30, 2000 at 07:39:43PM -0300, Garst R. Reese wrote: > > Just tested it. It's really nice to be able to get to TOC without having > > to find it in the doc. > > You can open the ToC popup using the "Edit->Table of contents" menu, > or by typing "M-e t". Duh, But

Re: wish list

On Mon, May 01, 2000 at 12:41:03PM +1000, Allan Rae wrote: > What did you have in mind for the citation popup? [...] > In addition one change I've been meaning to do for ages which should be > extremely simple is to change the combox operation so that if the last > character (non-white-space) of

Re: wish list

On Sun, Apr 30, 2000 at 07:39:43PM -0300, Garst R. Reese wrote: > Just tested it. It's really nice to be able to get to TOC without having > to find it in the doc. You can open the ToC popup using the "Edit->Table of contents" menu, or by typing "M-e t".

Re: wish list

On Mon, May 01, 2000 at 01:29:18AM -0300, Garst R. Reese wrote: > A further note on your TOC patch. I have a client's book with 77 poems, > divided into 5 "Chapters". Each poem is a Section. Your new menu TOC > shows the first 38 or so. In Netscape, when it runs out of room on > bookmarks, it ope

Re: wish list

On Mon, 1 May 2000, Allan Rae wrote: > On Fri, 28 Apr 2000, Dekel Tsur wrote: > > 2. Better citation popup (I know that it is possible to use external > > bibliography program, but I do want LyX to have something better than just a > > list of keys). > > I (one day) want to add the option of docu

Re: wish list

Dekel Tsur wrote: > > On Sun, Apr 30, 2000 at 12:26:43AM +0200, Asger K. Alstrup Nielsen wrote: > > > (1) void LyXParagraph::String(string & s) > > > that writes the paragraph into the string s. > > > > > > The alternative is > > > (2) string LyXParagraph::String() > > > that returns a string fro

Re: wish list

On Fri, 28 Apr 2000, Dekel Tsur wrote: > There are so many things I want to add to LyX, and so little time :( > To name few features that I want to add: [...] > 2. Better citation popup (I know that it is possible to use external > bibliography program, but I do want LyX to have something better

Re: wish list

Dekel Tsur wrote: > > On Sun, Apr 30, 2000 at 12:26:43AM +0200, Asger K. Alstrup Nielsen wrote: > > > (1) void LyXParagraph::String(string & s) > > > that writes the paragraph into the string s. > > > > > > The alternative is > > > (2) string LyXParagraph::String() > > > that returns a string fro

Re: wish list

On Sun, Apr 30, 2000 at 12:26:43AM +0200, Asger K. Alstrup Nielsen wrote: > > (1) void LyXParagraph::String(string & s) > > that writes the paragraph into the string s. > > > > The alternative is > > (2) string LyXParagraph::String() > > that returns a string from the paragraph. > > > This is w

Re: wish list

Jules Bean <[EMAIL PROTECTED]> writes: | (2) says what it means. If efficiency is bothering you, you can save a | copy by making th procedure return a string&. No you can't unless you have a static string in the method, or returning a temporary which is invalid. Lgb

Re: wish list

"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes: | > The alternative is | > (2) string LyXParagraph::String() | > that returns a string from the paragraph. | > | > Do you really think that (2) is clearer/better than (1) ? | > Should I stay with (1) ? | | If the method produces a new strin

Re: wish list

On Sun, Apr 30, 2000 at 01:15:12AM +0300, Dekel Tsur wrote: > Yes, but I think that the style I use is quite clear. > To refresh your memory, I've created a procedure > (1) void LyXParagraph::String(string & s) > that writes the paragraph into the string s. > > The alternative is > (2) string LyX

Re: wish list

> Yes, but I think that the style I use is quite clear. > To refresh your memory, I've created a procedure > (1) void LyXParagraph::String(string & s) > that writes the paragraph into the string s. > > The alternative is > (2) string LyXParagraph::String() > that returns a string from the paragra

Re: wish list

On Sat, Apr 29, 2000 at 04:48:58PM +0200, Asger K. Alstrup Nielsen wrote: > > I do know that the difference will not be noticeable by the user, but I think > > that returning complex objects from functions should be avoided. > > In general, it's more important for the code to be clear than for th

Re: wish list

> I do know that the difference will not be noticeable by the user, but I think > that returning complex objects from functions should be avoided. In general, it's more important for the code to be clear than for the code to be fast. This rule should only be lifted if profiling shows that there

Re: wish list

On Sat, Apr 29, 2000 at 12:41:34PM +0300, Dekel Tsur wrote: > > > ... why not return a string in stead of taking one as an argument? > > Because it is faster this way. I do know that the difference will not be noticeable by the user, but I think that returning complex objects from functions sho

Re: wish list

> Sorry for beeing a PITA, but why not rename your ToString to str? And Why not Str() or String()? > ... why not return a string in stead of taking one as an argument? Because it is faster this way.

Re: wish list

Dekel Tsur <[EMAIL PROTECTED]> writes: | > I would also like to have others views on this. | > | Done. Sorry for beeing a PITA, but why not rename your ToString to str? And ... why not return a string in stead of taking one as an argument? Lgb

Re: wish list

On Fri, Apr 28, 2000 at 11:41:44PM +0200, Lars Gullik Bj&resh;nnes wrote: > Dekel Tsur <[EMAIL PROTECTED]> writes: > Can you do those changes and send a new patch? > > I would also like to have others views on this. > Done. patch.gz

Re: wish list

Dekel Tsur <[EMAIL PROTECTED]> writes: | I've already manage to do (1) + (3). A patch is attached. I am currently looking at it. +{ + const max_numer_of_lines = 40; is not allowed, int const max_number_of_lines = 40; is. + if (!IsDummy()) { + if (isR

  1   2   >