ASLO2: Difference between revisions
Added a page about the ASLO2 idea |
Added info about features |
||
| Line 3: | Line 3: | ||
You can find the code here: https://github.com/SAMdroid-apps/aslo/ | You can find the code here: https://github.com/SAMdroid-apps/aslo/ | ||
== JSON Backend == | == Features == | ||
Here is a rundown from the mailing list: | |||
[We] need start with the features the actual ASLO have: | |||
* Stores every version of a activity (.xo, release notes, screenshots). | |||
Added that | |||
* Can search by text or activity description (English only) | |||
Yep. The search is even done client side so it is (almost) instant. | |||
* UI localized | |||
I have that feature, but no translations :) | |||
* Activities have categories | |||
I will add that. I'm not really sure what categories to do, maybe these: http://jsfiddle.net/H5sAH/2/ (I tried to base it off the ASLO but the ASLO's categories IMHO are pretty confusing)? | |||
Also maybe put the categories in a categories field in activity.info? | |||
* Users can add comments and stars | |||
Yep. | |||
* Offer the last activity version available based on the user Sugar version (if use Browse activity) | |||
etc | |||
Just did that. | |||
[You] can add the new features we need: | |||
* support i18n (search in languages different than English) | |||
Yep, got that. | |||
* make easier publish a new version | |||
* automatic publish of development versions with github hooks | |||
I think so. I've probably also made it a pain to not use github hooks :) | |||
* bugs reports? (will create bus in bugs.sugarlabs.org?) | |||
That is a good idea! Maybe let developers choose between that and github issues? | |||
* improve communication with the developers? | |||
Well the aslo2 has lost all references to firefox :) | |||
Also I have replies in that comments which let developers or community members reply, and I should add email notifications. | |||
== Implementation Details == | |||
=== JSON Backend === | |||
The data about the activities is stored in a json file. This json file is available via GitHub (currently https://github.com/SAMdroid-apps/sugar-activities). This is served with the correct content type here: http://aslo-bot-master.sugarlabs.org/data.json | The data about the activities is stored in a json file. This json file is available via GitHub (currently https://github.com/SAMdroid-apps/sugar-activities). This is served with the correct content type here: http://aslo-bot-master.sugarlabs.org/data.json | ||
== Activity Buildbots == | === Activity Buildbots === | ||
The aslo2 integrates a lot with GitHub. It offers a web hook for which the activity can be automatically built and listing data extracted. | The aslo2 integrates a lot with GitHub. It offers a web hook for which the activity can be automatically built and listing data extracted. | ||
Revision as of 06:25, 24 May 2014
The aslo2 is a hypothetical revision of the aslo site that brings new features. This pages discusses them.
You can find the code here: https://github.com/SAMdroid-apps/aslo/
Features
Here is a rundown from the mailing list:
[We] need start with the features the actual ASLO have:
* Stores every version of a activity (.xo, release notes, screenshots).
Added that
* Can search by text or activity description (English only)
Yep. The search is even done client side so it is (almost) instant.
* UI localized
I have that feature, but no translations :)
* Activities have categories
I will add that. I'm not really sure what categories to do, maybe these: http://jsfiddle.net/H5sAH/2/ (I tried to base it off the ASLO but the ASLO's categories IMHO are pretty confusing)?
Also maybe put the categories in a categories field in activity.info?
* Users can add comments and stars
Yep.
* Offer the last activity version available based on the user Sugar version (if use Browse activity)
etc
Just did that.
[You] can add the new features we need:
* support i18n (search in languages different than English)
Yep, got that.
* make easier publish a new version
* automatic publish of development versions with github hooks
I think so. I've probably also made it a pain to not use github hooks :)
* bugs reports? (will create bus in bugs.sugarlabs.org?)
That is a good idea! Maybe let developers choose between that and github issues?
* improve communication with the developers?
Well the aslo2 has lost all references to firefox :)
Also I have replies in that comments which let developers or community members reply, and I should add email notifications.
Implementation Details
JSON Backend
The data about the activities is stored in a json file. This json file is available via GitHub (currently https://github.com/SAMdroid-apps/sugar-activities). This is served with the correct content type here: http://aslo-bot-master.sugarlabs.org/data.json
Activity Buildbots
The aslo2 integrates a lot with GitHub. It offers a web hook for which the activity can be automatically built and listing data extracted.
Here is a diagram of the network:
GitHub ----Hook-Request----> Bot Master <----Activity-Data------.
^ | ^------Request-For-Task---> Bots
|-----Data-Committed---------|
Here is a list of data sorces for the activity listing:
- Title, Summary - activity.info for en-US and po/LANG.po for the translations
- Screenshots - /screenshots/LANG/NAME.png
- What's New - NEWS.LANG (NEWS defaults to en-US). Use this format https://github.com/ignaciouy/chat/blob/af7bbc9b8036fb7252cf21cd6a2e6d545a42ed5d/NEWS
- Compatibility - Robots reading through your code :)
- Authors - You need to do that manually
- Bundle - Automatically compiled by the robots
Commenting
Here are a few points:
- Live updating - via websockets
- Replying to comments
- 4 comment types: bug, question, idea and rating
Design / UX
SAMdroid (talk) I think it looks nicer. You compare: http://imgur.com/C4oxFtS
It is a html5 site with ajax, rather than just server side pages.