> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> lib/Makefile.am?
Yes. Note that we already set some Makefile variables for each
frontend, so it would not be really more complicated.
Lars> Hmm da hmm... and we talked about making separate configure
Lars> scorpts for the fron
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>
| Lars> No. ui files are for all frontends... glade just for one. So you
| Lars> must conditionalize in the make file (and this is the messy
| Lars> part really...) I do not thin
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> No. ui files are for all frontends... glade just for one. So you
Lars> must conditionalize in the make file (and this is the messy
Lars> part really...) I do not think that we should let frontent files
Lars> bleed into the s
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>
| | This would be solved if the glade files were put in lib/ui/glade for
| | example. Lars thinks that they should be with the gtk sources, I think
| | it is not a good idea...
>
|
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
| This would be solved if the glade files were put in lib/ui/glade for
| example. Lars thinks that they should be with the gtk sources, I think
| it is not a good idea...
Lars> I think it gets messy...
Why exactly? Glade files are
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>> "Jose'" == Jose' Matos <[EMAIL PROTECTED]> writes:
>
| Jose'>- gtk, it sucks to need to install the package to have it
| Jose'> running, or else as soon as you open any dialog:
>
| Jose'> (lyx-gtk:18135): libglade-WARNING **: could no
> "Jose'" == Jose' Matos <[EMAIL PROTECTED]> writes:
Jose'> - gtk, it sucks to need to install the package to have it
Jose'> running, or else as soon as you open any dialog:
Jose'> (lyx-gtk:18135): libglade-WARNING **: could not find glade file
Jose'> '' Aborted
This would be solved if the
On Fri, Mar 12, 2004 at 09:45:50AM +0100, Alfredo Braunstein spake thusly:
> Martin Vermeer wrote:
>
> > Alternative Great Idea(tm): give a full width inset _always_ the width
> > w - i, where w is screen max width and i is standard inset width. No
> > special casing.
>
> What's the standard in
Alfredo Braunstein wrote:
John Levon wrote:
Minipages. If I set two minipages to 50% it would be nice if they
appeared next to each other, like they used to. That's all.
Didn't knew that (never used that myself). I don't know if I would like it
though - that too much wysiwyg at the cost of clu
On Thu, Mar 11, 2004 at 11:40:39AM +, Angus Leeming spake thusly:
>
> Given that everything is an inset, why don't we have an "indent" inset
> and insert this as the first character in a paragraph? That would
> remove all this special casing from the core.
...
> --
> Angus
Alternative G
Martin Vermeer wrote:
> Alternative Great Idea(tm): give a full width inset _always_ the width
> w - i, where w is screen max width and i is standard inset width. No
> special casing.
What's the standard inset width?
Alfredo
John Levon wrote:
> On Thu, Mar 11, 2004 at 08:52:24PM +0100, Alfredo Braunstein wrote:
>
>> Of course, the question is *when uncollapsed*. I cannot draw it
>> uncollapsed with ascii-art because I don't know how it will rebreak
>> (exactly the question). My question is (third time) how does your
On Thu, Mar 11, 2004 at 08:52:24PM +0100, Alfredo Braunstein wrote:
> Of course, the question is *when uncollapsed*. I cannot draw it uncollapsed
> with ascii-art because I don't know how it will rebreak (exactly the
> question). My question is (third time) how does your ideal_width works... So
>
On Thu, Mar 11, 2004 at 07:30:23PM +, Angus Leeming wrote:
> Sure, but this visual info need not be the width of the area into
> which you're typing the text. It could be a horizontal arrow with the
> actual width as text. Eg:
>
> <-- Width 1 in -->
> -
Sure, why not, but
John Levon wrote:
>> >> blah blah blah [I] blah
>> >> blah blah blah blah blah bla
>> >
>> > I don't understand your example. Row breaking is done in left-to-right,
>> > top-to-bottom manner, how could the above ever have an unknown width ?
>>
>> Well soppose [I] is an inset full of text (i
John Levon wrote:
>> > Minipages. If I set two minipages to 50% it would be nice if they
>> > appeared next to each other, like they used to. That's all.
>>
>> Didn't knew that (never used that myself). I don't know if I would
>> like it though - that too much wysiwyg at the cost of clutter
>> edi
On Thu, Mar 11, 2004 at 07:50:21PM +0100, Alfredo Braunstein wrote:
> > Minipages. If I set two minipages to 50% it would be nice if they
> > appeared next to each other, like they used to. That's all.
>
> Didn't knew that (never used that myself). I don't know if I would like it
> though - that
John Levon wrote:
> Minipages. If I set two minipages to 50% it would be nice if they
> appeared next to each other, like they used to. That's all.
Didn't knew that (never used that myself). I don't know if I would like it
though - that too much wysiwyg at the cost of clutter editing.
> Colour
On Thu, Mar 11, 2004 at 11:40:39AM +, Angus Leeming wrote:
> Given that everything is an inset, why don't we have an "indent" inset
> and insert this as the first character in a paragraph? That would
> remove all this special casing from the core.
It would be lovely and of course several of
On Thu, Mar 11, 2004 at 09:41:13AM +0100, Alfredo Braunstein wrote:
> I mean, I'm sure you know it's not the only open bug in current cvs.
He he :)
(never ashamed to overuse emoticons myself!)
> > o how wide is the box
> > o what width does a char want (for full width insets: 100%, for
> > mi
Angus Leeming wrote:
>> The only real problem I see with the current implementation is the
>> inset placement in the first position of the first indented line of
>> a paragraph. It is probably easy IMHO to find a quick solution for
>> that without changing the overall scheme...
>
> Given that eve
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Given that everything is an inset, why don't we have an
Angus> "indent" inset and insert this as the first character in a
Angus> paragraph? That would remove all this special casing from the
Angus> core.
Angus> Guess we'd also need
On Thu, Mar 11, 2004 at 11:40:39AM +, Angus Leeming wrote:
> > The only real problem I see with the current implementation is the
> > inset placement in the first position of the first indented line of
> > a paragraph. It is probably easy IMHO to find a quick solution for
> > that without chang
Alfredo Braunstein wrote:
> Why would anyone want to waste the 75% of the screen!?? I think it's
> really silly to represent %col in a wysiwyg way. Then full row
> insets are already represented by the display() bool.
Hear! Hear!
> The only real problem I see with the current implementation is t
John Levon wrote:
> Not sure it's random, given the nubmer of times it's been discussed.
I mean, I'm sure you know it's not the only open bug in current cvs.
(emoticon elided)
> If you missed out the long discussions, then sorry, I had assumed they
> were somewhat unavoidable.
I've probably ign
On Wed, Mar 10, 2004 at 10:15:11PM +0100, Alfredo Braunstein wrote:
> Good for you. Well as I've started fixing drawing problems only a short time
> ago, I've probably missed it at that time. But you really expect me to
> remember your random solution to a random bug?
Not sure it's random, given
John Levon wrote:
> I really had thought I'd described the exact issue *several* times, *in
> detail*, and said what I thought should be done, and even started coding
> it.
Good for you. Well as I've started fixing drawing problems only a short time
ago, I've probably missed it at that time. But
Angus Leeming wrote:
> Alfredo Braunstein wrote:
>
>> Alfredo Braunstein wrote:
>>
>>> Jose' Matos wrote:
>>>
- xforms, using ERT to see how it works with Alfredo's patch, I
guess there is some kind of off by one error, see attached image.
The last character is hidden by the scro
On Wed, Mar 10, 2004 at 02:32:34PM +0100, Alfredo Braunstein wrote:
> Well, it turns out that this is not a trivial bug, but something structural
> with the drawing scheme we'd have to sort out. The problem is the
> following: in a paragraph with first indented line, the avail space is
> something
Alfredo Braunstein wrote:
> Alfredo Braunstein wrote:
>
>> Jose' Matos wrote:
>>
>>> - xforms, using ERT to see how it works with Alfredo's patch, I
>>> guess there is some kind of off by one error, see attached image.
>>> The last character is hidden by the scroll bar. Other than that I
>>> rea
Alfredo Braunstein wrote:
> Jose' Matos wrote:
>
>> - xforms, using ERT to see how it works with Alfredo's patch, I guess
>> there is some kind of off by one error, see attached image. The last
>> character is hidden by the scroll bar. Other than that I really like the
Well, it turns out that th
Jose' Matos wrote:
> - xforms, using ERT to see how it works with Alfredo's patch, I guess
> there is some kind of off by one error, see attached image. The last
> character is hidden by the scroll bar. Other than that I really like the
Uhm, confirmed, but it's not related to my patch, there's so
Hi,
issues:
- qt, I am using qt 3.3.1, after compiling lyx when I run it I get:
$ src/lyx
trying without Euro
Aborted
I remember having seen something saying that this is a bug related with qt
3.3.1 but I am not sure, anyway here it is the report.
- gtk, it sucks
33 matches
Mail list logo
