![]() |
devNote
d061001 |
0.07 2008-04-23 21:11 -0700 |
Status |
Date |
Description |
|
2007-12-01 | When the download material is updated and the regression set is deleted from the practical100 archive, there are also changes to be made to the license and manifest per #60.20. | ||
2007-11-28 | d061001i: Review the d061001h developer notes for actions to be taken with the 0.60 release. | ||
2007-11-18 | d061001h: Complete section 4.7, the final packaging, as part of putting up the complete 0.59 release as latest. Note whether there have been any adjustments or not. | ||
2007-11-18 | d061001h: Do something abut this: The regression set will have its own release notes, manifest, and sample information. This will support use of this simple confirmation program until we come up with something better. We will likely accomplish this in the packaging stage, where the regression sets may be moved and reconfirmed for future use as part of packaging and availability as confirmation programs for the runtime. I also need to run the tests. Note: These tests may be moved to a part of the deployment packaging tree for preservation there. This will be resolved after the odjni100 changes are completed in step 4.5. We might need to have the tests in both places because of packaging considerations. Interesting.} | ||
2007-11-18 | d061001: Upgrade when d061001h becomes current. | ||
2007-11-18 | d061001b: Point to d061001h when the deployment happens. | ||
2007-11-18 | d061001h: Wrap up things when the package is complete. Do not make current until the 0.59 deployment happens. | ||
2007-11-12 | All manifests and release notes must be updated to eliminate direct access to the ActiveODMA list and only refer to the ODMA contact page. This work items should be added to all ODMdev folios that have downloads with manifests and other notes. So (1) do it here and (2) propogate it to other folios. d061001h.txt, | ||
2007-09-23 | d061001g: Redo the Developer Notes in the style of d070701d. | ||
2007-08-19 | d061001g: See if the additional notes mentioned in the text have been applied or not. | ||
2007-08-19 | d061001g: review the manifest, the license text, the Release Notes, and the Zip file for proper handling of case in all materials. | ||
2007-08-19 | d061001f: review the manifest, the license text, the PreRelease notes, and the Zip file for proper handling of case in all materials. | ||
2007-08-19 | d061001e-license.txt: The link should be with DMware.info, not Dmware.info. Need to plan redirection if I go to lower-case at DMware.info where the master BSD Template License is stored. | ||
2007-08-19 | d061001e.txt: Correct to be served as UTF-8 no matter what. (This is mostly a problem with needing the BOM when FrontPage opens the page in its text editor.) | ||
2007-08-19 | d061001e.txt: Correct the title of the page in the first line. | ||
2007-08-16 | d061001d: Find out what to say about the test program, and how it was moved. | ||
2007-08-16 | d061001d: The business about recompiling from one class by dependency relationship needs to be pointed out was buggy and the classes have to be deleted before recompiling the package from source. | ||
2007-08-16 | d061001d: The statements about the batch files and other aspects of building need to be noted as obsoleted and where | ||
2007-08-16 | d061001d: The statement about Connection classes being invoked by applications needs to be corrected | ||
2007-08-16 | d061001d, e, f, g: Obsolescence notices and updating of the manifests and download packages should be carried out, just as for d061001c. | ||
2007-08-16 | d061001c: An obsolescence notice and the breaking changes needs to be added. The manifest should reflect that also, and we should make the proper form of Zip for any download. We will then delete the Practical100 forms from the hosted-site, never to be reachable again. | ||
2007-08-15 | d061001a: Split off completed items before 2007-08 into a diary archive page so this page is easier to handle and to review (see 2006-12-20 work item too). | ||
2007-03-02 | d061001g: Consider permalinking at the paragraph level | ||
2007-03-02 | d061001g: Add a synopsis and table of content | ||
2007-02-21 | d061001f: Ensure that the changes to 0.30alpha are reflected in the deployment releases that introduced them. Also make sure that the continuing reliance on the 0.30alpha package is reflected in the deployment packages. | ||
2007-02-21 | d061201e: That deployment page should have its notes updated to reflect the change to practical100 for the 0.30alpha deployment. | ||
2006-12-20 | d061001a: Move all of the completed items in 0.03 to an archive page so this page is easier to handle and contains only the still-open items. | ||
2006-12-18 | Now that openKnownDocument() has different null behavior than chooseDocument(), that result should also be checked in Null01, when it is expanded to provide aggressive checking. | ||
2006-12-17 |
OdmNullConnection 0.40alpha: reduce the OdmNullConnection
constructor from public to |
||
2006-12-14 | The Guide may deserve a set of state diagrams or other kind of transition diagrams that characterize the key behaviors and the moves that can be made, the results that are possible. | ||
2006-12-14 | We need to identify the simple, document-file content document model that practical100 is designed to support, pointing out that there are other document models and practical100 does not provide anything specific for them. [dh:2007-01-10 There are hints about this in some of the comments, but it needs to be made clear in the Guide.] | ||
2006-12-12 | OdmDocument: It may be desirable to have the DMS ID and the DMS Description available to the application for possible display to the user in providing an account of ODMA-aware behaviors. Resolve this for 0.50beta at the latest. [dh:2007-11-18 This only works for an actual document, not a null implementation, because we don't have any provision for internationalization. It is worth considering whether OdmNative100 can supply at least the DMS Description from the registry. When it can do that, depending on the Connection Manager version, it can also provide the DMS ID. | ||
2006-12-12 | At some point, substitute JavaDoc commentary and produce the JavaDocs for these interfaces. | ||
2006-12-10 |
d061001f: |
||
2006-12-10 | Tombstone the practical100.txt and Practical100-0.01alpha.zip files. These do not have to be carried over when the embargo is lifted. (That is handled by deleting them from ODMdevCompagno after the tombstones are posted. | ||
2006-12-10 | Rename the practical100.txt and Practical100-0.01alpha.zip packages to conform to the overall scheme. | ||
2006-12-01 | d061001f: There needs to be a Null01.java that works the null cases. That is, for every null situation, it tests the consequences for all other situations. Where there is not a null response, it does not exercise resulting non-null behaviors, but it will following a reset. [dh:2006-12-11 This is hinted in the 0.02 Pre-Release Notes. I need to take this farther.][dh:2007-01-10 The Pre-Release notes are adjusted about this, but it is apparent that Null01 should turn into the right kind of fella.] | ||
2006-10-25 | d061001: Introduce an attribution block on the folio cover. There is the interesting matter of references to the page itself and to the overall folio. This will be an interesting challenge. | ||
2006-10-25 | The insights that arose around the creation of the 0.05alpha version of the components are important to capture. | ||
2006-10-25 | d061001a: Review the code for items that should be tracked here as potential work items. | ||
2006-10-25 | d061001d: It would be useful to have a section that explains what can be done with this a little better. | ||
2006-10-25 | d061001d: Consider Permalinking the bullet list with subsection numbers. | ||
2006-10-19 | Switch to using the kind of manifest that is preferred for packages of this type. [dh:2006-10-20 This is needed when the embargo is lifted. It doesn't have to be done before that. That way I don't have to put in cross-references to the embargo area.] | ||
2006-10-19 | When the embargo is lifted, all references to the project pages must be corrected. This is a painful problem. Maybe everything we need to cross-reference about ODMJNI should be kept under devNotes and any cross-referencing to external embargoed material should be via an external link/bibliography page that can be updated as the embargo is lifted. That is occasion for another folio. [dh:2006-12-10 the other folio would be just to provide a directory/bibliography of related material that can be used to find the greater details at appropriate locations.] | ||
done 2007-11-21 |
2007-11-18 | d061001h: Complete section 4.6, the practical100 packaging, when the archive is put together and I am resolved around regression sets and the test subtree. | |
done 2007-11-21 |
2007-11-18 | d061001h.txt Create a manifest after the test code is dealt with. | |
done 2007-11-19 |
2007-11-18 | d061001h: Decide what to do about the test code. It looks like the regression code should be in the package. It also looks like the test tree should be there too, since that is how it is ever modified. The redundancy does not make a lot of sense though. I need to include this in the package now and I can remove it later if redundancy with the deployment packaging is important to eliminate. We'll see how I like it that way. I keep thinking test is part of the development tree, and the regression material should be separate. Whether the regression material is also replicated will be dealt with at the time. [dh:2007-11-19 The archive of the regression set is included in the code tree but its home base is d071001d, where it will be developed further after 0.59 is wrapped up. | |
done 2007-11-19 |
2007-11-18 | d061001h: Complete the Release Notes | |
done 2007-11-19 |
2007-10-03 | d061001h: The 0.30-regression is interesting in that it can be used against the deployment package as well. This raises the interesting question about where this test should be as a regression unit-test as opposed to a full build test. [dh:2007-10-13 Because practical100 is bundled for independent use, it must carry its regressions. The OdmPackage100 flavor might be a shared version of the same folder. It would make sense to do that. There is some naming and related work that is needed so that the running of the checks defaults properly for use under OdmPackage100.][dh:2007-11-19 I resolved this by putting the regression sets under d071001: ODMJNI 1.0 Confirmation Tests. There are additional adjustments needed to make it go smoothly] | |
done 2007-11-19 |
2007-10-03 | d061001h: Document the 0.30-regression with its own release notes, instructions, etc. [dh:2007-11-19 This is done in a separate d071001d-0.30-practical100.zip that is included in the practical100 development tree and also available at d071001d.htm. | |
done | 2007-11-18 | d061001h: Clean up the regression set and the Null01 check code. Clean up the results. | |
done 2007-11-18 |
2007-10-13 | d061001h: Alter the shared RunNull01.bat script to default properly and to work as a unit test properly. Do we need two scripts to have the cases all work? [dh:2007-11-18 It looks like the scheme for controlling the path is good enough.] | |
done 2007-11-18 |
2007-09-23 | d061001h: Add a caveat about OdmViewingDocument.transferToNewDocument. [dh:2007-11-18 I think this is about the format name not being acceptable to ODMJNI even though it is the format provided for the document being viewed. I don't know what we can do about that. Also, I don't think we want spaces in file extensions. This could be messy. | |
done | 2007-11-18 | d061001h: Expand the TOC to include the caveats subtitles | |
done | 2007-11-18 | d061001h: Complete the caveats section | |
done | 2007-11-18 | d061001h: Customize a license for this package | |
done | 2007-11-18 | d061001h: Add developer note about the transferToNewDocument concerns. | |
done | 2007-11-18 | d061001h: Derive a synopsis based on the d070701d. | |
done | 2007-11-13 | d061001h: Update to reflect completion of all known changes to practical100, along with corresponding ReleaseNotes draft. | |
done 2007-11-06 |
2007-10-30 | d061001h-ReleaseNotes: Use the start/stop of draft markers from d061101o-ReleaseNotes to clarify where there are new changes and where there is old material. | |
done | 2007-10-30 | d061001h: Put section 3.2 in the Contents | |
done 0.08 | 2007-10-16 | d061101h: Update with results from removing the OdmError exceptions for ill-formed string-valued parameters. A number of other observations and adjustments were made while making this relatively-simple change. | |
revised 2007-10-13 done 2007-08-19 |
2007-08-15 |
|
|
2007-10-13 | 2007-10-01 | d061001: Repave the anchor blocks to satisfy the style requirements of the repaving project. Elevate to the construction zone over devNotes: d061001, d061001a, d061001c, d061001d, d061001e, d061001f, d061001g, d061001h. When done this moves the repaving notice, below. | |
done 0.07 2007-10-13 |
2007-10-03 | d061101h: Review the BuildNull01 and RunNull01 batch files and customize for the 0.30-regression set. I need to decide whether to even include BuildNull01. I might rename the extension so that it can't be used without intentionally performing the build elsewhere. Discuss. [dh:2007-10-08 I think the source code and the build script can go into a Zip file that is in the folder with the runable test. The RunNull01 script works perfection without change.][dh:2007-10-13: The Null01-source.zip file holds all source code and the BuildNull01.bat script. It also holds the other "sources" for the prompted-IO, etc. | |
done 0.06 | 2007-10-10 | d061101h: Update to reflect the creation of the seed 0.59/0.60 regression set. | |
done 0.05 | 2007-10-09 | d061101h: Rename the regression sets and capture notes on what I want to accomplish around that and the questions that I am still mulling over. | |
done 0.04 | 2007-10-08 | d061101h: Update to reflect completion of the pre-0.59 regression capture and successful execution. | |
done 0.03 | 2007-10-04 | d061101h: Include recognition that we will zigzag through the two packages, evolving changes and their regressions. This might need to be rolled up to d070701d too. Update the catalog, etc. | |
done 0.02 | 2007-10-03 | Update the catalog to reflect the changes and publish the material to the site. | |
done 0.02 | 2007-10-03 | d061001h: Create the 0.30-regression material containing an independent branch of Null01 except for the shared Prompted-IO code. | |
done 0.01 2007-10-01 |
2007-09-23 | d061001h: Bring over the development progression from the 0.59beta progression definition of 09-20. | |
done 2007-09-23 |
2007-08-19 | d061001h: Start the 0.59beta page with a placeholder that is tied into the material but not yet made the latest. [dh:2007-08-19 See the 2007-08-15 note too.] | |
done 2007-09-23 |
2007-08-15 | d061001h: Create placeholder for 0.59beta preparation and the main changes | |
done | 2007-09-23 | d061001: Reflect update in the catalog table | |
done | 2007-09-23 | d061001h: Share file with hosted-site image | |
done 0.11 | 2007-09-23 | d061001g: Link to d061001h as its successor | |
done 0.06 | 2007-09-23 | d061001: Add d061001h to the list of available materials (although it is not the latest yet) | |
done 0.00 | 2007-09-23 | d061001h: Create a placeholder page for the 0.59beta candidate transition. | |
done | 2007-08-19 | d061001: Make sure that the hosted-site file names are the same as the development (FrontPage) names, and clear out the hosted-site image if necessary. | |
done 2007-08-19 |
2007-03-02 | d061001g: Go over the article and introduce monospace wherever appropriate | |
done 2007-08-19 |
2006-12-10 | d061001e: Review to make sure that monospacing is applied where required, and that the same style is used in each place. | |
done 2007-08-19 |
2006-12-10 | d061001f: As the pre-release actions become reality, reorganize the page so that ultimately the basic state is in the summary and the historical information is in later sections, with the most-historical closest to the end of the page. [dh:2007-08-19 This was also done earlier but not noted at the time.] | |
done 2007-08-19 |
2006-10-20 | The adjustment to lower-case accession-group letters needs to be made in the public archive and catalog no later than when the embargo on this material is lifted. [dh:2007-08-19 This seems to have been done earlier, but I forgot to note it.] | |
done 2007-08-19 |
2007-08-15 | Review all folio pages for conformance to the repaved Construction Structure and case sensitivity: d061001, d061001a, d061001b, d061001c, d061001d, d061001e, d061001f, d061001g | |
done | 2007-08-19 | d061001: Provide forward links for emphatic obsolescence statements: d061001c, d061001d, d061001e, d061001f | |
done | 2007-08-19 | d061001e: Review the manifest and license pages for accurate case-sensitive information. | |
done 2007-08-16 |
2006-10-20 |
d061001c: Link to the Guide document when it is reachable
on-line, possibly |
|
done | 2007-08-01 | Reviewed for consistency with "Java-ODMA Integration Kit" | |
done 0.07 | 2007-03-07 | d061001g: Correct package to 0.03 and update the page again. | |
done 0.07 | 2007-03-07 | d061001g: Reflect all changes in the narrative documentation and in the developer notes. | |
done 0.02 | 2007-03-07 | d061001g: Update the archive and manifest to 0.02 for correct OdmFormat.java version and the correct .class files. | |
done 0.02 2007-03-07 |
2007-03-06 | d061001g.txt 0.01 has an unbroken line in the summary information at the top | |
done | 2007-03-06 | index.htm: Reflect the 0.56beta update in the embargo catalog | |
done 0.06 | 2007-03-06 | d061001g: Update to reflect the revision of 0.56beta in anticipation of 0.57beta | |
done | 2007-03-04 | Update the embargo catalog to reflect release of 0.56beta | |
done | 2007-03-04 | d061001: Review for any changes along with making 0.56beta the latest [dh:2007-03-04 no changes needed] | |
done 0.11 | 2007-03-04 | d061001f: Review to reflect release of 0.56beta | |
done | 2007-03-04 | d061001b: Make d061001g the current version | |
done 0.02 2007-03-03 |
2007-03-02 | d061001g: Update the Release Notes to reflect the filters finally built | |
done | 2007-03-02 | d061001g: Recover from a crash that lost new content to d061001g earlier today. | |
done 2007-02-24 |
2007-02-21 | d061001g: Create a work-item list of steps to completion of this drop. | |
done 0.02 | 2007-02-24 | d061001g: Add Development Approach on how the initial confirmations will be carried out in iteration with the replacement of null implementations by the actual filters. | |
done 0.01 2007-02-23 |
2007-02-21 | d061001g: Create a ReleaseNote that describes the additions to the APIs and the behaviors. | |
done 0.00 | 2007-02-23 | d061001g: Customize a license.txt file for the 0.56beta package(s). | |
done 0.07 | 2007-02-22 | d061001e: Correct the link forward to d061001f | |
done 0.10 | 2007-02-22 | d061001f: Actually link to the manifest | |
done 0.10 2007-02-22 |
2007-02-21 |
d061001f: Make a version that reflects the changes that
came up in the 0.30alpha, 0.50beta and 0.52beta releases. Link to
the drops and link back from those drops. |
|
done 2007-02-22 |
2007-02-21 | d061001f: Complete the Manifest (d061001f.txt) and make sure it is added to the archive. | |
done 2007-02-22 |
2007-02-21 | d061001f: Make sure license is current and added to the .zip archive | |
done 2007-02-22 |
2007-02-21 | d061001f: Add PreReleaseNotes to the .zip archive | |
done 0.06 | 2007-02-22 | d061001f-PreReleaseNotes Clean up line breaks and the attribution version | |
done 0.05 2007-02-22 |
2007-02-21 | d061001f-PreReleaseNotes.txt: Section 1.5 is incorrect. The null behavior is to return a null Working Document, as expected. OdmError is thrown only for an invalid format of the given ODMA Document ID. | |
done | 2007-02-21 | index.htm: Reflect these updates in the embargo catalog. | |
done | 2007-02-21 | d061001: Add d061001h to the available materials | |
done | 2007-02-21 | d061001b: Use d061001f as the latest, until 0.56beta is deployed. | |
done | 2007-02-21 | d061001g: Create a placeholder for the 0.56beta release. This will be the implementation of checks and other lingering things (another NullBind.application method, for example). | |
done | 2007-02-21 | d061001f: Review all deployments after 0.25alpha to capture any further changes that were made to the 0.30alpha package. | |
done | 2007-01-10 | Post updated Pre-Release notes for linking here and from the 0.30alpha deployment page. | |
done 2007-01-10 |
2006-12-16 | Add the OdmFormat class (and see if it needs to be renamed in the Pre-Release Notes). [dh:2007-08-19 This was done and not noted until now.] | |
done 2007-01-10 |
2006-12-17 | Pre-Release Notes: Add the throws cases to the documentation of new and changed methods. | |
done 2007-01-10 |
2006-12-17 | Pre-Release Notes: section 3.3 on OdmError must reflect use for erroneous calls on document-manipulation operations in null documents. | |
closed 2007-01-10 |
2006-12-15 |
OdmWorkingDocument: Add note on commitChanges that
explains why a new document is not delivered and an update is produced
instead. |
|
done 2007-01-10 |
2006-12-14 | Pre-Release Notes: Report the change in null case for openKnownDocument() as a breaking change. | |
done 2007-01-10 |
2006-12-14 | Pre-Release Notes: Identify the commitChanges() function as a new addition to an existing class. | |
done 2007-01-10 |
2006-12-14 | Pre-Release Notes: Identify the commitContent() function as a new addition to an existing class. | |
done 2007-01-10 |
2006-12-13 |
0.30alpha Pre-Release Notes: Add |
|
done 2007-01-10 |
2006-12-13 |
Pre-Release Notes: Add |
|
done 2007-01-10 |
2006-12-13 | 0.30alpha Pre-Release Notes: Add dmsFormatName to the list of new ViewingDocument methods. | |
done 2007-01-10 |
2006-12-13 | 0.30alpha Pre-Release Notes: change bool to boolean in the first paragraph of section 4.1 | |
done 2006-12-20 |
2006-12-10 | d061001f: We need to do an 0.25alpha build that confirms the updates to practical100, also serving as a regression. This will also allow adjustment for the breaking changes when we are satisfied that practical100 is stable for at least 0.30alpha. This is probably done as an odmjni100 drop, but I am not sure about that at this point. [dh:2006-12-11 I am sure. This is how it will be done.] | |
done 0.03 | 2006-12-20 | Update this version as complete to the 0.25alpha level and refresh the embargo folder with content to date. | |
already done | 2006-12-20 | d061001: Update the front page to link in this preview, if needed. | |
already done | 2006-12-20 | d061001e: Forward link to d061001f if needed. | |
done 0.08 | 2006-12-20 | d061001f: Update to link to the sequestered material. | |
done | 2006-12-20 | Sequester a version of the 0.30alpha practical100 tree as it exists for the 0.25alpha build of odmjni100. | |
done | 2006-12-18 | The odmjni100 OdmApp will need to be reviewed to work with the new OdmNullConnection base class. There should be no difficulty rebuilding and rerunning Check03 over there. | |
done | 2006-12-18 | Rerun Null01 with these changes. It should not make any difference. | |
done | 2006-12-18 | OdmNullConnection find all of the returns of null implementations in OdmConnection methods and have them work through the protected final interface pointer in the class. Documents that can return null implementations will be given the interface upon their construction. | |
done | 2006-12-18 | OdmNullConnection add a final OdmNull reference and initialize it in the OdmNullConnection constructor. | |
done | 2006-12-18 | OdmNullConnection: Factor out the nullPending and nullWorking methods and the cache into a separate implementation class and interface that can be shared with non-null Document implementations. | |
done | 2006-12-18 | OdmNullCache is the class. Derive that from the definitions in OdmNullConnection. | |
done | 2006-12-18 | OdmNull is the interface. Derive that from the definitions in OdmNullConnection. | |
done | 2006-12-18 | OdmError: Make class and constructor pubic for use by odmjni100 classes. | |
done 2006-12-18 |
2006-12-12 | OdmConnection: The acceptNewDocument operation must have the docFormatName parameter checked for conformance to the format requirements of ODMA Document Format Names. | |
done 2006-12-18 |
2006-12-12 | OdmConnection: The openKnownDocument must have its docID parameter checked for conformance to the format requirements of an ODMA Document ID. | |
done | 2006-12-17 | Get Clean run of Null01 | |
done | 2006-12-17 | I erased all of the classes before a build and found that there were mis-compiled classes that were thought to be current, which is why the OdmNullPendingDocument constructor was not found. That was enough to get the regression to work after fixing the items that were still incorrect. | |
done | 2006-12-17 | See if making OdmNullPendingDocument protected gets rid of the runtime problem in finding the constructor. [dh:2006-12-17 No, this had nothing to do with it.] | |
done | 2006-12-17 | See if making OdmNullDocument protected gets rid of runtime problem in finding the constructor of OdmNullPendingDocument(2). [dh:2006-12-17 No, this had nothing to do with it either.] | |
done | 2006-12-17 | Get Clean compile of Null01.java | |
done | 2006-12-17 | Customize Null01.java | |
done | 2006-12-17 | Customize RunNull01.bat | |
done | 2006-12-17 | Customize BuildNull01.bat | |
done | 2006-12-17 | Create test\Null01 and clone Null00 into it for initial modification. | |
done | 2006-12-17 | Get a clean compile of the 0.30alpha interfaces and null implementations. | |
done | 2006-12-17 | Update the BuildClasses.bat. | |
done 2006-12-17 |
2006-12-16 | Add OdmNullBind.application for the recommended approach to instantiation of connections. Build this. It should give us everything we need automatically in making a clean compile. | |
done | 2006-12-17 | OdmNullWorkingDocument: Use the new constructor and throw an unchecked exception when commitChanges is attempted. | |
done 2006-12-17 |
2006-12-13 |
Add |
|
done 2006-12-17 |
2006-12-14 | After looking at how commitContent works, it may be necessary to reword the description of the OdmDocument methods with regard to the operation those items apply to. [dh:2006-12-17 This applies to the changed null forms too.] | |
done 2006-12-17 |
2006-12-16 | Customize OdmNullWorkingDocument for 0.30alpha [dh:2006-12-17 and correcting the handling of null-on-null with inclusion of unchecked OdmError exceptions. | |
done | 2006-12-17 | OdmNullPendingDocument: Correct the design to use new constructor and to throw an unchecked exception when commitContent is attempted. | |
done | 2006-12-17 | Review OdmNullDocument for changes that may apply for the repaired state-transition and null-document model. | |
done | 2006-12-17 | OdmNullConnection: Correct the design of null behavior documents and their constructors | |
done | 2006-12-17 | OdmWorkingDocument: Add information on the impact of release with regard to the document location. | |
done | 2006-12-17 | OdmWorkingDocument: Review and make sure the null commitChanges is described properly. | |
done | 2006-12-17 | OdmViewingDocument: Review and make sure the null Accept behaviors are described properly. | |
done 2006-12-17 |
2006-12-15 | OdmViewingDocument: emphasize that the various values can change after any content changes are committed to the DMS. | |
done | 2006-12-17 | OdmViewingDocument: Adjust null behavior, failure modes, and release/change consequences to reflect the 0.30alpha state-transition behavior. | |
done | 2006-12-17 | OdmPendingDocument: Add information on the impact of release with regard to the document location. | |
done | 2006-12-17 | OdmPendingDocument: Review and make sure the null commitContent is described properly. | |
done | 2006-12-17 | OdmDocument: Add information on the release behavior that is important to understand with regard to any uncommitted material. [dh:2006-12-17 This is minor at the OdmDocument level. The critical discussion is with the OdmPending and OdmWorking document behavior.] | |
done | 2006-12-17 | OdmDocument: Review and make sure the null behaviors are described properly. Add throws clauses where needed. | |
done | 2006-12-17 | OdmInterface and OdmConnection: Review to make sure they are neutral about the exception-throwing cases of null OdmDocument implementations. Add throws OdmError clauses where those are applicable. | |
done 2006-12-17 |
2006-12-16 | OdmError: Add the Exception class so it is available once we are ready to use it. [dh:2006-12-17 It is needed now for the erroneous use of null behaviors in document implementations from unsuccessful operations.] | |
done | 2006-12-16 | OdmInterface: Correct name of "available()" and clean up some of the comments. | |
done 2006-12-16 |
2006-12-12 | OdmInterface.interfaceImplementation() needs some sort of conventions and documentation at some point. [dh:2006-12-16 Added a FIXME to that effect and let it go for now.] | |
done 2006-12-16 |
2006-12-12 | OdmNullConnection: deliver an OdmWorkingDocument with failure status from openKnownDocument. | |
done | 2006-12-16 | Customize OdmNullPendingDocument for 0.30alpha | |
done | 2006-12-16 | OdmNullDocument: Customize for 0.30alpha behavior. This provides for all of the flavors of null behaviors that can arise in ODMJNI null and non-null document cases. | |
done | 2006-12-16 | Customize OdmNullConnection for 0.30alpha | |
done 2006-12-14 |
2006-12-13 | OdmPendingDocument: Customize for 0.30beta | |
done 2006-12-14 |
2006-12-13 | OdmWorkingDocument: Customize for 0.30beta | |
done | 2006-12-14 | OdmViewingDocument: review the initial commentary for transferToNewDocument, and correct the name. | |
done 2006-12-13 |
2006-12-11 | d061001f: 0.02 Pre-Release Notes, 1st paragraph in section 7 needs a line break. | |
done | 2006-12-13 | OdmViewingDocument: Customize for 0.30beta | |
done | 2006-12-13 | OdmInterface.availableConnection(): Rename this to available() and clean it up in everything already upgraded for 0.30beta. | |
done | 2006-12-13 | Correct the Pre-Release Note to include the change to availableConnection. | |
done | 2006-12-12 | Branch OdmWorkingDocument.java to make OdmViewingDocument.java too. OdmWorkingDocument will now extend OdmViewingDocument. | |
done | 2006-12-12 | OdmDocument interface: specify failure as the null response for openKnownDocument. | |
done | 2006-12-12 | Review OdmDocument for 0.30alpha. | |
done 2006-12-12 |
2006-10-20 | d061001d: In the OdmConnection file, the description of connection available and dmsDefaultAvailable must make it clear that, if there is no need for the connection in this case, the application should release() the connection interface. | |
done | 2006-12-12 | Review OdmConnection for consistency with the 0.30alpha release. | |
done 2006-12-12 |
2006-12-11 | d061001f: Make the changes to interfaces noticed on #56.53 | |
done | 2006-12-12 | Review OdmInterface for any 0.30beta changes. [dh:2006-12-12 Yes, it need to be checked in from the current tree and the headers and footers need tidying up.] | |
done | 2006-12-12 | d061001f: Make a version of the license that applies to this package. | |
done | 2006-12-12 | d061001f: Clone the d061001e Manifest for customization as the 0.30alpha Manifest | |
done 2006-12-11 |
2006-12-10 |
d061001e: connect to the d061001f page in the version
progression block, but leave |
|
done 2006-12-11 |
2006-12-10 | d061001f: Add the scenario changes that come with the 0.30alpha even though the behaviors come from odmjni100. [dh:2006-12-11 This is covered in the 0.02 Pre-Release Notes.] | |
done 2006-12-11 |
2006-12-10 | d061001f: Include breaking changes and how we intend to deal with them. Create a Pre-Release Note. | |
done | 2006-12-10 | d061001d.txt: Clean up and also reflect that d061001e is now the recommended version to use. | |
done | 2006-12-10 | d061001: Stitch d061001e and d061001f into the available material | |
done | 2006-12-10 | d061001f: Confirm existence of d061201d and also the title for that confirmation. | |
done | 2006-12-10 | d061001b: Make d061001e the latest version. | |
done | 2006-12-10 |
d061001d: connect to the d061001e |
|
done | 2006-12-10 | d061001e: There are no breaking changes. The only difference is modification of the development tree, use of OdmJava, and regression with Null00. Make that clear. | |
done | 2006-12-10 | d061001e: When the archive is in place, change the version progression description from found in to staged into with respect to 0.20alpha. | |
done 2006-12-10 |
2006-10-20 | Find the browser font style that lets keyboard format be shown at sizes that match the sizes of the surrounding non-keyboard text. [dh: It is by using the FrontPage font entry "Courier New (monospace)" that causes monospace to be used. I can also use font style="Courier New, Courier, Monospace" but monospace by itself may be sufficient, and it is certainly a lot easier.] | |
done | 2006-12-10 | d061001e: Add a license to the package and refer to it from the manifest. | |
done | 2006-12-10 | d061001e: Capture an archive before going further with development, since it will change the NuovoDoc version of the development tree. Get it onto the site in backup form at least. Then do the link to d061001e from d061001d. | |
done | 2006-12-10 | d061001f: Setup the page in anticipation of the 0.30alpha release. | |
done | 2006-12-10 | Correct the self-reference in the head title text for d061001d-f | |
done | 2006-12-01 | d061001e: Setup for the 0.20alpha version and the adjustments to line up with the other 0.20alpha materials. The interfaces will be updated to anticipate 0.30alpha and beyond. [dh:2006-12-10 This was basically the 0.05alpha material with a new test program and cleaned-up scripts and displays. The modifications of the API are deferred until staging for 0.30alpha.] | |
done | 2006-12-01 | d061001e: Modify Null00.java to operate with more like the SetupNN programs with the hierarchical layering of the exercise progression. | |
done 2006-12-01 |
2006-10-31 | The BuildTest.bat and RunTest.bat scripts need to not change directories from where we are operating. (#55.74 and see how this is handled on OdmNative use of scripts along with MyVC++ and MyPSDK). [dh:2006-12-01 we adopt the scheme already developed successfully for odmjni100, applying it in development of Null00] | |
done | 2006-12-01 | d061001e: Use BuildNull00 and RunNull00 scripts based on those used for odmjni100 test\setup02. | |
done | 2006-12-01 | d061001e: Move the test program from 0.05alpha to practical100\test\Null00 and rename the materials appropriately. | |
done | 2006-12-01 | d061001e: Repalce BuildAlpha by BuildClasses and customize it to simply build the classes in the same style as the current odmjni100 practice. | |
done | 2006-12-01 | d061001e: Create for holding the practical100 0.20alpha stage. | |
done 2006-12-01 |
2006-11-09 | We should change MyJava.bat to OdmJava.bat and put it up in info/odma/practical100. The one from odmjni100 might be shared, depending on whether there is more than OdmClasses to deal with - the Java directory for the JNI include files and such is one that we must also deal with. [dh:2006-12-01 I simply share the same one that is also used with odmjni100. The OdmJNI.bat is not needed for our work here, which is all pure Java.] | |
done | 2006-11-03 | Glean items from my notebook that should be carried in this job jar. | |
done | 2006-10-25 | There needs to be a job jar for the overall embargo section while more material is being developed there, prior to merging into the main branch of chronological material. | |
done | 2006-10-25 | d061001c, d061001d: Get the Harvard Style nonsense out of the attribution blocks. | |
done | 2006-10-25 | d061001: Check to make sure that current links to available material are correct. | |
done | 2006-10-25 | d061001d: Put page version in the attribution | |
done | 2006-10-25 | d061001d: Repair typos that are noted on notebook page #55.61. | |
done | 2006-10-25 | d061001d: The bullets under Developer Notes should use emphasis to call out the main point of each bullet. | |
done | 2006-10-25 | d061001d: The anchor block link is still to d061001c instead of the new d061001d. | |
done | 2006-10-25 | d061001c: Being obsoleted by d061001d should be emphasized | |
done | 2006-10-25 | d061001c: Put page version in the attribution and clean up text. | |
done 2006-10-24 |
2006-10-20 | d061001c: Update the page version before one is published with the summary and notes. Update the attribution to reflect the change in version. | |
done
0.05 2006-10-24 |
2006-10-20 | When d061001d is ready to publish, change d061001b to include it and update d061001c to refer to d061001d as its successor. | |
done
0.05 2006-10-23 |
2006-10-22 | d061001d: Build a minimal test program that exercises all methods of the OdmConnection interface and its derived interfaces | |
done
0.05 2006-10-23 |
2006-10-20 | Remember to make the visible interfaces visible for use by classes in different packages, such as test materials, that are not part of this package. (Tests and regressions should be at a different level in the package hierarchy.) | |
done
0.05 2006-10-22 |
2006-10-20 | d061001d: Resolve whether or not docLocation needs to be different for different cases, since the semantics is different. [dh:2006-10-22 I think so. I will think what the name needs to be.] | |
done
0.05 2006-10-22 |
2006-10-20 | d061001d: Consider adding dmsDefaultAvailable() to OdmInterface if not OdmConnection. This is needed to distinguish between having no default dms for chooseDocument and acceptNewDocument operations. The intention is to have openKnownDocument work (assuming that its DMS can be found independently.) | |
done
0.05 2006-10-22 |
2006-10-20 | Refactor the common status and generic operations to an OdmInterface common set that the other three will be derived from. [dh:20006-10-22 There's also an OdmDocument interface with common elements for OdmPendingDocument and OdmWorkingDocument] | |
done
0.05 2006-10-22 |
2006-10-20 | Add OdmPendingDocument interface for the new-document handover situation and to use the newer ideas about nomenclature. | |
done
0.05 2006-10-22 |
2006-10-20 | Rename Connection to OdmConnection to avoid possible confusion with names from other packages | |
done
0.05 2006-10-22 |
2006-10-20 | Rename Document to OdmWorkingDocument to avoid possible confusion with names from other packages and any confusion with OdmPendingDocument. | |
done
0.05 2006-10-22 |
2006-10-20 | Change close() to release() to avoid the idea of closing files, which has to happen other ways. | |
done | 2006-10-20 | d061001d: Make 0.05alpha and figure out the correct version as the modifications are made. [dh:2006-10-20 it is 0.05alpha by decree. The variable is content, not the version.] | |
done | 2006-10-20 | d061001c/d: Put the download information in the revision connection block. | |
done 2006-10-20 |
2006-10-19 | d061001d: Set to be using the conventional package naming, possibly with externally-visible identification too. | |
done | 2006-10-20 | Correct the links in the folio title to point back to d061001.htm: d061001a, d061001c, d061001d. | |
done | 2006-10-20 | Use lower-case "d" in the file names of this folio to avoid confusion in case-sensitive situations, such as on the Apache-implemented hosting site and various operating systems: d061001, d061001a, d061001b (head title), d061001c, d061001d. | |
done | 2006-10-20 | Adjust the embargo catalog to lower-case accession-group letters to match the actual file-system practice. | |
done | 2006-10-19 |
Change the embargoed-project page to now locate these
code drops at D061001b. Other material can be found from here as
cross-referencing kicks in. That cross-reference goes away
automatically when the embargo is lifted. [dh:2006-10-19 I used d061001c for now, after having trouble getting it right because of Apache case sensitivity.] |
|
done | 2006-10-19 | D061001c: Bring over the text file and have it available for examination before anyone downloads the Zip. Ultimately this is just for completeness of project history. | |
done | 2006-10-19 | D061001c: Bring over the package and use it just as named already. | |
done | 2006-10-19 | D061001c: Make simple version for holding the downloadable Zip file already used. | |
done | 2006-10-19 | D061001b: Link to D061001c and start using immediately as the anchor for the latest evolutionary step. | |
done | 2006-10-19 | D061001: Create minimal structure on the folio cover just as a way to find the immediately-available material | |
done | 2006-10-19 | Create this folio placeholder under embargo. The goal is to provide a place for the Zip packages and work up to providing an account of the progression and the latest material. |
![]() |
created 2006-10-19-20:36 -0700 (pdt) by
orcmid |