In addition to our effort to do our best documenting NHibernate there is
somebody else analyzing "the forest"
http://codebetter.com/blogs/patricksmacchia/archive/2008/08/26/nhibernate-2-0-changes-overview.aspx

<http://codebetter.com/blogs/patricksmacchia/archive/2008/08/26/nhibernate-2-0-changes-overview.aspx>For
NHibernate3 I have asked to Patrick Smacchia his new analysis... this time I
filter no-constructive comments by myself but for sure I will read the
others parts.

On Tue, Sep 28, 2010 at 4:05 PM, Oskar Berggren <[email protected]>wrote:

> Please Fabio, he was only asking politely. It seems unreasonable to
> demand proof that some other OSS project have documented their
> internals before you are allowed to ask if such information happens to
> exist for this project. Surely the usefulness of such documentation
> doesn't depend on some random other project having that kind of
> documentation?
>
> Reading source code is useful, and must ultimately be done to gain
> full understanding, but having a high-level map of the forest of
> details isn't worthless. IMHO.
>
> /Oskar
>
> Ps. I'm not suggesting that someone unpaid _must_ write such docs,
> unless they want to.
>
>
> 2010/9/28 Fabio Maulo <[email protected]>:
> > For example ?
> > Have you an example of the documentation you are looking for with a link
> to
> > those docs of another OSS project without a big business-monster behind
> it ?
> >
> > On Tue, Sep 28, 2010 at 2:05 PM, gwp <[email protected]> wrote:
> >>
> >> Hi, i would like to learn nhibernate internals, and therefore im
> >> trying to find some documentation for nhibernate source code. Most
> >> class contatin only briefly description, i would like see for example
> >> some diagram, some pattern usage , more technical infrormation.Of
> >> course i can read source code, but without proper information its very
> >> difficult task.  If anyone know if such docs exists? or documentation
> >> is only in source code and mailing list?
> >>
> >> thanks in advance.
> >
> >
> > --
> > Fabio Maulo
> >
> >
>



-- 
Fabio Maulo

Reply via email to