Features/Cordova Container for Sugar: Difference between revisions
No edit summary |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
<noinclude> | <noinclude> | ||
[[Category:Feature Page Incomplete]] | [[Category:Feature Page Incomplete]] | ||
[[Category:Feature| | [[Category:Feature|Cordova Container for Sugar]] | ||
[[Category:sugar cordova|.]] | [[Category:sugar cordova|.]] | ||
<!-- You can add categories to tie features back to real deployments/schools requesting them, for example | <!-- You can add categories to tie features back to real deployments/schools requesting them, for example | ||
| Line 20: | Line 20: | ||
== Current status == | == Current status == | ||
* Targeted release: 0.104 | * Targeted release: 0.104 | ||
* Last updated: | * Last updated: 2th, Sept,2014 | ||
* Percentage of completion: | * Percentage of completion: 80% | ||
== Detailed Description == | == Detailed Description == | ||
Cordova is basically used as a middle layer between the web app and the native source code. This layer abstracts the native source code by providing its own api which can be used to access most of the functionality features of the native source code. So basically we can access the low lying features (features closer to hardware) through the web app. This enables the developers to keep the same code at top and achieve the same functionality from different platforms. Thus, the web app developers dont need to change their HTML5 app's code to port it to different platforms if the app is made with cordova and the platform on which he has to port supports cordova. Thus, cordova helps us to make cross platforms apps. This will attract the web app developers to sugar community and help them launch their activities in sugar without playing or learning the native bindings. A single command line allow a developer to convert an existing HTML5 cordova app into a Sugar app. | [http://cordova.apache.org/ Cordova] is basically used as a middle layer between the web app and the native source code. This layer abstracts the native source code by providing its own api which can be used to access most of the functionality features of the native source code. So basically we can access the low lying features (features closer to hardware) through the web app. This enables the developers to keep the same code at top and achieve the same functionality from different platforms. Thus, the web app developers dont need to change their HTML5 app's code to port it to different platforms if the app is made with cordova and the platform on which he has to port supports cordova. Thus, cordova helps us to make cross platforms apps. This will attract the web app developers to sugar community and help them launch their activities in sugar without playing or learning the native bindings. A single command line allow a developer to convert an existing HTML5 cordova app into a Sugar app. | ||
== Benefit to Sugar == | == Benefit to Sugar == | ||
Sugar will be benefited from the cordova layer development as more people (those with knowing only html,js and css) can contribute to the Sugar. People can port their apps to the Sugar and see them working live. They | Sugar will be benefited from the cordova layer development as more people (those with knowing only html,js and css) can contribute to the Sugar. People can port their apps to the Sugar and see them working live. They don't need to learn the gtk stack or Sugar native api to build up activities. Sugar will support the cross platforms apps which work across different platforms and hence the Sugar audience would have a better experience | ||
== Scope == | == Scope == | ||
| Line 39: | Line 39: | ||
This feature is an enhanced, it does not have any direct impact on Sugar. It does not need a UI. The UI is depended on the cordova app which in turn is depended on the developer of the cordova app. | This feature is an enhanced, it does not have any direct impact on Sugar. It does not need a UI. The UI is depended on the cordova app which in turn is depended on the developer of the cordova app. | ||
The detailed | The detailed description regarding the project can be found here: http://sugarcordova.blogspot.com/ | ||
== How To Test == | == How To Test == | ||
<!--{{:{{PAGENAME}}/Testing}}--> | <!--{{:{{PAGENAME}}/Testing}}--> | ||
You can find instructions to test it on your systems here : | You can find instructions to test it on your systems here: [[Sugar Cordova]] | ||
== User Experience == | == User Experience == | ||
| Line 60: | Line 60: | ||
<!--''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''--> | <!--''Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''--> | ||
The topic was proposed as a part of Google Summer of Code. | The topic was proposed as a part of Google Summer of Code. | ||
* [[Summer of Code/2014]] | |||
* [[Summer of Code/2014/sugar cordova]] | |||
* [[Sugar Cordova]] | |||
* http://sugarcordova.blogspot.in/ | |||
http://sugarcordova.blogspot.in/ | |||
== Release Notes == | == Release Notes == | ||
<!--''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''--> | <!--''The Sugar Release Notes inform end-users about what is new in the release. An Example is [[0.84/Notes]]. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.''--> | ||
No release notes for this enhancement yet | No release notes for this enhancement yet. | ||
== Comments and Discussion == | == Comments and Discussion == | ||
| Line 75: | Line 74: | ||
* http://sugarcordova.blogspot.com/ | * http://sugarcordova.blogspot.com/ | ||
* http://lists.sugarlabs.org/archive/sugar-devel/ | * http://lists.sugarlabs.org/archive/sugar-devel/ | ||
* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. --> | * See [[{{TALKPAGENAME}}|the discussion tab for this feature.]] <!-- This adds a link to the "discussion" tab associated with your page. This provides the ability to have ongoing comments or conversation without bogging down the main feature page. --> | ||