On Wed, Oct 30, 2013 at 1:19 PM, Christopher Sean Morrison
wrote:
> What? You don't think
> http://svn.code.sf.net/p/brlcad/code/brlcad/trunk/src/librt/db5_types.c is a
> suitable WWW registry? ;)
...
> someone whip up a page on the wiki now?)
How about we do something like this for the main sit
BTW, the DB V5 doc repeatedly mentions a WWW registry of attribute key names. Isn't it time to have that clearly visible on the site? What? You don't think http://svn.code.sf.net/p/brlcad/code/brlcad/trunk/src/librt/db5_types.c is a suitable WWW registry? ;)(I agree. Maybe when we get to attribut
On Tue, Oct 29, 2013 at 4:32 PM, Tom Browder wrote:
> I think I understand now. How about something like this:
>
> As DB V5 goes now, there are two indicators for the end of the
> attribute block: two NULLs in a row AND total length
> (Attribute_Length). If we use the space AFTER the double NUL
On Tue, Oct 29, 2013 at 11:54 AM, Christopher Sean Morrison
wrote:
>
> This is actually pretty cool if it works as well as it claims:
> http://srackham.wordpress.com/blogpost-readme/
>
> Basically, it publishes Asciidoc documents to Wordpress and will do updates.
> With Pandoc converting Docbook t
On Tue, Oct 29, 2013 at 10:12 AM, Christopher Sean Morrison
wrote:
> On Oct 28, 2013, at 08:48 PM, Tom Browder wrote:
>
> I guess I need more on your ideas for binary attribute implementation.
>
> Is that more clear? Basically my idea was that we'd store the timestamps on
> objects directly as a
As a trial, I suggest someone convert the db5 spec to asciidoc (would be a good GCI task) since it's supposed to be faithful to Docbook (unlike markdown, it's a subset). It actually uses Docbook under the hood, so it should be a really good fit. Asciidoc has built-in support for editorial comment
On Oct 28, 2013, at 08:48 PM, Tom Browder wrote:Hm, I thought originally you thought that all attributes should get time stamps. I did, but I'm having trouble justifying the cost or imagining a value not already covered by just tracking timestamps per object.1. Are attributes to be time stamped? I
On Tue, Oct 29, 2013 at 7:13 AM, Tom Browder wrote:
...
I think converting the DB V5 into rst is very doable: no images, text
divided into sections, and mostly simple tables. I'll try the most
complex table and see how it looks in pdf and html.
Best,
-Tom
On Tue, Oct 29, 2013 at 7:09 AM, Tom Browder wrote:
> The co-ment site allows free use for public documents.
I just noticed this on the co-ment site:
Want your visitors to comment your text using co-ment while remaining
on your website? Paste on your site the piece of HTML code that is
provide
On Mon, Oct 28, 2013 at 8:16 PM, Clifford Yapp wrote:
> On Mon, Oct 28, 2013 at 8:48 PM, Tom Browder wrote:
>>
>>> We need some means to discuss and mark-up beyond comments in the xml.
>>> Suggestions? The spec used to exist as a word doc with reviewer comments.
>>> Docbook is rather limited in
On Mon, Oct 28, 2013 at 8:48 PM, Tom Browder wrote:
>
>> We need some means to discuss and mark-up beyond comments in the xml.
>> Suggestions? The spec used to exist as a word doc with reviewer comments.
>> Docbook is rather limited in that capacity.
>
> For sure. I guess we could put it back in
On Mon, Oct 28, 2013 at 11:53 AM, Christopher Sean Morrison
wrote:
>
> On Oct 28, 2013, at 6:53 AM, Tom Browder wrote:
>
>> (Note that I I think it is better not to mix
>> time stamps with attributes.)
>
> Not sure I understand this. If you're saying that we should not time stamp
> attributes th
On Oct 28, 2013, at 6:53 AM, Tom Browder wrote:
> (Note that I I think it is better not to mix
> time stamps with attributes.)
Not sure I understand this. If you're saying that we should not time stamp
attributes themselves, I agree. If you're saying we should not store time
stamps as attrib
On Thu, Aug 29, 2013 at 8:07 PM, Christopher Sean Morrison
wrote:
...
> Sounds quite reasonable to me. It fits the object data model best (as it is
> metadata) to store them in the database record as a set of attributes,
> ideally as binary int64 values but that's a problem we'll have to sort out
On Aug 29, 2013, at 4:48 PM, Tom Browder wrote:
> On Thu, Aug 29, 2013 at 3:23 PM, Christopher Sean Morrison
> wrote:
> On Aug 29, 2013, at 10:38 AM, Tom Browder wrote:
>> But it probably ought to be some kind of time struct (as you mentioned) on
>> the object itself. I'll look into that ins
On Thu, Aug 29, 2013 at 3:23 PM, Christopher Sean Morrison
wrote:
> On Aug 29, 2013, at 10:38 AM, Tom Browder wrote:
>
> But it probably ought to be some kind of time struct (as you mentioned) on
> the object itself. I'll look into that instead of the attribute route.
>
> I think it'll be a noti
On Aug 29, 2013, at 10:38 AM, Tom Browder wrote:On Thu, Aug 29, 2013 at 9:20 AM, Tom Browder wrote:On Wed, Aug 28, 2013 at 10:49 AM, Christopher Sean Morrison wrote:On Aug 28, 2013, at 11:29 AM, tbrowd...@users.sourceforge.net wrote:...Note that it'll also
On Thu, Aug 29, 2013 at 9:20 AM, Tom Browder wrote:
> On Wed, Aug 28, 2013 at 10:49 AM, Christopher Sean Morrison <
> brl...@mac.com> wrote:
>
>> On Aug 28, 2013, at 11:29 AM, tbrowd...@users.sourceforge.net wrote:
>>
> ...
>
>> Note that it'll also be highly desirable to timestamp all objects (
On Wed, Aug 28, 2013 at 10:49 AM, Christopher Sean Morrison
wrote:
> On Aug 28, 2013, at 11:29 AM, tbrowd...@users.sourceforge.net wrote:
>
...
> Note that it'll also be highly desirable to timestamp all objects (not
> just their attributes) ... and stash those timestamps as attributes. So
> thi
On Wed, Aug 28, 2013 at 10:49 AM, Christopher Sean Morrison
wrote:
> On Aug 28, 2013, at 11:29 AM, tbrowd...@users.sourceforge.net wrote:
>
> +#include >
>
> What time symbol is exposed in bu.h?
>
It no longer applies--I did have a time_t arg to bu_utctime for testing but
have removed it. (And
On Aug 28, 2013, at 11:29 AM, tbrowd...@users.sourceforge.net wrote:--- brlcad/trunk/include/bu.h 2013-08-28 14:24:01 UTC (rev 57223) +++ brlcad/trunk/include/bu.h 2013-08-28 15:29:09 UTC (rev 57224) @@ -86,6 +86,7 @@ #include #include +#include What time symbol is exposed in bu.h?+/* FIXME: st
21 matches
Mail list logo