We maintain many static webpages, but we have no capability to provide for user interaction. We are very dependent on APL, a .Net language. We want to implement our APL workspaces as web applications. Assistance is needed for the work described below. Each phase should be contracted separately. For more information, call Carl House at 561-368-7445, Skype "carl.house", or e-mail at "carlhous@gmail.com". (updated 12/13/11 11:30)

1. Objectives
   1. Objective is to create an important web application for planning & developing cities & villages throughout the world.
   2. Organize work in phases to help develop the team and to allow for evaluation of progress.
   3. More specific objectives & illustrations are expressed for each phase of the work.
2. Status
   1. We have a black box of algorithms which can be used with command line processing (written in a .Net language called APL).
   2. We have lots of test or demo data.
   3. We have documentation which can be the foundation for a help system.
   4. Reports are created in HTML though there is provision for creating output reports in other formats.
   5. Data is organized in a CMS & APL workspaces which Carl wrote. It has no provision for user interactivity except for navigation thru static pages.
   6. There is no user IO, nor a menu platform, nor editors. All that work is presently done with command line processing.
   7. Carl has Skype, GoToMyPc, and a Facebook API id.
   8. Skill with APL is not required as Carl (and his APL friends) are skilled in it.
3. Phases I, II, & III will be on http://www.sofl.cc/ (a very simple website & calculating workspace).
4. Phase I: Create a plan for completing this work in stages to best control quality and cost.
   1. Eric's dll utility will serve as the calculating engine
5. Phase II: Create The Mucky Duck as a ASP.NET application to be run on a virtual server: http://www.sofl.cc/muckyduck/
   1. Input form (1): http://www.sofl.cc/muckyduck/entryform.htm.
      1. Task #1: write one ASPX Web Page with C# code behind file mimicing entryform.htm. Deliver 2 files: EntryForm.aspx & EntryForm.aspx.cs (no need to write C# code)
      2. Because input is so modest, we should be able to do a superb job of error checking and ease of use. (swim times should be in the form mm:ss:hh)
   2. Output form (1): http://www.sofl.cc/muckyduck/carl-house.htm (as an example).
      1. Implement the narrative format and the chart format for interactive use if effort (cost) is modest.
   3. Membership
      1. Anyone should be allowed to use The Mucky Duck without membership, password, or saved data.
      2. If one wishes to save his/her data, then one needs to be a member.
   4. Database
      1. It should be optional for the user to have his data saved for his next session; this is because many people will play a little and not return.
   5. Other
      1. The Mucky Duck will be a free service; there is no need to provide for charging the user for use of our facility.
      2. User input is processed using algorithms in APL (http://www.apl2000.com/), a .Net language.
      3. Train Carl so he can maintain and expand our new web application website(s).
6. Phase III: Facebook (this is not essential for the March 31 target date, but it is probably very easy to do & will help marketing)
   1. Evaluate our Facebook group page 70% Water. Name should be "70% Water (SoFL.cc)".
   2. Create a Facebook fan page with the name "70% Water (SoFL.cc)".
   3. Develop code & strategy to make the sofl.cc home page show Facebook fans (photos) at the bottom of the page & for Carl to promote the website on Facebook.
7. Phase IV: Repeat Phase II but for http://www.anewhaiti.net/.
   1. This will require more tools than the new web application provides. Inputs & outputs are far more complex than for sofl.cc and The Mucky Duck.
   2. We believe that http://www.bennet-tec.com/BTProducts/TList/ might be a big help.
   3. User inputs are matrices which are not constant in shape: input views.
   4. Outputs are mostly time series data or analysis of time series data: output views.
   5. Presently outputs are expressed as HTML reports (pages), but other options should be easy.
   6. If we have a good demo by March 31, we can show it at http://www.sustainatopia.com/ & http://www.haiticonference.com/.
8. Phase V: Expand Phase IV so it can be used in any nation: http://www.saltpond.us/.
   1. Allow the user to select his native language and the currency of his nation.
9. Principles
   1. Everything should be straightforward so our product is little dependant on specific persons as possible. Object oriented programming is expected.
10. Criteria for the new template for webpages:
    1. Screen has top & bottom windows with navigation in top & content for the current page in the second window (rectangle).
    2. There might also be a thin window at the bottom providing "jump to the top" and other end of page options.
    3. Navigation is by drop down boxes in the top window; we must avoid custom work for ease of maintenance.
    4. This gives us maximum flexibility for content presentation; we will use this template for all our pages.
    5. The template must be impressive, perhaps flash, to overcome the fact that Carl's work has always been old fashioned in appearance.
    6. Keep the current logo (sunny face over water); we have it in horizontal & vertical versions.
    7. Install new webpage template on Carl's laptop computer and coach him on getting started in using it.

This work program is underway. More information about it is avaiiable at: www.whirp.org/qkw.