[brlcad-commits] SF.net SVN: brlcad:[66712] brlcad/branches/binary-attributes/README. binary_attributes

[<tbr...@us...>]

Revision: 66712
          http://sourceforge.net/p/brlcad/code/66712
Author:   tbrowder2
Date:     2015-11-29 13:08:31 +0000 (Sun, 29 Nov 2015)
Log Message:
-----------
update tests section and BA representation info

Modified Paths:
--------------
    brlcad/branches/binary-attributes/README.binary_attributes

Modified: brlcad/branches/binary-attributes/README.binary_attributes
===================================================================
--- brlcad/branches/binary-attributes/README.binary_attributes	2015-11-28 02:40:20 UTC (rev 66711)
+++ brlcad/branches/binary-attributes/README.binary_attributes	2015-11-29 13:08:31 UTC (rev 66712)
@@ -89,6 +89,8 @@
   AVS BA to/from on-disk attribute body
     see current functions:
 
+  ...
+
 Macro definitions needed
 ------------------------
 
@@ -122,9 +124,10 @@
 On-disk format of a binary attribute [following the (char*)NULL
 (char*)NULL end of the normal attributes]:
 
-After more deliberation I believe we ought to create a separate object
-structure section for binary attributes.  Following is the existing
-Table 1. in the V5 database format manual:
+While I believe we can use the existing AVS attribute section for BAs,
+I believe in the future we ought to create a separate object structure
+section for binary attributes, especially if we use a more compact
+binary representation such as CBOR.
 
 The following describes the current V5 db:
 
@@ -135,14 +138,25 @@
   BRL_CAD_g_format_V6.xml
  
 
-Test plan:
+Possible tests:
 
-1. Select a complex TGM in the db directory as a test subject.
-2. Create a script to:
+1. Simple TGM
+   + create a single-object TGM
+   + copy the TGM to a new file (TGM2)
+   + add multiple binary attributes to TGM2
+   + add a file to TGM2
+   + use the admin-db tool to check TGM2
+   + export the file; check that it is the same as was imported
+   + delete the added binary attributes from TGM2
+   + run cmp on TGM and TGM2 to see they are the same
 
+2. Complex TGM
+   + select a complex TGM in the db directory as a test subject
    + copy the TGM to a new file (TGM2)
    + add multiple binary attributes to TGM2
+   + add a file to TGM2
    + use the admin-db tool to check TGM2
+   + export the file; check that it is the same as was imported
    + delete the added binary attributes from TGM2
    + run cmp on TGM and TGM2 to see they are the same
 

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.