Android asset support/deployment advice needed

[BogDan]

Done. 
https://review.source.android.com/24746



----- Original Message -----
> From: BogDan <bog_dan_ro at yahoo.com>
> To: Thomas Senyk <thomas.senyk at nokia.com>
> Cc: "necessitas-devel at kde.org" <necessitas-devel at kde.org>
> Sent: Thursday, July 21, 2011 5:03 PM
> Subject: Re: Android asset support/deployment advice needed
> 
> Hi,
> 
> I've know that issue.
> The problem is that we can't/should't use AssetDir instead 
> of AAsset because AssetDir is using an internal (non-public) library. This will 
> not be a problem if we'll have access to the source code of all android 
> platforms, sadly we don't have access to the latest source code (yes, it 
> seems Google becomes a closed-source company day by day), so using AssetDir will 
> be very risky, so I'll try to another approach, I added two more functions 
> to official public asset implementation (check the attachment), one to get the 
> folders (AAssetDir_getNextDirName), and one to get the files count inside a 
> folder (AAssetDir_getFileCount), then I'll create a merge request to see if 
> Google will accept it.
> 
> Anyway, assets are similar with qt's built in resources (and AFAIK qrc 
> doesn't has any dir information), so I don't think anybody will expect 
> assets to be perfect.
> 
> Cheers,
> BogDan.
> 
> 
> 
> ----- Original Message -----
>>  From: Thomas Senyk <thomas.senyk at nokia.com>
>>  To: BogDan <bog_dan_ro at yahoo.com>
>>  Cc: "necessitas-devel at kde.org" <necessitas-devel at kde.org>
>>  Sent: Wednesday, July 20, 2011 6:03 PM
>>  Subject: Re: Android asset support/deployment advice needed
>> 
>>  I found the next problem with assets ... and this one might be a bigger 
> one.
>> 
>>  If you take a look at:
>>  AAssetDir_getNextFileName
>> 
>>  you'll see that it doesn't report sub-directories (intentionally!)
>>  This means: That way we can't do any sub-directory listing!
>> 
>> 
>>  AAssetDir doesn't provide anything else (or maybe I'm blind)
>>  AssetDir would provide it! 
>>  Do we want to use AssetDir instead? 
>>  We would basically rewrite all the AAset* stuff and use Aset* directly ... 
>>  right?
>> 
>> 
>>  I could start the work (but I'm on vacation next week)
>> 
>>  IMHO: If we want to do any release (alpha or beta) with asset support, we 
>>  absolutely need this.
>> 
>> 
>>  Greets
>>  Thomas
>> 
>>  On Thursday, July 07, 2011 02:11:41 AM ext BogDan wrote:
>>>   Done 
>>  http://commits.kde.org/android-qt/8519abd01958ac29801aec16eba452a9d224b
>>>   203
>>> 
>>>   Cheers,
>>>   BogDan.
>>> 
>>>   >________________________________
>>>   >From: Thomas Senyk <thomas.senyk at nokia.com>
>>>   >To: necessitas-devel at kde.org
>>>   >Sent: Tuesday, July 5, 2011 8:52 PM
>>>   >Subject: Re: Android asset support/deployment advice needed
>>>   >
>>>   >AAssetDir is never used.
>>>   >
>>>   >Therefor he can't do any listing ... I suspect this is the 
> problem.
>>>   >
>>>   >I'm going to look into it ... maybe I can fix it
>>>   >
>>>   >
>>>   >Greets
>>>   >Thomas
>>>   >
>>>   >On Tuesday, July 05, 2011 07:09:32 PM Thomas Senyk wrote:
>>>   >> Has anyone every tried more then one .qml file?
>>>   >> 
>>>   >> It seams he doesn't find the files within the same 
> directory.
>>>   >> 
>>>   >> I created a new "Qt Quck Application" and added a 
> new 
>>  MyRect.qml
>>>   >> But I can't create a MyRect Item in main.qml
>>>   >> 
>>>   >> Greets
>>>   >> Thomas
>>>   >> 
>>>   >> On Thursday, June 30, 2011 10:31:26 AM ext Niko Sams wrote:
>>>   >> > thanks!
>>>   >> > _______________________________________________
>>>   >> > Necessitas-devel mailing list
>>>   >> > Necessitas-devel at kde.org
>>>   >> > https://mail.kde.org/mailman/listinfo/necessitas-devel
>>>   >
>>>   >_______________________________________________
>>>   >Necessitas-devel mailing list
>>>   >Necessitas-devel at kde.org
>>>   >https://mail.kde.org/mailman/listinfo/necessitas-devel
>> 
> 
> _______________________________________________
> Necessitas-devel mailing list
> Necessitas-devel at kde.org
> https://mail.kde.org/mailman/listinfo/necessitas-devel
>