Differences

This shows you the differences between two versions of the page.

Link to this comparison view

req:app_store [2010/06/25 21:11]
glenn Update about Kusum's experiements, Symfony
req:app_store [2010/12/18 17:35] (current)
Line 11: Line 11:
 Ideally, an App Store could be built in such a way that it is generic and should work with both Agasti, Eden, and (further on) mobile components. ​ The modules will be cataloged referencing the platform and version, which will make finding compatible modules easy from a version of Agasti or Eden.  The system will basically deliver some compressed package and the respective Sahana version be responsible of installing it.  Ideally, an App Store could be built in such a way that it is generic and should work with both Agasti, Eden, and (further on) mobile components. ​ The modules will be cataloged referencing the platform and version, which will make finding compatible modules easy from a version of Agasti or Eden.  The system will basically deliver some compressed package and the respective Sahana version be responsible of installing it. 
  
-===== Features and Architecture =====+===== Features and Architecture ​Supporting Sahana Modules ​=====
  
 A Sahana App Store could broadly emulate the Android Marketplace and iPhone App Store. ​ Desirable features include: ​ A Sahana App Store could broadly emulate the Android Marketplace and iPhone App Store. ​ Desirable features include: ​
Line 28: Line 28:
   * the server that will host the app store centrally. ​ Its functionally should be pretty much independent of framework, version, or implementation type.  It should be to be able to support multiple versions of Sahana.   * the server that will host the app store centrally. ​ Its functionally should be pretty much independent of framework, version, or implementation type.  It should be to be able to support multiple versions of Sahana.
   * the client libraries (specific to Agasti, Eden, etc.) that will install/​uninstall the apps and otherwise interact with the store.   * the client libraries (specific to Agasti, Eden, etc.) that will install/​uninstall the apps and otherwise interact with the store.
 +
 +===== Eventual Support For Additional Store Offerings =====
 +After modules are well-supported,​ other potential offerings include:
 +
 +  * GUI themes
 +  * Language packs
 +  * Database initial content (e.g., geographic place names and locations. ​ Likely implemented by SQL scripting)
 +  * Specialized tools (e.g., to quickly configure an instance for a particular type of disaster)
 +  * Mobile apps
 +  * T-shirts and other swag?
  
 ===== Policy and Process for App Store Contributions ===== ===== Policy and Process for App Store Contributions =====
Line 68: Line 78:
  
 ===== Initial Experimentation ===== ===== Initial Experimentation =====
-In June, 2010, GSoC student Kusum Kumar Madarasu, working on the Agasti Module Manager project, ​has started learning about Drupal 6/7 and its modules of potential pertinence to an App Store.  ​As a familiarization experiment, he is considering ​a Drupal + Ubercart architecture with Acquia Prosper theme.+In June, 2010, GSoC student Kusum Kumar Madarasu, working on the Agasti Module Manager project, started learning about Drupal 6/7 and its modules of potential pertinence to an App Store.  ​He first considered ​a Drupal ​+ Ubercart architecture with Acquia Prosper theme.  The current prototyping direction drops Ubercart, in favor of a native Drupal custom node approach.
  
 ===== Conjectured Timeframe ===== ===== Conjectured Timeframe =====
req/app_store.txt · Last modified: 2010/12/18 17:35 (external edit)
Back to top
CC Attribution-Noncommercial-Share Alike 3.0 Unported
chimeric.de = chi`s home Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0