Porting Learn Na'vi to Android

Seze · May 24, 2010, 08:46:45 AM

I have some updated images you can use for the About and Disclaimer Pages. I was working on those sections yesterday. I put a copy of the PNGs with the rest of the PNGs in the Android trunk. They should be pretty easy to spot, they start with Capital letters...

Seze · May 24, 2010, 11:52:48 AM

I setup an Android Marketplace account for the App back when I announced that the App would be ported to Android. Let me know when you have a build you would like pushed out to the marketplace.

Muzer · May 24, 2010, 12:19:00 PM

You could release the APK on this forum for beta testing first...

(Are most devices able to install APKs not from the marketplace? I don't know, mine certainly can but it HAS been rooted)

Seze · May 24, 2010, 12:56:31 PM

I don't have any experience with it first hand, but I believe it was omängum fra'uti that said his device required the SDK in order to put non marketplace apps on his device.

I would be all for a simultaneous release of the App in the App Store and Android Market Place though. That gives the Android team a few weeks still to get the App 1.0 ready. Plus, Tuiq is changing up the way we the data for the dictionary, so its probably best to wait until that gets updated first, before doing the actual 1.0 release.

omängum fra'uti · May 24, 2010, 01:28:51 PM

Quote from: Seze on May 24, 2010, 08:46:45 AM
I have some updated images you can use for the About and Disclaimer Pages. I was working on those sections yesterday. I put a copy of the PNGs with the rest of the PNGs in the Android trunk. They should be pretty easy to spot, they start with Capital letters...

That will actually break the build. According to the sdk, it should just treat it as all lower case in the app, but in practice the eclipse plugin complains about files with upper case letters and wont build. Its pretty stupid. But I can fix that up and put it in the right place.

Anyway, any Android device /should/ be able to run non market apps, without being rooted. There is an option in settings to allow untrusted apps that has to be selected first. If they have that option removed, like mine, its still possible to turn on debugging over usb, install the sdk, and install it that way.

For the market, the app will need to be signed.

Seze · May 24, 2010, 01:42:34 PM

I knew it would break it, just left them as is so that you could easily find them...

Muzer · May 25, 2010, 01:58:00 AM

I really need to download the sdk fully - it's so big and my connection is so slow!

omängum fra'uti · May 25, 2010, 02:10:09 AM

I'll put up an (Unsigned) apk once I get search in, if anyone wants to give it a try without downloading the SDK.

okrìsti · May 25, 2010, 05:13:31 AM

I think every .apk has to be signed in order to being able to install. I will keep experimenting.

And it is said, that you have to use a real key, unsigned or debug key are bad.
€: Ok, installing of a the apk signed works like a charm.

Seze · May 25, 2010, 09:43:36 AM

I went ahead and tagged 0.6.5 as build number 135 in the repository. Where did 0.6.5 come from? The highest version of the iPhone version is 0.6.1. I moved the release post to its own topic so that its easier for others to find. In the future, lets try to release both versions at the same time. Say version 0.7.0, the release post would be for both iPhone and Android.

omängum fra'uti · May 25, 2010, 11:48:48 AM

0.6.5 came because I forgot what version you had for iPhone. Since features were getting close, I was aiming for a close version, thinking iPhone version was 7.0.

Seze · May 25, 2010, 11:57:24 AM

I'm going to wait on releasing 0.7.0 until Tuiq gets the new SQLite version of the datasource up and running (Hopefully that will happen in the next week). Most of the stuff I had been working on recently really needs to be put on hold until the new datasource is put in place. The next item on the list that doesn't have anything to do with the dictionary is to add "Na'vi in a Nutshell" to the App.

okrìsti · May 25, 2010, 12:08:41 PM

He wanted to contact you via IRC, I think he has finished (assumed).

Btw. what about splitting the background images up into the one background image and a transparent black layer which is displayed when the now dark image shows up, same with the text and buttons. Transparent png work (tested).

Muzer · May 26, 2010, 02:57:19 AM

Could you make the scroll bar draggable? Many other apps do, eg music.

hawnuyuna'viyä · May 31, 2010, 05:37:29 AM

Ma Seze,

I would like to help with maintaining and improving the android app. I started work on my own app about 2 days ago, based around the SearchableDictionary example - RAM based, so very fast - and was about to suggest that we pool the resources of the multiple android developers on this site, when I discovered this thread.

If you could point me to the repository you are using, I would very much appreciate it.
Irayo.

Seze · May 31, 2010, 09:10:44 AM

Take a look at the "Learn Na'vi App Development" Thread that is stickied in this section. Follow the directions in that thread to get involved with the project.

hawnuyuna'viyä · May 31, 2010, 04:25:23 PM

tam, irayo.

I have sent you a pm with my email address.
In the meantime, I have pulled a read-only copy of the code to familiarise myself with.

hawnuyuna'viyä · May 31, 2010, 04:53:48 PM

Quote from: Muzer on May 26, 2010, 02:57:19 AM
Could you make the scroll bar draggable? Many other apps do, eg music.

Committed as revision 141.
Will be available in the next release.

okrìsti · June 01, 2010, 04:50:53 PM

Tewti, such a tiny modification, I have not tried it yet, will do tomorrow.
I also tried to install it on two different installation running on a Virtual Box though it did not work at all.

omängum fra'uti · June 03, 2010, 03:32:17 AM

I wondered how that is setup, I hadn't quite gotten to the point of figuring it out. So simple!

Perhaps that will suffice rather than the direct jump to letter option. In fact, having both (At least how the iPhone app does jump to letter) might be confusing because the thumb would look like it is selecting a letter, where it might not be a perfect match.

Anyway, just put in a bunch of updates related to handling of orientation changes. All activities should now properly persist across screen orientation changes, as well as across the application being killed and restarted. That includes current search, and any dialogs currently shown. A few things are now being done closer to the recommended way.

Some things I'm not 100% happy about...

The way the current search is displayed was just a quick throw together thing. I'd rather something which provided the search term, an X button to clear it, and clicking on the search term would bring it back up in the search box. And more to the point, for landscape mode, it should probably be next to the dictionary mode button, not below it. Below just takes up too much space.