So I have been working on a re-write of the button code. The current code works just fine, but if the user selects the same button more than once, the button is re-drawn. It all work, but looks odd.
The challenge for my prosaic programming skills is to keep track of buttons used. Re-draw the button to indicste that the button has changed. Update those buttons when the text script is changed. Don’t update if the button is selected twice in a row. I.E., mama. Interesting logic issue to be sure.
I added changes to the interface. The user can select which type face they wish to use or rotate through the type faces on the fly.
I start in romaji:
Start in Romaji
I tap the green button or the center button near the bottom and rotate to hiragana:
Now in Hiragana
Finally, tap the green or center bottom button again and rotate to katakana
Now in Katakana
I have picked up some great feedback about the application and will implement the functionality in the near future. The end user wanted know if I could include a “space bar” in the app. Sure! It was suggested that the app be allowed to rotate to landscape mode… Since the app is just for the iPhone and screen size is at a premium, I don’t envision that happening. However, it won’t hurt to look at that kind of implementation. I could cascade the characters by splitting the screen and placing the pieces next to each other. Or, allow for scrolling in landscape mode, or lastly try the scroll-wheel for each character set. The last sounds intriguing to me. All three are possible, so the question becomes one of application and usability.
Stay tuned!
It took about a dozen characters fixed the view swipe issue. And I resubmitted the app and am waiting for approval.
I thought the issue would be very difficult to address, and am glad it wasn’t. This also makes me excited about some of the updates I want to accomplish.
I found a huge bug that we missed during testing. One of those things that you would never try, but via a mistaken swipe, just happens. I will work on the fix in the next few days!
I have submitted the update to iHear-Japanese, making it 1.01. This update fixes a few issues and a memory leak. The memory leak is insubstantial, but any leak is a bad one. I also updated a bit of functionality to give indication to which character set the end user is using. Just waiting for the review to finish.
The app, iHear-Japanese, is now in the App Store. I already have a minor update ready to go and will post that in a few days.
The store link is here.
Yahoo!
So I ended up re-downloaded the SDK and installed it. The validate and then submit buttons work as advertised. After validation, I click submit and it uploads as long as everything is good to go in the app.
So, now we wait.
I am a pretty patient person and this post should not be construed as a complaint in any way. But I sure do wish Apple app store was a bit quicker with the approval/denial system.
Darn it – I need to use the ‘Application Loader’ Apparently within the ‘Organizer’ the Validation & Submission buttons validate and then package the app for delivery to the App Store. Submit does NOT upload the app. So, I need to run the Application Loader to do so. I have to redownload the Application Loader – which is now included within the SDK – meaning to get one file I have to re-download the 4.16G installer. Due to the file’s size, I don’t hang onto the installer after ‘installing’
Buy hey, you live and learn.
