In the end I went for both approaches [1]. In order to get the external
documentation I instrumented each of the samples with some data about what
it does, and then wrote a DocumentSamples java utility that extracts this
data from the programs. This has allowed me to produce an HTML document
Folks,
Having a central place with detailed descriptions of the samples in an
organized fashion is a great idea. But this has nothing to do with the
structuring on disk, in my opinion.
Some folks will read the detailed docs. Others will simply get the code
and start playing. For the
I just checked in another sample which I'd be happy to take feedback on --
[1] (output appended as in my previous posts)
I would like to rearrange the packages of the samples, as I think the
current arrangement is not very helpful to someone trying to explore SDO
(specCodeSnippets,
Kelvin,
As a user, I would like to see a general ample index file that briefly
explains what each sample does rather than the categorization that is
mentioned here since the terms basic, intermediate, etc. are not well
defined and are open to interpretation. Instead I would like to go to a
