31,029
edits
Google Summer of Code Ideas 2013: Difference between revisions
Google Summer of Code Ideas 2013 (view source)
Revision as of 19:47, 12 February 2013
, 13 years agono edit summary
No edit summary |
|||
| Line 2: | Line 2: | ||
{{Template:SoC}} | {{Template:SoC}} | ||
Welcome on the page dedicated to the Idea List (suggested by the Dolibarr core team, Dolibarr users or students) for the Google Summer Of Code (please read the introduction before adding/editing your own idea). | Welcome on the page dedicated to the Idea List (suggested by the Dolibarr core team, Dolibarr users or students) for the Google Summer Of Code (please read the introduction before adding/editing your own idea). | ||
NOTE FOR STUDENT: WE MUST FIRST WAIT VALIDATION OF GOOGLE TO BE AN OFFICIAL MENTOR FOR GOOGLE SUMMER OF CODE BEFORE APPLYING FOR AN IDEA. THANKS TO COME BACK ON MARCH ON THIS PAGE. | |||
| Line 35: | Line 38: | ||
* Knowledge Prerequisite: Eclipse + GIT + [http://en.wikipedia.org/wiki/REST REST protocol] + PHP 5.3+ | * Knowledge Prerequisite: Eclipse + GIT + [http://en.wikipedia.org/wiki/REST REST protocol] + PHP 5.3+ | ||
* Mentor: [[Laurent Destailleur]] | * Mentor: [[Laurent Destailleur]] | ||
* Backup mentor: | * Backup mentor: To define | ||
* Why: Be more ready to cloud or mobile usage that need such API (preferred to SOAP) to exchange data. | * Why: Be more ready to cloud or mobile usage that need such API (preferred to SOAP) to exchange data. | ||
* Expected results: Having 100% of services actually covered by SOAP, covered by REST, including REST unit tests. | * Expected results: Having 100% of services actually covered by SOAP, covered by REST, including REST unit tests. | ||
| Line 47: | Line 50: | ||
* Expected results: Having a software we can use on an Android smartphone with a resolution of 640 x 240 (no fields cuts by screen size, easy navigation into menus). | * Expected results: Having a software we can use on an Android smartphone with a resolution of 640 x 240 (no fields cuts by screen size, easy navigation into menus). | ||
* Knowledge Prerequisite: Eclipse + GIT + PHP 5.3+ for server pages to develop + ([http://jquerymobile.com/ JQuery mobile] xor Android SDK, it depends on student technology choice) | * Knowledge Prerequisite: Eclipse + GIT + PHP 5.3+ for server pages to develop + ([http://jquerymobile.com/ JQuery mobile] xor Android SDK, it depends on student technology choice) | ||
* Mentor: | * Mentor: To define | ||
* Backup mentor: | * Backup mentor: To define | ||
* Why: Dolibarr is a web software. Using it with a smartphone works in the same way as using it from a browser desktop. However, screens are very rich with information and often too rich for a friendly usage with a small screen. Goal is to provide an interface with the most possible features that is optimized for smartphone screens. | * Why: Dolibarr is a web software. Using it with a smartphone works in the same way as using it from a browser desktop. However, screens are very rich with information and often too rich for a friendly usage with a small screen. Goal is to provide an interface with the most possible features that is optimized for smartphone screens. | ||
* Difficulty/time to achieve (Low/Medium/High): High | * Difficulty/time to achieve (Low/Medium/High): High | ||
| Line 76: | Line 79: | ||
* Expected results: | * Expected results: | ||
* Knowledge Prerequisite: Eclipse + GIT + [http://en.wikipedia.org/wiki/Model-driven_architecture MDA] + PHP 5.3+ | * Knowledge Prerequisite: Eclipse + GIT + [http://en.wikipedia.org/wiki/Model-driven_architecture MDA] + PHP 5.3+ | ||
* Mentor: | * Mentor: To define | ||
* Backup mentor: | * Backup mentor: To define | ||
* Why: Increase speed of developing business modules. | * Why: Increase speed of developing business modules. | ||
* Difficulty/time to achieve (Low/Medium/High): High | * Difficulty/time to achieve (Low/Medium/High): High | ||