I don't think you can solve this problem with static online documentation. Something as simple as what are the type coercers is not something you can document online since it's possible to add the dynamically. They only way to solve this is generate the documentation for the running system. This also has the benefit of documenting the version you are running. I think it's possible to do this an additional burden on the developers since Java already has standards (Javadoc) for this.
On Mon, Oct 14, 2013 at 3:48 PM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Mon, 14 Oct 2013 17:43:02 -0300, Muhammad Gelbana <m.gelb...@gmail.com> > wrote: > > I see your point Bob, It could be better the way it is. >> >> My point is if we different version of documentations for different >> versions of tapestry. Then we won't bother with broken source code links >> since each documentation version will statically refer to it's relevant >> source code. >> > > I'm sorry, Muhammad, but that would be hell to maintain. Imagine you wrote > a better description for something. Now you'd had to update at least for > documents for that. (5.1, 5.2, 5.3, 5.4). I'd give an automatic -1 vote on > that. We need to simplify stuff, not complicate them. People would probably > read documentation about the wrong version and not notice. In addition, in > Tapestry 5, things change in non-backward ways in a veeeeeeery slow pace. > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org> > For additional commands, e-mail: users-h...@tapestry.apache.org > >
