[prev in list] [next in list] [prev in thread] [next in thread]
List: kfm-devel
Subject: Re: Search Indicators in Dolphin
From: Vishesh Handa <me () vhanda ! in>
Date: 2013-06-06 14:55:14
Message-ID: CAOPTMKAn2RYQPyfmy+QtGox1RxB4PdSit74=mf-ehofdiFZEwQ () mail ! gmail ! com
[Download RAW message or body]
On Thu, Jun 6, 2013 at 8:11 PM, Frank Reininghaus
<frank78ac@googlemail.com>wrote:
> Hi Vishesh,
>
> 2013/6/6 Vishesh Handa:
> > I was thinking of showing the current directory which it is scanning
> > through, though I'm not sure how I would show that via the GUI or how I
> > would implement that.
> >
> > The reason for showing visual feedback is that if Nepomuk is not enabled
> > searching will take some time, and in that case there should be some
> visual
> > feedback as to where it is searching. Just a "processing" sign is not
> > enough.
>
> Right, I see what you mean. Showing the directory where it's currently
> searching in the status bar might be an option, but I'm not sure if
> there is a clean way to have a kioslave send that kind of information
> to Dolphin.
>
Right. Even I'm not sure how this would be done.
I'll investigate.
>
> >> (b) How would it be implemented?
> >>
> >> One option might be that we check (maybe in
> >> DolphinViewContainer::slotDirectoryLoadingStarted() ?) if Nepomuk is
> >> going to be used for the search, and ask Nepomuk somehow if a message
> >> as described in (a) should be shown, and if that is the case, just
> >> show it in the message widget. But maybe there are other options - I'm
> >> not extremely familiar with the search-related code, so I might not
> >> see the best solution.
> >
> >
> > I'm somewhat familiar with the code. Anyway, that's just an
> implementation
> > detail. I'm sure I can get it to work.
> >
> > The main question now is -
> >
> > Once the implementation is done, should I ask for an exception from the
> > release team? I would also probably need to ask the translation team.
> >
> > Or should we wait till 4.12?
>
> Well, I'd say that it depends on how much it affects the existing
> code. If it's as simple as calling a Nepomuk function to get a string
> that would be shown in the message widget, and that happens only if
> Nepomuk is enabled and not done with indexing (I'm thinking that this
> would not require more than ~20 lines of code on the Dolphin side, but
> I might be completely wrong), then I would not mind if we include it
> in 4.11.
>
The Nepomuk interfacing code will be quite small, but I'm not sure about
the UI code. Anyway, I'll try to implement it tomorrow or next week. Lets
see.
>
> Cheers,
> Frank
>
--
Vishesh Handa
[Attachment #3 (text/html)]
<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, \
Jun 6, 2013 at 8:11 PM, Frank Reininghaus <span dir="ltr"><<a \
href="mailto:frank78ac@googlemail.com" \
target="_blank">frank78ac@googlemail.com</a>></span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Hi Vishesh,<br> <br>
2013/6/6 Vishesh Handa:<br>
<div class="im">> I was thinking of showing the current directory which it is \
scanning<br> > through, though I'm not sure how I would show that via the GUI \
or how I<br> > would implement that.<br>
><br>
> The reason for showing visual feedback is that if Nepomuk is not enabled<br>
> searching will take some time, and in that case there should be some visual<br>
> feedback as to where it is searching. Just a "processing" sign is \
not<br> > enough.<br>
<br>
</div>Right, I see what you mean. Showing the directory where it's currently<br>
searching in the status bar might be an option, but I'm not sure if<br>
there is a clean way to have a kioslave send that kind of information<br>
to Dolphin.<br></blockquote><div><br></div><div>Right. Even I'm not sure how this \
would be done.<br><br></div><div>I'll investigate.<br> <br></div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
<div class="im"><br>
>> (b) How would it be implemented?<br>
>><br>
>> One option might be that we check (maybe in<br>
>> DolphinViewContainer::slotDirectoryLoadingStarted() ?) if Nepomuk is<br>
>> going to be used for the search, and ask Nepomuk somehow if a message<br>
>> as described in (a) should be shown, and if that is the case, just<br>
>> show it in the message widget. But maybe there are other options - \
I'm<br> >> not extremely familiar with the search-related code, so I might \
not<br> >> see the best solution.<br>
><br>
><br>
> I'm somewhat familiar with the code. Anyway, that's just an \
implementation<br> > detail. I'm sure I can get it to work.<br>
><br>
> The main question now is -<br>
><br>
> Once the implementation is done, should I ask for an exception from the<br>
> release team? I would also probably need to ask the translation team.<br>
><br>
> Or should we wait till 4.12?<br>
<br>
</div>Well, I'd say that it depends on how much it affects the existing<br>
code. If it's as simple as calling a Nepomuk function to get a string<br>
that would be shown in the message widget, and that happens only if<br>
Nepomuk is enabled and not done with indexing (I'm thinking that this<br>
would not require more than ~20 lines of code on the Dolphin side, but<br>
I might be completely wrong), then I would not mind if we include it<br>
in 4.11.<br></blockquote><div><br></div><div>The Nepomuk interfacing code will be \
quite small, but I'm not sure about the UI code. Anyway, I'll try to \
implement it tomorrow or next week. Lets see.<br> <br></div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">
<br>
Cheers,<br>
Frank<br>
</blockquote></div><br><br clear="all"><br>-- <br><span \
style="color:rgb(192,192,192)">Vishesh Handa</span><br> </div></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic