A good idea, although there is some added risk of broken links as source code gets moved around with new releases. Do you have any specific places in the documentation where you think a link to Tapestry's source code would be helpful?
On Mon, Oct 14, 2013 at 7:09 AM, Muhammad Gelbana <m.gelb...@gmail.com>wrote: > Opps ! Just hist a mysterious keyboard shortcut to send emails from GMail > !! > > Anyway, so the documentation page will discuss the subject thoroughly while > advanced users and source code explorers will have a better experience and > less time finding the relevant source code for the subject being discussed > in the documentation. > > What do you think ? > > *---------------------* > *Muhammad Gelbana* > http://www.linkedin.com/in/mgelbana > > > On Mon, Oct 14, 2013 at 1:07 PM, Muhammad Gelbana <m.gelb...@gmail.com > >wrote: > > > How about including references (links or embedded) to relative tapestry > > source code within a documentation page ? > > > > This could be even more informative than the documentation itself since > it > > has every detail, while the documentation only explains > > > > *---------------------* > > *Muhammad Gelbana* > > http://www.linkedin.com/in/mgelbana > > >
