We never say goodbye to the world because of true.
Alan Plotko
@alanplotko
Going to apply the term Ishi for the pebble app and AnkiDroid for the Android app, since we vaguely refer to generic terms.
Actually, I'll be explicit with pebble app and just use AnkiDroid for the Android app.
Taylor Foxhall
@hallfox
Yeah, they don't want the lexer to look ahead and figure out if the line ends or is continued during the compilation step.
Taylor Foxhall
@hallfox
Hey, they're working on a content provider.
Which is what I would have preferred when we made it.
That will allow us to make our own app and get their information without us having to change their own app.
Or even modify their app and use their ContentProvider so that pebble users don't have to download another app from us.
Alan Plotko
@alanplotko
Back. Had a late dinner. Wait, don't pebble users have to download our pebble app and Anki?
Taylor Foxhall
@hallfox
We could potentially make them download our own Android app on top of Ishi and Anki.
Alan Plotko
@alanplotko
Ohhhhh, that's interesting. So this new app would interface between Anki and Ishi then?
Taylor Foxhall
@hallfox
If they give us a content provider we could just do it from our own app, but if possible I'd like it to be a part of Anki so they have to download less stuff.
Alan Plotko
@alanplotko
Yeah, I'm with the "less stuff to download" side, but we're no different than any other app that interfaces with AnkiDroid. Take the Android Wear for example. Why do we get integrated in, but Wear has to go through the API? Not sure if we'd be let in.
Do we need to collection access in Java in a new app? Could we access their Content Provider from Ishi? How does Wear go about this?
Taylor Foxhall
@hallfox
The content provider is available to any app. It's an Android thing. If you ask for certain data a ContentProvider can, well, provide content. Our app would just get that ContentProvider and ask for deck information. The only tricky bit may be the scheduler, but I want to get my hands on the code for the ContentProvider.
Alan Plotko
@alanplotko
They said it hasn't been merged yet. Have you looked through pending pull requests for AnkiDroid?
Taylor Foxhall
@hallfox
It's this issue ankidroid/Anki-Android#823
Alan Plotko
@alanplotko
Looks like they cleared it, but still need to merge. At least the code is available for viewing.
I can continue documenting the pebble app. In the meantime, I guess you could start reviewing the ContentProvider and see how much work the needed changes would be.
Taylor Foxhall
@hallfox
If they did what I think they did it should be very easy.
Alan Plotko
@alanplotko
That's good to hear. As far as I've seen, it seems that everything is more or less handed to you and it's just a matter of communication between ContentProvider and Ishi.
What does key_ease do again?
I'm going to enjoy remembering all these cases. ><
Taylor Foxhall
@hallfox
That has to do with how difficult the user found the card.
Alan Plotko
@alanplotko
Oh, alright. I kept thinking animation.
Easing in and out on the menu.
Taylor Foxhall
@hallfox
No.
Alan Plotko
@alanplotko
As you can see, I was clearly stumped on this.
The numbers don't seem to match up with the variables we defined. Trying to see if I can replace all those random integers with their corresponding variables.
Alan Plotko
@alanplotko
Added docs.
I hope they suffice.
Taylor Foxhall
@hallfox
Cool.
I think I've passed the point where I can think clearly, but after reading over the code for the ContentProvider they have, we should be in a good place.
Alan Plotko
@alanplotko
Sounds good.
Yeah, it's getting late. Don't worry about it. Get some sleep.