Re: LyX Review
On Tue, 30 Oct 2001, Angus Leeming wrote: On Tuesday 30 October 2001 7:01 am, Allan Rae wrote: On Mon, 29 Oct 2001, Angus Leeming wrote: Allan (Rae) is overly kind in his words, largely because I was the first GUII-friendly person that took up his challenge! And after I drummed my doctrine into you you put wings on my baby and taught her to fly :-) Probably the nicest present I've ever received. Maybe you should append from a bloke. or in the form of code. to my earlier sentence. (-: Did I just read that you should get out more :-) But I am getting out more! I'm never bloody home! Tonight I start a new dance course (I'm not even sure what it's about!). I'm out Tuesday, Wednesday and Friday nights of every week and now I'm adding Thursday at least for the next six weeks. I'm out again on Saturday afternoon/evening. I'm out so much I have had to start sacrificing Monday night's English Premier League soccer highlight program in order to have more time to catch up with friends. Arrrggghhh! Bugger. And all the while I'm trying to squeeze in some time for my thesis and wondering if a particular young woman will ever talk to me again. But I digress... Allan. (ARRae)
Re: LyX Review
On Tue, 30 Oct 2001, Angus Leeming wrote: > On Tuesday 30 October 2001 7:01 am, Allan Rae wrote: > > On Mon, 29 Oct 2001, Angus Leeming wrote: > > > > > Allan (Rae) is overly kind in his words, largely because I was the > > > first GUII-friendly person that took up his challenge! > > > > And after I drummed my doctrine into you you put wings on my baby and > > taught her to fly :-) > > > > Probably the nicest present I've ever received. Maybe you should append "from a bloke." or "in the form of code." to my earlier sentence. > (-: Did I just read that you should get out more :-) But I am getting out more! I'm never bloody home! Tonight I start a new dance course (I'm not even sure what it's about!). I'm out Tuesday, Wednesday and Friday nights of every week and now I'm adding Thursday at least for the next six weeks. I'm out again on Saturday afternoon/evening. I'm out so much I have had to start sacrificing Monday night's English Premier League soccer highlight program in order to have more time to catch up with friends. Arrrggghhh! Bugger. And all the while I'm trying to squeeze in some time for my thesis and wondering if a particular young woman will ever talk to me again. But I digress... Allan. (ARRae)
Re: LyX Review
On Tuesday 30 October 2001 7:01 am, Allan Rae wrote: On Mon, 29 Oct 2001, Angus Leeming wrote: Allan (Rae) is overly kind in his words, largely because I was the first GUII-friendly person that took up his challenge! And after I drummed my doctrine into you you put wings on my baby and taught her to fly :-) Probably the nicest present I've ever received. (-: Did I just read that you should get out more :-)
Re: LyX Review
On Sat, 27 Oct 2001, Brian Proffitt wrote: Regarding LyX overall, what are some of the features you think users will appreciate the most when they use this application? In addition to all the previously mentioned stuff, it is well documented. We on the doc team have tried hard to provide help files which are complete, up-to-date, and readable. Between the written docs, Herbert Voss's incredible LyX/LaTeX tips website (http://www.educat.hu-berlin.de/~voss/lyx), and the lyx-users mailing list, there's no excuse for anyone to struggle with learning LyX. Mike Ressler - doc team member (and thus biased). Current maintainer of most of the English docs. Added support for American Astronomical Society's AASTeX while documenting how to add new classes to LyX :-) -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: LyX Review
On Tuesday 30 October 2001 7:01 am, Allan Rae wrote: > On Mon, 29 Oct 2001, Angus Leeming wrote: > > > Allan (Rae) is overly kind in his words, largely because I was the > > first GUII-friendly person that took up his challenge! > > And after I drummed my doctrine into you you put wings on my baby and > taught her to fly :-) > > Probably the nicest present I've ever received. (-: Did I just read that you should get out more :-)
Re: LyX Review
On Sat, 27 Oct 2001, Brian Proffitt wrote: > Regarding LyX overall, what are some of the features you think users will > appreciate the most when they use this application? In addition to all the previously mentioned stuff, it is well documented. We on the doc team have tried hard to provide help files which are complete, up-to-date, and readable. Between the written docs, Herbert Voss's incredible LyX/LaTeX tips website (http://www.educat.hu-berlin.de/~voss/lyx), and the lyx-users mailing list, there's no excuse for anyone to struggle with learning LyX. Mike Ressler - doc team member (and thus biased). Current maintainer of most of the English docs. Added support for American Astronomical Society's AASTeX while documenting how to add new classes to LyX :-) -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: LyX Review
On Mon, 29 Oct 2001, Angus Leeming wrote: Allan (Rae) is overly kind in his words, largely because I was the first GUII-friendly person that took up his challenge! And after I drummed my doctrine into you you put wings on my baby and taught her to fly :-) Probably the nicest present I've ever received. Allan. (ARRae)
Re: LyX Review
On Mon, 29 Oct 2001, Angus Leeming wrote: > Allan (Rae) is overly kind in his words, largely because I was the > first GUII-friendly person that took up his challenge! And after I drummed my doctrine into you you put wings on my baby and taught her to fly :-) Probably the nicest present I've ever received. Allan. (ARRae)
Re: LyX Review
Specifically, I am interested in the status of the GUI Independence Project. I have looked over the status report on your Web site, but I wanted to ask some additional questions: The GUII project has been running for a very long time. Thoughts about the project were floating around even before KLyX appeared. After KLyX, it took a few attempts to find the right approach. Now, my understanding is that LyX is approaching GUII in a technically sound and scalable manner. The focus is to structure the code according to the Model-View-Control design pattern. The Model corresponds to the LyX core which handles the basic text data structure, the Control-code that controls the user interaction, and which is shared across different toolkit, and finally the View-code that creates and shows the GUI and which is specific for each front-end. There has been a lot of work to ensure that the View-code is minimal -- i.e. to allow sharing of control-code between frontends. In this manner, we can conclude that basically all dialogs in Lyx are GUII, and well-done at that. The next tasks for GUII is the main window. This window is composed of a menu, a toolbar, the work-area and the status bar. The main challenge at this point is the work-area. Some work has been done in this area, such as implementing an abstract painter, but the task of handling user interaction has yet to be tackled. I see that as the last remaining mayor issue before LyX is truly GUII. The problem at this point is developer time. The core developers that know most about this aspect of LyX are tied up with professional work. Also, these people have other things to tend to: Fix bugs in the core code, and otherwise making sure that the core of LyX is being kept alive. Therefore, it is very hard to estimate a completion date for the GUII project. It is completed once the core developers have time to do it, or some of the other developers with time on their hands take the dive in and do something about it. If somebody with the skills and the time works at the problem for a month or two, we could have a complete beta GUII LyX. But don't hold your breath. Regarding LyX overall, what are some of the features you think users will appreciate the most when they use this application? 1) The separation of content and display. 2) Easy to use. 3) Mature. LyX has been in production use for many years. 4) Powerful: It has all the components you need in a word processor, except possibly automatic grammar. Partial feature list: - The best math editor around - The best tables around - Spell-checking with ispell or aspell - Thesaurus will come in 1.2.0 - Paragraph styles, including user definable - Graphics - Bullets, cross-references, table-of-contents, bibliography, citations 5) LaTeX support comes in two ways: If you are a LaTeX expert, you can exploit your knowledge. If you are LaTeX ignorant, you can still make very beautiful documents. What's the biggest thing you want to change for LyX? Introducing character styles. With these, the DocBook support can be completed, and LyX will also become a killer DocBook word processor. Greets, Asger Alstrup (Retired LyX core developer)
Re: LyX Review
On Sat, 27 Oct 2001, Brian Proffitt wrote: What is the overall strategy of the GIP? Asger and John have answered this pretty well. What are the most challenging aspects of the GIP? Convincing the nay-sayers that it was worthwhile in the first place then spending three years trying to build a team of developers to get the GUII work done. GUII makes you think beyond the limits of your favourite toolkit. It makes you think beyond a simple port to an alternate toolkit which is what happened with KLyX and what several people wanted to do for a Gnome/GTK+ port. GUII is a very large step toward platform/system independence. Persistence, publicity (mostly through LyX Development News -- some might say propaganda) and persperation eventually won the battle of minds. Is there a timeline for completing the project? :-) I thought we'd have had it done years ago but it took ages to get a team of enthusiastic porters together and a couple of people who were prepared to build the infrastructure. The timeline goes (vertically) something like: dialogs,toolbar + menubar workarea The workarea is the major remaining area. Most dialogs are independent and being revised/improved. The toolbar/menubar abstractions are pretty good but could use some more refining. The dialogs are now, largely due to the brilliant design work of Angus Leeming, a snap to port. Angus was responsible for the MVC implementation that Asger talks about in his email. Regarding LyX overall, what are some of the features you think users will appreciate the most when they use this application? They can stop messing about with fiddly document layout crap and get down to the task of writing the content. LyX and LaTeX will get the document to look beautiful in about 98% of cases from my own experience and in the remianing 2% you tweak a couple of LaTeX settings (for cases where LaTeX needs some user assistance in placing figures for example). Hebrew and Arabic support. Support for Chinese, Japanese and Korean via an unofficial patch (this work will be superceded or at least incorporated sometime in the future). What's the biggest thing you want to change for LyX? Better integration with LaTeX. I want support for more LaTeX document classes and to do this we need some tools to help LyX users get LyX working with new classes easily. Ummm... Actually, the thing I'd most like to change is the apparently general misconception that LyX is going nowhere and doesn't do anything useful anyway. Converts to LyX love the way they can concentrate on the content but it requires a change of mindset and operational model from that most word processors inflict upon their hapless users. To a small extent the above wish would also help overcome this because LyX is currently geared toward technical content such as for engineering and science texts and journals. Dekel Tsur's work to support multi-lingual documents and in particular the support for Hebrew and Arabic documents are significant also. How many other free software editors of _any_ description can handle Hebrew, let alone typeset it beautifully? How many people are working on LyX now and how is the work organized? There are about 15 significant current contributors to LyX. These could all be called core developers although if you just count those of us with CVS write access as core developers I think you'd get about 8. There are essentially four teams involved in LyX development (where the word team is used rather loosely). A documentation team led by Mike Ressler. An internationalisation team consisting of translators for the interface and documentation. A debugging/testing team consisting of a number of bleeding-edge users, this isn't really a formal team. Michael Schmitt is the main man in the test team as he maintains a list of bugs and has run extensive Purify tests for us. The development team has several specialists, such as Juergen Vigna (who wrote all the table code), but every one of the core developers work in any area of the code (including Juergen). Of the 20 major contributors I'd say 5 spend most of their time working on the GUII ports. Jean Marc Lasgouttes has control of the stable releases (currently 1.1.6) and handles most of the user contributed patches. Lars has overall control. There are a couple of feature articles in LyX Development News that try to explain the development process we are using. Take a look through the various issues: http://www.lyx.org/news/archive.php3 The main ones to look are probably: http://www.lyx.org/news/2217.php3 for the original announcement of change of development process http://www.lyx.org/news/20001220.php3 coverage of yet another GUII debate and some details of why it is a good thing. If you could answer these questions even partially, it would be of great help. Since I expect multiple replies, please be sure to identify yourself and your relationship to
Re: LyX Review
> Specifically, I am interested in the status of the GUI Independence Project. > I have looked over the status report on your Web site, but I wanted to ask > some additional questions: The GUII project has been running for a very long time. Thoughts about the project were floating around even before KLyX appeared. After KLyX, it took a few attempts to find the right approach. Now, my understanding is that LyX is approaching GUII in a technically sound and scalable manner. The focus is to structure the code according to the Model-View-Control design pattern. The Model corresponds to the LyX core which handles the basic text data structure, the Control-code that controls the user interaction, and which is shared across different toolkit, and finally the View-code that creates and shows the GUI and which is specific for each front-end. There has been a lot of work to ensure that the View-code is minimal -- i.e. to allow sharing of control-code between frontends. In this manner, we can conclude that basically all dialogs in Lyx are GUII, and well-done at that. The next tasks for GUII is the main window. This window is composed of a menu, a toolbar, the work-area and the status bar. The main challenge at this point is the work-area. Some work has been done in this area, such as implementing an abstract painter, but the task of handling user interaction has yet to be tackled. I see that as the last remaining mayor issue before LyX is truly GUII. The problem at this point is developer time. The core developers that know most about this aspect of LyX are tied up with professional work. Also, these people have other things to tend to: Fix bugs in the core code, and otherwise making sure that the core of LyX is being kept alive. Therefore, it is very hard to estimate a completion date for the GUII project. It is completed once the core developers have time to do it, or some of the other developers with time on their hands take the dive in and do something about it. If somebody with the skills and the time works at the problem for a month or two, we could have a complete beta GUII LyX. But don't hold your breath. > Regarding LyX overall, what are some of the features you think users will > appreciate the most when they use this application? 1) The separation of content and display. 2) Easy to use. 3) Mature. LyX has been in production use for many years. 4) Powerful: It has all the components you need in a word processor, except possibly automatic grammar. Partial feature list: - The best math editor around - The best tables around - Spell-checking with ispell or aspell - Thesaurus will come in 1.2.0 - Paragraph styles, including user definable - Graphics - Bullets, cross-references, table-of-contents, bibliography, citations 5) LaTeX support comes in two ways: If you are a LaTeX expert, you can exploit your knowledge. If you are LaTeX ignorant, you can still make very beautiful documents. > What's the biggest thing you want to change for LyX? Introducing character styles. With these, the DocBook support can be completed, and LyX will also become a killer DocBook word processor. Greets, Asger Alstrup (Retired LyX core developer)
Re: LyX Review
On Sat, 27 Oct 2001, Brian Proffitt wrote: > What is the overall strategy of the GIP? Asger and John have answered this pretty well. > What are the most challenging aspects of the GIP? Convincing the nay-sayers that it was worthwhile in the first place then spending three years trying to build a team of developers to get the GUII work done. GUII makes you think beyond the limits of your favourite toolkit. It makes you think beyond a simple port to an alternate toolkit which is what happened with KLyX and what several people wanted to do for a Gnome/GTK+ port. GUII is a very large step toward platform/system independence. Persistence, publicity (mostly through LyX Development News -- some might say propaganda) and persperation eventually won the battle of minds. > Is there a timeline for completing the project? :-) I thought we'd have had it done years ago but it took ages to get a team of enthusiastic porters together and a couple of people who were prepared to build the infrastructure. The timeline goes (vertically) something like: dialogs,toolbar + menubar workarea The workarea is the major remaining area. Most dialogs are independent and being revised/improved. The toolbar/menubar abstractions are pretty good but could use some more refining. The dialogs are now, largely due to the brilliant design work of Angus Leeming, a snap to port. Angus was responsible for the MVC implementation that Asger talks about in his email. > Regarding LyX overall, what are some of the features you think users will > appreciate the most when they use this application? They can stop messing about with fiddly document layout crap and get down to the task of writing the content. LyX and LaTeX will get the document to look beautiful in about 98% of cases from my own experience and in the remianing 2% you tweak a couple of LaTeX settings (for cases where LaTeX needs some user assistance in placing figures for example). Hebrew and Arabic support. Support for Chinese, Japanese and Korean via an unofficial patch (this work will be superceded or at least incorporated sometime in the future). > What's the biggest thing you want to change for LyX? Better integration with LaTeX. I want support for more LaTeX document classes and to do this we need some tools to help LyX users get LyX working with new classes easily. Ummm... Actually, the thing I'd most like to change is the apparently general misconception that LyX is going nowhere and doesn't do anything useful anyway. Converts to LyX love the way they can concentrate on the content but it requires a change of mindset and operational model from that most word processors inflict upon their hapless users. To a small extent the above wish would also help overcome this because LyX is currently geared toward technical content such as for engineering and science texts and journals. Dekel Tsur's work to support multi-lingual documents and in particular the support for Hebrew and Arabic documents are significant also. How many other free software editors of _any_ description can handle Hebrew, let alone typeset it beautifully? > How many people are working on LyX now and how is the work organized? There are about 15 significant current contributors to LyX. These could all be called core developers although if you just count those of us with CVS write access as core developers I think you'd get about 8. There are essentially four teams involved in LyX development (where the word "team" is used rather loosely). A documentation team led by Mike Ressler. An internationalisation team consisting of translators for the interface and documentation. A debugging/testing team consisting of a number of bleeding-edge users, this isn't really a formal team. Michael Schmitt is the main man in the test team as he maintains a list of bugs and has run extensive Purify tests for us. The development team has several specialists, such as Juergen Vigna (who wrote all the table code), but every one of the core developers work in any area of the code (including Juergen). Of the 20 major contributors I'd say 5 spend most of their time working on the GUII ports. Jean Marc Lasgouttes has control of the stable releases (currently 1.1.6) and handles most of the user contributed patches. Lars has overall control. There are a couple of feature articles in LyX Development News that try to explain the development process we are using. Take a look through the various issues: http://www.lyx.org/news/archive.php3 The main ones to look are probably: http://www.lyx.org/news/2217.php3 for the original announcement of change of development process http://www.lyx.org/news/20001220.php3 coverage of yet another GUII debate and some details of why it is a good thing. > If you could answer these questions even partially, it would be of great > help. Since I expect multiple replies, please be sure to identify yourself > and your
Re: LyX Review
Hi Brian, I use Lyx at my workplace. I may not quote my company (my contract forbids it), but let's say we write Ada software to control big hardware. Brian Proffitt wrote: Regarding LyX overall, what are some of the features you think users will appreciate the most when they use this application? I and my coworkers use LyX to write our software documentation. We switched from Interleaf when the company was bought by Quicksilver and the future became uncertain (even gloomy). So we undertook to migrate to a safe harbour and chose LyX for the following reasons : - It is easy to use (easier than TeX and easier than Word to technical staff). - You can write new styles and users have to obey the styles (which makes for cleanly structured documents). - LyX is meaning-oriented and not Wysiwyg like Interleaf, so that anybody browsing a document can understand how it is built (e.g. references and labels) and spot where people forgot to use the right features (e.g. the guy hardcoded a see section 3.2.3.2 instead of a reference to a label set in the correct section. This error was both common and difficult to spot with Interleaf). - LyX has pretty good HTML output thanks to Latex2html (this was the winning argument, Word 97 generates crappy HTML). - The LyX file format is easy to understand, so we could write Python scripts to convert Interleaf ASCII files to LyX files. Also this means that we can leave LyX for another system by writing scripts easily (this argument was used to convince our management that we could NOT be left in the dust). - LyX files are pure text files, so they are easy to manage with a RCS-based versioning system (such as CVS or our home-brewed SPM system). We also manage the DIA figures and eps files under the versioning system. - The style files are also managed under a versioning system - The postscript/PDF output is great since it is TeX. So, you can see that LyX brought many improvements to our work and allowed us to avoid a migration to Word which would have been a nightmare (I had to write a 2 page Word document this week and it was very painful. The styles were a mess and I had to cut and paste data I could have generated automatically for LyX (with the right formatting and structure since the file format is simple)). What's the biggest thing you want to change for LyX? Version 1.2 will bring a few great features, but the most urgent is a better handling of read-only files. In 1.1.6 read-only files were unpleasant in LyX, since it meant that many functions and menus were disabled. In LyX 1.2, you can see any important parameter of a LyX file even if it is read-only. This feature is very important if you want to manage your LyX files under CVS : the watches that allow you to prevent conflicts with your coworkers are base on making files read-only until a cvs edit xxx.lyx command has been issued. Also, I want revision bars to track changes in the LyX files. Lars already expressed interest in such a feature, but for now I need to generate them at the LateX level (ERT would not work since too much layout magic happens when LyX generates LaTeX output so that you can easily generate invalid LaTeX code). Last, I'd like LyX to display the style of each paragraph in the left margin in the way Interleaf 5 used to. This was a great feature that allowed the user to understand the styling of the whole screen at a glance. At the moment, you need to point your cursor in every paragraph to know their style. sincerely, P.O. Gaillard
Re: LyX Review
On Sat, Oct 27, 2001 at 11:01:35AM -0500, Brian Proffitt wrote: I have looked over the status report on your Web site, but I wanted to ask some additional questions: What is the overall strategy of the GIP? Flexibly supporting the internal interfaces, with the minimum of duplicated code, and maximum ease of implementation for the UI coders. For example, the dialog GUII code is currently in a very nice state - I can implement and test a dialog very quickly for Qt2, as I don't have to concern myself much with lyx internals. The architecture is such that it enables me to concentrate more on the interface design than tedious interface code. What are the most challenging aspects of the GIP? Avoid lowest-common-denominator design that limits what better toolkits such as Qt can support. Not adversely affecting the lyx core (this will be a significant aspect when it comes to supporting GUII work area (the work area is the document view onto the rendered document view). Is there a timeline for completing the project? *shrug* Regarding LyX overall, what are some of the features you think users will appreciate the most when they use this application? I think latex's main strength : concentrating on content rather than presentation. This is advantageous in terms of avoiding getting in the way of the author. What's the biggest thing you want to change for LyX? Table GUI interface. A better GUI design (very hard thing for amateurs ;) How many people are working on LyX now and how is the work organized? There are around 5 main developers. There are probably 10/20 or so more people like me working on the fringes. Then lots of other people with occasional fixes, and, crucially, bug reports - since Michael Schmitt has joined the project, lyx has improved a /lot/ from his excellent bug reports. help. Since I expect multiple replies, please be sure to identify yourself and your relationship to the project so I can attribute the right information to the right person. I work on the GUII code, with my main focus on the Qt2 frontend. regards john -- If the software that a company produces isn't reliable, adding a bunch of 'Mother, may I' rules to the language and the code won't fix it. - Pete Becker
Re: LyX Review
Hi Brian, I use Lyx at my workplace. I may not quote my company (my contract forbids it), but let's say we write Ada software to control big hardware. Brian Proffitt wrote: > Regarding LyX overall, what are some of the features you think users will > appreciate the most when they use this application? > I and my coworkers use LyX to write our software documentation. We switched from Interleaf when the company was bought by Quicksilver and the future became uncertain (even gloomy). So we undertook to migrate to a safe harbour and chose LyX for the following reasons : - It is easy to use (easier than TeX and easier than Word to technical staff). - You can write new styles and users have to obey the styles (which makes for cleanly structured documents). - LyX is meaning-oriented and not Wysiwyg like Interleaf, so that anybody browsing a document can understand how it is built (e.g. references and labels) and spot where people forgot to use the right features (e.g. the guy hardcoded a "see section 3.2.3.2" instead of a reference to a label set in the correct section. This error was both common and difficult to spot with Interleaf). - LyX has pretty good HTML output thanks to Latex2html (this was the winning argument, Word 97 generates crappy HTML). - The LyX file format is easy to understand, so we could write Python scripts to convert Interleaf ASCII files to LyX files. Also this means that we can leave LyX for another system by writing scripts easily (this argument was used to convince our management that we could NOT be left in the dust). - LyX files are pure text files, so they are easy to manage with a RCS-based versioning system (such as CVS or our home-brewed SPM system). We also manage the DIA figures and eps files under the versioning system. - The style files are also managed under a versioning system - The postscript/PDF output is great since it is TeX. So, you can see that LyX brought many improvements to our work and allowed us to avoid a migration to Word which would have been a nightmare (I had to write a 2 page Word document this week and it was very painful. The styles were a mess and I had to cut and paste data I could have generated automatically for LyX (with the right formatting and structure since the file format is simple)). > What's the biggest thing you want to change for LyX? > Version 1.2 will bring a few great features, but the most urgent is a better handling of read-only files. In 1.1.6 read-only files were unpleasant in LyX, since it meant that many functions and menus were disabled. In LyX 1.2, you can see any important parameter of a LyX file even if it is read-only. This feature is very important if you want to manage your LyX files under CVS : the watches that allow you to prevent conflicts with your coworkers are base on making files read-only until a "cvs edit xxx.lyx" command has been issued. Also, I want revision bars to track changes in the LyX files. Lars already expressed interest in such a feature, but for now I need to generate them at the LateX level (ERT would not work since too much "layout magic" happens when LyX generates LaTeX output so that you can easily generate invalid LaTeX code). Last, I'd like LyX to display the style of each paragraph in the left margin in the way Interleaf 5 used to. This was a great feature that allowed the user to understand the styling of the whole screen at a glance. At the moment, you need to point your cursor in every paragraph to know their style. sincerely, P.O. Gaillard
Re: LyX Review
On Sat, Oct 27, 2001 at 11:01:35AM -0500, Brian Proffitt wrote: > I have looked over the status report on your Web site, but I wanted to ask > some additional questions: > > What is the overall strategy of the GIP? Flexibly supporting the internal interfaces, with the minimum of duplicated code, and maximum ease of implementation for the UI coders. For example, the dialog GUII code is currently in a very nice state - I can implement and test a dialog very quickly for Qt2, as I don't have to concern myself much with lyx internals. The architecture is such that it enables me to concentrate more on the interface design than tedious interface code. > What are the most challenging aspects of the GIP? Avoid lowest-common-denominator design that limits what better toolkits such as Qt can support. Not adversely affecting the lyx core (this will be a significant aspect when it comes to supporting GUII work area (the work area is the "document view" onto the rendered document view). > Is there a timeline for completing the project? *shrug* > Regarding LyX overall, what are some of the features you think users will > appreciate the most when they use this application? I think latex's main strength : concentrating on content rather than presentation. This is advantageous in terms of avoiding getting in the way of the author. > What's the biggest thing you want to change for LyX? Table GUI interface. A better GUI design (very hard thing for amateurs ;) > How many people are working on LyX now and how is the work organized? There are around 5 main developers. There are probably 10/20 or so more people like me working on the fringes. Then lots of other people with occasional fixes, and, crucially, bug reports - since Michael Schmitt has joined the project, lyx has improved a /lot/ from his excellent bug reports. > help. Since I expect multiple replies, please be sure to identify yourself > and your relationship to the project so I can attribute the right > information to the right person. I work on the GUII code, with my main focus on the Qt2 frontend. regards john -- "If the software that a company produces isn't reliable, adding a bunch of 'Mother, may I' rules to the language and the code won't fix it." - Pete Becker
Re: LyX review
"Amir" == Amir Karger [EMAIL PROTECTED] writes: Amir http://www.showmelinux.com/092000/inreview.html Hmm, better than the appreciation given i nthe first paragraph of http://linux.com/desktops/newsitem.phtml?sid=91aid=10740 I've already read that LyX is ugly, but arcane... JMarc
Re: LyX review
> "Amir" == Amir Karger <[EMAIL PROTECTED]> writes: Amir> http://www.showmelinux.com/092000/inreview.html Hmm, better than the appreciation given i nthe first paragraph of http://linux.com/desktops/newsitem.phtml?sid=91=10740 I've already read that LyX is ugly, but arcane... JMarc
Re: LyX Review at LinuxPower
On Sun, Mar 14, 1999 at 11:10:52PM +1000, Allan Rae wrote: I don't recall anyone telling us about this review. Dated Feb 15. by Jeremy "Unknwn" Katz on LyX-1.0 http://linuxpower.org/display_item.phtml?id=103 Fairly short review, recommends reading tutorial and the author feels LyX "has a stronger feature set than any other word processor currently available for Linux, although it has a slightly larger learning curve." Glad someone is being praised, rather than criticized, for calling LyX the best *word* processor around. sigh. -- lsm
Re: LyX Review at LinuxPower
On Sun, 14 Mar 1999 [EMAIL PROTECTED] wrote: Glad someone is being praised, rather than criticized, for calling LyX the best *word* processor around. sigh. They not only call LyX a *word processor*, they still call it a *frontend to latex*. But it's good to see that they understand the advantages of the WYSIWYM model. :) Alejandro
Re: LyX Review at LinuxPower
On Sun, Mar 14, 1999 at 11:10:52PM +1000, Allan Rae wrote: > > I don't recall anyone telling us about this review. > Dated Feb 15. by Jeremy "Unknwn" Katz on LyX-1.0 > > http://linuxpower.org/display_item.phtml?id=103 > > Fairly short review, recommends reading tutorial and the author feels LyX > "has a stronger feature set than any other word processor currently > available for Linux, although it has a slightly larger learning curve." Glad someone is being praised, rather than criticized, for calling LyX the best *word* processor around. . -- lsm
Re: LyX Review at LinuxPower
On Sun, 14 Mar 1999 [EMAIL PROTECTED] wrote: > Glad someone is being praised, rather than criticized, for calling > LyX the best *word* processor around. . They not only call LyX a *word processor*, they still call it a *frontend to latex*. But it's good to see that they understand the advantages of the WYSIWYM model. :) Alejandro
