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 o
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
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 Securi
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
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 redemptio
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 co
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
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
I vote for (a).
João.
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
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/
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
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 leng
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 r
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 eithe
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 b
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
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
>
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.
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 wh
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
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 c
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
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
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
> pi
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 poss
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, no
On Mon, Oct 28, 2002 at 01:35:07PM -0600, Bruce Tyler wrote:
> What would be wrong with gtk?
Nothing. Are you saying you want to help out with the gnome frontend ?
Or start a non-gnome gtk frontend ? Great !
One of the side-benefits of the GUII work is that we get call people's
bluff before a to
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.]
>
> Wha
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 p
I go for (b) as well. I played around with a snapshot of 1.3 some time
back and there are some very nice features there, but I'm in no
desperate hurry to upgrade. Since LyX is going up a major notch in
version number, it may as well do it with a bang.
Robin
--
"A free man ought not to learn a
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
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 doc
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
>
> Sor
On Mon, Oct 28, 2002 at 06:38:49PM +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
On Mon, Oct 28, 2002 at 06:38:49PM +0200, Tuukka Toivonen wrote:
> Maybe this was supposed to go to the list?
Not really. It looked like a private question of you and I want to bury
that topic now...
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do
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*
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
On Monday 28 October 2002 15:20, slitt 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 t
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
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 a
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
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
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" -
On Mon, Oct 28, 2002 at 04:26:03PM +0100, Andre Poenitz 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 c
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
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
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 d
On Mon, Oct 28, 2002 at 03:22:57PM +0100, Jacek Pop?awski wrote:
> 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,
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
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
>
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
On Mon, Oct 28, 2002 at 03:32:41PM +0100, Johannes Behr wrote:
> BTW: Just wondering, I don't try to start a flamewar. What is with the
> gnome frontend? Is it dead?
Nobody works on it currently as far as I can tell.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will
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
--
"
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
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 Servi
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 o
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"
> "Jacek" == Jacek Pop³awski <[EMAIL PROTECTED]> writes:
Jacek> I just compiled LyX with qt frontend (I don't have xforms
Jacek> installed at all). Looks nice, but first thing I want to tell -
Jacek> compiling LyX requires A LOT of memory. I had 256MB without
Jacek> swap, and gcc has been kill
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
> "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.
J
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 simu
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
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
On Mon, Oct 28, 2002 at 04:57:36PM +1100, Steven Homolya wrote:
> Having got frustrated with the bugs in lyx 1.2.0 and the inability to edit lyx
I hope these bugs are already known, or you have reported them :)
> You can get a linux executable (redhat 7.2) here:
> http://www.spme.monash.edu.au/
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)
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 c
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.
(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 fun
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,
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.
>
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 everythi
> 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é
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
> 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
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
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 woul
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
78 matches
Mail list logo
