On 6 Dec 2013, at 01:24, Scott Ribe wrote:
> On Dec 5, 2013, at 11:09 AM, Gerriet M. Denkmann wrote:
>
>> Really. But I just changed all non-european characters to German characters
>> and the time changed from 53 sec to 1.2 seconds.
>>
>> Looks like CoreText does not like non-european chara
On 2013 Dec 05, at 08:15, Gerriet M. Denkmann wrote:
On 5 Dec 2013, at 19:55, Roland King wrote:
On 5 Dec, 2013, at 8:34 pm, Gerriet M. Denkmann
wrote:
Don't send 2Mb of search results to your webview. Do you really
need the case where you search for one character only? Don't send
data unt
On 6 Dec 2013, at 01:24, Scott Ribe wrote:
> On Dec 5, 2013, at 11:09 AM, Gerriet M. Denkmann wrote:
>
>> Really. But I just changed all non-european characters to German characters
>> and the time changed from 53 sec to 1.2 seconds.
>>
>> Looks like CoreText does not like non-european chara
On Dec 5, 2013, at 11:09 AM, Gerriet M. Denkmann wrote:
> Really. But I just changed all non-european characters to German characters
> and the time changed from 53 sec to 1.2 seconds.
>
> Looks like CoreText does not like non-european characters very much. And that
> WebKit is really not to b
On 5 Dec 2013, at 19:55, Roland King wrote:
>
> And really .. 50 seconds to render 2Mb, sure you don't want to check that
> again?
Really. But I just changed all non-european characters to German characters and
the time changed from 53 sec to 1.2 seconds.
Looks like CoreText does not like
On Dec 5, 2013, at 4:47 AM, Gerriet M. Denkmann wrote:
> 10.9.0. Given a search field, the user enters some chars, and a WebView is
> filled with all words containing these chars.
>
> Works fine, but one problem:
> When the user wants all words containing "no" but types a bit slowly, then
> th
On Dec 5, 2013, at 3:47 AM, Gerriet M. Denkmann wrote:
> How can I keep my user interface responsive?
You can have an explicit “Search” button, and wait till the button is pressed
to initiate the search. Not all search UIs have to be search-as-you-type.
Also, I agree with Roland that 50 secon
On 5 Dec 2013, at 19:55, Roland King wrote:
>
> On 5 Dec, 2013, at 8:34 pm, Gerriet M. Denkmann wrote:
>
>>>
>>> Don't send 2Mb of search results to your webview. Do you really need the
>>> case where you search for one character only? Don't send data until you
>>> have more than one and d
On 5 Dec, 2013, at 8:34 pm, Gerriet M. Denkmann wrote:
>>
>> Don't send 2Mb of search results to your webview. Do you really need the
>> case where you search for one character only? Don't send data until you have
>> more than one and don't send obviously too much data to be useful to the
>>
On 5 Dec 2013, at 19:25, Roland King wrote:
>
> On 5 Dec, 2013, at 7:47 pm, Gerriet M. Denkmann wrote:
>
>> 10.9.0. Given a search field, the user enters some chars, and a WebView is
>> filled with all words containing these chars.
>>
>> Works fine, but one problem:
>> When the user wants a
On 5 Dec, 2013, at 7:47 pm, Gerriet M. Denkmann wrote:
> 10.9.0. Given a search field, the user enters some chars, and a WebView is
> filled with all words containing these chars.
>
> Works fine, but one problem:
> When the user wants all words containing "no" but types a bit slowly, then
> t
10.9.0. Given a search field, the user enters some chars, and a WebView is
filled with all words containing these chars.
Works fine, but one problem:
When the user wants all words containing "no" but types a bit slowly, then this
happens:
- actionMethodFromSearchField: sender
receives "
12 matches
Mail list logo
