date:20130509

Re: patch for scrolling issue - LyXscrollpatch20130302.diff (1/1) - LyXscrollpatch20130421.diff (1/1) - LyXscrollpatch20130427.diff (1/1) - LyXscrollpatch20130509.diff (1/1)

2013-05-09 Thread pdv

In article 517ee12b.4040...@lyx.org,
 Jean-Marc Lasgouttes lasgout...@lyx.org wrote:

 Le 28/04/2013 13:06, pdv a écrit :
  OK, here is a new version. Let me know if you experience anymore
  problems.
  For the time being I've left the clean-up step of the map as it was,
  although I realize it's of limited value; when entering the same word
  multiple times, the partial words get included anyway;
 
  The map itself is still defined in the BufferView class, but as a shared
  static map. The reason for this is that when the user makes changes to
  the screen fonts, the map becomes useless and I think the best option is
  to clear it at that point.
  I've added the case LFUN_SCREEN_FONT_UPDATE: to BufferView::dispatch()
  and added a corresponding request in GuiApplication::dispatch();
 
 You should move the code that computes text width to 
 GuiFontMetrics::width(docstring). This is the right place for storing a 
 map, that could be static if you want to keep your current solution or 
 just a member of the GuiFontMetrics object so that you do not have to 
 play tricks with font attributes.
 
 Moreover, if your mùap is in GuiFontMetrics it will be reset 
 automatically by the code in GuiApplication.cpp.
 
 This will be much easier in my opinion.
 
  I noticed then that the map was cleared and rebuild twice ...
  ... because in GuiPreferences::dispatchParams() there is first a call
  dispatch(FuncRequest(LFUN_LYXRC_APPLY, ss.str()))
  later followed by
  dispatch(FuncRequest(LFUN_SCREEN_FONT_UPDATE))
  but the first dispatch runs GuiReset() which also sends a
  LFUN_SCREEN_FONT_UPDATE.
  Therefore I've commented out the 2nd explicit LFUN_SCREEN_FONT_UPDATE
  request.
 
 Not sure about that, but things should become clearer once code is at 
 the right place.
 
 JMarc

I've moved the code to GuiFontMetrics which is indeed much better.
Solved also a remaining issue with smallcaps.

begin 644 LyXscrollpatch20130509.diff
M1G)O;2`W9#)C.3(W,S`W,CW93DX,#(T96,X,C0X83X8F4U,#,Q,5F,68V
M($UO;B!397`@,3@,#`Z,#`Z,#`@,C`P,0IF]M.B!0871R:6-K($1E(%9I
MW-C:5R92`\1V:7-S8VAEF5`961P;F5T+F)E/@I$871E.B!7960L(#$@
M36%Y(#(P,3,@,C(Z-38Z,3$@*S`R,#`*4W5B:F5C=#H@6U!!5$-(72!-;W9E
M9!T:4@=5X=%=I9'1H*D@9G)O;2!497AT365TFECR!T;R!'=6E;VYT
M365TFECRP*(')E;F%M960@:70@86YD(9I5D('-M86QL8V%PRX*BTM
M+0H@W)C+T)U9F9EE9I97N8W!P(`@(`@(`@(`@(`@(`@('P@(`T
M(LMB!SF,O0G5F9F5R5FEE=RYH(`@(`@(`@(`@(`@(`@(`@?`@
M(#,@*RT*('-R8R]497AT365TFECRYC'`@(`@(`@(`@(`@(`@(!\
M(#(Y,R`K*RLK*RLK*RLK*RLK*RLK*RLK*RLK*RLK*RLK*RLK*RTM+0H@W)C
M+U1E'1-971R:6-S+F@@(`@(`@(`@(`@(`@(`@('P@(#$X(LK+0H@
MW)C+V9R;VYT96YDR];VYT365TFECRYH(`@(`@(`@('P@(`R(L*
M('-R8R]FF]N=5N9',O70T+T=U:49O;G1-971R:6-S+F-P!\(`T.`K
M*RLK*RL*('-R8R]FF]N=5N9',O70T+T=U:49O;G1-971R:6-S+F@@(!\
M(`@-B`KB!SF,O9G)O;G1E;F1S+W%T-]'=6E086EN=5R+F-P`@(`@
M?`@(#(@*PH@W)C+V9R;VYT96YDR]Q=#0O1W5I4')E9G,N8W!P(`@(`@
M('P@(`S(LMB!SF,OF]W%I;G1EBYC'`@(`@(`@(`@(`@(`@
M(`@?`@,S@*RLK*RL*(#$P(9I;5S(-H86YG960L(#,X-2!I;G-EG1I
M;VYS*LI+`S,2!D96QE=EO;G,H+2D*F1I9F8@+2UG:70@82]SF,O0G5F
M9F5R5FEE=RYC'`@8B]SF,O0G5F9F5R5FEE=RYC'`*:6YD97@@9%A,#5A
M-BXN-S4Y-S(V.2`Q,#`V-#0*+2TM($OW)C+T)U9F9EE9I97N8W!PBLK
M*R!B+W-R8R]=69F97)6:65W+F-P`I`0`M.38U+#@*SDV-2PW($!`('9O
M:60@0G5F9F5R5FEE=SHZ=7!D871E1]C=6UE;G1#;%SRA$;V-U;65N=$-L
M87-S0V]NW10='(@;VQD9,IB`*(`EB=69F97)?+F5RF]RR@B0VQAW,@
M4W=I=-H(BD[B!]BT**PD*(`H@+RHJ(%)E='5R;B!T:4@8VAA;F=E('-T
M871UR!A=!C=7)S;W(@]S:71I;VXL('1A:VEN9R!I;B!A8V-O=6YT('1H
M90H@(H@W1A='5S(%T(5A8V@@;5V96P@;V8@=AE(1O8W5M96YT(ET
M97)A=]R(AA('1A8FQE(EN($@95L971E9`I`0`M,38P,PW(LQ-C`P
M+#@0$`@=F]I9!=69F97)6:65W.CID:7-P871C:A=6YC4F5Q=65S=!C
M;VYS=`F(-M9P@1ES%T8VA297-U;'0@)B!DBD*(`EC87-E($Q54Y?
M4T-2145.7U)%0T5.5$52.@H@0ER96-E;G1Eb...@i.ph@0EBF5A:SL*+0HK
M0D)B`)8V%S92!,1E5.7T))0E1%6%]$051!0D%315]!1$0Z('L*(`D)0W5R
MV]R('1M-UB`](-UCL*(`D)9FEN9$ENV5T*'1M-UBP@0DE5$58
M7T-/1$4L(9A;'-E*3L*9EF9B`M+6=I=!A+W-R8R]=69F97)6:65W+F@@
M8B]SF,O0G5F9F5R5FEE=RYHFEN95X(,W9F(T8S$N+C$X9#-A,6,@,3`P
M-C0TBTM+2!A+W-R8R]=69F97)6:65W+F@**RLK((OW)C+T)U9F9EE9I
M97N:`I`0`M,S(P+#@*S,R,PW($!`('!U8FQI8SH*(`EB;V]L(-L:6-K
M86)L94ENV5T*D@8V]NW0[B`)+R\OB`)=F]I9!M86ME1]C=6UE;G1#
M;%Sr...@i.phmBL)B!PFEV871E.@H@2\O+R!N;VYC;W!Y86)L90H@4)U
M9F9EE9I97H0G5F9F5R5FEE=R!C;VYS=`F*3L*0$`@+3,V,2PV(LS-C$L
M-R!`0!PFEV871E.@H@B`)W1R=6-T(%!R:79A=4[B`)4')I=F%T92`J
M(-O;G-T(0[BL)B!].PH@B`O+R\@V]M92!S%C92!F;W(@9')A=VEN
M9R!T:4@)VYEW1E9@;6%R:V5RR`H:6X@EX96PIF1I9F8@+2UG:70@
M82]SF,O55X=$UE=')I8W,N8W!P((OW)C+U1E'1-971R:6-S+F-P`II
M;F1E`T93P9,P+BYD-S0Y-V(Y(#$P,#8T-`HM+2T@82]SF,O55X=$UE
M=')I8W,N8W!PBLK*R!B+W-R8R]497AT365TFECRYC'`*0$`@+30Y+#$P
M(LT.2PQ-B!`0`H@(VEN8VQU94@(F9R;VYT96YDR];VYT365TFECRYH
M(@H@(VEN8VQU94@(F9R;VYT96YDR]086EN=5R+F@BB`**R-I;F-L=61E
M()FF]N=5N9',O70T+T=U:49O;G1,;V%D97(N:(**PH@(VEN8VQU94@
M(G-U'!OG0O95B=6N:(*(-I;F-L=61E()S=7!P;W)T+V1O8W-TFEN
M9U]L:7-T+F@BB`C:6YC;'5D92`BW5P]R=]G971T97AT+F@BB`C:6YC
M;'5D92`BW5P]R=]L87-S97)T+F@BBLC:6YC;'5D92`BW5P]R=]Q
MW1R:6YG7VAE;'!EG,N:(**R-I;F-L=61E()S=7!P;W)T+W1E'1U=EL
MRYH(@HKBLC:6YC;'5D92`\471'=6DO449O;G1-971R:6-S/@H@B`C:6YC

Re: patch for scrolling issue - LyXscrollpatch20130302.diff (1/1) - LyXscrollpatch20130421.diff (1/1) - LyXscrollpatch20130427.diff (1/1)

2013-05-09 Thread pdv

In article 5186ae01.4080...@lyx.org,
 Jean-Marc Lasgouttes lasgout...@lyx.org wrote:

 Le 05/05/13 20:36, pdv a écrit :
  What exactly takes 17.4s?
 
  I suppose that's the time taken by GuiPainter::text(), but I don't know
  enough of the Instruments app and it's modules to give any more details.
 
  I've now monitored both functions with pmprof:
  ( I scroll through a document of mine starting from the top down to the
  same location with the down arrow key (line per line not page per page) )
 
 A related question: will you be somewhat available during the coming 
 week? I'd like at the developers meeting (from Thursday to Sunday) to 
 start from your patch and apply it to master branch. We will probably 
 diverge significantly from what you propose but nevertheless it would be 
 useful to know whether there are times when you are available. The plan 
 is probably to set up a branch on git to work on.
 
 JMarc

Yes, I'm available.
I've posted another version as you might already have noticed.

Re: patch for scrolling issue - LyXscrollpatch20130302.diff (1/1) - LyXscrollpatch20130421.diff (1/1) - LyXscrollpatch20130427.diff (1/1) - LyXscrollpatch20130509.diff (1/1)

2013-05-09 Thread Jean-Marc Lasgouttes


Le 09/05/2013 09:37, pdv a écrit :

I've moved the code to GuiFontMetrics which is indeed much better.
Solved also a remaining issue with smallcaps.


Very good. Thanks.

JMarc

Re: XML For LyX

2013-05-09 Thread Alex Vergara Gil

 
 I have started to think seriously about moving to XML for LyX's native 
 file format. I doubt that we will want to do this for 2.1, as it is too 
 late, really, so I am thinking about doing it for some time early in the 
 2.2 cycle, which means starting now.
 
First of all, This is a very old feature request that will be greatly 
appreciated at least from my part! So if you manage to achieve this it will be 
a huge improvement but just a starting point for the rest of things that can be 
done with an XML native format. There is a thread for this named Would a 
native LyX XML schema be accepted?.

 My plan is first to write routines that will output a pure XML version 
 of a LyX document and then to worry about the read routines once that is 
 working. I think it will be fairly easy to get that much done, by 
 working off the XHTML stuff. Some of that will prove re-usable.
 
 Thinking ahead, however: Should we use some SAX library to read the XML? 
 Or should we just adapt the Lexer for this purpose?
 
 Richard
 

I think there are much work done in this sense, please read Nico Williams' 
approach. I think is the correct way to follow.

My 5c

Alex

[ANNOUNCE] LyX 2.0.6 Released

2013-05-09 Thread Richard Heck


Public release of LyX version 2.0.6
===

We are pleased to announce the release of LyX 2.0.6. This is the sixth
maintenance release in the 2.0.x series.

LyX 2.0.6 is the result of on-going efforts to make our stable version
even more reliable and stable. We have fixed a number of bugs and made
a number of improvements. These are detailed below. We encourage all
LyX users to upgrade to this version.

LyX is a document processor that encourages an approach to writing based
on the structure of your documents and not simply their appearance. It is
released under a Free and Open Source Software license.

You can download LyX 2.0.6 from http://www.lyx.org/Download/.

If you think you found a bug in LyX 2.0.6, either e-mail the LyX
developers' mailing list (lyx-devel at lists.lyx.org), or open a bug
report at http://www.lyx.org/trac/wiki/BugTrackerHome.

If you have trouble using LyX or have a question, consult the
documentation that comes with LyX and the LyX wiki, which lives at
http://wiki.lyx.org/. If you can't find the answer there, e-mail the LyX
users' list (lyx-users at lists.lyx.org).

We hope you enjoy using LyX 2.0.6.

The LyX team.
http://www.lyx.org


What's new in LyX 2.0.6
===


** Updates:
***

* DOCUMENT INPUT/OUTPUT

- New layout file for the document class APA6 (bug 8391).

- Output BibTeX metadata in LyXHTML output (bug 8451).

- Added CSS styling for Memoir's epigraphs (bug 8611).

- Use master document's setting for all HTML math output (bug 8607).


* TEX2LYX IMPROVEMENTS

- support for listings with options (bug 8066).

- add new option -m to select needed modules (bug 8393).


* USER INTERFACE

- Categorize paragraph styles of the linguistics module.

- Show a symbol on collapsed branches indicating whether they are
  active.


* DOCUMENTATION AND LOCALIZATION

- Updated German, French, Interlingua, Italian, Japanese, Spanish, Slovak,
  Swedish and Ukrainian user interface localizations.

- Updated the lilypond example file.


** Bug fixes:
*

* DOCUMENT INPUT/OUTPUT

- Fixed occasional crash when exporting a document while View-Source is
  open and being updated (bug 8425).

- Load the babel package also if the document is English-only (bug 8423).

- Fix call of nonsense font packages in some localizations.

- Documents with document language Belarusian are now compilable (bug 8593).

- Documents with document language Serbian (using Cyrillic letters) are now
  compilable (bug 8590).

- Do not let child document's settings override master settings (bug 5941).

- Correct output of text in changed font size and with decorations (bug 
8424).


- Layout file for JASATeX: solved problems with natbib and added missing
  short title for the document title

- Fix problem using lyxpak.py when outside the LyX tree: Variable was
  undefined.

- When using the knitr module, use new encoding parameter of knitr if
  available (bug 8504).

- Fix layout conversion bug involving quoted Flex inset names that do not
  contain spaces.

- Fix crash while exporting document with images to xhtml from the 
command-line


- In order to avoid NFSS problems with certain font packages, load the 
needed
  font encodings when inserting Cyrillic and/or Greek characters (bug 
8467).


- Reordering citations in LyX is now rendered in the output (bug 6955).

- Fix InsetLayout's LatexParam output: \begin{inset}[latexparam].

- Fix TeX crash involving font changes in URLs.

- Properly output alias for formatted chapter references, so prettyref
  documents work when converted tor refstyle.

- Fix lyx2lyx bug with non-ASCII layout file names (Debian bug 700828).

- Made \lyxadded and \lyxdeleted robust (bug 8435).


* USER INTERFACE

- Fix crash when clicking on a completion in math mode (bug 8296).

- Fix assertion when searching for next change (bug 8370).

- Fix regression in which clicking in the main work area always resets
  the selected format in View - Source (bug 8411).

- When selecting text and then using the menu Insert - Preview, immediately
  display the preview (bug 8075).

- If 2 columns are chosen for the document they are now also displayed RTL
  if the document language is a RTL language (bug 6389).

- Allow arguments in PassThru environments (bug 7646).

- Consider deleted text when inserting quote inset.

- Fix a few selection bugs in tabular (bugs 4981, 7988).

- Handle properly undo after deleting a paragraph break when change
  tracking is enabled (bug 8633).

- Fix `select whole inset' function in math editor.

- Fix confusing behavior in search when changing directions (bug 8543)

- Fix several issues when using multicolumns/multirows and decimal 
alignment in

  table cells (bug 8285).

- Show the output of configure.py while the LaTeX packages are being checked
  rather than all at once at the end of the check (bug 8477).

- Do not crop wide characters in Symbols dialog (bug 5707).

- Make sure that inset-forall does not

Re: [ANNOUNCE] LyX 2.0.6 Released

2013-05-09 Thread José Matos

On Thursday 09 May 2013 09:38:01 Richard Heck wrote:
 Public release of LyX version 2.0.6

Hi Richard,
note that the press release at http://www.lyx.org/News#item2 still 
refers to the 2.0.5 announcement instead of the 2.0.6 as it should.

Regards,
-- 
José Abílio

Re: [ANNOUNCE] LyX 2.0.6 Released

2013-05-09 Thread Richard Heck


On 05/09/2013 12:00 PM, José Matos wrote:

On Thursday 09 May 2013 09:38:01 Richard Heck wrote:

Public release of LyX version 2.0.6

Hi Richard,
note that the press release at http://www.lyx.org/News#item2 still 
refers to the 2.0.5 announcement instead of the 2.0.6 as it should.


Hmm. I see 2.0.6. Cached?

I re-ordered so GSoC is below it now.

Richard

XML Parsing Library [was Re: XML For LyX]

2013-05-09 Thread Richard Heck


On 05/08/2013 06:24 PM, José Matos wrote:

On Wednesday 08 May 2013 17:43:41 Richard Heck wrote:

Thinking ahead, however: Should we use some SAX library to read the XML? Or 
should we just adapt the Lexer for this purpose?

Richard

Lars had that working for a previous version of lyx with lexer. His branches 
are still available in git, I think...


I just had a look at those. He had an XML parser here:
http://www.lyx.org/trac/browser/lyxsvn/lyx-devel/branches/personal/larsbj/xml/src/support/xmlparser.h?rev=19478
but it appears to be based upon xmlpp, which I cannot get to compile on 
my machine. It's a very old library. An older version uses expat, which 
is pretty heavy duty.


I did some googling and found this page:
http://lars.ruoff.free.fr/xmlcpp/
which describes a bunch of free XML libraries and was updated 2/2012. 
Most of what's there is either (a) very large, like Xerces and libxml2, 
or else (b) a DOM-style parser, which is not what we wantm, I think. The 
best of the options appears to be:

http://www.fxtech.com/xmlio/
which is a very lightweight (53KB source) and simple, SAX-like parser. 
LGPL. It is also quite old, but it compiles just fine here. Of course, 
it also writes XML.


It could probably use some updating if we were going to use it, but the 
code is very simple, so this would be easy to do.


Richard

Re: XML Parsing Library [was Re: XML For LyX]

2013-05-09 Thread Rob Oakes




On Thu, May 9, 2013 at 10:52 AM, Richard Heck rgh...@lyx.org wrote:


I just had a look at those. He had an XML parser here:
http://www.lyx.org/trac/browser/lyxsvn/lyx-devel/branches/personal/larsbj/xml/src/support/xmlparser.h?rev=19478
but it appears to be based upon xmlpp, which I cannot get to compile 
on my machine. It's a very old library. An older version uses expat, 
which is pretty heavy duty.


I did some googling and found this page:
http://lars.ruoff.free.fr/xmlcpp/
which describes a bunch of free XML libraries and was updated 2/2012. 
Most of what's there is either (a) very large, like Xerces and 
libxml2, or else (b) a DOM-style parser, which is not what we wantm, 
I think. The best of the options appears to be:

http://www.fxtech.com/xmlio/
which is a very lightweight (53KB source) and simple, SAX-like 
parser. LGPL. It is also quite old, but it compiles just fine here. 
Of course, it also writes XML.


It could probably use some updating if we were going to use it, but 
the code is very simple, so this would be easy to do.


Is there a reason we would want to avoid libxml? I've found it to offer 
the best feature set and ease of use. It also ships with a set of 
excellent Python bindings, which we could incorporate into the Python 
we ship. Between the two, there is very little that wouldn't be 
possible from an XML processing standpoint.


We might even be able to incorporate some of the XSL processing that 
some of the users have been salivating over.

Re: [ANNOUNCE] LyX 2.0.6 Released

2013-05-09 Thread Maria Gouskova

The link to the announcement on that page still points to
http://www.lyx.org/announce/2_0_5.txt (though the page
http://www.lyx.org/announce/2_0_6.txt exists).

On Thu, May 9, 2013 at 12:42 PM, Richard Heck rgh...@lyx.org wrote:

 On 05/09/2013 12:00 PM, José Matos wrote:

 On Thursday 09 May 2013 09:38:01 Richard Heck wrote:

 Public release of LyX version 2.0.6

 Hi Richard,
 note that the press release at http://www.lyx.org/News#item2still 
 refers to the 2.0.5 announcement instead of the 2.0.6 as it should.


 Hmm. I see 2.0.6. Cached?

 I re-ordered so GSoC is below it now.

 Richard

Re: [ANNOUNCE] LyX 2.0.6 Released

2013-05-09 Thread Richard Heck


On 05/09/2013 01:59 PM, Maria Gouskova wrote:
The link to the announcement on that page still points to 
http://www.lyx.org/announce/2_0_5.txt (though the page 
http://www.lyx.org/announce/2_0_6.txt exists).


Oh, I see. Thanks.

rh



On Thu, May 9, 2013 at 12:42 PM, Richard Heck rgh...@lyx.org 
mailto:rgh...@lyx.org wrote:


On 05/09/2013 12:00 PM, José Matos wrote:

On Thursday 09 May 2013 09:38:01 Richard Heck wrote:

Public release of LyX version 2.0.6

Hi Richard,
note that the press release at
http://www.lyx.org/News#item2 still refers to the 2.0.5
announcement instead of the 2.0.6 as it should.


Hmm. I see 2.0.6. Cached?

I re-ordered so GSoC is below it now.

Richard

Re: XML Parsing Library [was Re: XML For LyX]

2013-05-09 Thread Richard Heck

On 05/09/2013 01:39 PM, Rob Oakes wrote:

On Thu, May 9, 2013 at 10:52 AM, Richard Heck rgh...@lyx.org wrote:
I just had a look at those. He had an XML parser here:
http://www.lyx.org/trac/browser/lyxsvn/lyx-devel/branches/personal/larsbj/xml/src/support/xmlparser.h?rev=19478
but it appears to be based upon xmlpp, which I cannot get to compile
on my machine. It's a very old library. An older version uses expat,
which is pretty heavy duty. I did some googling and found this page:
http://lars.ruoff.free.fr/xmlcpp/ which describes a bunch of free XML
libraries and was updated 2/2012. Most of what's there is either (a)
very large, like Xerces and libxml2, or else (b) a DOM-style parser,
which is not what we wantm, I think. The best of the options appears
to be: http://www.fxtech.com/xmlio/ which is a very lightweight (53KB
source) and simple, SAX-like parser. LGPL. It is also quite old, but
it compiles just fine here. Of course, it also writes XML. It could
probably use some updating if we were going to use it, but the code
is very simple, so this would be easy to do.

Is there a reason we would want to avoid libxml? I've found it to
offer the best feature set and ease of use. It also ships with a set
of excellent Python bindings, which we could incorporate into the
Python we ship. Between the two, there is very little that wouldn't be
possible from an XML processing standpoint.

The libxml2 sources, unzipped, are 45MB. The C++ bindings, in libxml++,
are another 7.1MB. That's my main worry. The entire LyX src/ directory
is only 11MB. Something that powerful also feels a bit like overkill for
what we will be doing.

On Linux, of course, it is different. One would just expect this library
already to be installed. But things do not work that way on the other OSs.

Richard

Re: XML Parsing Library [was Re: XML For LyX]

2013-05-09 Thread Pavel Sanda

Richard Heck wrote:
 On Linux, of course, it is different. One would just expect this library 
 already to be installed. But things do not work that way on the other OSs.

I belive we should actually _include_ some leightweight library in our sources
so it is fixed and we do not rely in any versioning problem or avalability
on various architectures.

Pavel

bug on Lyx 2.0.6?

2013-05-09 Thread Nicola Scafetta, Ph. D.

Dear Lyx-develop,

thank you for your update and for the hard work for producing Lyx, which is a 
very useful program.

However, I had some problem that was apparently not present in version 2.0.4 
with the HTML export.

When I use the HTML export a window opens and asks the following question: 
“How do you want to open this type of file (.py)?” 

I do not know what to do. It appears that there is some broken shortcut 
somewhere and nothing happens.


If I compile the file with  LyxHTML, I also have some problem with references 
and table, but these are other unrelated issues.


I am using Windows 8 pro. In Linux no problem exists with HTML export.


I would appreciate if you can give a solution with the HTML export function and 
indicate what I need to do with the “How do you want to open this type of file 
(.py)?” problem.

(Solutions such as “uninstall” and “reinstall”, do not work).

thank you

Nicola

76 matches

Mail list logo