Am I the only one that finds it strange that there aren't more people in the GWT community interested in creating JS libraries using GWT? It may seem counterintuitive, I don't know, but I really think one vector for expanding GWT use is by creating more building blocks that can be used by the greater web community.
You'd think there'd be lots more companies that have made management decisions to adopt JS that have cool Java libraries sitting around that their teams would like to expose for the next generation of apps. What's more likely, that a decent-sized company greenlights a breadwinner app being developed with GWT, or that it greenlights a team to create a library using GWT as long as it provides an JS API to play nice with the rest of the company's tech? Which brings me to a concern: that there is still no out-of-the-box support JS library creation in GWT and that we still have to rely on other tools (which are very helpful, thanks Ray Cromwell) or workarounds to achieve these goals. And of course at the end of the day the JS user is not going to care why some JS methods failed to be generated or why the JS docs weren't as complete as their javadoc counterparts, they are simply going to seek alternative solutions... So I'm wondering if there are people in the community that feel they've "perfected" the automated JS API & doc creation process for large maintainable libraries...another ease of use factor is being able to feed the generated JS library to IDEs like IntelliJ for javascript autocompletion, which is not normally possible due to the way the JS is generated in GWT. Could there be any workaround to this? -- 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/groups/opt_out.
