NRAO Home  >  Green Bank  |  Wiki Topic:    GB > Data > FormRequirements
   Changes | Index | Contents | Search | Statistics | Jump to Topic

Form Requirements for Integrated Desktop


The architectural guideline for developing forms is: we develop them as standalone applications. We integrate them into the IntegratedDesktopPrototype by making them children of the integrated desktop. We can use them alone or in context.

We have to arrange these in some kind of priority order. It would also be helpful to come up with a numbering scheme, so for example, we could refer to a particular application as "Form 555" and that would be the name of the source code file too (555.py). This way, we don't have to worry about managing long descriptive names. (SAP, Siebel and Amdocs built their products this way, and it works great.)

  1. proto Parent/Integrated Desktop - needs to get over to Linux machine before we can call it "done"
  2. Observational Setup (configure/observe)
  3. Observing Table
  4. Status Panel
  5. in progress Device Explorer
  6. Data Browser
  7. Data Quality Browser
  8. proto Text Editor (9/26 - ashelton)
  9. done Access to Glish Command Line (10/1 - ashelton)
  10. User Preferences
  11. FQL GUI

-- AmyShelton - 02 Oct 2003

Topic FormRequirements . { Edit | Attach | Ref-By | Printable | Diffs | r1.5 | > | r1.4 | > | r1.3 | More }
Revision r1.5 - 19 Feb 2004 - 03:32 GMT - NicoleRadziwill Content copyright © 1999-2007 by the contributing authors.
All material on this collaboration platform is the property of the contributing authors.