to home page
 Home   E-Mail   Page Bottom   Aceso Healing       • Home Page  • Whats New  • FAQ  • Site Map  • Resources  • aerobics  • findingjoy  • forseniors  • Home Theatre  • L A Fitness B C  • lifeanew  • nutrition  • ptlog  • PT2go  • Strength  • thanks  • tools 

pv List Demo

  1. abcdefghijklmnopqrstuvwxyz abcdefghijklm
    1. nopqrstuvwxyz abcdefghijklmnopqrstuvwxyz
      1. abcdefghijklmnopqrstuvwxyz abcdefghijkl
      2. abcdefghijklmnopqrstuvwxyz abcdefghijkl
    2. mnopqrstuvwxyz abcdefghijklmnopqrstuvwxy
      1. abcdefghijklmnopqrstuvwxyz abcdefghijkl
  2. abcdefghijklmnopqrstuvwxyz abcdefghijklm
    1. nopqrstuvwxyz abcdefghijklmnopqrstuvwxyz
      1. abcdefghijklmnopqrstuvwxyz abcdefghijkl
      2. abcdefghijklmnopqrstuvwxyz abcdefghijkl
    2. mnopqrstuvwxyz abcdefghijklmnopqrstuvwxy
      1. abcdefghijklmnopqrstuvwxyz abcdefghijkl

technologies available or emergingour needs
  1. APL implemented as a .NET language.
  2. a vast library of utilities created by APL geniae.
  3. Visual Studio 2010.
  4. Microsoft .NET Framework 4, Windows 7 (64 bit systems).
  5. a vast library of C## utilities created by geniae of many disciplines.
  1. algorithmic requirements richly met in APL (.NET compatible)
  2. need for grid forms created from "properties" (as the APL grid object would do) (maybe TList)
  3. need for organizing functionality (as used to be done in MDI fashion)

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. We expect that tasks will be identified and contracted separately as we build our team. For more information, call Carl House at 561-368-7445, Skype "", or e-mail at "". (updated 3/22/19 15:13)

  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 (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 enable APL & Carl's APL software to serve as the calculating engine
    2. .Net languages (C# only), Visual Studio, & ASP.Net are important for our use of .Net
    3. CMS, if needed, could be: DotNEtNuke, Umbraco CMS & KEntico CMS (all 3 are free open source) & Telerik sitefinity (not free)
  5. Phase II: Create The Mucky Duck as a Visual Studio application to be run on a virtual server:
  6. Phase III: Facebook (to help us learn to market via social media), see: Facebook: Test Pages
    1. Evaluate our Facebook community page 70% Water. Name should be "70% Water (".
    2. Create, enhance & promote a Facebook fan page with the name "70% Water (" as lead for 70% Water Community Page.
    3. Enhance & promote the existing Facebook community page "APL Bricollage".
    4. Create, enhance & promote a Facebook fan page with the name "Interfaith Engagement" as lead for .
    5. Develop strategy for marketing via Facebook, e.g. make a web home page show Facebook fans (photos) at the bottom of the page. What else (lots more) ?
  7. Phase IV: Repeat Phase II but for (uses Landev.w3, our second APL model)
    1. Our first accomplishment will be to implement Landev with layered inputs so the primary input form can be as simple as The Mucky Duck.
    2. If we have a good demo by March 31, we can show it at &
    3. To really empower the user we will require more tools. Inputs & outputs are far more complex than for and The Mucky Duck.
    4. We believe that might be a big help.
    5. User inputs are matrices which are not constant in shape: input views.
    6. Outputs are mostly time series data or analysis of time series data: output views.
    7. Presently outputs are expressed as HTML reports (pages), but other options should be easy.
  8. Phase V: Expand Phase IV so it can be used in any nation:
    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 provides description and instructions for a "Click Once" software platform that has been created from C# and Visual Studio 2010 by Lescasse Consulting. (updated 3/22/19 15:13)

  1. The Mucky Duck ClickOnce application is at: (version
    1. ClickOnce and .NET Framework Resources (Visual Studio 2010 & C#)
  2. done
    1. hide passwords while typing so they are not revealed, no need to change passwords yet as testing & demo are easy now
    2. change the combo boxes turn50 & turn1500 to TextBoxes so the user can specify any number of seconds including negative numbers (gain in a turn)
    3. Server ISP addresses and Nameservers have been assigned.
    4. assign domain name "" to the new Virtual Server (IP address & assignment should be available 2/22/2011)
    5. we can remotely connect to our new Virtual Server using Windows Terminal Services (mstsc), for instructions see:
    6. install this to Carl's local machine so he can develop with both APL & C# sessions. high priority
    7. Eric configured the new Virtual Server
    8. Eric published the Mucky Duck ClickOnce application to our Virtual Server
  3. things to do ASAP: high priority
    1. improve wording on our C# Windows Form
    2. Carl will write VarsToErase to be called by SaveToDropbox
    3. Carl will do more testing, especially saving changed data and entering new swimmer data in the database (this MUST work perfectly in all cases)
    4. write first draft of documentation & instructions & then continually improve it. high priority (release (version), republish (Publish), recompile (Rebuild Solutionn)
    5. by making the QKW apl app have same look & feel as The Mucky Duck, we'll make it credible that we can deploy QKW as we did The Mucky Duck
  4. things to do when Eric has time:
    1. maintain updates on Carl's local computer (write instructions for this to reduce need for Eric's time)
  5. someday maybe
    1. Implement the narrative format and the chart format for interactive use if effort (cost) is modest.
    2. change our database from Colossal Files to SQL Server
  6. Membership (our intent, maybe not fully implement til later)
    1. Maybe anyone should be allowed to use The Mucky Duck without membership, password, or saved data.
    2. It should be optional for the user to have his data saved for his next session because many people will play a little and not return. We should make this easy.
    3. If one wishes to save his/her data, then one needs to be a member with a password.
  7. Other
    1. The Mucky Duck will be a free service; there is no need to provide for charging the user for use of The Mucky Duck.
    2. User input is processed using algorithms in APL (, a .Net language.
    3. Train Carl so he can maintain and expand our new web application website(s).
  8. Eric should write the procedure for creating a QKW app similar to The Mucky Duck, here is what we said the steps were for The Mucky Duck
    1. Input form (1):
      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. Murali's original
      3. Eric's revision
      4. 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): (as an example).
      1. At this point we will have proved that we can work on a server.
    3. Carl will create data for a prototype model in Landev.w3, data will be assembled from "systems to support human life" so the input form will not be more complicated than the one for The Mucky Duck
    4. Carl imagines writing these top level fns for the QKW platform (inspired by The Mucky Duck, running in APL only for now)
      1. qkwCalc : process one set of QKW data for one project (dkCalc)
      2. qkwInit : initialize vars needed for the QKW platform (dkInit)
      3. qkwCF_Form : transfer input data back & forth between Colossal File format & format for the ASPX form (dkCF_Form)
      4. qkwData : handle IO for QKW data (one project) (one instance one user all data) (dkData)
      5. qkwLoop : do batch processing to assure that everything still works right (dkLoop)
      6. qkwFiles : define FLF FLI FLO FLS et al to identify files required (dkFiles)
      7. qkwRelease : release procedure for the QKW C# applications running as Click Once & run major C# fns (dkRelease)

• Home Page  • Whats New  • FAQ  • Site Map  • Resources  • aerobics  • findingjoy  • forseniors  • Home Theatre  • L A Fitness B C  • lifeanew  • nutrition  • ptlog  • PT2go  • Strength  • thanks  • tools 

 Home   E-Mail   Page Top