Re: Unit testing: The Small Plan
Hello Cyrille, On Wed, May 8, 2013 at 1:28 AM, Cyrille Artho c.ar...@aist.go.jp wrote: Hi Elmar, I think your plan covers the question HOW do we want to unit test the software well. However, we have not thought much about the WHAT do we want to test? question. Essentially, we need to think about which classes/functions to test first. I think it is not realistic to aim for a high test coverage with software as large as LyX. Unit tests make sense in certain cases and less in others. So we should identify these use cases first, and start with a few selective unit tests. We can then grow them as we see fit. Yes, I share this vision of let the tests grow. That's the reason, why it's only a small plan. A plan can't tell the people what they want to test. It's the decision of the people themself, driven by different motivations. A plan can only leverage. There are at least two questions: * What do I want to test? * What can I test at all, at reasonable costs. When I write new software in other languages, I write code and tests side by side, resulting in a test coverage of approximately 100%, without extra costs, as I need to run the code anyway. Writing tests for existing software, is much more difficult. In the beginning that are extra costs. They pay on the long run by fewer bugs. I have to weight. For user-driven actions (LFUNs), LyX already has a test framework. However, these tests do not cover internals of LyX. Right, unit testing is only one class of testing. That's why it has it's own path tests/unit. Gui testing needs completely different approaches and more support by testing framewoks resulting in tests/gui or similar. Probably there are also tools to cover memory leaks or performance. Which internals do not require a complex sequence of actions (or a complex internal state) to be tested? (Those that do are maybe better covered with other types of tests.) Where has the code changed often in the past, and is expected to change often in the future? What kinds of (internal) functions are often covered by bug reports and thus warrant better test automation? Likely the most error-prone corners are the haredest to tests, because of the same reasons. To get started, I would need to do some more simple cases first. I hope some of the veteran developers can help answer these questions. \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Unit testing: The Small Plan
Hello Cyrille, On Wed, May 8, 2013 at 1:28 AM, Cyrille Artho <c.ar...@aist.go.jp> wrote: > Hi Elmar, > I think your plan covers the question "HOW do we want to unit test the > software" well. However, we have not thought much about the "WHAT do we > want to test?" question. Essentially, we need to think about which > classes/functions to test first. > > I think it is not realistic to aim for a high test coverage with software > as large as LyX. Unit tests make sense in certain cases and less in others. > So we should identify these use cases first, and start with a few selective > unit tests. We can then grow them as we see fit. > > Yes, I share this vision of let the tests grow. That's the reason, why it's only a small plan. A plan can't tell the people what they want to test. It's the decision of the people themself, driven by different motivations. A plan can only leverage. There are at least two questions: * What do I want to test? * What can I test at all, at reasonable costs. When I write new software in other languages, I write code and tests side by side, resulting in a test coverage of approximately 100%, without extra costs, as I need to run the code anyway. Writing tests for existing software, is much more difficult. In the beginning that are extra costs. They pay on the long run by fewer bugs. I have to weight. > For user-driven actions (LFUNs), LyX already has a test framework. > However, these tests do not cover internals of LyX. > > Right, unit testing is only one class of testing. That's why it has it's own path "tests/unit". Gui testing needs completely different approaches and more support by testing framewoks resulting in "tests/gui" or similar. Probably there are also tools to cover memory leaks or performance. > Which internals do not require a complex sequence of actions (or a complex > internal state) to be tested? (Those that do are maybe better covered with > other types of tests.) Where has the code changed often in the past, and is > expected to change often in the future? What kinds of (internal) functions > are often covered by bug reports and thus warrant better test automation? > Likely the most error-prone corners are the haredest to tests, because of the same reasons. To get started, I would need to do some more simple cases first. > > I hope some of the veteran developers can help answer these questions. > > \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Unit testing: The Small Plan
Hello list, I'd like to come up with a small plan for getting started with unit testing: == 1.) Directory structure: tests/unit/ == * Unit tests stay their own directory separated from src/. * Below tests/unit the directory structure mirrors the structure of src/. * The reason for the subfolder unit is, that unit tests are not the only type of tests. Unit tests test the single units of the source. == 2.) Mocking: googlemock == This weekend I researched for alternatives, but there was none that made a stable impression to me apart from googlemock. With C++ mocking can take two approaches: 2.a) Turning classes into Templates, to be able to replace members by mocks. http://programmaticallyspeaking.blogspot.de/2010/04/beautiful-dependency-injection-in-c.html This seems to invasive into the existing sources for me. 2.b) Inheriting the mocks from the real objects, so that they are of the same type. This is the approach of googlemock. Googlemock can be used with any mocking framework. It best integrates with googletest. == 3.) Testing framework: any == Unit tests are independent units, so any framework or none can be used. For the reason of mocks, googletest is recommended. == 4.) Runnig all tests == To be able to run all tests at once they need to be detected. * The naming pattern of the binary to support this: whateverTest * A successful test binary returns 0, the others an Error. * The global test detector and runner is a Python script. == 5.) Dependency injection == Dependency injection (the mock objects) is more difficult with C++ for multiple reasons like the missing garbage collection or reflection. The approach that looks most forward and less intrusive for the sources to me, is to directly access the private members by making them public during testing and only during testing. That is not really kosher, but at least a simple way to get started directly. It is done by use of a simple preprocessor directive: #public_on_testing Once a wall of tests is created to ensure the behaviour of the given API, more skilled approaches can be introduced. \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Unit testing: The Small Plan
On Tue, May 7, 2013 at 9:20 PM, Pavel Sanda sa...@lyx.org wrote: Elmar Hinz wrote: If somebody can give improvements to the plan, it's welcome. I guess people will let you do almost anything what you like in test/* but they will become much more picky when it comes to changes in src/. Perhaps the best way is to try example, post patch here and and look what people think. Pavel Hi Pavel, as long as people don't become picky it's a good sign. They even shouldn't become picky, during big refactoring of the sources. It works in two steps. In the first step you write tests, that prove the existing API is fully functioning. Then you start with new functions or other kind of refactoring. The test bell should immediately ring when something is broken, long before people get picky at all. The drawback may be that people don't notice that you are working until you come out with the new feature. Fotunatly the world is never that perfect. \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Unit testing: The Small Plan
I would like to see some examples of mocking and injection. Thank you, Vincent, I tried to write some tests using the google framework, and started with the Buffer class. This immediately gives you the problem that it is dependent on a large number of other classes. So, this would mean that you have to fake a large part of the LyX codebase. Well yes, actually I would start with the smallest class and do the Buffer class as the last one. I guess it requires a lot of experiance to tame that. Then I tried to link against all libraries of LyX, but then I ran into problems that the application was not initialized (e.g., Package, translations etc.) I'm afraid we can't do much testing until the above is solved. So a few tests already brought up a vision of what need to be solved. That's exactly their most important strength. They are a perfect teacher. Here we find out how everything currently depends on everything. We couldn't even take a little piece out, to use it as a library for something completly different. Regards \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Unit testing: The Small Plan
Ideally, one would not need to care about private variables because we are only interested in that the public interface does what it is supposed to do. Right ? Yes, at least as far as it concerns the testing. Denpendency Injection has other aspects. As an example, if there is a class that prints to stdout you mayby would not test that, taking it as an interal behaviour. With DI you inject the output stream, with the result that you can use different printers in future. Lyx already does this in many caes. Exactly that is dependancy injection. Now you could drop in a MockStream to prove that the class uses the stream object like expacted. Regards \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Unit testing: The Small Plan
Hello list, I'd like to come up with a small plan for getting started with unit testing: == 1.) Directory structure: "tests/unit/" == * Unit tests stay their own directory separated from src/. * Below "tests/unit" the directory structure mirrors the structure of "src/". * The reason for the subfolder "unit" is, that unit tests are not the only type of tests. Unit tests test the single units of the source. == 2.) Mocking: googlemock == This weekend I researched for alternatives, but there was none that made a stable impression to me apart from googlemock. With C++ mocking can take two approaches: 2.a) Turning classes into Templates, to be able to replace members by mocks. http://programmaticallyspeaking.blogspot.de/2010/04/beautiful-dependency-injection-in-c.html This seems to invasive into the existing sources for me. 2.b) Inheriting the mocks from the real objects, so that they are of the same type. This is the approach of googlemock. Googlemock can be used with any mocking framework. It best integrates with googletest. == 3.) Testing framework: any == Unit tests are independent units, so any framework or none can be used. For the reason of mocks, googletest is recommended. == 4.) Runnig all tests == To be able to run all tests at once they need to be detected. * The naming pattern of the binary to support this: whateverTest * A successful test binary returns 0, the others an Error. * The global test detector and runner is a Python script. == 5.) Dependency injection == Dependency injection (the mock objects) is more difficult with C++ for multiple reasons like the missing garbage collection or reflection. The approach that looks most forward and less intrusive for the sources to me, is to directly access the private members by making them public during testing and only during testing. That is not really kosher, but at least a simple way to get started directly. It is done by use of a simple preprocessor directive: #public_on_testing Once a wall of tests is created to ensure the behaviour of the given API, more skilled approaches can be introduced. \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Unit testing: The Small Plan
On Tue, May 7, 2013 at 9:20 PM, Pavel Sanda <sa...@lyx.org> wrote: > Elmar Hinz wrote: > > If somebody can give improvements to the plan, it's welcome. > > I guess people will let you do almost anything what you like in test/* > but they will become much more picky when it comes to changes in src/. > Perhaps the best way is to try example, post patch here and > and look what people think. > > Pavel > Hi Pavel, as long as people don't become picky it's a good sign. They even shouldn't become picky, during big refactoring of the sources. It works in two steps. In the first step you write tests, that prove the existing API is fully functioning. Then you start with new functions or other kind of refactoring. The test bell should immediately ring when something is broken, long before people get picky at all. The drawback may be that people don't notice that you are working until you come out with the new feature. Fotunatly the world is never that perfect. \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Unit testing: The Small Plan
> I would like to see some examples of mocking and injection. > > Thank you, Vincent, > I tried to write some tests using the google framework, and started with > the Buffer class. This immediately gives you the problem that it is > dependent on a large number of other classes. So, this would mean that you > have to fake a large part of the LyX codebase. > Well yes, actually I would start with the smallest class and do the Buffer class as the last one. I guess it requires a lot of experiance to tame that. > Then I tried to link against all libraries of LyX, but then I ran into > problems that the application was not initialized (e.g., Package, > translations etc.) > > I'm afraid we can't do much testing until the above is solved. > So a few tests already brought up a vision of what need to be solved. That's exactly their most important strength. They are a perfect teacher. Here we find out how everything currently depends on everything. We couldn't even take a little piece out, to use it as a library for something completly different. Regards \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Unit testing: The Small Plan
> Ideally, one would not need to care about private variables because we are only interested in that the public interface does what it is supposed to do. Right ? Yes, at least as far as it concerns the testing. Denpendency Injection has other aspects. As an example, if there is a class that prints to stdout you mayby would not test that, taking it as an "interal" behaviour. With DI you inject the output stream, with the result that you can use different printers in future. Lyx already does this in many caes. Exactly that is dependancy injection. Now you could drop in a MockStream to prove that the class uses the stream object like expacted. Regards \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Best practive for dependency incjection
Hello list, I am used to test the code I while I am writing it. The big advantage is, that the code is quality tested. The immediate advantage is, that it gives a simple method to run the code, to see how it works at all, without firering up the whole application. Being new with C++ I try to transfer this approach from other languages like Java or Ruby. Depencency injection is important, to be able to replace dependencies by mock objects. However with C++ it is necessary to mangage the memory usage. For dependency injection this brings up the question, when and where to free the memory. Do you have a policy how to deal with this for Lyx in special and is there a good tutorial how to handle that with C++ in general? THX \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Best practive for dependency incjection
Hello Pavel. IIRC there were few discussions but no one ever came with realistic plan. I don't think it needs a big plan at all. Each test is independed, so you can even mix tests from different frameworks. Also testing has already been started. Simply proceed instead of big plans. Especially the sources are completely independet from the tests and should be. The important point is, that testing leads to restructure the source step by step in the spirit of more independency of each class. That makes them better maintainable and reusable. Because of this independence of the tests from the sources it makes sense to put the tests in it's own directory tree: src/go/here/ tests/unit/go/here/ tests/behaviour/go/here/ tests/integration/go/here/ I will evaluate if it's possible to move the existing tests out of the sources as on of the next steps. Regards \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Best practive for dependency incjection
On Mon, May 6, 2013 at 11:27 AM, Pavel Sanda sa...@lyx.org wrote: Elmar Hinz wrote: The important point is, that testing leads to restructure the source step by step in the spirit of more independency of each class. That restructure is probably what I called plans if I understand your aim... P The little difference is, that I would take the path of wild growing instead of big plans in the case of testing. The reason is, that I trust in self optimization, that inherits testing. It's the permanent search for the best solution. To work with big plans, you need strong organization. That can be conserved for other matters, where it is more in need. :) \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Best practive for dependency incjection
Hello list, I am used to test the code I while I am writing it. The big advantage is, that the code is quality tested. The immediate advantage is, that it gives a simple method to run the code, to see how it works at all, without firering up the whole application. Being new with C++ I try to transfer this approach from other languages like Java or Ruby. Depencency injection is important, to be able to replace dependencies by mock objects. However with C++ it is necessary to mangage the memory usage. For dependency injection this brings up the question, when and where to free the memory. Do you have a policy how to deal with this for Lyx in special and is there a good tutorial how to handle that with C++ in general? THX \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Best practive for dependency incjection
Hello Pavel. IIRC there were few discussions but no one ever came with realistic plan. > I don't think it needs a big plan at all. Each test is independed, so you can even mix tests from different frameworks. Also testing has already been started. Simply proceed instead of big plans. Especially the sources are completely independet from the tests and should be. The important point is, that testing leads to restructure the source step by step in the spirit of more independency of each class. That makes them better maintainable and reusable. Because of this independence of the tests from the sources it makes sense to put the tests in it's own directory tree: src/go/here/ tests/unit/go/here/ tests/behaviour/go/here/ tests/integration/go/here/ I will evaluate if it's possible to move the existing tests out of the sources as on of the next steps. Regards \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Best practive for dependency incjection
On Mon, May 6, 2013 at 11:27 AM, Pavel Sanda <sa...@lyx.org> wrote: > Elmar Hinz wrote: > > The important point is, that testing leads to restructure the source > step by > > step in the spirit of more independency of each class. > > That "restructure" is probably what I called plans if I understand your > aim... > P > The little difference is, that I would take the path of "wild growing" instead of big plans in the case of testing. The reason is, that I trust in self optimization, that inherits testing. It's the permanent search for the best solution. To work with big plans, you need strong organization. That can be conserved for other matters, where it is more in need. :) \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Give me some bug please
I set up my own LyX-mirror on github: https://github.com/t3elmar/Lyx By mirror do you mean that it will be updated automatically? Nope, not a real mirror. It's just the master branch and it's updated when I play with lyx. I plan to use the repository to present my sketches, before gaining enough reputation to send them in. Now I would like to fix some bugs. I have some buglettes in random notes that I wanted to eventually look at. I told someone else that I would organize them and post them. I will try to do that soon. I will put the 'easyfix' keyword on them in trac. These will be bugs that I think I will be able to guide someone to fixing if they get stuck. I am sure that there will be several that I misjudged and that are actually complicated bugs. But either (1) you'll learn stuff anyway or (2) someone will let us know that a bug is probably not an 'easyfix'. I'll try to do this within the next week. Still interested in this. \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Give me some bug please
> I set up my own LyX-mirror on github: https://github.com/t3elmar/Lyx > By mirror do you mean that it will be updated automatically? > Nope, not a real mirror. It's just the master branch and it's updated when I play with lyx. I plan to use the repository to present my sketches, before gaining enough reputation to send them in. > Now I would like to fix some bugs. > > I have some buglettes in random notes that I wanted to eventually look > at. I told someone else that I would organize them and post them. I > will try to do that soon. I will put the 'easyfix' keyword on them in > trac. These will be bugs that I think I will be able to guide someone > to fixing if they get stuck. I am sure that there will be several that > I misjudged and that are actually complicated bugs. But either (1) > you'll learn stuff anyway or (2) someone will let us know that a bug > is probably not an 'easyfix'. I'll try to do this within the next > week. > > Still interested in this. \Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: SVN in the Wiki
What pages? The search says this pages (55). I was woundering, if I should change some, while reading the wiki. Elmar Results of search for * list=LyX svn*: BibTeX http://wiki.lyx.org/BibTeX/BibTeX / Publist http://wiki.lyx.org/BibTeX/Publist Devel http://wiki.lyx.org/Devel/Devel / Administration http://wiki.lyx.org/Devel/Administration Advsearch http://wiki.lyx.org/Devel/Advsearch BuglistsForLyX150 http://wiki.lyx.org/Devel/BuglistsForLyX150 BuglistsForTrunk http://wiki.lyx.org/Devel/BuglistsForTrunk BuildSystemSpecificationshttp://wiki.lyx.org/Devel/BuildSystemSpecifications BundleRoadmap http://wiki.lyx.org/Devel/BundleRoadmap BundleSuggestions http://wiki.lyx.org/Devel/BundleSuggestions ChangeLogs http://wiki.lyx.org/Devel/ChangeLogs Collaboration http://wiki.lyx.org/Devel/Collaboration Cursor http://wiki.lyx.org/Devel/Cursor Devel http://wiki.lyx.org/Devel/Devel Git http://wiki.lyx.org/Devel/Git GSoC2008 http://wiki.lyx.org/Devel/GSoC2008 GSoC2011ApplicationTemplatehttp://wiki.lyx.org/Devel/GSoC2011ApplicationTemplate Guidelines http://wiki.lyx.org/Devel/Guidelines Hunspell http://wiki.lyx.org/Devel/Hunspell JoostInstallerNotes http://wiki.lyx.org/Devel/JoostInstallerNotes LyXFileFormat http://wiki.lyx.org/Devel/LyXFileFormat Macros http://wiki.lyx.org/Devel/Macros NotesOnPatchProcess http://wiki.lyx.org/Devel/NotesOnPatchProcess POFAQ http://wiki.lyx.org/Devel/POFAQ RecentChanges http://wiki.lyx.org/Devel/RecentChanges RegressionListSVN http://wiki.lyx.org/Devel/RegressionListSVN ReleaseProcedure http://wiki.lyx.org/Devel/ReleaseProcedure SourceCodeExploration http://wiki.lyx.org/Devel/SourceCodeExploration Statistics http://wiki.lyx.org/Devel/Statistics Subversion http://wiki.lyx.org/Devel/Subversion Tips http://wiki.lyx.org/Devel/Tips UweInstallerNotes http://wiki.lyx.org/Devel/UweInstallerNotes WindowsInstallerPlan http://wiki.lyx.org/Devel/WindowsInstallerPlan FAQ http://wiki.lyx.org/FAQ/FAQ / FurtherHelp http://wiki.lyx.org/FAQ/FurtherHelp Field http://wiki.lyx.org/Field/Field / AllRecentChanges http://wiki.lyx.org/Field/AllRecentChanges LaTeX http://wiki.lyx.org/LaTeX/LaTeX / LatexBugs http://wiki.lyx.org/LaTeX/LatexBugs LyX http://wiki.lyx.org/LyX/LyX / Complaints http://wiki.lyx.org/LyX/Complaints Download http://wiki.lyx.org/LyX/Download FeaturePoll1 http://wiki.lyx.org/LyX/FeaturePoll1 LyxFunctions http://wiki.lyx.org/LyX/LyxFunctions LyXOnCygwin http://wiki.lyx.org/LyX/LyXOnCygwin LyXOnDebian http://wiki.lyx.org/LyX/LyXOnDebian LyXOnUbuntu http://wiki.lyx.org/LyX/LyXOnUbuntu LyXVsScientificWorkplace http://wiki.lyx.org/LyX/LyXVsScientificWorkplace NewInLyX16 http://wiki.lyx.org/LyX/NewInLyX16 NewInLyX20 http://wiki.lyx.org/LyX/NewInLyX20 NewInLyX21 http://wiki.lyx.org/LyX/NewInLyX21 Presentations http://wiki.lyx.org/LyX/Presentations SystemDir http://wiki.lyx.org/LyX/SystemDir UserDir http://wiki.lyx.org/LyX/UserDir PersonalChr http://wiki.lyx.org/PersonalChr/PersonalChr / CompileFromSVN http://wiki.lyx.org/PersonalChr/CompileFromSVN RecentChanges http://wiki.lyx.org/PersonalChr/RecentChanges Site http://wiki.lyx.org/Site/Site / AllRecentChanges http://wiki.lyx.org/Site/AllRecentChanges InterMap http://wiki.lyx.org/Site/InterMap Tips http://wiki.lyx.org/Tips/Tips / Compiling http://wiki.lyx.org/Tips/Compiling CorrectingSplitSubversionKeywordshttp://wiki.lyx.org/Tips/CorrectingSplitSubversionKeywords UseInkscapeSVGImages http://wiki.lyx.org/Tips/UseInkscapeSVGImages 55 pages found out of 804 pages searched. -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: SVN in the Wiki
> What pages? The search says this pages (55). I was woundering, if I should change some, while reading the wiki. Elmar Results of search for * list=LyX svn*: BibTeX <http://wiki.lyx.org/BibTeX/BibTeX> / Publist <http://wiki.lyx.org/BibTeX/Publist> Devel <http://wiki.lyx.org/Devel/Devel> / Administration <http://wiki.lyx.org/Devel/Administration> Advsearch <http://wiki.lyx.org/Devel/Advsearch> BuglistsForLyX150 <http://wiki.lyx.org/Devel/BuglistsForLyX150> BuglistsForTrunk <http://wiki.lyx.org/Devel/BuglistsForTrunk> BuildSystemSpecifications<http://wiki.lyx.org/Devel/BuildSystemSpecifications> BundleRoadmap <http://wiki.lyx.org/Devel/BundleRoadmap> BundleSuggestions <http://wiki.lyx.org/Devel/BundleSuggestions> ChangeLogs <http://wiki.lyx.org/Devel/ChangeLogs> Collaboration <http://wiki.lyx.org/Devel/Collaboration> Cursor <http://wiki.lyx.org/Devel/Cursor> Devel <http://wiki.lyx.org/Devel/Devel> Git <http://wiki.lyx.org/Devel/Git> GSoC2008 <http://wiki.lyx.org/Devel/GSoC2008> GSoC2011ApplicationTemplate<http://wiki.lyx.org/Devel/GSoC2011ApplicationTemplate> Guidelines <http://wiki.lyx.org/Devel/Guidelines> Hunspell <http://wiki.lyx.org/Devel/Hunspell> JoostInstallerNotes <http://wiki.lyx.org/Devel/JoostInstallerNotes> LyXFileFormat <http://wiki.lyx.org/Devel/LyXFileFormat> Macros <http://wiki.lyx.org/Devel/Macros> NotesOnPatchProcess <http://wiki.lyx.org/Devel/NotesOnPatchProcess> POFAQ <http://wiki.lyx.org/Devel/POFAQ> RecentChanges <http://wiki.lyx.org/Devel/RecentChanges> RegressionListSVN <http://wiki.lyx.org/Devel/RegressionListSVN> ReleaseProcedure <http://wiki.lyx.org/Devel/ReleaseProcedure> SourceCodeExploration <http://wiki.lyx.org/Devel/SourceCodeExploration> Statistics <http://wiki.lyx.org/Devel/Statistics> Subversion <http://wiki.lyx.org/Devel/Subversion> Tips <http://wiki.lyx.org/Devel/Tips> UweInstallerNotes <http://wiki.lyx.org/Devel/UweInstallerNotes> WindowsInstallerPlan <http://wiki.lyx.org/Devel/WindowsInstallerPlan> FAQ <http://wiki.lyx.org/FAQ/FAQ> / FurtherHelp <http://wiki.lyx.org/FAQ/FurtherHelp> Field <http://wiki.lyx.org/Field/Field> / AllRecentChanges <http://wiki.lyx.org/Field/AllRecentChanges> LaTeX <http://wiki.lyx.org/LaTeX/LaTeX> / LatexBugs <http://wiki.lyx.org/LaTeX/LatexBugs> LyX <http://wiki.lyx.org/LyX/LyX> / Complaints <http://wiki.lyx.org/LyX/Complaints> Download <http://wiki.lyx.org/LyX/Download> FeaturePoll1 <http://wiki.lyx.org/LyX/FeaturePoll1> LyxFunctions <http://wiki.lyx.org/LyX/LyxFunctions> LyXOnCygwin <http://wiki.lyx.org/LyX/LyXOnCygwin> LyXOnDebian <http://wiki.lyx.org/LyX/LyXOnDebian> LyXOnUbuntu <http://wiki.lyx.org/LyX/LyXOnUbuntu> LyXVsScientificWorkplace <http://wiki.lyx.org/LyX/LyXVsScientificWorkplace> NewInLyX16 <http://wiki.lyx.org/LyX/NewInLyX16> NewInLyX20 <http://wiki.lyx.org/LyX/NewInLyX20> NewInLyX21 <http://wiki.lyx.org/LyX/NewInLyX21> Presentations <http://wiki.lyx.org/LyX/Presentations> SystemDir <http://wiki.lyx.org/LyX/SystemDir> UserDir <http://wiki.lyx.org/LyX/UserDir> PersonalChr <http://wiki.lyx.org/PersonalChr/PersonalChr> / CompileFromSVN <http://wiki.lyx.org/PersonalChr/CompileFromSVN> RecentChanges <http://wiki.lyx.org/PersonalChr/RecentChanges> Site <http://wiki.lyx.org/Site/Site> / AllRecentChanges <http://wiki.lyx.org/Site/AllRecentChanges> InterMap <http://wiki.lyx.org/Site/InterMap> Tips <http://wiki.lyx.org/Tips/Tips> / Compiling <http://wiki.lyx.org/Tips/Compiling> CorrectingSplitSubversionKeywords<http://wiki.lyx.org/Tips/CorrectingSplitSubversionKeywords> UseInkscapeSVGImages <http://wiki.lyx.org/Tips/UseInkscapeSVGImages> 55 pages found out of 804 pages searched. -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Git Cloning Error
Hello, I created a kind of mirror of the master branch on github. You may try if it makes a difference to clone from that. https://github.com/t3elmar/Lyx Elmar You may try to On Fri, Apr 26, 2013 at 7:56 PM, Abhishek Sharma abhios...@gmail.comwrote: Hello I'm having problem on cloning git through the command git clone git://git.lyx.org/lyxas mentioned on the official site. the error I get is this $ git clone git://git.lyx.org/lyx Cloning into 'lyx'... error: Proxy CONNECT aborted while accessing https://git.lyx.org/lyx/info/refs fatal: HTTP request failed My college uses cyberoam as a filter to web. Also, we work through a proxy: http://172.16.73.12:3128 Hence, I tried adding this proxy to git as follows: $ export http_proxy=http://172.16.73.12:3128 $ git config --global http.proxy $http_proxy But still the same error remains. Kindly help me with this issue. Yours sincerely Abhishek -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Git Cloning Error
Hello, I created a kind of mirror of the master branch on github. You may try if it makes a difference to clone from that. https://github.com/t3elmar/Lyx Elmar You may try to On Fri, Apr 26, 2013 at 7:56 PM, Abhishek Sharma <abhios...@gmail.com>wrote: > Hello > > I'm having problem on cloning git through the command > > git clone git://git.lyx.org/lyxas mentioned on > the official site. > > the error I get is this > > $ git clone git://git.lyx.org/lyx > Cloning into 'lyx'... > error: Proxy CONNECT aborted while accessing > https://git.lyx.org/lyx/info/refs > fatal: HTTP request failed > > My college uses cyberoam as a filter to web. > Also, we work through a proxy: http://172.16.73.12:3128 > > Hence, I tried adding this proxy to git as follows: > $ export http_proxy=http://172.16.73.12:3128 > $ git config --global http.proxy $http_proxy > > But still the same error remains. > > Kindly help me with this issue. > > Yours sincerely > Abhishek > -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Directory layout for unit tests
/insets/ExternalTransforms.cpp 436 src/Session.cpp 437 src/graphics/GraphicsCacheItem.cpp 439 src/frontends/qt4/GuiCharacter.cpp 446 src/insets/InsetListings.cpp 448 src/LyXVC.cpp 451 src/HunspellChecker.cpp 454 src/insets/InsetCitation.cpp 456 src/frontends/qt4/GuiBox.cpp 459 src/Length.cpp 461 src/graphics/GraphicsLoader.cpp 464 src/ConverterCache.cpp 468 src/support/os_cygwin.cpp 479 src/insets/InsetInfo.cpp 480 src/frontends/qt4/GuiSymbols.cpp 495 src/insets/InsetCommandParams.cpp 510 src/Changes.cpp 512 src/mathed/InsetMathSideset.cpp 526 src/frontends/qt4/TocWidget.cpp 528 src/frontends/qt4/GuiRef.cpp 528 src/insets/InsetFloat.cpp 539 src/LaTeXFonts.cpp 542 src/insets/ExternalSupport.cpp 548 src/AspellChecker.cpp 554 src/frontends/qt4/GuiBibtex.cpp 570 src/KeyMap.cpp 573 src/insets/ExternalTemplate.cpp 581 src/frontends/qt4/GuiClipboard.cpp 587 src/Undo.cpp 592 src/frontends/qt4/CategorizedCombo.cpp 599 src/frontends/qt4/FindAndReplace.cpp 606 src/frontends/qt4/qt_helpers.cpp 606 src/mathed/MathFactory.cpp 609 src/frontends/qt4/GuiPainter.cpp 620 src/insets/InsetLayout.cpp 627 src/frontends/qt4/GuiSpellchecker.cpp 629 src/support/Systemcall.cpp 633 src/support/docstream.cpp 634 src/insets/InsetIPAMacro.cpp 646 src/Counters.cpp 650 src/frontends/qt4/GuiListings.cpp 650 src/insets/Inset.cpp 654 src/insets/InsetCollapsable.cpp 656 src/DocIterator.cpp 658 src/frontends/qt4/GuiExternal.cpp 662 src/support/os_win32.cpp 674 src/factory.cpp 674 src/insets/InsetBox.cpp 677 src/Trans.cpp 689 src/client/client.cpp 690 src/mathed/MathStream.cpp 691 src/support/ForkedCalls.cpp 695 src/FontInfo.cpp 720 src/frontends/qt4/LayoutBox.cpp 727 src/mathed/InsetMathFrac.cpp 753 src/Font.cpp 763 src/frontends/qt4/GuiKeySymbol.cpp 766 src/support/Package.cpp 769 src/frontends/qt4/ButtonPolicy.cpp 769 src/graphics/PreviewLoader.cpp 778 src/frontends/qt4/GuiCitation.cpp 790 src/mathed/InsetMathScript.cpp 796 src/mathed/MathSupport.cpp 817 src/Converter.cpp 829 src/tex2lyx/Parser.cpp 834 src/support/docstring.cpp 841 src/Format.cpp 845 src/frontends/qt4/GuiGraphics.cpp 861 src/insets/InsetExternal.cpp 866 src/Compare.cpp 869 src/insets/InsetIndex.cpp 888 src/insets/InsetSpace.cpp 897 src/insets/InsetListingsParams.cpp 907 src/frontends/qt4/GuiCompleter.cpp 910 src/mathed/MathMacro.cpp 966 src/Lexer.cpp 974 src/Text2.cpp 975 src/mathed/MathData.cpp 1008 src/support/FileName.cpp 1025 src/frontends/qt4/GuiTabular.cpp 1026 src/insets/InsetBibtex.cpp 1046 src/insets/InsetText.cpp 1047 src/output_xhtml.cpp 1069 src/support/filetools.cpp 1092 src/BiblioInfo.cpp 1096 src/rowpainter.cpp 1127 src/tex2lyx/tex2lyx.cpp 1189 src/insets/InsetGraphics.cpp 1191 src/insets/InsetInclude.cpp 1194 src/Encoding.cpp 1216 src/Server.cpp 1262 src/LaTeX.cpp 1282 src/output_latex.cpp 1344 src/CutAndPaste.cpp 1374 src/mathed/MathMacroTemplate.cpp 1416 src/tex2lyx/table.cpp 1445 src/support/lstrings.cpp 1474 src/LyX.cpp 1523 src/Layout.cpp 1526 src/mathed/MathExtern.cpp 1530 src/lyxfind.cpp 1590 src/mathed/InsetMathGrid.cpp 1637 src/TextClass.cpp 1682 src/LaTeXFeatures.cpp 1929 src/tex2lyx/Preamble.cpp 2105 src/frontends/qt4/GuiWorkArea.cpp 2110 src/mathed/MathParser.cpp 2132 src/Text.cpp 2205 src/mathed/InsetMathNest.cpp 2252 src/VCBackend.cpp 2253 src/TextMetrics.cpp 2271 src/mathed/InsetMathHull.cpp 2305 src/frontends/qt4/Menus.cpp 2555 src/Cursor.cpp 2867 src/frontends/qt4/GuiApplication.cpp 3006 src/BufferParams.cpp 3071 src/Text3.cpp 3123 src/BufferView.cpp 3462 src/frontends/qt4/GuiPrefs.cpp 3517 src/LyXRC.cpp 3759 src/LyXAction.cpp 3898 src/frontends/qt4/GuiDocument.cpp 3965 src/Paragraph.cpp 4219 src/frontends/qt4/GuiView.cpp 4763 src/tex2lyx/text.cpp 4803 src/Buffer.cpp 6403 src/insets/InsetTabular.cpp -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Directory layout for unit tests
/insets/ExternalTransforms.cpp 436 src/Session.cpp 437 src/graphics/GraphicsCacheItem.cpp 439 src/frontends/qt4/GuiCharacter.cpp 446 src/insets/InsetListings.cpp 448 src/LyXVC.cpp 451 src/HunspellChecker.cpp 454 src/insets/InsetCitation.cpp 456 src/frontends/qt4/GuiBox.cpp 459 src/Length.cpp 461 src/graphics/GraphicsLoader.cpp 464 src/ConverterCache.cpp 468 src/support/os_cygwin.cpp 479 src/insets/InsetInfo.cpp 480 src/frontends/qt4/GuiSymbols.cpp 495 src/insets/InsetCommandParams.cpp 510 src/Changes.cpp 512 src/mathed/InsetMathSideset.cpp 526 src/frontends/qt4/TocWidget.cpp 528 src/frontends/qt4/GuiRef.cpp 528 src/insets/InsetFloat.cpp 539 src/LaTeXFonts.cpp 542 src/insets/ExternalSupport.cpp 548 src/AspellChecker.cpp 554 src/frontends/qt4/GuiBibtex.cpp 570 src/KeyMap.cpp 573 src/insets/ExternalTemplate.cpp 581 src/frontends/qt4/GuiClipboard.cpp 587 src/Undo.cpp 592 src/frontends/qt4/CategorizedCombo.cpp 599 src/frontends/qt4/FindAndReplace.cpp 606 src/frontends/qt4/qt_helpers.cpp 606 src/mathed/MathFactory.cpp 609 src/frontends/qt4/GuiPainter.cpp 620 src/insets/InsetLayout.cpp 627 src/frontends/qt4/GuiSpellchecker.cpp 629 src/support/Systemcall.cpp 633 src/support/docstream.cpp 634 src/insets/InsetIPAMacro.cpp 646 src/Counters.cpp 650 src/frontends/qt4/GuiListings.cpp 650 src/insets/Inset.cpp 654 src/insets/InsetCollapsable.cpp 656 src/DocIterator.cpp 658 src/frontends/qt4/GuiExternal.cpp 662 src/support/os_win32.cpp 674 src/factory.cpp 674 src/insets/InsetBox.cpp 677 src/Trans.cpp 689 src/client/client.cpp 690 src/mathed/MathStream.cpp 691 src/support/ForkedCalls.cpp 695 src/FontInfo.cpp 720 src/frontends/qt4/LayoutBox.cpp 727 src/mathed/InsetMathFrac.cpp 753 src/Font.cpp 763 src/frontends/qt4/GuiKeySymbol.cpp 766 src/support/Package.cpp 769 src/frontends/qt4/ButtonPolicy.cpp 769 src/graphics/PreviewLoader.cpp 778 src/frontends/qt4/GuiCitation.cpp 790 src/mathed/InsetMathScript.cpp 796 src/mathed/MathSupport.cpp 817 src/Converter.cpp 829 src/tex2lyx/Parser.cpp 834 src/support/docstring.cpp 841 src/Format.cpp 845 src/frontends/qt4/GuiGraphics.cpp 861 src/insets/InsetExternal.cpp 866 src/Compare.cpp 869 src/insets/InsetIndex.cpp 888 src/insets/InsetSpace.cpp 897 src/insets/InsetListingsParams.cpp 907 src/frontends/qt4/GuiCompleter.cpp 910 src/mathed/MathMacro.cpp 966 src/Lexer.cpp 974 src/Text2.cpp 975 src/mathed/MathData.cpp 1008 src/support/FileName.cpp 1025 src/frontends/qt4/GuiTabular.cpp 1026 src/insets/InsetBibtex.cpp 1046 src/insets/InsetText.cpp 1047 src/output_xhtml.cpp 1069 src/support/filetools.cpp 1092 src/BiblioInfo.cpp 1096 src/rowpainter.cpp 1127 src/tex2lyx/tex2lyx.cpp 1189 src/insets/InsetGraphics.cpp 1191 src/insets/InsetInclude.cpp 1194 src/Encoding.cpp 1216 src/Server.cpp 1262 src/LaTeX.cpp 1282 src/output_latex.cpp 1344 src/CutAndPaste.cpp 1374 src/mathed/MathMacroTemplate.cpp 1416 src/tex2lyx/table.cpp 1445 src/support/lstrings.cpp 1474 src/LyX.cpp 1523 src/Layout.cpp 1526 src/mathed/MathExtern.cpp 1530 src/lyxfind.cpp 1590 src/mathed/InsetMathGrid.cpp 1637 src/TextClass.cpp 1682 src/LaTeXFeatures.cpp 1929 src/tex2lyx/Preamble.cpp 2105 src/frontends/qt4/GuiWorkArea.cpp 2110 src/mathed/MathParser.cpp 2132 src/Text.cpp 2205 src/mathed/InsetMathNest.cpp 2252 src/VCBackend.cpp 2253 src/TextMetrics.cpp 2271 src/mathed/InsetMathHull.cpp 2305 src/frontends/qt4/Menus.cpp 2555 src/Cursor.cpp 2867 src/frontends/qt4/GuiApplication.cpp 3006 src/BufferParams.cpp 3071 src/Text3.cpp 3123 src/BufferView.cpp 3462 src/frontends/qt4/GuiPrefs.cpp 3517 src/LyXRC.cpp 3759 src/LyXAction.cpp 3898 src/frontends/qt4/GuiDocument.cpp 3965 src/Paragraph.cpp 4219 src/frontends/qt4/GuiView.cpp 4763 src/tex2lyx/text.cpp 4803 src/Buffer.cpp 6403 src/insets/InsetTabular.cpp -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Directory layout for unit tests
Hello, Scott Kostyshak skost...@lyx.org was interested in unit tests. For me working with unit tests is the most simple way to fix a bug, as I only need to focus on the iussue, without running the rest of the system. As a proof of concept I testet the googletest framework today. It is controlled by cmake. I think my little test is self-explanatory. Simple clone it from github. Four lines on the shell: git clone https://github.com/t3elmar/Playground.Cpp.git cd Playground.Cpp/GettingStartedWithGTest/2.directoryLayout/ chmod +x HOWTO.sh ./HOWTO.sh Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Directory layout for unit tests
Hello, Scott Kostyshak <skost...@lyx.org> was interested in unit tests. For me working with unit tests is the most simple way to fix a bug, as I only need to focus on the iussue, without running the rest of the system. As a proof of concept I testet the googletest framework today. It is controlled by cmake. I think my little test is self-explanatory. Simple clone it from github. Four lines on the shell: git clone https://github.com/t3elmar/Playground.Cpp.git cd Playground.Cpp/GettingStartedWithGTest/2.directoryLayout/ chmod +x HOWTO.sh ./HOWTO.sh Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
SVN in the Wiki
Hello, in the wiki i find entries related to SVN. Are they obsolete or is there still a SVN repository? Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Give me some bug please
Hello, I practiced to complie the code with cmake. I set up my own LyX-mirror on github: https://github.com/t3elmar/Lyx Now I would like to fix some bugs. I am experienced with OOP and design patterns. I am not experienced with C++. Hence it should be some rather easy bugs just to get started. By the way, I is there an infrastucture for unit tests? Thanks Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Mac OS X 10.7.5: First copying QT libs then conflicting
Hello, there is still one issue to solve with compiling on OS X. I compile LyX with the prebuild QT libraries (framework). I don't compile QT itself. When I build the package the QT libraries are copied into the build. Now, when I start the application it first warns that it is not certain which of the libraries it will use, the original or the copy. Then it breaks because the same object was loaded twice with different IDs. I can solve this be removing the original library. My compiled application itself is working. What setting do I need to prohibt this confilct, when I have QT twice, once in the system, once in the build? Thank you Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Current master breaks
Hello, when I try to compile Lyx the latest version (and some older ones) breaks: BREAKING: commit d243e53f54e861c90ce7135f3d1a8d68d6202555 Author: Jean-Marc Lasgouttes lasgout...@lyx.org Date: Sat Apr 27 20:14:43 2013 +0200 Another assertion that got transformed in 1b1f8dd2 ERROR: /Users/elmar/lyx/src/insets/InsetCommandParams.cpp:87:25: error: default initialization of an object of const type 'const lyx::ParamInfo' requires a user-provided default constructor static const ParamInfo pi; WORKING: commit 88d9f0880626736fe58e90b00fb85f1e7a49c854 Author: Richard Heck rgh...@lyx.org Date: Sun Apr 7 18:11:27 2013 -0400 Add a bunch of comments about the different exceptions. I am to new to this project, to tell if that is a normal behaviour. Just wanted to mention. Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Current master breaks
On Sat, Apr 27, 2013 at 9:25 PM, Jean-Marc Lasgouttes lasgout...@lyx.orgwrote: Le 27/04/2013 21:15, Elmar Hinz a écrit : ERROR: /Users/elmar/lyx/src/insets/**InsetCommandParams.cpp:87:25: error: default initialization of an object of const type 'const lyx::ParamInfo' requires a user-provided default constructor static const ParamInfo pi; I am surprised that my changes can cause such a problem. I do not see that. Are you sure that you do not have local changes? JMarc Hello, no, it's not from today. I can't tell, when it started. I can only tell the the given version from Date: Sun Apr 7 18:11:27 2013 -0400 is still working. Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Give me some bug please
Hello Scott, I have some buglettes in random notes that I wanted to eventually look at. I told someone else that I would organize them and post them. I will try to do that soon. I will put the 'easyfix' keyword on them in trac. These will be bugs that I think I will be able to guide someone to fixing if they get stuck. I am sure that there will be several that I misjudged and that are actually complicated bugs. But either (1) you'll learn stuff anyway or (2) someone will let us know that a bug is probably not an 'easyfix'. I'll try to do this within the next week. Thank you. If you have an idea for implementing a unit test framework, I would be interested. I think it would be a lot of work though and that we aren't ready for it yet. On the contrary. From my experiance it is cheap and simple to get started with unit testing. You don't need to write all the tests at once. All you need to do is two steps: 1.) decide the testing framework i.e. googletesthttp://code.google.com/p/googletest/. 2.) decide the directory layout The directory layout is typically the layout of the sources. Similiar to this: project/src/my/superfeature/superclass.cpp project/tests/unit/my/superfetures/superclassTest.cpp Now everybody can create test classes. With every bugfix a new test is added. Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
SVN in the Wiki
Hello, in the wiki i find entries related to SVN. Are they obsolete or is there still a SVN repository? Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Give me some bug please
Hello, I practiced to complie the code with cmake. I set up my own LyX-mirror on github: https://github.com/t3elmar/Lyx Now I would like to fix some bugs. I am experienced with OOP and design patterns. I am not experienced with C++. Hence it should be some rather easy bugs just to get started. By the way, I is there an infrastucture for unit tests? Thanks Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Mac OS X 10.7.5: First copying QT libs then conflicting
Hello, there is still one issue to solve with compiling on OS X. I compile LyX with the prebuild QT libraries (framework). I don't compile QT itself. When I build the package the QT libraries are copied into the build. Now, when I start the application it first warns that it is not certain which of the libraries it will use, the original or the copy. Then it breaks because the same object was loaded twice with different IDs. I can solve this be removing the original library. My compiled application itself is working. What setting do I need to prohibt this confilct, when I have QT twice, once in the system, once in the build? Thank you Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Current master breaks
Hello, when I try to compile Lyx the latest version (and some older ones) breaks: BREAKING: commit d243e53f54e861c90ce7135f3d1a8d68d6202555 Author: Jean-Marc Lasgouttes <lasgout...@lyx.org> Date: Sat Apr 27 20:14:43 2013 +0200 Another assertion that got transformed in 1b1f8dd2 ERROR: /Users/elmar/lyx/src/insets/InsetCommandParams.cpp:87:25: error: default initialization of an object of const type 'const lyx::ParamInfo' requires a user-provided default constructor static const ParamInfo pi; WORKING: commit 88d9f0880626736fe58e90b00fb85f1e7a49c854 Author: Richard Heck <rgh...@lyx.org> Date: Sun Apr 7 18:11:27 2013 -0400 Add a bunch of comments about the different exceptions. I am to new to this project, to tell if that is a normal behaviour. Just wanted to mention. Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Current master breaks
On Sat, Apr 27, 2013 at 9:25 PM, Jean-Marc Lasgouttes <lasgout...@lyx.org>wrote: > Le 27/04/2013 21:15, Elmar Hinz a écrit : > > ERROR: >> >> /Users/elmar/lyx/src/insets/**InsetCommandParams.cpp:87:25: error: >> default >> initialization of an >>object of const type 'const lyx::ParamInfo' requires a >> user-provided default constructor >> static const ParamInfo pi; >> > > I am surprised that my changes can cause such a problem. I do not see > that. Are you sure that you do not have local changes? > > JMarc > Hello, no, it's not from today. I can't tell, when it started. I can only tell the the given version from Date: Sun Apr 7 18:11:27 2013 -0400 is still working. Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Give me some bug please
Hello Scott, I have some buglettes in random notes that I wanted to eventually look > at. I told someone else that I would organize them and post them. I > will try to do that soon. I will put the 'easyfix' keyword on them in > trac. These will be bugs that I think I will be able to guide someone > to fixing if they get stuck. I am sure that there will be several that > I misjudged and that are actually complicated bugs. But either (1) > you'll learn stuff anyway or (2) someone will let us know that a bug > is probably not an 'easyfix'. I'll try to do this within the next > week. > Thank you. If you have an idea for implementing a unit test framework, I would be > interested. I think it would be a lot of work though and that we > aren't ready for it yet. > On the contrary. From my experiance it is cheap and simple to get started with unit testing. You don't need to write all the tests at once. All you need to do is two steps: 1.) decide the testing framework i.e. googletest<http://code.google.com/p/googletest/>. 2.) decide the directory layout The directory layout is typically the layout of the sources. Similiar to this: project/src/my/superfeature/superclass.cpp project/tests/unit/my/superfetures/superclassTest.cpp Now everybody can create test classes. With every bugfix a new test is added. Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Compiling LyX on Mac OS 10.7.5
Hello, before diving into coding I need to learn how to compile LyX. The documentation for Mac is a little out-of-date, so I try to find my own way. I compiled Qt4 and LyX. The first build did break immediately upon start. Currently I try to compile both with export CPPFLAGS=-arch i386 export LDFLAGS=-arch i386 This will take some time. Any further suggestions required for a contemporary Mac? Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Compiling LyX on Mac OS 10.7.5
here is the command line I use (with cmake, out of source build) in a build directory (different from LyX main directory). It works with QT installed via the QT installer package (not from source): cmake -DLYX_BUNDLE=ON -DLYX_COCOA=ON -DLYX_INSTALL=ON -DLYX_RELEASE=OFF -DLYX_DEBUG=ON PATH_TO_LYX_MAIN_DIRECTORY and then make LyX2.1 (to build the binary only) or make package (to get a mac bundle) Best, Benjamin Hello Benjamin, I did: brew install cmake cmake -DLYX_BUNDLE=ON -DLYX_COCOA=ON -DLYX_INSTALL=ON -DLYX_RELEASE=OFF -DLYX_DEBUG=ON . # = DOT, current dir It is missing libintl.h. Sie issue is mentioned here: http://www.gnu.org/software/gnulib/manual/html_node/libintl_002eh.html It tried to fix it with brew install gettext unforutnatly without success. Any other workaround? Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Compiling LyX on Mac OS 10.7.5
Summary: * QT 4.8.4 installed via the QT installer package (not from source) * brew install cmake * cmake -DLYX_NLS=OFF -DLYX_BUNDLE=ON -DLYX_COCOA=ON -DLYX_INSTALL=ON -DLYX_RELEASE=OFF -DLYX_DEBUG=ON -DLYX_EXTERNAL_LIBINTL=OFF . * make * make install Errors from cmake: CMake Error: Target LyX Info.plist template /Users/elmar/lyx/build/src/../Info.plist could not be found. Errors from make install: -- fixup_bundle -- app='/Users/elmar/lyx/LyX/LyX.app' -- libs='' -- dirs='' -- warning: *NOT* handled - .app directory case... CMake Error at /usr/local/Cellar/cmake/ 2.8.10.2/share/cmake/Modules/BundleUtilities.cmake:668 (message): error: fixup_bundle: not a valid bundle The second one seems to be cased by the first one. The application LyX/LyX.app/Contents/MacOS/LyX is running an looks fine. Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Compiling LyX on Mac OS 10.7.5
The second one seems to be cased by the first one. OK didn't follow the instruction: make LyX2.1 (to build the binary only) or make package (to get a mac bundle) Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Re: Compiling LyX on Mac OS 10.7.5
or prefered: b.) Install the devel package for libc6 (on ubuntu libc6-dev) Elmar Kornel Hello, IMHO there is no libc6 for mac. There is a /usr/lib/libSystem.dylib - libSystem.B.dylib Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Compiling LyX on Mac OS 10.7.5
OK didn't follow the instruction: make LyX2.1 (to build the binary only) or make package (to get a mac bundle) Anyway, That doesn't bring in the missing Info.plist. Question: Why is there no Info.plist in the source? -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Re: Re: Compiling LyX on Mac OS 10.7.5
On Fri, Apr 26, 2013 at 6:29 PM, Kornel Benko kor...@lyx.org wrote: ** Am Freitag, 26. April 2013 um 18:23:56, schrieb Elmar Hinz t3el...@googlemail.com Hello, IMHO there is no libc6 for mac. There is a /usr/lib/libSystem.dylib - libSystem.B.dylib Elmar Is there also a appropriate devel *package*? Kornel I find a _debug* and a _profile* variant: -r-xr-xr-x 1 root wheel 475K 22 Mär 2012 /usr/lib/libSystem.B.dylib -r-xr-xr-x 1 root wheel 475K 12 Apr 2012 /usr/lib/libSystem.B_debug.dylib -r-xr-xr-x 1 root wheel 475K 12 Apr 2012 /usr/lib/libSystem.B_profile.dylib lrwxr-xr-x 1 root wheel17B 22 Mär 2012 /usr/lib/libSystem.dylib - libSystem.B.dylib lrwxr-xr-x 1 root wheel23B 2 Mär 13:51 /usr/lib/libSystem_debug.dylib - libSystem.B_debug.dylib lrwxr-xr-x 1 root wheel25B 2 Mär 13:51 /usr/lib/libSystem_profile.dylib - libSystem.B_profile.dylib However I am new with Mac OS and still can't explain how it handles the stuff we know as libc6 and libc6-dev. This gives start: http://docstore.mik.ua/orelly/unix3/mac/ch05_02.htm For today I wanted to learn how to compile LyX and succeded largeley. Next step is to bring in a patch to learn the workflow of the project. Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Compiling LyX on Mac OS 10.7.5
Hello, before diving into coding I need to learn how to compile LyX. The documentation for Mac is a little out-of-date, so I try to find my own way. I compiled Qt4 and LyX. The first build did break immediately upon start. Currently I try to compile both with export CPPFLAGS="-arch i386" export LDFLAGS="-arch i386" This will take some time. Any further suggestions required for a contemporary Mac? Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Compiling LyX on Mac OS 10.7.5
here is the command line I use (with cmake, out of source build) in a build directory (different from LyX main directory). It works with QT installed via the QT installer package (not from source): > > cmake -DLYX_BUNDLE=ON -DLYX_COCOA=ON -DLYX_INSTALL=ON -DLYX_RELEASE=OFF > -DLYX_DEBUG=ON PATH_TO_LYX_MAIN_DIRECTORY > > and then > > make LyX2.1 (to build the binary only) > or > make package (to get a mac bundle) > > Best, > Benjamin > Hello Benjamin, I did: > brew install cmake > cmake -DLYX_BUNDLE=ON -DLYX_COCOA=ON -DLYX_INSTALL=ON -DLYX_RELEASE=OFF -DLYX_DEBUG=ON . # <= DOT, current dir It is missing "libintl.h". Sie issue is mentioned here: http://www.gnu.org/software/gnulib/manual/html_node/libintl_002eh.html It tried to fix it with "> brew install gettext" unforutnatly without success. Any other workaround? Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Compiling LyX on Mac OS 10.7.5
Summary: * QT 4.8.4 installed via the QT installer package (not from source) * brew install cmake * cmake -DLYX_NLS=OFF -DLYX_BUNDLE=ON -DLYX_COCOA=ON -DLYX_INSTALL=ON -DLYX_RELEASE=OFF -DLYX_DEBUG=ON -DLYX_EXTERNAL_LIBINTL=OFF . * make * make install Errors from cmake: CMake Error: Target LyX Info.plist template "/Users/elmar/lyx/build/src/../Info.plist" could not be found. Errors from make install: -- fixup_bundle -- app='/Users/elmar/lyx/LyX/LyX.app' -- libs='' -- dirs='' -- warning: *NOT* handled - .app directory case... CMake Error at /usr/local/Cellar/cmake/ 2.8.10.2/share/cmake/Modules/BundleUtilities.cmake:668 (message): error: fixup_bundle: not a valid bundle The second one seems to be cased by the first one. The application LyX/LyX.app/Contents/MacOS/LyX is running an looks fine. Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Compiling LyX on Mac OS 10.7.5
> The second one seems to be cased by the first one. > OK didn't follow the instruction: make LyX2.1 (to build the binary only) or make package (to get a mac bundle) Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Re: Compiling LyX on Mac OS 10.7.5
> or prefered: > > b.) Install the devel package for libc6 (on ubuntu libc6-dev) > > > > > Elmar > > > > > Kornel > Hello, IMHO there is no libc6 for mac. There is a /usr/lib/libSystem.dylib -> libSystem.B.dylib Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Compiling LyX on Mac OS 10.7.5
> OK didn't follow the instruction: > make LyX2.1 (to build the binary only) > or > make package (to get a mac bundle) > Anyway, That doesn't bring in the missing Info.plist. Question: Why is there no Info.plist in the source? -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Re: Re: Compiling LyX on Mac OS 10.7.5
On Fri, Apr 26, 2013 at 6:29 PM, Kornel Benko <kor...@lyx.org> wrote: > ** > > Am Freitag, 26. April 2013 um 18:23:56, schrieb Elmar Hinz < > t3el...@googlemail.com> > > > Hello, > > > > > > IMHO there is no libc6 for mac. There is a > > > > > > /usr/lib/libSystem.dylib -> libSystem.B.dylib > > > > > > Elmar > > > > > > > Is there also a appropriate devel *package*? > > > > Kornel > I find a _debug* and a _profile* variant: -r-xr-xr-x 1 root wheel 475K 22 Mär 2012 /usr/lib/libSystem.B.dylib -r-xr-xr-x 1 root wheel 475K 12 Apr 2012 /usr/lib/libSystem.B_debug.dylib -r-xr-xr-x 1 root wheel 475K 12 Apr 2012 /usr/lib/libSystem.B_profile.dylib lrwxr-xr-x 1 root wheel17B 22 Mär 2012 /usr/lib/libSystem.dylib -> libSystem.B.dylib lrwxr-xr-x 1 root wheel23B 2 Mär 13:51 /usr/lib/libSystem_debug.dylib -> libSystem.B_debug.dylib lrwxr-xr-x 1 root wheel25B 2 Mär 13:51 /usr/lib/libSystem_profile.dylib -> libSystem.B_profile.dylib However I am new with Mac OS and still can't explain how it handles the stuff we know as libc6 and libc6-dev. This gives start: http://docstore.mik.ua/orelly/unix3/mac/ch05_02.htm For today I wanted to learn how to compile LyX and succeded largeley. Next step is to bring in a patch to learn the workflow of the project. Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Customizing Lyx
Exporting the markup syntax is a different issue. I can think of a couple ways to do it. The first, and most involved, would be to write export routines, in the LyX source itself, similar to the LyXHTML export routines. Another would be to write some kind of simple converter that would convert some format LyX already exports (perhaps the plaintext format?) to Markdown. Hello Richard, if I would like to transform LyXHTML to Markdown, I would need an XSL library or at least an XML parser. Is there already something like this contained in the sources? If not, what is your suggestion to use? Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
Re: Customizing Lyx
> Exporting the markup syntax is a different issue. I can think of a couple > ways to do it. The first, and most involved, would be to write export > routines, in the LyX source itself, similar to the LyXHTML export routines. > Another would be to write some kind of simple converter that would convert > some format LyX already exports (perhaps the plaintext format?) to Markdown. Hello Richard, if I would like to transform LyXHTML to Markdown, I would need an XSL library or at least an XML parser. Is there already something like this contained in the sources? If not, what is your suggestion to use? Regards Elmar -- Elmar Hinz Freiherr-vom-Stein-Str. 1 33014 Bad Driburg TYPO3 community contact: t.3.e.l.m.a...@.g.m.a.i.l.dot.c.o.m personal contact: e.l.m.a.r.dot.h.i.n...@.g.m.a.i.l.dot.c.o.m
