Angus Leeming wrote:
> > BTW I'd prefer a drop down list to the buttons. In the qt dialogs,
> > the buttons are taking a lot of space and the dir combo gets too
> > short. And probably we can even store bookmarks.
>
> What's stopping you ... ;-)
Currently the float-dialogs-do-not-update-correctly
Juergen Spitzmueller wrote:
>> Are you describing a "Qt feature request"? ;-)
>
> Indeed, it is not possible with the native qt dialog AFAICS. I think
> that the restrictions of the qt file dialog are enough to judge a
> kde frontend. The kde file dialog rocks.
It's GPL code isn't it? Why not jus
Angus Leeming wrote:
I think the philosophy is to make LyX as easy and comfortable to use
as possible. The native (Finder) browser in Mac OS X is not only
more attractive and versatile than the Qt browser that LyX sometimes
uses, but is more familiar and intuitive to a Mac user. Hence it
makes s
Angus Leeming wrote:
> Are you describing a "Qt feature request"? ;-)
Indeed, it is not possible with the native qt dialog AFAICS. I think that the
restrictions of the qt file dialog are enough to judge a kde frontend. The
kde file dialog rocks.
BTW I'd prefer a drop down list to the buttons. In
Andre Poenitz wrote:
> On Wed, Feb 25, 2004 at 03:04:38PM +0100, Alfredo Braunstein wrote:
>> Jean-Marc Lasgouttes wrote:
>>
>> >>> So the question boils down to: does the benefit of these buttons
>> >>> overweights the benefit of native dialogs?
>> >
>> > Angus> Definitely.
>> >
>> > Is that a
On Wed, Feb 25, 2004 at 03:04:38PM +0100, Alfredo Braunstein wrote:
> Jean-Marc Lasgouttes wrote:
>
> >>> So the question boils down to: does the benefit of these buttons
> >>> overweights the benefit of native dialogs?
> >
> > Angus> Definitely.
> >
> > Is that a statement on the whole sentence
Ronald Florence wrote:
> I think the philosophy is to make LyX as easy and comfortable to use
> as possible. The native (Finder) browser in Mac OS X is not only
> more attractive and versatile than the Qt browser that LyX sometimes
> uses, but is more familiar and intuitive to a Mac user. Hence i
Jean-Marc Lasgouttes wrote:
>>> So the question boils down to: does the benefit of these buttons
>>> overweights the benefit of native dialogs?
>
> Angus> Definitely.
>
> Is that a statement on the whole sentence, or an answer to the
> question?
Yes.
Alfredo
Jean-Marc Lasgouttes wrote:
>>> So the question boils down to: does the benefit of these buttons
>>> overweights the benefit of native dialogs?
>
> Angus> Definitely.
>
> Is that a statement on the whole sentence, or an answer to the
> question?
I *like* the buttons. I find them *very* useful. I
Angus Leeming wrote:
OK, the `problem' is that several places call
QFileDialog::getOpenFileName explicitly:
And if we could call this function for every use of a file browser in
LyX, the GUI would be consistent for a Mac OS X user. I don't know what
impact this would have on other operating sys
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>> However, it would be better to have browse*File use the native file
>> dialogs when possible.
Angus> Agreed. if (extra_buttons.empty()) call getOpenFileName else
Angus> roll our own ?
Except that these are almost never empty, and it i
Jean-Marc Lasgouttes wrote:
> OK, the `problem' is that several places call
> QFileDialog::getOpenFileName explicitly:
>
> As you can see, the status of QExternalDialog has changed in
> 1.4.0cvs. And this imo a bug that it does not use broweRelFile
> anymore (since what we want is really a relativ
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> browseRelFile is defined in
Angus> frontends/controllers/helper_funcs.C. Maybe you could dig some
Angus> more?
OK, the `problem' is that several places call
QFileDialog::getOpenFileName explicitly:
schuss: grep -ri QFileDialog::ge
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Ok. What I tried to show by pasting in the snippets of code
Angus> from LyX 1.4, above, is that the BibTeX and External dialogs
Angus> both invoke the same routine, browseRelFile, to launch the file
Angus> browser dialog. I fail to
Ronald Florence wrote:
> Angus Leeming wrote:
>
>> what about InsetGraphics?
>>
>> In 1.4, ControlBibtex::browse invokes:
>> return browseRelFile(in_name, kernel().bufferFilepath(),
>> title, filters, false, dir1);
>>
>> ControlExternal::browse
>> re
Angus Leeming wrote:
what about InsetGraphics?
In 1.4, ControlBibtex::browse invokes:
return browseRelFile(in_name, kernel().bufferFilepath(),
title, filters, false, dir1);
ControlExternal::browse
return browseRelFile(input, bufpath, title, filter, fal
Ronald Florence wrote:
> This may be a helpful in discerning why LyX/Mac sometimes uses the
> native (Finder) for FileDialog and sometimes uses the Qt dialog.
>
> On LyX/Mac-1.3.4, the native (Finder) dialog is used for the Print,
> BibTeX and Externalinsets, and the Qt dialog is used only for
>
This may be a helpful in discerning why LyX/Mac sometimes uses the
native (Finder) for FileDialog and sometimes uses the Qt dialog.
On LyX/Mac-1.3.4, the native (Finder) dialog is used for the Print,
BibTeX and Externalinsets, and the Qt dialog is used only for File->Open.
One LyX/Mac-1.4.0, th
On Feb 24, 2004, at 12:00 PM, Jean-Marc Lasgouttes wrote:
Ronald> In LyX/Mac, the External insets use the familiar native system
Ronald> Finder. Would it be possible to use the system file browser
Ronald> for the File->Open dialog as well? [...]
The only difference that I can see is that the Exte
> "Ronald" == Ronald Florence <[EMAIL PROTECTED]> writes:
Ronald> In LyX/Mac, the External insets use the familiar native system
Ronald> Finder. Would it be possible to use the system file browser
Ronald> for the File->Open dialog as well? This would make the
Ronald> application much more Mac-
In LyX/Mac, the External insets use the familiar native system Finder.
Would it be possible to use the system file browser for the File->Open
dialog as well? This would make the application much more Mac-like.
(The windows-pc style browser used in the File->Open dialog is
unfamiliar and off-pu
21 matches
Mail list logo
