Good luck with things like Roassal or Seaside. As of Java, sure, but Javadoc is only a small part. Try to understand Swing with Javadocs and no thick book, good luck with that.
The Java Tutorial is another matter. Phil This email has been sent from a virus-free computer protected by Avast. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Sat, Mar 26, 2016 at 3:50 PM, Cyril Ferlicot D. <[email protected] > wrote: > Le 26/03/2016 09:19, stepharo a écrit : > > > > But you see you are becoming the most aware for athens > > and what we should do is document document. > > Now I got ****EXHAUSTED**** to document things that I did not build or > > use daily. This effort for me is gigantic > > and I cannot do it each time. > > In my opinion Pharo should refuse to include any class without at least > a one line documentation for the small classes. And when someone review > a bug correction and see that an important class have a really small > documentation it should be a stop for the integration. > > I never saw a Java class without documentation on oracle site. > > This will slow down the integration of some project, but since everyone > agree that pharo included too many project, this should not be a > problem. At least we would integrate only projects understandable by the > others. > > > -- > Cyril Ferlicot > > http://www.synectique.eu > > 165 Avenue Bretagne > Lille 59000 France > >
