<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 03/06/2013, at 11:02 PM, Greg Hellings <<a href="mailto:greg.hellings@gmail.com">greg.hellings@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">Of course, this type of behavior adapted to Scope is fine on a desktop or even a netbook or most tablets. But it's unacceptable for a truly low-powered device.</div></blockquote></div><br><div>I guess we need to have some sort of implementation with which to try this out with. I remember that trying to create a cLucene search index on my old iPhone 3G was sufficiently silly that I removed that functionality in PS. But I needed to test it to confirm that it was a stupid idea to allow users to attempt it. (I would say the same for BibleTime mini & say that 2.5hrs is way too long to even suggest a user plug in their phone and run it overnight! But that's just my sanity shining through, and I'll resume my insanity in a moment)...</div><div><br></div><div>My thoughts about this entire subject are: let's attempt to do this programmatically and not have Scope or anything else like that in the conf file. Having seen the number of emails to this list from module makers who have issues with properly forming conf files, I think the easier we make it for them, the better! :) :)</div><div><br></div><div>So, give it a go. No point arguing about whether it'll be fast enough or not at this point. Try it. We can always only use that functionality on desktop front-ends? Alternatively, people have suggested caching the results and the like. I do that for caching a listing of entries in dictionaries and it works pretty well... :)</div><div><br></div><div>And this is coming from a developer who only writes code for "truly low-powered devices"... And on that note, I'm about to pull a feature from my latest beta cause it's too processor intensive on phones, even though it works great on my own model of iPhone. :)</div><div><br></div><div><br></div><div>just my random thoughts... :)</div><div>Thanks, ybic</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>nic... :)</div><div><br></div><div>ps: the problem with my entire argument is that someone actually needs to write the code for this to happen. ;) It's not looking like I'll have time in the near future, so I'll leave it to others... :D And on that topic, I have a 2nd job interview tomorrow for a cool job (down to the final 2 applicants!) if anyone's able to quickly pray for it? :) :)</div></body></html>