On 25 juin, 19:40, Stefan Bachert <[email protected]> wrote: > Hi Shedokan, > > I think this approach will fail. > > a) you can't give you code away. Because GWT needs the source. > b) to use GWT code as JavaScript-lib fails. GWT compiles only what is > needed. So how could you be sure, that ALL code comes in the > JavaScript? > c) ANd when you even achieve this, your JavaScript-Size is larger then > need becauses the GWT-App needs just 10%
Have a look at how GWT-Exporter is used with Timepedia's Chronoscope: http://timepedia.org/chronoscope/ You obviously download much unneeded code most of the time (depending on your use of the API), but at least you can code in Java/GWT and publish a re-usable JS-only lib. People using GWT will of course benefit from using the Chronoscope GWT code directly. @Shedokan: you should really give GWT-Exporter a try. It does what you'd be able to do in JSNI, but does it automagically based on annotations you put on your classes. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
