The problem is not the javadocs but that one makes internals of a class API and has to live with it forever.
Tom Von meinem iPhone gesendet Am 02.09.2013 um 02:09 schrieb Pedro Duque Vieira <pedro.duquevie...@gmail.com>: > Hi, > > Sorry for sending in several emails to the mailing list at once. > > I'm having some issues while creating a custom chart - a XYBarChart, which > is a BarChart that can have both axis as ValueAxis. > > The main issue I'm having is that there are a lot of fields and methods > which are "package private" and I need to access them. > I see there is already another person in this mailing list that is also > having trouble extending some other part of the framework because of > "package private" fields/methods. > > Maybe there should be more inclination towards making things protected > rather than "package private". I can see the problem that this could > potentially flood the javadocs with methods and fields but I think that not > being able to extend some framework class is worse. > > Thanks, best regards, > > > -- > Pedro Duque Vieira
