[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: Seaching for a string
From:       bbeschow () cs ! tu-berlin ! de
Date:       2009-10-29 1:38:15
Message-ID: d6482b43a49c53f3e18af1982c6203ac.squirrel () mail ! cs ! tu-berlin ! de
[Download RAW message or body]

> On Wednesday 28. October 2009 18.49.32 bbeschow@cs.tu-berlin.de wrote:
>> Well, you can use KTE::SearchInterface::searchText(), which is
>> implemented
>> by KateDocument. However, you'd have to supply the ranges for searching
>> manually. Is this sufficient for your needs?
>
> As long as I can supply the range "the whole document" and i can use
> KateView's findNext() method for getting the next hit. (My 'n' command,
> i.e.
> "next hit" is simply m_view->findNext().)

Sure, you could supply the whole document range for searching to that
method but the findNext *button* wouldn't work as expected. So if you
could live without the findNext button working, go with the searchText()
method. Otherwise, I don't currently see an easy solution.

>> BTW, I've started to refactor the search stuff. I'm planning to separate
>> the business logic from the presentation, which means that searching
>> from
>> the current cursor position will be available without the search bar.
>
> ♥
>
>> Unfortunately, due to my university work, my time is currently very
>> limited. But be prepared that after the sprint this will be finished ;-)
>
> i'll do your homework for you while you implement it ;-)

Sounds like a good deal to me: You finish my diploma thesis and I do the
refactoring for you ;-) (which I have half way done BTW)

Greetings,
Bernhard


_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel

[prev in list] [next in list] [prev in thread] [next in thread]