Thanks Thomas! I appreciate your response.
I thought that JSNI could be implemented with beginControl("public native
void foo()/*-"); , but JavaWriter checks for open scopes. However I think
that JavaWriter is still a valid option for non JSNI code, and the API will
evolve to support more use cases.
- Andrés Testi
El viernes, 28 de febrero de 2014 11:07:59 UTC-3, Thomas Broyer escribió:
>
> JavaWriter has many small limitations, and in the case of GWT, the main
> one is that it's impossible to make it emit JSNI methods (other limitations
> include: annotations on method arguments, and generic/parameterized
> methods).
> It's a really great lib, but I believe it'll never support JSNI (I doubt
> Jesse/Jake would accept adding support for it; on the other hand, JSNI as
> we know it is about to disappear if I understood Goktug properly)
>
> On Thursday, February 27, 2014 4:06:46 PM UTC+1, Andrés Testi wrote:
>>
>> Hi contribs:
>>
>> Are you aware of Square's JavaWriter API? (
>> https://github.com/square/javawriter). It comes from the
>> Dagger/Guice/Guava team, and is widely used for code generation (Dagger,
>> AutoFactory and AutoValue
>> What do you think about introduce this dependency as replacement for
>> SourceWriter family in order to reduce GWT core and increase compatibility
>> with external tools?
>>
>> - 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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
