> Why GWT is designed that way, so hard to extend? Is that a reflection of a > desperate need for contributors to the project, by having to "fork the > whole thing"? Or is it to force the developers to use paid frameworks built > on top of GWT? > Why package-scoped classes? > Why private fields on classes that are supposed to be extended? >
Because it is generally a good practice to start as closed as possible and then open up APIs you feel comfortable with. As a library / toolkit / SDK you can not blindly make everything public because then you can never refactor that API as it would break lots of people who became dependent on these public APIs in the mean time. But you can always bring up specific cases on the gwt-contrib mailing list so it can be discussed and maybe its fine to open up the API a bit here and there. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
