On Tue, Sep 1, 2015 at 2:01 PM, Christopher Sean Morrison <brl...@mac.com>
wrote:
>
> On Aug 30, 2015, at 8:37 AM, Tom Browder <tom.brow...@gmail.com> wrote:
>
>> Sean, I hope to get to that before too long, but I'm hard pressed at
>> the moment with prepping for my reunion. I don't remember having any
>> real spec, but I do have some notes. I have at least successfully
>> built head from a recent trunk revision but I have not attempted a
>> merge to my experimental branch yet.

Sean, I'm now ready back onto the binary attributes. I have a currently
building trunk, and have brought my attribute branch up-to-date. I have now
switched to my attr branch (attr-extension-mods) and get a good build.

I would like to move any unique attr code to the trunk (and delete the
branch). All new binary attr code is protected by ifdef guards
(USE_BINARY_ATTRIBUTES) so no effects should bleed into normal trunk
builds. The only new file so far is a README.binary_attributes in which I
am assembling some notes.  It currently resides in the top level directory
but I can put it anywhere you like.

I would appreciate some guidance on exactly what mged UI there should be
for the use of binary attributes as well as some examples of actual input
to be used. Also, should there be a separate man page for binary attributes
or include it in the existing one?

I would also like suggestions for where test code should reside (e.g.,
regress or a tests subdir).

Best regards,

-Tom
------------------------------------------------------------------------------
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel

Reply via email to