Helge Hafting ha scritto:
Can the "advanced" search do a simple search?
Ok, the current implementation has only search, but, if LyX is going
to integrate the feature, I'll be glad to implement the replace part
as well. It should not be difficult at all: the searched text is already
selected, so
Tommaso Cucinotta <[EMAIL PROTECTED]> writes:
> Jean-Marc Lasgouttes ha scritto:
>> Another great feature we could steal from acrobat reader is to show a
>> list of hits in the document (with some context) allowing the user to
>> go directly to the right one. Of course, if the side bar is already
Jean-Marc Lasgouttes wrote:
Tommaso Cucinotta <[EMAIL PROTECTED]> writes:
Actually, the curious thing is that, AFAIK, LyX would be the
1st word processor ever with such a find feature (e.g. not a
simple text field, but an enhanced one, especially useful
for searching complex maths). But I'm
Jean-Marc Lasgouttes ha scritto:
Another great feature we could steal from acrobat reader is to show a
list of hits in the document (with some context) allowing the user to
go directly to the right one. Of course, if the side bar is already
full like it is now, it is a bit difficult. But I think
Tommaso Cucinotta <[EMAIL PROTECTED]> writes:
> Actually, the curious thing is that, AFAIK, LyX would be the
> 1st word processor ever with such a find feature (e.g. not a
> simple text field, but an enhanced one, especially useful
> for searching complex maths). But I'm just considering
> the few
Abdelrazak Younes ha scritto:
Probably a few other use cases where it could be used are:
- having a split-window feature, that would allow to have
more workareas (on same or different buffers) in the same
LyX View
Probably, I've thought of another possible use case for using another
GuiWorkA
Hans Meine ha scritto:
http://feanor.sssup.it/~tommaso/findadv.png
http://feanor.sssup.it/~tommaso/findadv-re.png
Great, really!
Actually, the curious thing is that, AFAIK, LyX would be the
1st word processor ever with such a find feature (e.g. not a
simple text field, but an enhanc
Tommaso Cucinotta wrote:
In the first place, I was thinking it had to be a single-par widget,
but probably it is an unneeded restriction.
I think we shouldn't put this restriction in the initial design indeed.
Anyway, having a simple-to-use LyX Widget would help a lot reuse. By
simple-to-u
Tommaso Cucinotta wrote:
Abdelrazak Younes ha scritto:
I would say "for having more workarea widgets around".
Probably, whether embedded into dialogs, toolbars or tab
panes is not that important.
Yes, we also want split views but I see the two kinds as separate. I
have plans to implement split
On Samstag 06 Oktober 2007, Tommaso Cucinotta wrote:
> I've uploaded a couple of screenshots that show what the idea (actually,
> the current
> uncomplete implementation) looks like here:
>
> http://feanor.sssup.it/~tommaso/findadv.png
> http://feanor.sssup.it/~tommaso/findadv-re.png
Great, re
Edwin Leuven ha scritto:
Abdelrazak Younes wrote:
For advance search&replace. The idea would be that you can search for
a chunk of text containing insets (including math or charstyle) and
could replace it with another text containing insets.
Clearer?
so the idea is to replace qt's line edit
Abdelrazak Younes ha scritto:
I would say "for having more workarea widgets around".
Probably, whether embedded into dialogs, toolbars or tab
panes is not that important.
Yes, we also want split views but I see the two kinds as separate. I
have plans to implement split view but not as an embedde
Cucinotta Tommaso wrote:
On Fri, 5 Oct 2007 20:38:52 +0200
Andre Poenitz <[EMAIL PROTECTED]> wrote:
>>we need a good infrastructure for embedding one or more workareas
>>into a dialog.
I would say "for having more workarea widgets around".
Probably, whether embedded into dialogs, toolbars or
On Fri, 5 Oct 2007 20:38:52 +0200
Andre Poenitz <[EMAIL PROTECTED]>
wrote:
>>we need a good infrastructure for embedding one or
more workareas
>>into a dialog.
I would say "for having more workarea widgets around".
Probably, whether embedded into dialogs, toolbars or tab
panes is not that im
Andre Poenitz wrote:
Use case 1: I want to replace all occurrence of "xxx" with "\emph{xxx}".
Use case 2: I want to replace all occurrence of "a_{b}" with "a_{b^2}"
Clearer?
Sounds like firing up vi on the .lyx file in an xterm is the fastest way
to solve this ;-)
What about implementin
On Fri, Oct 05, 2007 at 02:39:33PM +0200, Abdelrazak Younes wrote:
> Edwin Leuven wrote:
> >Abdelrazak Younes wrote:
> >>we need a good infrastructure for embedding one or more workareas
> >>into a dialog.
> >
> >could you explain briefly why?
>
> For advance search&replace. The idea would be that
On Fri, Oct 05, 2007 at 11:27:12AM +0200, Abdelrazak Younes wrote:
> Hello,
>
> I would like to help Tommaso to finish his Advanced Search dialog (see
> http://bugzilla.lyx.org/show_bug.cgi?id=3998). For this, we need a good
> infrastructure for embedding one or more workareas into a dialog. So
Edwin Leuven wrote:
Abdelrazak Younes wrote:
For advance search&replace. The idea would be that you can search for
a chunk of text containing insets (including math or charstyle) and
could replace it with another text containing insets.
Clearer?
so the idea is to replace qt's line edits wit
Abdelrazak Younes wrote:
For advance search&replace. The idea would be that you can search for a
chunk of text containing insets (including math or charstyle) and could
replace it with another text containing insets.
Clearer?
so the idea is to replace qt's line edits with proper (single par)
Edwin Leuven wrote:
Abdelrazak Younes wrote:
we need a good infrastructure for embedding one or more workareas
into a dialog.
could you explain briefly why?
For advance search&replace. The idea would be that you can search for a
chunk of text containing insets (including math or charstyle)
Abdelrazak Younes wrote:
we need a good infrastructure for embedding one or more workareas
into a dialog.
could you explain briefly why?
Hello,
I would like to help Tommaso to finish his Advanced Search dialog (see
http://bugzilla.lyx.org/show_bug.cgi?id=3998). For this, we need a good
infrastructure for embedding one or more workareas into a dialog. So far
we have two options:
1) The dialog is a main window dependent dock wi
22 matches
Mail list logo
