Envelope/Quill XtC24081999

- Last edited November 17, 1999
Previous: XtC17081999 Next: XtC31081999
Meeting 24th August 1999 The Yorkshire Grey

Agenda

Minutes Deliverables

Here's what we did xpdeveloper.com/cgi-bin/cvsweb.cgi/xtc/ It took 2.5 hours to implement things, i'm not sure DoingTheLoadFactor? on this granularity of time holds water.

Action


24/Aug/99

[1]

Story: Write words

 Priority: 1
 Estimate: < 1
 Author: OliBye

I want to write some words and have other people see and edit those words when I finish.

Engineering Tasks

  1. Save a string or object and get it back

    1. Wrote a test (TestEdit?.testSaving) that simply stores and loads a string.
    2. We then wrote the PageSaver? class to get this test running. Notice that this code only uses an instance variable to "save". However this is enough to get the test running.
    3. We versioned this work in [Xtc.xtc0_99] as our first running example.

  2. Displaying a string in a web page

    1. First we tried to write "TestEdit?.testDisplaying" that calls doGet on a servlet. We envisioned extending our PageSaver? to be a servlet and calling PageSaver?.doGet to display the text we can already save. Leaving changing the text via HTTP until the next EngineeringTask?.
    2. When we wrote the servlet code, we discovered that our test failed. A closer examination of doGet revealed that we needed to mock up request and response objects. These objects have big interfaces that are a lot of work to create. We decided to try an alternative approach (our task was in danger of taking too long, we had already spent 20 minutes). We had a bit of experience writing HTTP request code, so we clipped it from an example to help us move on with our test. This didn't feel so great, but we wanted to get something running
    3. We versioned this work in [Xtc.xtc1_00] as our second running example.

    4. The differences between [Xtc.xtc1_00] an [Xtc.xtc1_01] are:
    5. [Xtc.xtc1_01] to [Xtc.xtc1_02]

- Last edited November 17, 1999

https://casino-brain.com/