| | 1 | [TOC] |
| | 2 | |
| | 3 | == Basic Coding Projects == |
| | 4 | ''Projects for beginning coders, or if new to Python or web services'' |
| | 5 | |
| | 6 | === Easy Tickets === |
| | 7 | ''GCI'' |
| | 8 | * Pick from these [/report/18 easy bugs for new Eden developers]. |
| | 9 | |
| | 10 | === Feature Enhancements === |
| | 11 | * Fix UI issues, add features, provide user-requested enhancements. |
| | 12 | * You can pick from these [/report/21 feature requests]. |
| | 13 | |
| | 14 | * The landing page for each module is different -- some have descriptive text, others have statistics (a "dashboard"). Each has a different layout of menus. |
| | 15 | * Are any of these landing pages useful? What would be better for a typical workflow? |
| | 16 | * Make appropriate changes. |
| | 17 | * Is there a common sort of menu that would be useful? |
| | 18 | |
| | 19 | === Building Assessments === |
| | 20 | We had a basic Building Assessments tool added to Sahana recently (which is based on the ATC forms), although it was done in a Web2Py style & so didn't get completed & isn't yet merged to Trunk. |
| | 21 | |
| | 22 | The Data model is all there, so just needs the S3 REST Controller plugging-in & then using components to get sections onto Tabs (as per Rapid Assessment Tool). |
| | 23 | |
| | 24 | This would be a real nice easy project to learn the beauty of the S3 Framework & would really add value :) |
| | 25 | |
| | 26 | Current code is here: |
| | 27 | * https://code.launchpad.net/~flavour/sahana-eden/buildingAssessments |
| | 28 | |
| | 29 | Original Blueprint: |
| | 30 | * http://wiki.sahanafoundation.org/doku.php/req:housing_registry_and_reconstruction |
| | 31 | |
| | 32 | === CAP: Common Alerting Protocol === |
| | 33 | * BluePrintMessagingModule#CAP |
| | 34 | * Complete the Model definitions that have been started in [http://bazaar.launchpad.net/~flavour/sahana-eden/trunk/view/head:/models/msg.py#L353 models/msg.py] |
| | 35 | * Think about some workflow for how this could be used |
| | 36 | |
| | 37 | === Common Operational Datasets === |
| | 38 | * http://oneresponse.info/resources/imtoolbox/publicdocuments/IASC%20Guidelines%20on%20Common%20Operational%20Datasets%20in%20Disaster%20Preparedness%20and%20Response%201%20Nov.%202010.pdf |
| | 39 | * Complete the Model definitions that have been started in [http://bazaar.launchpad.net/~flavour/sahana-eden/trunk/view/head:/models/08_assess.py#L1825 models/08_assess.py] |
| | 40 | * Think about how we could make use of them |
| | 41 | * Display on the Map |
| | 42 | * Have Reports which compare the baseline & situational assessments |
| | 43 | |
| | 44 | === Translations Admin Panel === |
| | 45 | * Add a page to {{{controllers/admin.py}}} to handle Translations. |
| | 46 | * Update the InstallationGuidelines with the new optional requirements. |
| | 47 | * Gracefully give nice error messages if the translate toolkit isn't installed. |
| | 48 | * Update UserGuidelinesLocalisation |
| | 49 | |
| | 50 | ==== Export PO file ==== |
| | 51 | * Dropdown to select which language |
| | 52 | * Button to call [http://translate.sourceforge.net/wiki/toolkit/py2web2po web2py2po] to convert the .py file to a standard PO file for the user to download |
| | 53 | |
| | 54 | ==== Import PO file ==== |
| | 55 | * Upload Widget which calls [http://translate.sourceforge.net/wiki/toolkit/py2web2po po2web2py] onaccept to convert a .po file to a Web2Py .py file stored in the languages folder |
| | 56 | * Use the same filename prefix or prompt? |
| | 57 | * Do a merge |
| | 58 | |
| | 59 | ==== Update Pootle ==== |
| | 60 | Provide a set of admin scripts (bzr post-commit hook?) to update Pootle with any changed strings as a Merge. |
| | 61 | |
| | 62 | === GIS/Mapping === |
| | 63 | These are a various GIS/Mapping Tasks: |
| | 64 | * Add a delay to the onHover tooltip (highlightControl) |
| | 65 | * Something like [http://cherne.net/brian/resources/jquery.hoverIntent.html hoverIntent] |
| | 66 | * Continue Integration of [http://wiki.openstreetmap.org/wiki/Potlatch_2/Deploying_Potlatch_2 Potlatch] |
| | 67 | * for editing the main OSM database |
| | 68 | * for editing a local OSM database |
| | 69 | * Make the display_feature() & display_features() popup a Window instead of opening in a DIV |
| | 70 | * This was working in FF before: http://eden.sahanafoundation.org/browser/views/sahana_scripts_min.html?rev=836#L39 |
| | 71 | * Replace the Measure Length/Area tools with [http://trac.geoext.org/wiki/ux/Measure GeoExt.ux] |
| | 72 | * Option to go Full screen & back |
| | 73 | * Full screen view (No Ext window) will be required for use on a small-screen, such as a Mobile device |
| | 74 | * [http://dev.geoext.org/trunk/geoext/examples/tree.html Layer Tree] |
| | 75 | * Separate Overlays folder into Internal/External |
| | 76 | * Sub-folders of Overlays e.g. for: |
| | 77 | * Projects by Theme |
| | 78 | * Projects by Donor |
| | 79 | * Get a pr/person/presence record upon login if HTML5 !GeoLocation available & not changed since last time |
| | 80 | * login_next |
| | 81 | * Map Preview when Lat/Lon set in pr/person/presence (auto or not) |
| | 82 | |
| | 83 | ==== OSM Importer UI ==== |
| | 84 | * There is an import stylesheet for .osm files: static/xslt/import/osm.xsl |
| | 85 | * This currently has hard-coded mappings between OSM admin levels & Sahana admin levels |
| | 86 | * * http://wiki.openstreetmap.org/wiki/Tag:boundary%3Dadministrative#10_admin_level_values_for_specific_countries |
| | 87 | * A custom controller should be written |
| | 88 | * provide a UI to the user to select their country from the dropdown which pre-populates the mapping fields for manual verification/adjustment |
| | 89 | * process the results of this to pass new variables back to the stylesheet: |
| | 90 | * http://pub.nursix.org/eden/s3xrc/vita.modules.s3xrc.s3rest.S3Resource-class.html#import_xml |
| | 91 | {{{ |
| | 92 | resource = s3xrc.resource("gis", "location") |
| | 93 | template = os.path.join(request.folder, resource.XSLT_PATH, "osm", "import.xsl") |
| | 94 | resource.import_xml("uploaded_filename.osm", template=template, mynewvar="xxx") |
| | 95 | }}} |
| | 96 | * The Stylesheet needs updating to act on these vars when found |
| | 97 | |
| | 98 | A nice further refinement would be to provide a UI to select a BBOX & optional filter to pull down the .osm file via [http://wiki.openstreetmap.org/wiki/XAPI XAPI] |
| | 99 | * Initially this could be manual text box entry of BBOX/filter |
| | 100 | * Then add a Map-based BBOX selection & dropdowns for the filter (which prepopulate the real dropdowns for manual verification/amendment) |
| | 101 | |
| | 102 | === Suggestion Box === |
| | 103 | Here are some potential features for a "suggestion box", roughly in order of priority: |
| | 104 | * Text data entry form -- just use standard Eden database fields like "timestamp", "authorstamp", and "comments", maybe with a subject field. |
| | 105 | * Allow defining topics or keywords. Let user choose a topic for their suggestion. Add all module names as an initial list of topics. |
| | 106 | * Simple search in the body of posts -- match words. |
| | 107 | * Regexp search. |
| | 108 | * Allow commenting on (replying to) suggestions -- show comment thread with original post. |
| | 109 | * Some form of importance rating (e.g. voting up or down). |
| | 110 | * Original suggestion from: http://groups.google.com/group/sahana-eden/browse_thread/thread/bbda1e98b73e1437 |
| | 111 | |
| | 112 | === !SysAdmin === |
| | 113 | * [wiki:SysAdmin#ToDo] |
