-
Notifications
You must be signed in to change notification settings - Fork 3
Planned Additions/Fixes for 0.1.0 #3
Comments
Can you add instructions in the README for development instructions? Like setting it up in Android Studio. |
I was thinking about doing something like that in the wiki page. https://github.com/heb12/heb12-mobile/wiki |
@pufflegamerz Maybe, or maybe a development.md or something. We need something in a better place than the wiki, because it needs to be downloaded when someone clones the repo. |
Either way, it should be added. |
I think the app is ready to be released. I've fixed most of the major problems. Tell me if you find any bugs. |
Sorry. But I think we need more translations for more people to accept it. Don't you think? Maybe we should release the app as version 0.1.0 (following semantic versioning) now. |
I was hesitant about adding more translations, because it might make the app slower, and it already takes a while to load. What translations should I add? I don't see myself using more than 2. |
Okay. We need a better solution then. Can we load them into RAM only after they are selected? |
I just figured out a way to load the bible files only when a new translation is selected. I tried to do it before, and it didn't work. I guess I did something different and now it functional. |
Another few things which need to be done:
You should be able to reproduce all those issues. I found them in the 13th's version of the app. So you may have fixed some. Here are some more things which should probably be done:
|
Not sure you can do much about this, but it would be pretty useful to be able to use the up and down arrow keys on an Android hardware keyboard to move up and down on the Bible passage. |
Another thing we should do before the new version is released is the ability to easily compare versions in the popup. You can decide the best way to impliment it. |
Ok. I'll look into the issues. About the android keyboard part, are you talking about an external keyboard? |
Yes I am. It isn't a big deal, but I was trying to scroll down with the arrow keys and it didn't works. Kinda odd for a web based app when you think about it. Another question is, how hard would this app be to translate? Do you use external Android strings? |
Another thing is, could you possibly be more descriptive in your commit messages? That's kinda important for both other contributors and for looking back at code later. |
Another bug:
|
Ouch. The NET seems to be entirely broken. It says "undefined" where the Scripture should be. |
Press next, it should work. |
I attached a keyboard to my phone and the scrolling with arrow keys worked. |
Oh, I understand now. It kinda works like TAB by selecting all of the verse numbers. The NET still doesn't work, and the previous button should be fixed. It is entirely inconsistent. |
I fixed some of the issues. The NET should work now. |
I kinda want to make a dedicated website for Heb12 Mobile, because the one we have right now just looks a little plain. |
Okay. You can do that. Put it in a gh-pages branch |
I put it in the |
Awesome! I like it. By the way, how can I help with Heb12 Mobile? What do you need me to do? |
Thanks! The side menu definitely needs some touching up, and the online NET translation css needs some work. The verse of the day comes from the Bible Labs API. http://labs.bible.org/api/?passage=votd |
@pufflegamerz If I have a chance I will work on it. We need to do as much work as we can in the next week. Hopefully we can publish it on Google Play within a week (at least some kind of beta). Then later F-Droid as well. |
I'm pretty sure there is a $25 fee to get a developer account on Google Play. The Amazon App store is free though. |
Yeah. I know. I might see about paying it if I can. I'll see about putting it in the Amazon app store. F-Driod is also free but can be cumbersome. |
You don't have to. I have an Amazon Developer account where I published a couple of apps a couple of years ago. |
@pufflegamerz. Okay. But to be honest, I would like to have access to it somehow. Because I am the owner of Heb12. Of course you are the lead (and only) developer of Heb12 Mobile, so I am fine with you publishing it. Once we agree on the release of 0.1.0 you can publish it. |
Could I make a folder in the heb12.github.up repository named Mobile so I can put the website in it? The code and website probably shouldn't be in the same repository. |
Yes. That is totally fine. |
@pufflegamerz Verse selection in NET is very broken. |
It works for me. What book and chapter is it?
…On Saturday, March 9, 2019, MasterOfTheTiger ***@***.***> wrote:
@pufflegamerz <https://github.com/pufflegamerz> Verse selection in NET is
very broken.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ae3qssM7Osdi5b5i44Xrc7aqCDvs1IXgks5vU_MlgaJpZM4aynbW>
.
|
Oh. I see it. The highlighting won't work.I'll investigate.
…On Saturday, March 9, 2019, Petabyte Studios ***@***.***> wrote:
It works for me. What book and chapter is it?
On Saturday, March 9, 2019, MasterOfTheTiger ***@***.***>
wrote:
> @pufflegamerz <https://github.com/pufflegamerz> Verse selection in NET
> is very broken.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#3 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/Ae3qssM7Osdi5b5i44Xrc7aqCDvs1IXgks5vU_MlgaJpZM4aynbW>
> .
>
|
The API sends the text in some wierd format:
http://labs.bible.org/api/?passage=John%203&type=json&callback=myfunction
…On Saturday, March 9, 2019, Petabyte Studios ***@***.***> wrote:
Oh. I see it. The highlighting won't work.I'll investigate.
On Saturday, March 9, 2019, Petabyte Studios ***@***.***>
wrote:
> It works for me. What book and chapter is it?
>
> On Saturday, March 9, 2019, MasterOfTheTiger ***@***.***>
> wrote:
>
>> @pufflegamerz <https://github.com/pufflegamerz> Verse selection in NET
>> is very broken.
>>
>> —
>> You are receiving this because you were mentioned.
>> Reply to this email directly, view it on GitHub
>> <#3 (comment)>,
>> or mute the thread
>> <https://github.com/notifications/unsubscribe-auth/Ae3qssM7Osdi5b5i44Xrc7aqCDvs1IXgks5vU_MlgaJpZM4aynbW>
>> .
>>
>
|
… On Saturday, March 9, 2019, Petabyte Studios ***@***.***> wrote:
The API sends the text in some wierd format: http://labs.bible.org/
api/?passage=John%203&type=json&callback=myfunction
On Saturday, March 9, 2019, Petabyte Studios ***@***.***>
wrote:
> Oh. I see it. The highlighting won't work.I'll investigate.
>
> On Saturday, March 9, 2019, Petabyte Studios ***@***.***>
> wrote:
>
>> It works for me. What book and chapter is it?
>>
>> On Saturday, March 9, 2019, MasterOfTheTiger ***@***.***>
>> wrote:
>>
>>> @pufflegamerz <https://github.com/pufflegamerz> Verse selection in NET
>>> is very broken.
>>>
>>> —
>>> You are receiving this because you were mentioned.
>>> Reply to this email directly, view it on GitHub
>>> <#3 (comment)>,
>>> or mute the thread
>>> <https://github.com/notifications/unsubscribe-auth/Ae3qssM7Osdi5b5i44Xrc7aqCDvs1IXgks5vU_MlgaJpZM4aynbW>
>>> .
>>>
>>
|
@pufflegamerz In addition, normal verse selection doent seem to be working consistently. |
It should work in the latest apk. |
For some reason, I uploaded an older apk file. It should work now. |
The font size still does not work. It reads "NaN". I am able to change the Heb12 config file to a valid number to change this though. Plus. Shouldn't the config file be in the Android assigned location for heb12? (Android/data/io.github.heb12.heb12mobile or something like that).that should fix the storage problem. |
Hmmm. It works good on my phone. What version of Android are you using?
…On Sunday, March 10, 2019, MasterOfTheTiger ***@***.***> wrote:
The font size still does not work. It reads "NaN". I am able to change the
Heb12 config file to a valid number to change this though.
Plus. Shouldn't the config file be in the Android assigned location for
heb12? (Android/data/io.github.heb12.heb12mobile or something like that).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ae3qsmTdXTj8vAiZouZ1gPyef-iDaBHKks5vVPqkgaJpZM4aynbW>
.
|
5.0. But shouldn't that be irrelevent? Try deleting the app and the configuration file and try again. |
By the way Android 4.x doesn't work. It installs, but the app gets stuck at the loading part. |
I'm pretty sure every version has a different webview version.
…On Mon, Mar 11, 2019, 6:11 AM MasterOfTheTiger ***@***.***> wrote:
By the way Android 4.x doesn't work. It installs, but the app gets stuck
at the loading part.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ae3qstI30iQmJ2izDKve4xaUo60xZUoLks5vVivYgaJpZM4aynbW>
.
|
There might be a way to update it though.
On Mon, Mar 11, 2019, 3:23 PM Petabyte Studios <brikbusters@gmail.com>
wrote:
… I'm pretty sure every version has a different webciew version.
On Mon, Mar 11, 2019, 6:11 AM MasterOfTheTiger ***@***.***>
wrote:
> By the way Android 4.x doesn't work. It installs, but the app gets stuck
> at the loading part.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#3 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/Ae3qstI30iQmJ2izDKve4xaUo60xZUoLks5vVivYgaJpZM4aynbW>
> .
>
|
You need to make sure that it opens the last Bible translation used (if you haven't done that already). |
I've tried making that work for hours, but I was never able to fix it. |
Odd. Shouldn't it work the same as storing previously opened books and chapters? Either way, that is a pretty big deal as it is expected to work that way... |
It gets stored in the config file, then when the app opens It goes to the default. I'll try my best to fix it. |
Okay. Thanks! I am going to download Android Studio myself right now and see if I can help with something later. |
Okay. I am closing this now since 0.1.0 is released. Open new issues for individual features from now on I guess. |
The text was updated successfully, but these errors were encountered: