Hi Tim,<div><br></div><div>Thanks for contacting me. </div><div><br></div><div>Please understand that in terms of skills and acquired knowledge, I'm not an iOS app developer, nor do I have a Mac platform. cf. I imagine it would be much harder to develop and test iOS apps from a Windows PC.</div><div><br></div><div>It's great that you've got involved. We know why Nic is busy. I think Mannfred Bergman is also pretty tied up in terms of spare time since he became a father. </div><div><br></div><div>After iOS 9 was released was the time when issues began to arise with installing search index. It's only got worse with subsequent versions. Also from what Nic has written before, maintaining backwards compatibility is desirable, as one cannot assume that every PS user keeps his device up to date. Sometimes that's an impossible goal to implement though.</div><div><br></div><div>cf. The same goes for modules in a different way. One cannot assume that every user has the most recent version of an installed module. This is why Nic also maintained a separate search index for older module releases.</div><div><br></div><div>Also since we gained access to the huge Bible modules repository at eBible.org, none of these yet have an installable index, AFAIK. NB. Updates to such modules can occur quite often, as Michael improves things with Haiola.</div><div><br></div><div>Nic had hoped to move away from downloading and installing the search index for each module, and implement the creation of the search index using the device itself. This was beyond the capability of the earliest iOS devices in terms of speed and efficiency. That no longer is the case. cf. AndBible has always done the index creation within the Android device. All the more recent types of iPhone and iPad should be able to do this speedily if someone can write the code.</div><div><br></div><div>btw. Another unpublicised issue is why installing a module in Maintainer Mode along with its Lucene search index as created using Xiphos, and included within the same Zip archive usually leaves the index as not found by PS. According to Nic, an index made using Xiphos should be compatible with PS. I've only seen the compatibility demonstrated for two private Bible modules that I made for my own personal use, one of which was the English Revised Version of 1885.</div><div><br></div><div>I have TestFlight installed in my iPad Mini. It's a long time since I last used it to try out prerelease of PS for Nic.</div><div><br></div><div>Final thought. When he was active in PS development, Nic used Twitter as the main support communications channel. I'm not a tweeter.</div><div><br></div><div>Best regards,</div><div><br></div><div>David Haslam</div><div><br></div><div><br><br>On Thursday, 8 September 2016, Timothy Shen-McCullough <<a href="mailto:truelab@icloud.com">truelab@icloud.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
I’m trying to reach David Haslam. I’m interested in helping out programming for the PocketSword iPhone app. and have actually written in the past to Nic so I know from his reply that he’s quite busy. I’m also very concerned about the development of PocketSword. Months ago due to changes in the iOS code or ?? the app stopped being able to download searching modules. I posted the bug on the tracker. I eventually wrote a fixed version months ago and emailed Nic about it. This is the version I use now. The version that I edited though was before a contributor named Mannfred worked on the code. So, I don’t think that my version can be used due to it being pre-ARC support and pre-64 bit compliance and etc. I have however been looking at his newer version. I am slowly working my way through it. I can’t compile the code and it seems that more updates are required to the code, but I don’t feel comfortable going into details as I’m not sure exactly where this email is going. I’ve never used a newsgroup before and so I don’t want to violate any rules or etc. without knowing it.<br>
<br>
-Tim</blockquote></div><br><br>-- <br>Best regards,<br><br>David F. Haslam<br>