GCompris for iOS

[Timothée Giet]

Hi,

After discussing about it with Johnny, we think it would not be very 
fair to offer the complete iOS version for free.
It would be better to also set the ACTIVATION_MODE to "internal" there.
It would also allow to cover the licensing/apple-developer account fees 
as needed.

As for the suggestion to remove the MacOS version from apple store and 
distribute it on gcompris.net, that is a good idea.

We can continue the discussion off-list for the technical details.

Timothée


Le 17/06/2017 à 09:38, Bruno Coudoin a écrit :
>
>
>
> Le 14/06/2017 à 10:34, Johnny Jazeix a écrit :
>>
>> You can use 0.70, it's the same one except one fix for Windows.
>>
>>     I had to work around a few points to go through the compilation:
>>
>>     1. VERSION_CODE is expected in ApplicationInfo.h
>>     Not sure about what it is, I just defined it as some numeric
>>     constant in config.h.
>>
> I just pushed an updated config.h and instruction on the master 
> branch. It will fix the undefined constant.
>
> What you can do is to make a native CMake build. It works on MacOS but 
> the resulting binary cannot be packaged for an app store release.
>
>
>>
>> For BUILD_DATE, I guess you'll have it in the config.h created in the 
>> build folder once you have compiled with cmake (see below).
>>
>> For ACTIVATION_MODE, it would be better to have the confirmation, but 
>> it should be "inapp".
> I think you should stick to NO. Well this is a commercial issue. My 
> suggestions:
>
> - Remove the Macos version out of Apple store and distribute it on 
> gcompris.net like for the Windows version. In this case, set the 
> ACTIVATION_MODE to "internal".
> - For the iOS version as we don't sell it anymore the ACTIVATION_MODE 
> should be "no".
>
>>     Then I end up with a complete build (modulo some iOS signing
>>     magic), but it lacks all the resources.
>>     That doesn't surprise me since I skipped those lines from the
>>     platforms/ios readme file:
>>
>>     "At root dir create the directory
>>     mkdir rcc
>>     mkdir translations
>>     And fill copy the appropriate files in them."
>>     --> which files shall I copy? Those from src/activities? Should I
>>     process them with CMake before?
>>
> Yes, the CMake process include these builds. Well I am even not sure 
> the translations are built. The easiest is to make a Linux build and 
> copy those dirs to you mac.
>
> On linux:
> cd build
> make getSvnTranslations
> cmake ..
> make BuildTranslations
> make
>
> Now you have all the files in share/gcompris-qt/rcc  and 
> share/gcompris-qt/translations
> Copy these directories to your mac.
>>
>>
>>
>>     Bruno, if you have some hints about those points to resolve them
>>     properly it would be of great help!
>>
>>
> Here you are ;)
>
> If you send me your itunes email address I can add you as admin of 
> GCompris on the Apple store.
>
> Bruno.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/gcompris-devel/attachments/20170623/d8644713/attachment.html>