ASLO2: Difference between revisions

Line 3:

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

== 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.

@@ Line 3: / Line 3: @@
 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
-== 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.