> > Deprecating SourceWriter and replacing it with JavaWriter means > encouraging our users (and our own code-base) to move out of SourceWriter > to JavaWriter. > If we decide APT is the way to go then if someone is going to write > generator, it should be APT - in that case internally we may use JavaWriter > and externally they could use whatever they want (including the JavaWriter). > However, If the generator is already written, then it is a meaningless > effort to move out of SourceWriter. > All of these together there is very little value compared to the cost of > such move (including the annoyance caused by it). >
Deprecation doesn't implies removal. It could stay deprecated forever, discouraging people to use it for new developments. We don't have yet evidence that APT is able to cover all the Generator use cases. Anyway, as Thomas said, we should priorize modularization. - Andrés Testi -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
