Android - Revision history

Skalogryz: /* =Api and Engine */

2017-02-10T03:59:25Z

‎=Api and Engine

2017-02-10T03:59:13Z

‎Billing

2017-02-08T04:03:05Z

‎Billing

2017-02-08T03:50:57Z

‎Billing

2017-02-08T03:49:57Z

2017-02-08T03:49:44Z

‎Billing

2017-02-08T03:49:16Z

‎Billing

2017-02-08T03:48:57Z

‎Billing

2017-02-08T03:48:38Z

‎Billing

2017-02-08T03:42:27Z

‎Billing

@@ Line 112: / Line 112: @@
    ...
      .\com\android\vending\billing\IInAppBillingService.java
-===Api and Engine==
+===Api and Engine===
 It's somewhat a downside for a "native" based engines, that a purchase APIs are Java based only and there's no way to have a NDK counterpart. However, since the purchase process from UI point of view, has to happen within managed environment (switching Activities), etc, it makes sense. It also plays to a benefit, since whoever, does the implementation of In-app billing for the first time, will actually be forced to rewrite the any example (i.e. TrivialBilling) to something more convenient to their need.
 [[Category:Dev]]

@@ Line 112: / Line 112: @@
    ...
      .\com\android\vending\billing\IInAppBillingService.java
 [[Category:Dev]]

@@ Line 106: / Line 106: @@
   com\android\vending\billing\IInAppBillingService.java
 Presumably ready for building. I wonder how much different the generated .java file would be across different Android platforms.
 [[Category:Dev]]

@@ Line 105: / Line 105: @@
 That's it. and after that I'm getting
   com\android\vending\billing\IInAppBillingService.java
-Presumably ready for building. I wonder how much different the generated .java file could be across different Android platforms.
+Presumably ready for building. I wonder how much different the generated .java file would be across different Android platforms.
 [[Category:Dev]]

← Older revision		Revision as of 03:49, 8 February 2017
Line 1:		Line 1:
		+	'''Disclaimer:''' ''this whole process is done this way, because I don't want to study tricks and hints of Java and 3d-party build systems in depth. ''
		+	''It will eventually come anyway (just because one have to understand what he/she doing)''
		+	''But for now, I just want it to compile. Compile from the plain command-line, using tools provided in SDK/NDK only!''
	==Creating Apk==		==Creating Apk==
	===Signing Apk===		===Signing Apk===

@@ Line 66: / Line 66: @@
 *[http://journals.ecs.soton.ac.uk/java/tutorial/native1.1/implementing/method.html GetMethodID reference]
 ==Billing==
-'''Disclaimer:''' ''this whole process is done this way, because I don't want to study tricks and hints of Java and 3d-party build systems in depth.
+'''Disclaimer:''' ''this whole process is done this way, because I don't want to study tricks and hints of Java and 3d-party build systems in depth. ''
-It will eventually come anyway (just because one have to understand what he/she doing)
+''It will eventually come anyway (just because one have to understand what he/she doing)''
-But for now, I just want it to compile. Compile from the plain command-line, using tools provided in SDK/NDK only!''
+''But for now, I just want it to compile. Compile from the plain command-line, using tools provided in SDK/NDK only!''
 As usual Android is full of tricks:

@@ Line 78: / Line 78: @@
   rem this is not the command-line you're looking for
   aidl IInAppBillingService.aidl
 results in

@@ Line 83: / Line 83: @@
 error.
-Some extra googling suggest
+Some extra googling suggests, that each "android-xx" platform package comes with "frameworks.aidl" file. This while is "preprocessed" interface file,
 [[Category:Dev]]