Cool! Do you mind if I remove the TOC sample from the Deployment
section? I guess since at the end it will be generated by some kind
of macro, keeping a manual TOC piece doesn't buy us anything.
Andrus
On Mar 7, 2006, at 3:25 PM, Cris Daniluk wrote:
> The TOC isn't ready yet, but the docs themselves are in fairly good
> shape... there is no reason why you couldn't merge the 1.2 user guide
> in. Just don't link to the javadocs at this time :)
>
> Cris
>
> On 3/7/06, Andrus Adamchik <andru..bjectstyle.org> wrote:
>> Cris, Kevin --
>>
>> I just finished the first cut of the nested DataContext commit
>> functionality and wanted to make a release. I was wondering how close
>> are we to using CAYDOC Wiki space for release documentation. I recall
>> we had these unresolved issues:
>>
>> 1. Smart hyperlinking to JavaDocs (IMO we can ship the docs with this
>> not fully resolved),
>> 2. Table of Contents. We want it to be off for the PDF export and on
>> for the HTML. I guess we can go with PDF only option in M12 (and
>> temporarily remove sample ToC from the Deployment section)??
>> 3. ... anything else I am missing??
>>
>> An unrelated question. Cris, I was going to merge all stuff under
>> here:
>>
>> http://objectstyle.org/confluence/display/CAY/1.2+User+Guide
>>
>> to CAYDOC user guide. Wanted to check if this would interfere with
>> your work and whether I should hold it off for now.
>>
>> Andrus
>>
>
This archive was generated by hypermail 2.0.0 : Tue Mar 07 2006 - 07:46:26 EST