onepf / appdf Goto Github PK
View Code? Open in Web Editor NEWApplication description file for the appstores. Best way to distribute your apps!
Application description file for the appstores. Best way to distribute your apps!
For example the following XML:
<included-activities>
<in-app-billing>no</in-app-billing>
<gambling>no</gambling>
<advertising>no</advertising>
<user-generated-content>no</user-generated-content>
<user-to-user-communications>no</user-to-user-communications>
<account-creation>no</account-creation>
<personal-information-collection>no</personal-information-collection>
</included-activities>
Should we create Enum with all included activity tag options or simply pass a string?
Our main library for AppDF file support will be in Java. It should support the following functionality:
Couple of questions about the library structure:
There is no word 'refference' in English.
In order to add information about the AppsLib one needs to create a developer account there, publish a test application (you can take Life sample from https://github.com/onepf/AppDF/tree/master/samples/Life) and collection information about supported features.
You should add information about SK Telekom T-Storeto all tag descriptions here:
https://github.com/onepf/AppDF/blob/master/specification/appds_spec_1_0.md#descriptionxml-structure
as well as general information about the store there:
https://github.com/onepf/AppDF/blob/master/specification/appds_spec_1_0.md#application-store-support
and category mapping to:
https://github.com/onepf/AppDF/blob/master/specification/appds_spec_1_0.md#category-list
It looks like it's a good idea to generate categories.xml and all such resources ( languages etc.) during build of parser-lib. Easiest way from my point of view would be to extract javascript code already wroten for that to separate file and call it via Rhino during build.,
Does it make sense to include some login to the model classes? For example make a class for a file inside AppDF package (screenshot, icon, APK file, etc) and where appropriate return such class instead of String?
It will allow to automatically check that the files exist, provide functionality to extract these files, etc.
There is a Life game sample in the "samples/Life" folder:
https://github.com/onepf/AppDF/tree/master/samples/Life
We need to create complete sample of AppDF file here:
https://github.com/onepf/AppDF/tree/master/samples/Life/appdf
This project is already started but needs to be finished
In order to add information about the Nook AppStore one needs to create a developer account there, publish a test application (you can take Life sample from https://github.com/onepf/AppDF/tree/master/samples/Life) and collection information about supported features.
You should add information about Nook AppStore to all tag descriptions here:
https://github.com/onepf/AppDF/blob/master/specification/appds_spec_1_0.md#descriptionxml-structure
as well as general information about the store there:
https://github.com/onepf/AppDF/blob/master/specification/appds_spec_1_0.md#application-store-support
and category mapping to:
https://github.com/onepf/AppDF/blob/master/specification/appds_spec_1_0.md#category-list
Check which browsers are supported right now. Add checking that a supported browser is used. Show error message if unsupported browser is used.
Create reference PHP code for parsing AppDF file. It should be located here
tools/parser/php
In order to add information about the SK Telekom T-Store one needs to create a developer account there, publish a test application (you can take Life sample from https://github.com/onepf/AppDF/tree/master/samples/Life) and collection information about supported features.
You should add information about SK Telekom T-Storeto all tag descriptions here:
https://github.com/onepf/AppDF/blob/master/specification/appds_spec_1_0.md#descriptionxml-structure
as well as general information about the store there:
https://github.com/onepf/AppDF/blob/master/specification/appds_spec_1_0.md#application-store-support
and category mapping to:
https://github.com/onepf/AppDF/blob/master/specification/appds_spec_1_0.md#category-list
Right now is used in very different ways on different stores. We need to split it in two tags.
If you an owner of an Android app it will be great if you can create an AppDF file for it.
Just check the specification:
https://github.com/onepf/AppDF/blob/master/specification/appds_spec_1_0.md
and make a ZIP archive with all the APK files, screenshots, images and description.xml file.
If you can post it as a sample to this repository (inside the Samples folder) it will be a big help for other Android developers.
Here is a detailed description of SlideMe SlideLock which seems to be similar to Google LVL:
http://slideme.org/slidelock
Google Play could show the following error message for some APK files:
You uploaded an APK that is not zip aligned. You will need to run a zip align tool on your APK and upload it again.
We should also learn how to check it
"Store Specific" section allows to add custom stores (not from the store list). We need to add validation that only small English letters are used in store name and show error message is a user tried to add a store with wrong characters in the name
Editor code for the Requirements section is already written but we need also to create code to save the data into XML.
This code should be implemented in generateRequirementsXML function in appdfxmlsaving.js file
What this library should do:
Where this library will be used:
So the question is: which language should we use for this parser/validator library?
The AppDF editor already supports editing of the Requirements section but there is no loading. This logic should be added in the follosing three places:
AppDF specification is described here:
https://github.com/onepf/AppDF/blob/master/specification/appds_spec_1_0.md
The central place of the specification is description.xml file that is described there as well.
We need to create XML Schema based on this specification.
More about XML Schema:
http://www.w3.org/XML/Schema.html
http://en.wikipedia.org/wiki/XML_Schema
http://www.w3schools.com/schema/default.asp
Note that the specification is not final, so be ready to update the XML Schema when the specification is updated.
Not sure what store data are publicly available yet. As soon as it is open for general submission, publish a test application (you can take Life sample from https://github.com/onepf/AppDF/tree/master/samples/Life) and collection information about supported features.
You should add information about Ouya to all tag descriptions here:
https://github.com/onepf/AppDF/blob/master/specification/appds_spec_1_0.md#descriptionxml-structure
as well as general information about the store there:
https://github.com/onepf/AppDF/blob/master/specification/appds_spec_1_0.md#application-store-support
and category mapping to:
https://github.com/onepf/AppDF/blob/master/specification/appds_spec_1_0.md#category-list
One can add a device model to the list of unsupported devices in Requirements/Unsupported Devices. Right now the input box supports typeahead selection but the suggest list is a dummy one.
We need to find the actual list of all Android device models and put it there. I think such list should be a separate .js file in the data folder and populated in Javascript.
Let's try to go with client-side only JavaScript code.
A good example how such technology could work is here:
http://android-ui-utils.googlecode.com/hg/asset-studio/dist/index.html
In order to add information about the Android Pit AppCenter one needs to create a developer account there, publish a test application (you can take Life sample from https://github.com/onepf/AppDF/tree/master/samples/Life) and collection information about supported features.
You should add information about AppCenter to all tag descriptions here:
https://github.com/onepf/AppDF/blob/master/specification/appds_spec_1_0.md#descriptionxml-structure
as well as general information about the store there:
https://github.com/onepf/AppDF/blob/master/specification/appds_spec_1_0.md#application-store-support
and category mapping to:
https://github.com/onepf/AppDF/blob/master/specification/appds_spec_1_0.md#category-list
If I enter just one letter "a" in the "Application store name" input field (id=storespecific-input) in the "Store Specific" section and select the first value (amazon) from the typeahead suggestion dropbox it is not added to the input field.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.