Today I started out with making a pull request to your GitHub project. Luckily the fix wasn't too intensive - I managed to fix it with a few changes to the manifest.
The Geolocation API wasn't working, so I decided to check the manifest. Luckily, the fix was that the app wasn't allowing the Geolocation APIs, so by allowing these in the manifest, the app was able to access such libraries.
Making a pull request was pretty easy after we figured it out. My issue was that I was trying to clone your repo and make a pull request into it. What I needed to do was fork the repository, then change the origin:
git remote remove origin
git remote add origin [fork repository url]
After that I could push into my forked repository, which I could then create a pull request to fix it.
I also worked awhile on fixing contacts. Our only issue was that it wasn't continuing through the loop. We were using:
this.continue;
Instead of:
this.continue();
This resulted in only being able to get the first item of the result array, when there were a lot more available. By having a continue afterwards, we were able to successfully loop through the array.
Monday, April 20, 2015
Monday, April 13, 2015
Brackets! (4/13/15)
I've been recently going home and starting a few experiments of my own with Javascript. A few days ago, one of my friends told me about a new program called Brackets. It's written and hosted by Adobe, and so far is one of the greatest web development programs I've ever used. It's open source, too, so I'm sure it is going to be something that quite a bit of people are going to use!
It's similar to a Java IDE in that it has auto-completion of tags, code completion, etc. The main reason I installed it, however, was a directory structure on the left. I couldn't use Firefox's WebIDE for my personal projects, since they weren't FirefoxOS apps.
Anyway, I thought I'd introduce it. I love to use it so far, and it's saving me quite a bit of time!
On a side note, I've started to look into the Chapters bug. While I haven't found anything obvious that's creating this bug yet, I'll continue to look into it tomorrow and see if I can make some progress.
It's similar to a Java IDE in that it has auto-completion of tags, code completion, etc. The main reason I installed it, however, was a directory structure on the left. I couldn't use Firefox's WebIDE for my personal projects, since they weren't FirefoxOS apps.
Anyway, I thought I'd introduce it. I love to use it so far, and it's saving me quite a bit of time!
On a side note, I've started to look into the Chapters bug. While I haven't found anything obvious that's creating this bug yet, I'll continue to look into it tomorrow and see if I can make some progress.
Sunday, April 12, 2015
Working with Scaled Vector Graphics and App Logo (4/10/15)
On Friday, I worked on the app's logo and scaled vector graphics. I thought it would be a good time to step back a bit from the specific bug and get something done that was a bit more important.
I learned a lot about SVGs! One of the coolest things I found out was that if you opened it in a text editor, it showed all of the properties about the SVG, such as default width, height, colors, etc. I found that really interesting, because you're able to easily change any specific property of the image just by changing a line of text, rather than manually drawing it in.
Another thing that I found interesting was that it was so easy to scale. All I had to do was drop it in the app's icons folder and it instantaneously scaled for all device sizes, which made it a whole lot easier to make, rather than individual png images which we would have had to resize.
On Monday, I plan to code the base for a few new features. I'm not going to make too much, however, because I want to continue condensing the app as much as possible.
I also have to start working on a bug that relates to chapter objects. Apparently, our app was denied from the marketplace until we fix a bug that has to do with chapters being one greater than we should. While I don't ever remember noticing this, it's possible that it was a result of our refactoring. I'll have to look into it a bit more.
I learned a lot about SVGs! One of the coolest things I found out was that if you opened it in a text editor, it showed all of the properties about the SVG, such as default width, height, colors, etc. I found that really interesting, because you're able to easily change any specific property of the image just by changing a line of text, rather than manually drawing it in.
Another thing that I found interesting was that it was so easy to scale. All I had to do was drop it in the app's icons folder and it instantaneously scaled for all device sizes, which made it a whole lot easier to make, rather than individual png images which we would have had to resize.
On Monday, I plan to code the base for a few new features. I'm not going to make too much, however, because I want to continue condensing the app as much as possible.
I also have to start working on a bug that relates to chapter objects. Apparently, our app was denied from the marketplace until we fix a bug that has to do with chapters being one greater than we should. While I don't ever remember noticing this, it's possible that it was a result of our refactoring. I'll have to look into it a bit more.
Wednesday, April 8, 2015
Refactoring and Bugfixes
To start today, I fixed the README file so that it states that it's an audiobook player, rather than a port.
I then began to start refactoring for the book.html page. I noticed that it wasn't saving information for the slider, specifically CSS code. I'm still trying to fix this, and I'm not exactly sure why it's occurring. It's either a JQueryMobile issue or an issue with the page refreshing.
I also noticed that the method can be shortened by quite a bit. There's a lot of useless lines of code that can be changed, and I'll go into detail on that after I can fix this bug.
I then began to start refactoring for the book.html page. I noticed that it wasn't saving information for the slider, specifically CSS code. I'm still trying to fix this, and I'm not exactly sure why it's occurring. It's either a JQueryMobile issue or an issue with the page refreshing.
I also noticed that the method can be shortened by quite a bit. There's a lot of useless lines of code that can be changed, and I'll go into detail on that after I can fix this bug.
Subscribe to:
Posts (Atom)