Nandaka wrote:Never seen that path before, usually sd card is mounted to /sdcard and I'm using Environment.getExternalStorageDirectory() to get the sdcard path.
My device has it's own primary storage under SDcard, and it's added memory to external_SD. It also creates two drives when connecting to the computer, while the main device has the folder external_SD, there's nothing in it. When going to the device, all of the stuff on the external storage is in that folder. It might be just me, and if it is, can someone help me with this issue?
Bloodscythe wrote:2 GBs!?
Holy cow. I thought that was impossible. I mean 1 chapter is barely 1mb and a full res image is 5-10mb....
Unless you downloaded say 150 full res images you wouldn't get close to 1GB, let alone 2...
Then again, 1 novel=about 7-12 images...
If you're that concerned about it, why don't you clear image cache?
I mean you're here to read not look at the pretty pictures...
I am here to look at the pretty photos. Why do you think Animes are made from this shit. The writing? Psht, do you know how much of the anime cuts out the novel, some of the good material too. They leave in some of the bad stuff also to "fill in the gaps"
Updated the GitHub, minor bug fix from crash report in google play dev console.
- Update styles to use Sherlock for api > 14.
- Add synchronized lock for dbhelper.
- Add tryParseInt for DisplaySettings, Update key for load novel task.
- Add null check for some activity.
- Launch main activity when ending update history activity if called from update service notification.
ShadowfoxEX wrote:My device has it's own primary storage under SDcard, and it's added memory to external_SD. It also creates two drives when connecting to the computer, while the main device has the folder external_SD, there's nothing in it. When going to the device, all of the stuff on the external storage is in that folder. It might be just me, and if it is, can someone help me with this issue?
Your device sd card path in not standard one, I think. To handle this, we need to modify the way it get the db path (read from shared pref? not sure if can resolve the pref before loading db), or you can create a symbolic-link to map the path of images/db to your external sd card (see: http://forum.xda-developers.com/showthr ... ?t=1083308)
Just downloaded youre recent changes (im somewhat free from exams for the moment, until i get these exam's grades... damn)
And there are 2 things i am having some issues:
1 - "Code migration" - android is requesting for me to change all SWITCHs to IF-ELSEs... i did that (i looked into it, its better), not really an issue, just... saying.
2 - @ DisplayNovelTabFragment: Lines 38 and 58: getChildFragmentManager() > undefined. I expected it to be part of the support lib but... it just advices me to change to getFragmentManager()...
In theory, practice and theory are the same.
but, practically, they arent.
Erakk wrote:Just downloaded youre recent changes (im somewhat free from exams for the moment, until i get these exam's grades... damn)
And there are 2 things i am having some issues:
1 - "Code migration" - android is requesting for me to change all SWITCHs to IF-ELSEs... i did that (i looked into it, its better), not really an issue, just... saying.
Why/what code migration? it is clearer to use switch though (as long you aware with the fall-through code, e.g.: no break/return on end of case statement)
Erakk wrote:
2 - @ DisplayNovelTabFragment: Lines 38 and 58: getChildFragmentManager() > undefined. I expected it to be part of the support lib but... it just advices me to change to getFragmentManager()...
Not sure about this, need to ask ThatDot7 as he(or she?) is the one who integrate the ActionBarSherlock to the project.
EDIT: see http://stackoverflow.com/questions/1437 ... entmanager , you might need to update the lib/sdk, then do clean and rebuild the project.
The migration is done with the IDE's help ("select" the switch statement and press ctrl+1)
On the other issue, i might need to redownload the SDK... i cant seem to fix it. it asks for me to update the SDK, when i try, it says there are no updates. poke my life, right?
now that i got back to BakaReader EX, Eclipse greets me with stones.
In theory, practice and theory are the same.
but, practically, they arent.
Erakk wrote:The migration is done with the IDE's help ("select" the switch statement and press ctrl+1)
On the other issue, i might need to redownload the SDK... i cant seem to fix it. it asks for me to update the SDK, when i try, it says there are no updates. poke my life, right?
now that i got back to BakaReader EX, Eclipse greets me with stones.
There was an Android 4.2.2 update a week ago or so, there was a new SDK that came out with it. So I am not sure if you have updated to that one or not.
As for the getChildFragmentManager(), it should be from the support library. Maybe try to re-import the support library again? I believe both the ABS and the main project need the support library if you plan to do that.
(getChildFragmentManager() is used to deal with fragments in a fragment)
In one point in time, I was also getting that error as well. I am not sure how I fixed it. The solution was somewhere between a lot of "cleaning" and a lot of reimporting the library and a lot of recloning the repo >.<
Yeah, i will clean install everything and re-clone the repository...
Ah man...
Well, i did have the support library... maybe its related to the update i couldn't do.
I never suspected you were a she...
Everyboddy is a "he" on the internet, unless proven (as in really good proof) otherwise.
In theory, practice and theory are the same.
but, practically, they arent.
Erakk wrote:Everyboddy is a "he" on the internet, unless proven (as in really good proof) otherwise.
tits or gtfo?
@erakk seconded
@Nandaka I dont get it. . .
baka reader is already for downloading right? so this thread is for its updates. . totally connects me to BT updates more often now. .
P.S. Feel free to PM me anything you want, oh, be as random as possible
Irritated beyond endurance, I gripped the table's edge, and prepared to use the technique which had been passed down by my grandfather, namely «Table Flip».
nah, just replying to Errak, if someone claiming that she (the poster) is a girl in the internet (or 4chan). they will reply with that (show us some proof ==> pic of her boobs, or I'll ignore you =>gtfo/get the poke out)
carinderyeah wrote:
baka reader is already for downloading right? so this thread is for its updates. . totally connects me to BT updates more often now. .
well that is some cold hard proof you are demanding there for. .
Baka Reader EX . . great. .
P.S. Feel free to PM me anything you want, oh, be as random as possible
Irritated beyond endurance, I gripped the table's edge, and prepared to use the technique which had been passed down by my grandfather, namely «Table Flip».
Ooh, I must have been influenced by movies too much . .
P.S. Feel free to PM me anything you want, oh, be as random as possible
Irritated beyond endurance, I gripped the table's edge, and prepared to use the technique which had been passed down by my grandfather, namely «Table Flip».
Lets be honest here, whether it is cold or hot, hard or soft... any sort of "proof" will get us kicked off the forums.
In terms of the app, has there been a decision on which "test" to use?
Is it worth exporting the apk for other testers to use?
And probably the craziest for that I would like to put off forever:
Is it worth implementing pagination?
It seems like a lot of the reviews in the play store seem to request pagination of the novels.
There is 1 way I have thought of doing this without massively changing the structure of the app, but when I tried to code it, I couldn't really get the numbers right.
But here is it if any of you are daring enough to try and how I envision this to work.
Like Microsoft Word, we can split content into multiple columns without worrying about text being clipped or half images being show.
What if we split the novel into columns and only show 1 column at a time as a page?
This actually can be done using Javascript/CSS with the webkitColumnCount and webkitColumnGap parameter.
So here are the steps ("inspired" by Pocket)
1) The app detect a swipe to the side (onFling in the OnGestureListener class)
2) If the app isn't in "pagination" mode, it will make it so, if so then it will flip to the next "page" (ie, next column)
3) When the user starts scrolling up and down, it will go back into scroll mode
This is one way to deal with pagination. The next way isn't a way I am a big fan off but see will happen in the app.
1) Have a setting toggle for pagination
2) If the toggle is set, use another CSS file to render the HTML