8,288
edits
Changes
Jump to navigation
Jump to search
mLine 3:
Line 3: − + Line 28:
Line 28: − + Line 34:
Line 34: − +
update link
</noinclude>
</noinclude>
{{Note/important|WE NEED YOU!|[https://github.com/samdroid-apps/sugar-activities#sugar-activities Add you activity!]}}
{{Note/important|WE NEED YOU!|[https://github.com/samdroid-apps/sugar-activities#sugar-activities Add your activity!]}}
Right now, publishing an activity is a lot harder than it needs to be; making it easier gives developers more time to develop activities. The new ASLO '''automatically builds the activities and extracts metadata''' from their code/PO files. It integrates with GitHub to automatically build on push. Releasing a new version is as easy as changing the version number and "git push". Development copies are build on every push, helping get the latest versions to users who want to be more involved in the development process.
Right now, publishing an activity is a lot harder than it needs to be; making it easier gives developers more time to develop activities. The new ASLO '''automatically builds the activities and extracts metadata''' from their code/PO files. It integrates with GitHub to automatically build on push. Releasing a new version is as easy as changing the version number and "git push". Development copies are build on every push, helping get the latest versions to users who want to be more involved in the development process.
Commenting is also a very one way thing on the old ASLO; you can post a comment but developers can't reply. This is helpful to developers of Sugar - it only scares users off our activities. By integrating [[Features/SocialHelp|SocialHelp]] with the comments, the '''comments can start a discussion''' between developers and users. This will allow us to create software that better helps users. Moving the comments to [[Features/SocialHelp|SocialHelp]] also unifies the point of contact for Sugar users.
Commenting is also a very one way thing on the old ASLO; you can post a comment but developers can't reply. This is helpful to developers of Sugar - it only scares users off our activities. By integrating [[Features/Social_Help|Social Help]] with the comments, the '''comments can start a discussion''' between developers and users. This will allow us to create software that better helps users. Moving the comments to [[Features/Social_Help|Social Help]] also unifies the point of contact for Sugar users.
The new ASLO also '''loads faster'''. According to the Firefox Dev Tools, for ruler activity the difference is 53kb (1sec) vs 362kb (10sec) without cache. There is still an improvement with a primed cache. This comes from not using jquery or any javascript for example - this is just an app store, not interactive computer game.
The new ASLO also '''loads faster'''. According to the Firefox Dev Tools, for ruler activity the difference is 53kb (1sec) vs 362kb (10sec) without cache. There is still an improvement with a primed cache. This comes from not using jquery or any javascript for example - this is just an app store, not interactive computer game.
Since the new ASLO uses a '''microservices''' structure, it can be simpler to maintain reliability. The web interface (what users see) can be run without any external dependencies on anything that runs docker. The backend (all the services oriented on processing activities to json) are based around a message queue for a clean service design.
Since the new ASLO uses a '''microservices''' structure, it can be simpler to maintain reliability. The web interface (what users see) can be run without any external dependencies on anything that runs docker. The backend (all the services oriented on processing activities to json) are based around a message queue for a clean service design.
The new ASLO will also provide a '''platform for innovation''' by making the dataset publicly available and versioned in git. For example, instead of manually adding forums for activities to SocialHelp, that can be automatically done with the new ASLO data.
The new ASLO will also provide a '''platform for innovation''' by making the dataset publicly available and versioned in git. For example, instead of manually adding forums for activities to Social Help, that can be automatically done with the new ASLO data.
== Scope ==
== Scope ==