Thanks for your response. I am contributing the mvp4g framework. The framework uses annotations for events, presenters views, etc and has not to deal with -ui.xml, -html, css -files. Everything is pure Java. I have rewritten the generators. Now they are using IncrementalGenerators. But, because, the framework rescans the whole application every time and then generates the code, SDM is not as fast as it could be. Thinking about your answer, I will think about changing mvp4g to use annotation processing. This could be a real speed up.
Am Freitag, 13. Februar 2015 16:12:50 UTC+1 schrieb Thomas Broyer: > > > > On Friday, February 13, 2015 at 12:15:42 PM UTC+1, Frank Hossfeld wrote: >> >> @Thomas: >> That sounds like GWT will use annotation processing instead of generators >> in the future. Is it a good idea to start writing annotation processors as >> an alternative for generators in new projects? >> > > If you ask for my (very personal) opinion, I'd say that if you can use an > annotation processor, then go ahead and do it. > I believe there are still good use-cases for GWT generators (for example, > annotation processors are not designed to have dependencies on non-Java > sources –such as ui.xml, gss or properties files–, and GWT generators are > run once per permutation and can generate code specific to that > permutation; choosing the right code-path for a given permutation when > generating code through an annotation processor wouldn't be as easy). On > the other hand GWT generators require you to fully manage your inputs and > outputs if you want to take full advantage of incremental builds and not > slow down SDM. > > >> >> Am Donnerstag, 22. Januar 2015 00:20:03 UTC+1 schrieb Thomas Broyer: >>> >>> GWT itself won't run annotation processors (yet), but if your IDE runs >>> them automatically on file save then it should work just as well as GWT >>> generators. >> >> -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/94350bad-31fb-42fc-a6bc-87fc42485531%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
