Hmm might be challenging since I rely on the APT APIs when turning the template into Java (check types, read template as resource, validate CSS selectors, ...). Overriding methods is just a small part of it.
I don't see why running the annotation processor is such a pain. Moving towards GWT 3.0 lots of new annotation processors should pop up. So for me it's more like finding a standard way of how to integrate them in the code-refresh browser-cycle. Am Mittwoch, 12. August 2015 17:31:52 UTC+2 schrieb Thomas Broyer: > > IMO, the appropriate way to deal with this is to have a separate tool turn > the template into Java, then have an annotation processor (if needed) tie > everything together (e.g. extend the generated code and > implementing/overriding a few methods, etc.) > > How to trigger the intermediate tool and whether this is manual or > automatic is currently left as an exercise for the user (build tool, IDE, > external file watcher, etc.) > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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 http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
