No subject
Thu Oct 29 11:12:40 MST 2009
Thu Nov 26 15:40:10 2009 DEBUG [MacSword] [SwordSearching -createIndexAndReportTo:] start indexing...
Thu Nov 26 15:40:17 2009 WARN [MacSword] [SwordBible -indexContentsIntoIndex:] key = nil!
Thu Nov 26 15:40:51 2009 WARN [MacSword] [SwordBible -indexContentsIntoIndex:] key = nil!
Thu Nov 26 15:41:03 2009 DEBUG [MacSword] [SwordSearching -createIndexAndReportTo:] stopped indexing
so my guess of over 50 seconds was off -- it was 47 secs... :)
Oh, btw, while I remember: I have a patch or 2 to send you for some of the backend of MacSword2. :) Will send them 1st thing in the morning :)
On 27/11/2009, at 10:17 PM, Manfred Bergmann wrote:
> Hi Nic.
>
> How did you measure indexing? Best is to look in the log file. For indexing there should be lines like this:
> ------------
> Wed Nov 4 07:46:43 2009 DEBUG [MacSword] [SwordSearching -createIndexAndReportTo:] start indexing...
> Wed Nov 4 07:46:52 2009 DEBUG [MacSword] [SwordSearching -createIndexAndReportTo:] stopped indexing
> ------------
>
> Which mark start and finish of index process.
>
>
>
> Manfred
>
>
> Am 26.11.2009 um 05:27 schrieb Nic Carter:
>
>>
>> Thanks for the quick reply, Greg :)
>>
>> I have CLucene running fine on the iPhone (I found getting cURL a bit more tricky!), I'm just curious about CLucene .23 (faster, less memory footprint) vs .21 (which is what sword currently uses) and Nathan was looking into this, I think?
>>
>> Just timed indexing KJV on my 2.5 year old MacBook Pro (using MacSword2 - which I'm loving, btw!) & it was over 50 seconds. I'm laughing at how long that would take on an iPhone or any such device! What have others done for search on small/similar devices?
>>
>> Thanks, ybic
>> nic... :)
>>
>> ps: I've submitted PocketSword to the App Store. I'm giving it 2 weeks before I allow myself to wonder how it's going.... Will ping to the list when it gets accepted (cause it WILL be accepted!!!) :)
>>
>> On 26/11/2009, at 3:54 PM, Greg Hellings wrote:
>>
>>> Nic,
>>>
>>> On Wed, Nov 25, 2009 at 10:43 PM, Nic Carter <niccarter at mac.com> wrote:
>>>>
>>>> Hi there Nathan. :)
>>>>
>>>> I was wondering how you were going on this?
>>>>
>>>> I'm working on an iPhone front-end & am about to start work on v1.1. The main feature for 1.1 is search & I'm examining the various options that I have to do this....... I pulled it from v1.0 due to the headaches it caused & so now I have to face up to it! ;)
>>>
>>> I can't answer for Nathan, and I haven't bothered with anything for
>>> the iPhone in quite some time (I found their GUI creator kit to be
>>> completely a black art, and their idea of a "delegator" didn't seem to
>>> match up with my experience of event listeners). However, I do have
>>> some experience with bending configuration utilities into submission.
>>>
>>> CLucene, if I'm not mistaken, defaults its build system to CMake.
>>> Here you're in luck, because CMake is actually comprehensible to the
>>> uninitiated, while autotools has a very steep learning curve. You
>>> might just want to try building a version of the CLucene library for
>>> iPhone and link that into your SWORD build.
>>>
>>> This link http://stackoverflow.com/questions/794137/how-to-set-up-cmake-to-build-a-library-for-the-iphone
>>> seems to have some helpful hints, including a promise of a full How-To
>>> guide at the bottom. Seeing as you managed to build SWORD for the arm
>>> processor, I'm guessing you have most of the inside details needed. A
>>> possibly more up-to-date version of the mentioned guide for 3.0 and
>>> 3.1 also appears here
>>> http://sites.google.com/site/michaelsafyan/coding/articles/iphone/cross-compiling-for-the-iphone-using-cmake.
>>>
>>> Best of luck, I hope to see your app in the AppStore soon!
>>>
>>> --Greg
>>>
>>>>
>>>> Any direction you could give me would be greatly appreciated.
>>>>
>>>> Thanks, ybic
>>>> nic... :)
>>>>
>>>> On 20/10/2009, at 4:28 AM, Nathan Anderson wrote:
>>>>
>>>>> Matthew,
>>>>>
>>>>> Thanks for letting me know -- I kinda wondered if that was the case.
>>>>> I have already deb-ized the .21b for this device to get something going.
>>>>> When I have some free time; I will come back and work on understanding what
>>>>> sword needs from Clucene and will attempt to make a #DEFINE able patch to
>>>>> allow .23 or .21 to work.
>>>>>
>>>>> As for indexes, I'm not sure -- I understand .21 is compatible with
>>>>> 1.8/9 branch of Jlucene. But .23 is compatible with 2.3.2 branch of Jlucene
>>>>> and that version of J/C Lucene is much faster, with if, I recall correctly,
>>>>> a slightly lower memory footprint. Since the device I'm working with is a
>>>>> low memory and a embedded arm chip; faster and lower memory requirements is
>>>>> a very (very) nice perk. ;-)
>>>>>
>>>>> Nathan.
>>>>>
>>>>> -----Original Message-----
>>>>> From: Matthew Talbert [mailto:ransom1982 at gmail.com]
>>>>> Sent: Monday, October 19, 2009 12:02 PM
>>>>> To: SWORD Developers' Collaboration Forum
>>>>> Subject: Re: [sword-devel] Clucene .09.23 and Sword 1.6.0 / 1.6-svn
>>>>> -Compiling Help
>>>>>
>>>>>> I'm working on porting the whole stack to another device that
>>>>>> does not have any of the libraries yet. I will "use" 21b if I have
>>>>>> to to get past the issue. But I would love to use .23 if possible.
>>>>>
>>>>> I think it would be great to have support for .23. As far as I know, no one
>>>>> has worked on this at all. It is important (imo) to keep compatibility with
>>>>> 21b, as that is what will be in all the linux distros until .23 is marked
>>>>> stable. I would be interested in trying out .23 on Windows though, if it
>>>>> proves to be reasonably stable (I have no clue if the indexes it creates are
>>>>> compatible with .21b; that could be an issue).
>>>>>
>>>>> Matthew
>>>>>
>>>>> _______________________________________________
>>>>> sword-devel mailing list: sword-devel at crosswire.org
>>>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>>>> Instructions to unsubscribe/change your settings at above page
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> sword-devel mailing list: sword-devel at crosswire.org
>>>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>>>> Instructions to unsubscribe/change your settings at above page
>>>>
>>>>
>>>> _______________________________________________
>>>> sword-devel mailing list: sword-devel at crosswire.org
>>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>>> Instructions to unsubscribe/change your settings at above page
>>>>
>>>
>>> _______________________________________________
>>> sword-devel mailing list: sword-devel at crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>> Instructions to unsubscribe/change your settings at above page
>>
>>
>> _______________________________________________
>> sword-devel mailing list: sword-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
>
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel
mailing list