Quote:
Originally Posted by Clemenseken
@spooky69:
But anyway I don't mind anybody using my code so far as base for an application of their own.
So there's still hope for you: Just go ahead!
It may take another week or two until I have results for my tests. It might take a little longer, then...
(  I will ask my product marketing team next time what they think I should promise or announce...) |
Sorry about the flood of suggestions! I really think the button switching is essential since it would make a lot more sense to have the page turn buttons act as the cursor on the 505 and would make typing about 75% less awkward. That would be my #1 change I would make for better usability. I'm not a programmer but I'd love to see other people take a crack at this thing once you've got it to where you want it.
Quote:
Originally Posted by =X=
@spooky69
If you notice the sequential search would have taken us 10 reads to find "J". The "binary search" algorithm only took 3 reads.
The real hard part is SONY's API since it is not published I don't know if there is a way to jump to line numbers.
|
This is pretty similar to what I would have suggested as a search algorithm, though I think there's a way of programming slightly smarter "jumping" in a set of data this large and of this type. If we can figure out a way to get it to jump to a line, then I'll give my best shot at describing one.