Re: Small poll
Andre Since 1.2 works pretty well at the moment I would like to wait for 1.3 to have a fully (or as near as possible) Qt front end. Pete Martin
Re: Small poll
Hi, On Monday, 28. October 2002 07:40, Andre Poenitz wrote: | What would _you_ prefer if you had the choice: | (b) release 1.3.0 if the Qt frontend is ready and put everything | else to sleep until then. I'm still using lyx 1.1.6fix4 and I'm pretty pleased by this version. A QT-GUI would be a serious reason for me to switch to a new version of lyx, so I would prefer finishing the QT-GUI before release version 1.3. Michael.
RE: Small poll
Hi, My vote ist for (b). (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. Bye
Re: Small poll
Just a small poll [As background: the Qt frontend is the single big item on the 1.3 list that's not done and won't be finished within the next few weeks.] What would _you_ prefer if you had the choice: (a) have 1.3.0 now as-is with its barely functional Qt frontend, start with the 1.4 cycle immediately. (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. (c) I don't care Alternative (b): The only major annoyance that I'm bothered by, and which I'd like to see a patch for in 1.2.2, is the problem that LyX doesn't notice when Xfig- och Tgif images have been modified on disk. Other than that I think it's a great program :-) -- Christian Ridderström http://www.md.kth.se/~chr Mechatronics division Department of Machine Design http://www.md.kth.se
Re: Small poll
On Monday 28 October 2002 07:40, Andre Poenitz wrote: Just a small poll [As background: the Qt frontend is the single big item on the 1.3 list that's not done and won't be finished within the next few weeks.] What would _you_ prefer if you had the choice: (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. IMHO, will bring a lot of new LyX users. Most Linux Newbies are only using KDE applications and even dont know that there are a lot of other apps that would do the job better. Due to my experience a lot of the people using LyX for the first time in a LyX course are a bit detered when they see lyx pop up the first time. Thomas
Re: Small poll
What would _you_ prefer if you had the choice: (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. (b) would be great, and having a version of Lyx that copes with underscores in equation references will be even better:-) Jose -- José L Gómez Dans PhD student Tel: +44 114 222 5582 Radar Communications Group FAX; +44 870 132 2990 Department of Electronic Engineering University of Sheffield UK
Re: Small poll
On Mon, Oct 28, 2002 at 07:40:47AM +0100, Andre Poenitz wrote: What would _you_ prefer if you had the choice: (a) have 1.3.0 now as-is with its barely functional Qt frontend, start with the 1.4 cycle immediately. (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. (c) I don't care I would prefer (b) BUT only if Lyx would then fully support UTF-8/Xft2/fontconfig. Alexander
Re: Small poll
On Mon, Oct 28, 2002 at 12:59:35PM +0100, Alexander Volovics wrote: (a) have 1.3.0 now as-is with its barely functional Qt frontend, start with the 1.4 cycle immediately. (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. (c) I don't care I would prefer (b) BUT only if Lyx would then fully support UTF-8/Xft2/fontconfig. How do you vote in a real ballot: Make a cross somewhere and write down BUT only if he reduces taxes? Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: Small poll
Le Lundi 28 Octobre 2002 07:40, Andre Poenitz a écrit : (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. I am waiting for the Qt front-end and prefer to wait for it to be ready before 1.3 is released. -- Renaud Michel L' oûrs piede ses poy, mins måy ses lêdès manîres.
Re: Small poll
(b) for me too Tx Paul Andre Poenitz wrote: Just a small poll [As background: the Qt frontend is the single big item on the 1.3 list that's not done and won't be finished within the next few weeks.] What would _you_ prefer if you had the choice: (a) have 1.3.0 now as-is with its barely functional Qt frontend, start with the 1.4 cycle immediately. (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. (c) I don't care Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: Small poll
On Mon, Oct 28, 2002 at 01:06:01PM +0100, Andre Poenitz wrote:
(a) have 1.3.0 now as-is with its barely functional Qt frontend,
start with the 1.4 cycle immediately.
(b) release 1.3.0 if the Qt frontend is ready and put everything
else to sleep until then.
(c) I don't care
I would prefer (b)
BUT only if Lyx would then fully support UTF-8/Xft2/fontconfig.
How do you vote in a real ballot: Make a cross somewhere and write down
BUT only if he reduces taxes?
Sometimes {^_-}
OK how about:
I would prefer (b)
BUT only if Lyx would then fully support UTF-8/Xft2/fontconfig
else (a)
Forced multiple choice is too black and white here.
Alexander
Re: Small poll
The consensus from respondants appears to be strongly for b). I too offer my preference for b. My current 1.2 release works well enough for my current uses but a QT GUI would certainly be enough for me to upgrade. praedor -- Beware the leader who bangs the drums of war in order to whip the citizenry into a patriotic fervor...the citizenry, infused with fear and blinded with patriotism, will offer up all their rights unto the leader and gladly so. --unknown
Re: Small poll
On Mon, Oct 28, 2002 at 02:00:23PM +0100, Alexander Volovics wrote: Forced multiple choice is too black and white here. That was the intention ;-) Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: Small poll
On Mon, Oct 28, 2002 at 12:59:35PM +0100, Alexander Volovics wrote: BUT only if Lyx would then fully support UTF-8/Xft2/fontconfig. I don't think we will have proper unicode support. However, if your Qt is built for anti-aliased fonts, you get it for free. regards john -- All photography is accurate - none of it is truth. - Richard Avedon
compiling LyX
I just compiled LyX with qt frontend (I don't have xforms installed at all). Looks nice, but first thing I want to tell - compiling LyX requires A LOT of memory. I had 256MB without swap, and gcc has been killed in process of compiling. Adding swap helps, but no other source requires so much memory to compile. -- http://decopter.sf.net - free unrealistic helicopter simulator
dialog-preferences
I have bad fonts in menu (ISO-8559-1 instead -2), wanted to change it without editing config files... So I clicked Preferences - no window opened! I just see (dialog-preferences) at bottom of main window. PS. current CVS, qt frontend -- http://decopter.sf.net - free unrealistic helicopter simulator
Re: dialog-preferences
Jacek == Jacek Pop³awski [EMAIL PROTECTED] writes: Jacek I have bad fonts in menu (ISO-8559-1 instead -2), wanted to Jacek change it without editing config files... So I clicked Jacek Preferences - no window opened! I just see Jacek (dialog-preferences) at bottom of main window. Jacek PS. current CVS, qt frontend Preference frontend is not yet done for qt. Note that posting about the qt frontend should be done on lyx-devel. JMarc
Re: Small poll
On Mon, 2002-10-28 at 07:40, Andre Poenitz wrote: Just a small poll [As background: the Qt frontend is the single big item on the 1.3 list that's not done and won't be finished within the next few weeks.] What would _you_ prefer if you had the choice: (a) have 1.3.0 now as-is with its barely functional Qt frontend, start with the 1.4 cycle immediately. (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. (c) I don't care Andre' Hi, I vote (b) ! BTW: Just wondering, I don't try to start a flamewar. What is with the gnome frontend? Is it dead? bye johannes -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson) -- Johannes Behr [EMAIL PROTECTED] Computer Graphics Center
[qt-cvs] encoding
can't set ecoding in any way I put this in ~/.lyx/lyxrc \screen_font_encoding iso8859-2 \screen_font_roman -*-times \screen_font_sans -*-helvetica \screen_font_typewriter -*-courier \screen_font_popup -*-helvetica-medium-r \screen_font_menu -*-helvetica-bold-r when I run lyx -dbg 512 I see: Debugging `font' (Font handling) This font is NOT an exact match XFLD: -adobe-helvetica-bold-r-normal--14-140-75-75-p-82-iso10646-1 Font 'Bezszeryfowy, Pogrubiony, Prosty, Normalny, ty, KursywaWy, Podkrelony Wy, Kapitaliki Wy, Jzyk: English' matched by -adobe-helvetica-bold-r-normal--14-140-75-75-p-82-iso10646-1 The font has size: 15 Font 'Bezszeryfowy, Pogrubiony, Prosty, Normalny, ty, KursywaWy, Podkrelony Wy, Kapitaliki Wy, Jzyk: English' matched by -adobe-helvetica-bold-r-normal--14-140-75-75-p-82-iso10646-1 The font has size: 15 -- http://decopter.sf.net - free unrealistic helicopter simulator
Re: dialog-preferences
On Mon, Oct 28, 2002 at 03:31:51PM +0100, Jean-Marc Lasgouttes wrote: Jacek I have bad fonts in menu (ISO-8559-1 instead -2), wanted to Jacek change it without editing config files... So I clicked Jacek Preferences - no window opened! I just see Jacek (dialog-preferences) at bottom of main window. Jacek PS. current CVS, qt frontend Preference frontend is not yet done for qt. Note that posting about the qt frontend should be done on lyx-devel. Besides, you cannot set the widget fonts from LyX for Qt anyway. Use qtconfig (I think it is ..) john -- All photography is accurate - none of it is truth. - Richard Avedon
Re: Small poll
On Mon, 28 Oct 2002, Andre Poenitz wrote: (c) I don't care While the current UI may not be the prettyist, it works and -- for me -- that's what matters the most. Eye candy takes a much lower priority. Rich Dr. Richard B. Shepard, President Applied Ecosystem Services, Inc. (TM) 2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A. + 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | [EMAIL PROTECTED] http://www.appl-ecosys.com/
Re: dialog-preferences
On Mon, Oct 28, 2002 at 03:31:51PM +0100, Jean-Marc Lasgouttes wrote: Preference frontend is not yet done for qt. Note that posting about the qt frontend should be done on lyx-devel. I haven't seen lyx source yet, I don't have time now to contribute, so I decided to post only here, to not make developers angry :) -- http://decopter.sf.net - free unrealistic helicopter simulator
Re: Small poll
On Mon, Oct 28, 2002 at 06:44:13AM -0800, Rich Shepard wrote: While the current UI may not be the prettyist, it works and -- for me -- that's what matters the most. Eye candy takes a much lower priority. Eye candy is not what the GUII effort and the Qt frontend is about. regards john -- All photography is accurate - none of it is truth. - Richard Avedon
Re: dialog-preferences
On Mon, Oct 28, 2002 at 02:46:24PM +, John Levon wrote: Besides, you cannot set the widget fonts from LyX for Qt anyway. Use qtconfig (I think it is ..) Could you tell me what should I set in qtconfig? -- http://decopter.sf.net - free unrealistic helicopter simulator
Re: compiling LyX
On Mon, Oct 28, 2002 at 03:20:46PM +0100, Jacek Pop?awski wrote: I just compiled LyX with qt frontend (I don't have xforms installed at all). Looks nice, but first thing I want to tell - compiling LyX requires A LOT of memory. I had 256MB without swap, and gcc has been killed in process of compiling. Adding swap helps, but no other source requires so much memory to compile. You could switch off debug info. I can compile and link within 64M this way. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: dialog-preferences
On Mon, Oct 28, 2002 at 04:14:02PM +0100, Jacek Pop?awski wrote: On Mon, Oct 28, 2002 at 02:46:24PM +, John Levon wrote: Besides, you cannot set the widget fonts from LyX for Qt anyway. Use qtconfig (I think it is ..) Could you tell me what should I set in qtconfig? No idea. Do the other Qt-based programs work fine ? If so, why ? john -- All photography is accurate - none of it is truth. - Richard Avedon
Re: Small poll
On Mon, Oct 28, 2002 at 07:40:47AM +0100, Andre Poenitz wrote: (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. -- Bo Peng
Re: Small poll
On Monday 28 October 2002 01:40 am, you wrote: Just a small poll [As background: the Qt frontend is the single big item on the 1.3 list that's not done and won't be finished within the next few weeks.] What would _you_ prefer if you had the choice: (a) have 1.3.0 now as-is with its barely functional Qt frontend, start with the 1.4 cycle immediately. (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. (c) I don't care Andre' I vote for A. We've lived with xforms for years -- another few months won't hurt. And, as you all are probably tired of hearing me say, BY FAR the worst LyX deficiency is the lack of character styles, and that should be top priority in 1.4. There's only so long the color pseudo-styles will work, because there are very few colors that are practical, and keeping track of them is difficult. Compared to the lack of character styles, xforms' problems are cosmetic. Steve -- _ Steve Litt Author: * Universal Troubleshooting Process courseware * Troubleshooting Techniques of the Successful Technologist * Rapid Learning: Secret Weapon of the Successful Technologist http://www.troubleshooters.com Troubleshooters.Com Webmaster (Legal Disclaimer) Follow these suggestions at your own risk. -
Re: dialog-preferences
On Mon, Oct 28, 2002 at 02:46:24PM +, John Levon wrote: On Mon, Oct 28, 2002 at 03:31:51PM +0100, Jean-Marc Lasgouttes wrote: Jacek I have bad fonts in menu (ISO-8559-1 instead -2), wanted to Jacek change it without editing config files... So I clicked Jacek Preferences - no window opened! I just see Jacek (dialog-preferences) at bottom of main window. Jacek PS. current CVS, qt frontend Preference frontend is not yet done for qt. Note that posting about the qt frontend should be done on lyx-devel. Besides, you cannot set the widget fonts from LyX for Qt anyway. Use qtconfig (I think it is ..) qtconfig will not help. Currently, the QT frontend have few problems with non iso-8859-1 languages.
[Re] Small pool
Hi I've used version 1.2 occasionaly but didn't ffound any major problems, so I'd prefer to have QT GUI ready. So option b is my choice. Regards EJ
Re: Small poll - Results (fwd)
Maybe this was supposed to go to the list? On Mon, Oct 28, 2002 at 06:00:14PM +0200, Tuukka Toivonen wrote: Maybe you should have mentioned what new features LyX has, for which people need to wait longer if they want to have Qt too? Better search and replace. Instant dvi preview e.g. for math. Ability to read any .lyx down to version 0.10. Smoother cursor navigation. Smoother handling of CutPaste. Support for short section titles etc. Support for wasy Symbols. Re-worked counters. Two or three new .layouts. Even somewhat working Qt frontend And of course loads of bugfixes. And probably some more. Andre'
Re: dialog-preferences
On Mon, Oct 28, 2002 at 05:58:28PM +0200, Dekel Tsur wrote: Currently, the QT frontend have few problems with non iso-8859-1 languages. Could you tell me how to set Polish keyboard in qt frontend ? (I have polish keyboard in X) -- http://decopter.sf.net - free unrealistic helicopter simulator
Re: Small poll
On Mon, Oct 28, 2002 at 07:40:47AM +0100, Andre Poenitz wrote: (a) have 1.3.0 now as-is with its barely functional Qt frontend, start with the 1.4 cycle immediately. Release version with QT frontend as fast as possible, so milions of people can use it and send bug raports, but *please* put any docs about qt frontend (fonts, keyboard!, working and non-working features) or just tell where are they (I can't find anything...). -- http://decopter.sf.net - free unrealistic helicopter simulator
Re: Small poll
On Mon, Oct 28, 2002 at 05:54:56PM +0100, Jacek Pop?awski wrote: Release version with QT frontend as fast as possible, so milions of people can There is no point releasing a frontend that has big missing features (like no tabular dialog). use it and send bug raports, but *please* put any docs about qt frontend (fonts, keyboard!, working and non-working features) or just tell where are There are no docs. It is still under development. If you want to help test it out, that's fine, but please bear in mind it's under development. For example, if you're having keyboard problems, please give exact cases where it fails, along with lyx -dbg logs, and post to the developer's list. And hopefully somebody who understands foreign (if you'll excuse me) input/languages/fonts can fix it regards john -- All photography is accurate - none of it is truth. - Richard Avedon
Re: Small poll
Just a small poll [As background: the Qt frontend is the single big item on the 1.3 list that's not done and won't be finished within the next few weeks.] What would _you_ prefer if you had the choice: (a) have 1.3.0 now as-is with its barely functional Qt frontend, start with the 1.4 cycle immediately. (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. (c) I don't care Andre' I vote for A, too. For me it is really important the math stuff and it is really encouraging how math has evolved from the 1.1.6 up to 1.2. More particularly, the math-extern feature is one of the most notable improvements i have seen and I am sure that for the 1.4 cycle there are many other math enhancements waiting for, specially in the math-extern functionality, I hope. -- http://www.iit.upco.es/~oscar Your life would be very empty if you had nothing to regret.
Re: Small poll
On Monday 28 October 2002 12:16 pm, John Levon wrote: On Mon, Oct 28, 2002 at 04:42:18PM +, José Luis Gómez Dans wrote: won't hurt. And, as you all are probably tired of hearing me say, BY FAR the worst LyX deficiency is the lack of character styles, and that should be top priority in 1.4. There's only so long the color Sorry, but could you enlighten me to what character styles are? A decent character style system allows you to create semantic names and associate those with visual mark-up, on a character level. So you can define a Employee style, and set the style to always be italic or whatever. It is without a doubt the number one missing functionality from LyX. regards john Exactly! My book, Troubleshooting Techniques of the Successful Technologist discusses the 10 step Universal Troubleshooting Process. Each step is a short phrase. It was absolutely vital that any references to these steps have their own appearance. I wanted the ability to highlight the phrase, click a drop box similar to the current Environment drop box, and pick out the UTP_step character style, thereby formatting the style. But LyX lacks that ability. One might suggest I simply fine tune every occurrence of a UTP step in my book. But look at the disadvantages: * It's an affront to the WYSIWYM philosophy. * Mistake prone: One would need to remember the exact formatting of steps throughout the book. * If one ever wanted to change the appearance of the steps, it would require hunting them all down. Even a VI search and replace wouldn't work because those same font attributes could be applied to other pieces of text. Four chapters into the book I discovered the lack of character styles, and almost dumped LyX. Fortunately, Dekel Tsur showed me how to apply colors to character styles to accomplish what I wanted. The result is an outstanding book. But even so, the limited number of colors forced me to format source code scraps (source code phrases inside an otherwise normal paragraph) as a monospaced font, rather than as a character style. So if it's ever necessary to format these source code snippets differently, it would require several days of painstaking and mistake prone work. WordPerfect had character styles since their 1988 Version 5.0. When I started working with MS Word in 1994, it had character styles. StarOffice and OpenOffice have them. As a matter of fact, if you want to understand character styles, OpenOffice is an excellent way to learn about them. In every way OTHER than character styles, LyX beats the daylights out of WordPerfect, Word, StarOffice, OpenOffice, and all the others when it comes to writing long documents. IMHO LyX should be fitted with character styles as soon as possible. Steve -- _ Steve Litt Author: * Universal Troubleshooting Process courseware * Troubleshooting Techniques of the Successful Technologist * Rapid Learning: Secret Weapon of the Successful Technologist http://www.troubleshooters.com Troubleshooters.Com Webmaster (Legal Disclaimer) Follow these suggestions at your own risk. -
Re: Small poll
What's the big deal about qt? What would be wrong with gtk? On Mon, Oct 28, 2002 at 07:40:47AM +0100, Andre Poenitz opined: Just a small poll [As background: the Qt frontend is the single big item on the 1.3 list that's not done and won't be finished within the next few weeks.] What would _you_ prefer if you had the choice: (a) have 1.3.0 now as-is with its barely functional Qt frontend, start with the 1.4 cycle immediately. (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. (c) I don't care Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson) -- **Bruce Tyler* Field of Development Sociology **Cornell University** There is no way to peace; peace is the way.
Re: Small poll
On Mon, Oct 28, 2002 at 01:35:07PM -0600, Bruce Tyler wrote: What's the big deal about qt? We are almost finished with the Qt port. What would be wrong with gtk? Nobody does any work on a gtk port. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
How to edit postscript?
Dear list, I have a document that is confidential, and I will export it when finished into postscript. I would then like to take the postscript and either put black boxes over the confidential stuff or remove it. But what remains must be pixel-accurate compared to the uncencored version - if possible. I figure this is possible in ps, just subtract text and add box objects - but I have no idea how to do it. Are there any editors I can get my hands on that will do that? Thanks heaps! Have fun, Darren Freeman
Re: How to edit postscript?
On Monday 28 October 2002 1349 pm, Darren Freeman wrote: I have a document that is confidential, and I will export it when finished into postscript. I would then like to take the postscript and either put black boxes over the confidential stuff or remove it. But what remains must be pixel-accurate compared to the uncencored version - if possible. The Gimp -- but it would be rather fiddly if you have a lot of black boxes to put in. -- L. R. Denham -- Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
Tables violate margins
Dear list, Is there an easy way to tell a table to grow up to the width given by the margins, and then become automatically fixed-width after that? I have a table that fits on the page but I only just found out that it violates my margins - if it automatically went to fixed width at that point I would have removed some characters to return to single-line cells. Feature request maybe? BTW I'm using 1.3.0CVS Have fun, Darren
How do I insert horizontal space?
Dear list, I know how to insert an hfill. I want something like that, but for a fixed space (like a good ol' tab stop =) Have fun, Darren
Re: How to edit postscript?
On Tue, 2002-10-29 at 06:57, Les Denham wrote: On Monday 28 October 2002 1349 pm, Darren Freeman wrote: I have a document that is confidential, and I will export it when finished into postscript. I would then like to take the postscript and either put black boxes over the confidential stuff or remove it. But what remains must be pixel-accurate compared to the uncencored version - if possible. The Gimp -- but it would be rather fiddly if you have a lot of black boxes to put in. Yes it would, and it wouldn't be something you could throw at a printer and get optimal resolution etc. Plus storing it would suck =) I'd have to carry it on CD if I rendered to 600 dpi times 60 pages =) What I really want is to edit the PS file itself, and save as PS without the text that was covered up - then I could post the result on the Web without people accessing the hidden text from the PS. It seems like such a simple request, too! I mean, I've seen people edit PS by hand to move things in figures, but never to the scale I'm talking about. But it should be possible... L. R. Denham -- Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html BTW I read the link in your signature, and I agree. I'll make a similar (identical?) signature for myself shortly. Have fun, Darren
Re: How to edit postscript?
Les Denham wrote: On Monday 28 October 2002 1349 pm, Darren Freeman wrote: I have a document that is confidential, and I will export it when finished into postscript. I would then like to take the postscript and either put black boxes over the confidential stuff or remove it. But what remains must be pixel-accurate compared to the uncencored version - if possible. The Gimp -- but it would be rather fiddly if you have a lot of black boxes to put in. You can then achieve your censoring effect by changing the background colour of the text to black while still in LyX (though of course this wouldn't work if you're distributing the .ps file rather than a printout, since anyone with a text editor could read the file directly). The only workaround I could think of in that case would be to convert it into some impenetrable binary format (even PDF is convertable to text, though the average non-UNIX, non-DTP professional probably won't know this). The problem with editing the .ps file is that unless you use a fixed-width font, it's virtually impossible to calculate the exact length of your blank. I said virtually - it depends on how much of yur life you want to spend learning PostScript. Robin -- A free man ought not to learn anything under duress. Compulsory physical exercise does no harm to the body, but compulsory learning never sticks in the mind. - Plato Robin Turner IDMYO, Bilkent University Ankara 06533 Turkey www.bilkent.edu.tr/~robin
Re: How to edit postscript?
On Tue, Oct 29, 2002 at 06:19:48AM +1030, Darren Freeman wrote:
Dear list,
I have a document that is confidential, and I will export it when
finished into postscript.
I would then like to take the postscript and either put black boxes over
the confidential stuff or remove it. But what remains must be
pixel-accurate compared to the uncencored version - if possible.
I figure this is possible in ps, just subtract text and add box objects
- but I have no idea how to do it.
Are there any editors I can get my hands on that will do that?
Perhaps Adobe Illustrator can read/write arbitrary Postscript.
Also pstoedit can convert from Postscript to other editable formats.
But perhaps the best option is to put the text you want to omit inside
\hidetext{} command, and add to the preamble
\usepackage{soul,texpower}
%\newcommand{\hidetext}[1]{#1}
If you do want to show the hidden text, add a % before the first line, and
remove the % before the 2nd one.
Re: How do I insert horizontal space?
On Tue, Oct 29, 2002 at 07:40:45AM +1030, Darren Freeman wrote:
Dear list,
I know how to insert an hfill. I want something like that, but for a
fixed space (like a good ol' tab stop =)
\hspace{1cm} in ERT inset.
Re: Tables violate margins
On Tue, Oct 29, 2002 at 07:36:24AM +1030, Darren Freeman wrote: Dear list, Is there an easy way to tell a table to grow up to the width given by the margins, and then become automatically fixed-width after that? I have a table that fits on the page but I only just found out that it violates my margins - if it automatically went to fixed width at that point I would have removed some characters to return to single-line cells. Feature request maybe? This is tabularx in latex, which is currently not supported by LyX. It will be supported in the future.
Re: How do I insert horizontal space?
Le Lundi 28 Octobre 2002 22:10, Darren Freeman a écrit :
I know how to insert an hfill. I want something like that, but for a
fixed space (like a good ol' tab stop =)
Then you should use the \hspace{} command, the argument is the length of the
space (there is \vspace{} for vertical space).
If you use \hspace*{} (or \vspace*{}) the white space won't be removed, even
if it is at the begining or the end of a line.
Note that \hspace{\fill} is equivalent to \hfill.
--
Renaud Michel
Tous les matins du monde sont sans retour.
Re: How to edit postscript?
On Tue, 2002-10-29 at 08:15, Dekel Tsur wrote:
On Tue, Oct 29, 2002 at 06:19:48AM +1030, Darren Freeman wrote:
Dear list,
I have a document that is confidential, and I will export it when
finished into postscript.
I would then like to take the postscript and either put black boxes over
the confidential stuff or remove it. But what remains must be
pixel-accurate compared to the uncencored version - if possible.
I figure this is possible in ps, just subtract text and add box objects
- but I have no idea how to do it.
Are there any editors I can get my hands on that will do that?
Perhaps Adobe Illustrator can read/write arbitrary Postscript.
Also pstoedit can convert from Postscript to other editable formats.
Don't have it =(
But perhaps the best option is to put the text you want to omit inside
\hidetext{} command, and add to the preamble
\usepackage{soul,texpower}
%\newcommand{\hidetext}[1]{#1}
Does that cause the hidden text to take up the same amount of space, or
would formatting be altered by hiding it?
Also would I need to go and look for that package or is it pretty much
standard?
If you do want to show the hidden text, add a % before the first line, and
remove the % before the 2nd one.
I'll try it later.. thanks
Have fun,
Darren
Re: How to edit postscript?
On Tue, 2002-10-29 at 09:04, Robin Turner wrote: Les Denham wrote: On Monday 28 October 2002 1349 pm, Darren Freeman wrote: I have a document that is confidential, and I will export it when finished into postscript. I would then like to take the postscript and either put black boxes over the confidential stuff or remove it. But what remains must be pixel-accurate compared to the uncencored version - if possible. The Gimp -- but it would be rather fiddly if you have a lot of black boxes to put in. You can then achieve your censoring effect by changing the background colour of the text to black while still in LyX (though of course this wouldn't work if you're distributing the .ps file rather than a printout, since anyone with a text editor could read the file directly). Good idea, at the minimum I need the printout in a *hurry* to have it bound. The rest I can sit on if need be =) Robin Thanks
Re: How to change table alignments individually?
On Tue, 2002-10-29 at 08:30, Dekel Tsur wrote: On Tue, Oct 29, 2002 at 06:34:18AM +1030, Darren Freeman wrote: Dear list, I noticed that when I changed the alignment of text in a table from centred to left, it changed the whole column. What if I want just the one cell? Or a row? Make that cell a multicolumn cell. ? I mean, what if I want to change the alignment of one cell and leave the rest alone. Is that what you were talking about too? Darren
Re: How do I insert horizontal space?
On Tue, 2002-10-29 at 09:02, Renaud MICHEL wrote:
Le Lundi 28 Octobre 2002 22:10, Darren Freeman a écrit :
I know how to insert an hfill. I want something like that, but for a
fixed space (like a good ol' tab stop =)
Then you should use the \hspace{} command, the argument is the length of the
space (there is \vspace{} for vertical space).
If you use \hspace*{} (or \vspace*{}) the white space won't be removed, even
if it is at the begining or the end of a line.
Note that \hspace{\fill} is equivalent to \hfill.
Ahaaa..
Thanks!
Renaud Michel
Darren
Re: Small poll
I choose c. Andre Poenitz wrote: (c) I don't care It is not that I am ignorant about this, but LyX looks fine if you change the colours to your taste. The other things the developers want to implement in 1.3.x seem more important to me than the GUI, so if they have it ready and want to release it, release it right away. Not with a barely functional GUI, I'd say. Then stick to XForms for one more release.
Bug or not?
LyX doesn't break words in the editor at the end of a line, but it would break subscript or superscript at the end of line. __ Do you Yahoo!? Y! Web Hosting - Let the expert host your web site http://webhosting.yahoo.com/
Re: Small poll
Late, as the majority seem to have spoken, but... (a) and make 1.4.0 the qt release, as it seems to be what everyone wants. Rod On Mon, 28 Oct 2002, Andre Poenitz wrote: Just a small poll [As background: the Qt frontend is the single big item on the 1.3 list that's not done and won't be finished within the next few weeks.] What would _you_ prefer if you had the choice: (a) have 1.3.0 now as-is with its barely functional Qt frontend, start with the 1.4 cycle immediately. (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. (c) I don't care Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson) _ rod | Beneath the waves, the waves / That's where I will be / | I'm going to see the cow beneath the sea. | They Might Be Giants, Lincoln
Re: Small poll
I vote for (a). João.
Re: Small poll
On Mon, Oct 28, 2002 at 01:33:07PM +, John Levon wrote: I don't think we will have proper unicode support. However, if your Qt is built for anti-aliased fonts, you get it for free. I don't understand the connection between anti-alising and utf8. Could you explain this? Thanks Paul -- *Paul Tremblay * *[EMAIL PROTECTED]*
Re: Small poll
On Mon, Oct 28, 2002 at 10:20:40AM -0500, slitt wrote: I vote for A. We've lived with xforms for years -- another few months won't hurt. And, as you all are probably tired of hearing me say, BY FAR the worst LyX deficiency is the lack of character styles, and that should be top priority in 1.4. There's only so long the color pseudo-styles will work, because there are very few colors that are practical, and keeping track of them is difficult. Compared to the lack of character styles, xforms' problems are cosmetic. I strongly second this. Paul -- *Paul Tremblay * *[EMAIL PROTECTED]*
Re: Small poll
On Mon, Oct 28, 2002 at 09:24:45PM -0500, Paul Tremblay wrote: I don't think we will have proper unicode support. However, if your Qt is built for anti-aliased fonts, you get it for free. I don't understand the connection between anti-alising and utf8. Could you explain this? No connection. You get it ( == anti-aliasing) for free. john -- All photography is accurate - none of it is truth. - Richard Avedon
Small poll - Results
I've counted (a) 2 (b) 13 (c) 3 This obviously won't change if me, myself and I cast their votes. [For lyx-devel: I hereby officially admit defeat and I solemnly promise to do my growling and howling regarding this particular issue silently in a dark corner for the rest of the year. I really did not expect that kind of clear preference of appearance over functionality. Well, not the first time I've been proven wrong I guess.] Andre'
Re: Small poll - Results
On Mon, Oct 28, 2002 at 03:47:47PM +, John Levon wrote: [For lyx-devel: I hereby officially admit defeat and I solemnly promise to do my growling and howling regarding this particular issue silently in a dark corner for the rest of the year. I still am completely lost as to why you can't work in a branch, to be honest. Because I work better with immediate feedback and quite a few things would clash with places Lars wants to handle next anyway... I really did not expect that kind of clear preference of appearance over functionality. Well, not the first time I've been proven wrong I guess.] You were wrong because your assumptions are wrong. It has not so much to do with appearance. The sooner you understand this, the better have Qt asap (and - unspoken - let that ugly xform thingy die) is about appearance in my eyes. What else? Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: Small poll - Results
On Mon, Oct 28, 2002 at 05:27:00PM +0100, Andre Poenitz wrote: I still am completely lost as to why you can't work in a branch, to be honest. Because I work better with immediate feedback Mmmm, fair point and quite a few things would clash with places Lars wants to handle next anyway... You would have this problem anyway, no ? :) You were wrong because your assumptions are wrong. It has not so much to do with appearance. The sooner you understand this, the better have Qt asap (and - unspoken - let that ugly xform thingy die) is about appearance in my eyes. What else? Tried to use xforms menus recently ? (just a trivial example, naturally) john -- All photography is accurate - none of it is truth. - Richard Avedon
Re: Small poll - Results
On Mon, 28 Oct 2002, Andre Poenitz wrote: I really did not expect that kind of clear preference of appearance over functionality. Well, not the first time I've been proven wrong I guess.] I guess for many people the problem is that xforms is clunky enough to be not only ugly beyond redemption, but actually a usability hindrance. For instance: - it's nearly impossible to navigate with the keyboard - font changes easily render dialogs unusable. I have a 1600x1200 screen and because of this I'm forced to use lyx with nearly unreadable fonts. Every other app runs with nice fonts at normal physical sizes (but with lots of pixels for rendering). - Did I mention the thing was so ugly as to be almost painful to look at? Anyway, I've been a happy user of Lyx for 5 years and I could live with the xforms junk for another 5 if need be. Lyx is _that_ good (currently finishing my dissertation with 1.1.6f4). But believe me, I'll be one happy camper when xforms is wiped off the face of the earth. That thing is long overdue for being taken behind the barn and acquainted with the bright end of a shotgun. Cheers, f.
Check out Steve Litt's guide
If you haven't had a chance, please check out Steve Litt's guide to LyX at: http://www.troubleshooters.com/lpm/200210/200210.htm It is one of the most professional guides on open source software that I have come across. It should prove useful to both novices and experienced LyX users. One of my biggest complaints with open source software is the unreadable documentation that makes it extremelly difficult, if not impossible to use. Often this documentation is full of jargon, gratituous geek humor, and undecipherable sentences. Worst, open source documentation seems to have an aversion to good practical examples. Take a look at any of the man pages for a linux system sometimes. Steve's document avoids all of these faults. For example, it gives a lengthy example on how to set up your own style, and then explains line by line how what each piece of code means. Using this document, I set up my own style in a matter of minutes. If I have any complaint with Steve's document, it is that it is too short. He handles a number of important topics skillfully. If he tackled all aspects of LyX and made it into a book, it would undoubtedly be the best selling book for LyX. Good job, Steve! Paul -- *Paul Tremblay * *[EMAIL PROTECTED]*
Re: How do I insert horizontal space?
On Tue, Oct 29, 2002 at 07:40:45AM +1030, Darren Freeman wrote:
I know how to insert an hfill. I want something like that, but for a
fixed space (like a good ol' tab stop =)
\hspace{5cm} in ERT?
Yes, that should hurt ;-)
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
Re: Small poll
On Tue, Oct 29, 2002 at 01:07:26AM +0100, Vinay Ramnath wrote: It is not that I am ignorant about this, but LyX looks fine if you change the colours to your taste. The other things the developers want to implement in 1.3.x seem more important to me than the GUI, so if they have it ready and want to release it, release it right away. Not with a barely functional GUI, I'd say. Then stick to XForms for one more release. Oh, it's not an either xforms or Qt question. xform will stay anyway. The question is whether there should be additionally a Qt frontend. But it has been decided now anyway... Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: Bug or not?
On Mon, Oct 28, 2002 at 03:40:53PM -0800, Max Bian wrote: LyX doesn't break words in the editor at the end of a line, but it would break subscript or superscript at the end of line. Super/subscripts a faked anyway... Does it hurt you badly? Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: Small poll
Andre Since 1.2 works pretty well at the moment I would like to wait for 1.3 to have a fully (or as near as possible) Qt front end. Pete Martin
Re: Small poll
Hi, On Monday, 28. October 2002 07:40, Andre Poenitz wrote: | What would _you_ prefer if you had the choice: | (b) release 1.3.0 if the Qt frontend is ready and put everything | else to sleep until then. I'm still using lyx 1.1.6fix4 and I'm pretty pleased by this version. A QT-GUI would be a serious reason for me to switch to a new version of lyx, so I would prefer finishing the QT-GUI before release version 1.3. Michael.
RE: Small poll
Hi, My vote ist for (b). (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. Bye
Re: Small poll
Just a small poll [As background: the Qt frontend is the single big item on the 1.3 list that's not done and won't be finished within the next few weeks.] What would _you_ prefer if you had the choice: (a) have 1.3.0 now as-is with its barely functional Qt frontend, start with the 1.4 cycle immediately. (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. (c) I don't care Alternative (b): The only major annoyance that I'm bothered by, and which I'd like to see a patch for in 1.2.2, is the problem that LyX doesn't notice when Xfig- och Tgif images have been modified on disk. Other than that I think it's a great program :-) -- Christian Ridderström http://www.md.kth.se/~chr Mechatronics division Department of Machine Design http://www.md.kth.se
Re: Small poll
On Monday 28 October 2002 07:40, Andre Poenitz wrote: Just a small poll [As background: the Qt frontend is the single big item on the 1.3 list that's not done and won't be finished within the next few weeks.] What would _you_ prefer if you had the choice: (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. IMHO, will bring a lot of new LyX users. Most Linux Newbies are only using KDE applications and even dont know that there are a lot of other apps that would do the job better. Due to my experience a lot of the people using LyX for the first time in a LyX course are a bit detered when they see lyx pop up the first time. Thomas
Re: Small poll
What would _you_ prefer if you had the choice: (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. (b) would be great, and having a version of Lyx that copes with underscores in equation references will be even better:-) Jose -- José L Gómez Dans PhD student Tel: +44 114 222 5582 Radar Communications Group FAX; +44 870 132 2990 Department of Electronic Engineering University of Sheffield UK
Re: Small poll
On Mon, Oct 28, 2002 at 07:40:47AM +0100, Andre Poenitz wrote: What would _you_ prefer if you had the choice: (a) have 1.3.0 now as-is with its barely functional Qt frontend, start with the 1.4 cycle immediately. (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. (c) I don't care I would prefer (b) BUT only if Lyx would then fully support UTF-8/Xft2/fontconfig. Alexander
Re: Small poll
On Mon, Oct 28, 2002 at 12:59:35PM +0100, Alexander Volovics wrote: (a) have 1.3.0 now as-is with its barely functional Qt frontend, start with the 1.4 cycle immediately. (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. (c) I don't care I would prefer (b) BUT only if Lyx would then fully support UTF-8/Xft2/fontconfig. How do you vote in a real ballot: Make a cross somewhere and write down BUT only if he reduces taxes? Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: Small poll
Le Lundi 28 Octobre 2002 07:40, Andre Poenitz a écrit : (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. I am waiting for the Qt front-end and prefer to wait for it to be ready before 1.3 is released. -- Renaud Michel L' oûrs piede ses poy, mins måy ses lêdès manîres.
Re: Small poll
(b) for me too Tx Paul Andre Poenitz wrote: Just a small poll [As background: the Qt frontend is the single big item on the 1.3 list that's not done and won't be finished within the next few weeks.] What would _you_ prefer if you had the choice: (a) have 1.3.0 now as-is with its barely functional Qt frontend, start with the 1.4 cycle immediately. (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. (c) I don't care Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: Small poll
On Mon, Oct 28, 2002 at 01:06:01PM +0100, Andre Poenitz wrote:
(a) have 1.3.0 now as-is with its barely functional Qt frontend,
start with the 1.4 cycle immediately.
(b) release 1.3.0 if the Qt frontend is ready and put everything
else to sleep until then.
(c) I don't care
I would prefer (b)
BUT only if Lyx would then fully support UTF-8/Xft2/fontconfig.
How do you vote in a real ballot: Make a cross somewhere and write down
BUT only if he reduces taxes?
Sometimes {^_-}
OK how about:
I would prefer (b)
BUT only if Lyx would then fully support UTF-8/Xft2/fontconfig
else (a)
Forced multiple choice is too black and white here.
Alexander
Re: Small poll
The consensus from respondants appears to be strongly for b). I too offer my preference for b. My current 1.2 release works well enough for my current uses but a QT GUI would certainly be enough for me to upgrade. praedor -- Beware the leader who bangs the drums of war in order to whip the citizenry into a patriotic fervor...the citizenry, infused with fear and blinded with patriotism, will offer up all their rights unto the leader and gladly so. --unknown
Re: Small poll
On Mon, Oct 28, 2002 at 02:00:23PM +0100, Alexander Volovics wrote: Forced multiple choice is too black and white here. That was the intention ;-) Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: Small poll
On Mon, Oct 28, 2002 at 12:59:35PM +0100, Alexander Volovics wrote: BUT only if Lyx would then fully support UTF-8/Xft2/fontconfig. I don't think we will have proper unicode support. However, if your Qt is built for anti-aliased fonts, you get it for free. regards john -- All photography is accurate - none of it is truth. - Richard Avedon
compiling LyX
I just compiled LyX with qt frontend (I don't have xforms installed at all). Looks nice, but first thing I want to tell - compiling LyX requires A LOT of memory. I had 256MB without swap, and gcc has been killed in process of compiling. Adding swap helps, but no other source requires so much memory to compile. -- http://decopter.sf.net - free unrealistic helicopter simulator
dialog-preferences
I have bad fonts in menu (ISO-8559-1 instead -2), wanted to change it without editing config files... So I clicked Preferences - no window opened! I just see (dialog-preferences) at bottom of main window. PS. current CVS, qt frontend -- http://decopter.sf.net - free unrealistic helicopter simulator
Re: dialog-preferences
Jacek == Jacek Pop³awski [EMAIL PROTECTED] writes: Jacek I have bad fonts in menu (ISO-8559-1 instead -2), wanted to Jacek change it without editing config files... So I clicked Jacek Preferences - no window opened! I just see Jacek (dialog-preferences) at bottom of main window. Jacek PS. current CVS, qt frontend Preference frontend is not yet done for qt. Note that posting about the qt frontend should be done on lyx-devel. JMarc
Re: Small poll
On Mon, 2002-10-28 at 07:40, Andre Poenitz wrote: Just a small poll [As background: the Qt frontend is the single big item on the 1.3 list that's not done and won't be finished within the next few weeks.] What would _you_ prefer if you had the choice: (a) have 1.3.0 now as-is with its barely functional Qt frontend, start with the 1.4 cycle immediately. (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. (c) I don't care Andre' Hi, I vote (b) ! BTW: Just wondering, I don't try to start a flamewar. What is with the gnome frontend? Is it dead? bye johannes -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson) -- Johannes Behr [EMAIL PROTECTED] Computer Graphics Center
[qt-cvs] encoding
can't set ecoding in any way I put this in ~/.lyx/lyxrc \screen_font_encoding iso8859-2 \screen_font_roman -*-times \screen_font_sans -*-helvetica \screen_font_typewriter -*-courier \screen_font_popup -*-helvetica-medium-r \screen_font_menu -*-helvetica-bold-r when I run lyx -dbg 512 I see: Debugging `font' (Font handling) This font is NOT an exact match XFLD: -adobe-helvetica-bold-r-normal--14-140-75-75-p-82-iso10646-1 Font 'Bezszeryfowy, Pogrubiony, Prosty, Normalny, ty, KursywaWy, Podkrelony Wy, Kapitaliki Wy, Jzyk: English' matched by -adobe-helvetica-bold-r-normal--14-140-75-75-p-82-iso10646-1 The font has size: 15 Font 'Bezszeryfowy, Pogrubiony, Prosty, Normalny, ty, KursywaWy, Podkrelony Wy, Kapitaliki Wy, Jzyk: English' matched by -adobe-helvetica-bold-r-normal--14-140-75-75-p-82-iso10646-1 The font has size: 15 -- http://decopter.sf.net - free unrealistic helicopter simulator
Re: dialog-preferences
On Mon, Oct 28, 2002 at 03:31:51PM +0100, Jean-Marc Lasgouttes wrote: Jacek I have bad fonts in menu (ISO-8559-1 instead -2), wanted to Jacek change it without editing config files... So I clicked Jacek Preferences - no window opened! I just see Jacek (dialog-preferences) at bottom of main window. Jacek PS. current CVS, qt frontend Preference frontend is not yet done for qt. Note that posting about the qt frontend should be done on lyx-devel. Besides, you cannot set the widget fonts from LyX for Qt anyway. Use qtconfig (I think it is ..) john -- All photography is accurate - none of it is truth. - Richard Avedon
Re: Small poll
On Mon, 28 Oct 2002, Andre Poenitz wrote: (c) I don't care While the current UI may not be the prettyist, it works and -- for me -- that's what matters the most. Eye candy takes a much lower priority. Rich Dr. Richard B. Shepard, President Applied Ecosystem Services, Inc. (TM) 2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A. + 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | [EMAIL PROTECTED] http://www.appl-ecosys.com/
Re: dialog-preferences
On Mon, Oct 28, 2002 at 03:31:51PM +0100, Jean-Marc Lasgouttes wrote: Preference frontend is not yet done for qt. Note that posting about the qt frontend should be done on lyx-devel. I haven't seen lyx source yet, I don't have time now to contribute, so I decided to post only here, to not make developers angry :) -- http://decopter.sf.net - free unrealistic helicopter simulator
Re: Small poll
On Mon, Oct 28, 2002 at 06:44:13AM -0800, Rich Shepard wrote: While the current UI may not be the prettyist, it works and -- for me -- that's what matters the most. Eye candy takes a much lower priority. Eye candy is not what the GUII effort and the Qt frontend is about. regards john -- All photography is accurate - none of it is truth. - Richard Avedon
Re: dialog-preferences
On Mon, Oct 28, 2002 at 02:46:24PM +, John Levon wrote: Besides, you cannot set the widget fonts from LyX for Qt anyway. Use qtconfig (I think it is ..) Could you tell me what should I set in qtconfig? -- http://decopter.sf.net - free unrealistic helicopter simulator
Re: compiling LyX
On Mon, Oct 28, 2002 at 03:20:46PM +0100, Jacek Pop?awski wrote: I just compiled LyX with qt frontend (I don't have xforms installed at all). Looks nice, but first thing I want to tell - compiling LyX requires A LOT of memory. I had 256MB without swap, and gcc has been killed in process of compiling. Adding swap helps, but no other source requires so much memory to compile. You could switch off debug info. I can compile and link within 64M this way. Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson)
Re: dialog-preferences
On Mon, Oct 28, 2002 at 04:14:02PM +0100, Jacek Pop?awski wrote: On Mon, Oct 28, 2002 at 02:46:24PM +, John Levon wrote: Besides, you cannot set the widget fonts from LyX for Qt anyway. Use qtconfig (I think it is ..) Could you tell me what should I set in qtconfig? No idea. Do the other Qt-based programs work fine ? If so, why ? john -- All photography is accurate - none of it is truth. - Richard Avedon
Re: Small poll
On Mon, Oct 28, 2002 at 07:40:47AM +0100, Andre Poenitz wrote: (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. -- Bo Peng
Re: Small poll
On Monday 28 October 2002 01:40 am, you wrote: Just a small poll [As background: the Qt frontend is the single big item on the 1.3 list that's not done and won't be finished within the next few weeks.] What would _you_ prefer if you had the choice: (a) have 1.3.0 now as-is with its barely functional Qt frontend, start with the 1.4 cycle immediately. (b) release 1.3.0 if the Qt frontend is ready and put everything else to sleep until then. (c) I don't care Andre' I vote for A. We've lived with xforms for years -- another few months won't hurt. And, as you all are probably tired of hearing me say, BY FAR the worst LyX deficiency is the lack of character styles, and that should be top priority in 1.4. There's only so long the color pseudo-styles will work, because there are very few colors that are practical, and keeping track of them is difficult. Compared to the lack of character styles, xforms' problems are cosmetic. Steve -- _ Steve Litt Author: * Universal Troubleshooting Process courseware * Troubleshooting Techniques of the Successful Technologist * Rapid Learning: Secret Weapon of the Successful Technologist http://www.troubleshooters.com Troubleshooters.Com Webmaster (Legal Disclaimer) Follow these suggestions at your own risk. -
Re: dialog-preferences
On Mon, Oct 28, 2002 at 02:46:24PM +, John Levon wrote: On Mon, Oct 28, 2002 at 03:31:51PM +0100, Jean-Marc Lasgouttes wrote: Jacek I have bad fonts in menu (ISO-8559-1 instead -2), wanted to Jacek change it without editing config files... So I clicked Jacek Preferences - no window opened! I just see Jacek (dialog-preferences) at bottom of main window. Jacek PS. current CVS, qt frontend Preference frontend is not yet done for qt. Note that posting about the qt frontend should be done on lyx-devel. Besides, you cannot set the widget fonts from LyX for Qt anyway. Use qtconfig (I think it is ..) qtconfig will not help. Currently, the QT frontend have few problems with non iso-8859-1 languages.
[Re] Small pool
Hi I've used version 1.2 occasionaly but didn't ffound any major problems, so I'd prefer to have QT GUI ready. So option b is my choice. Regards EJ
Re: Small poll - Results (fwd)
Maybe this was supposed to go to the list? On Mon, Oct 28, 2002 at 06:00:14PM +0200, Tuukka Toivonen wrote: Maybe you should have mentioned what new features LyX has, for which people need to wait longer if they want to have Qt too? Better search and replace. Instant dvi preview e.g. for math. Ability to read any .lyx down to version 0.10. Smoother cursor navigation. Smoother handling of CutPaste. Support for short section titles etc. Support for wasy Symbols. Re-worked counters. Two or three new .layouts. Even somewhat working Qt frontend And of course loads of bugfixes. And probably some more. Andre'
Re: dialog-preferences
On Mon, Oct 28, 2002 at 05:58:28PM +0200, Dekel Tsur wrote: Currently, the QT frontend have few problems with non iso-8859-1 languages. Could you tell me how to set Polish keyboard in qt frontend ? (I have polish keyboard in X) -- http://decopter.sf.net - free unrealistic helicopter simulator
Re: Small poll
On Mon, Oct 28, 2002 at 07:40:47AM +0100, Andre Poenitz wrote: (a) have 1.3.0 now as-is with its barely functional Qt frontend, start with the 1.4 cycle immediately. Release version with QT frontend as fast as possible, so milions of people can use it and send bug raports, but *please* put any docs about qt frontend (fonts, keyboard!, working and non-working features) or just tell where are they (I can't find anything...). -- http://decopter.sf.net - free unrealistic helicopter simulator
