@Ivan Markov Please invest some time to SDBG, it's great tool, very convenient. Despite of Chrome dev.tools, I still prefer SDBG as more natural for java developer.
On Thursday, May 31, 2018 at 6:02:43 AM UTC-7, Ivan Markov wrote: > > Don't you think there could've been 2x or even 3x as much people working > on porting GWT2 stuff over to J2CL if J2CL was released in the first place? > For one, releasing J2CL could've made me reconsider how much time I invest > in my own SDBG pet project. Which - at the current situation is exactly > zero. Or whether to invest time in the abandoned typescript2java effort, > which would bring seamless JSInterop with gazillions of .d.ts'd JS > libraries without the need to manually code JSInterop bindings... > > Say what you want, but 3 months since my original rant that at the top of > this thread, the "basic Bazel building issues" of Goktug seem still to be a > roadblock and J2CL is still nowhere to be seen. > > ... and then we had Daniel planning to write a book on J2CL end of 2016, > remember? Come on guys, it is Q3 2018 now... I might now agree with Learner > Evermore on his points 2) to 5), but with point 1) he nailed it: > "1. The backing company backed off but kept the crucial new piece secret - > J2CL." > > > On Wednesday, May 30, 2018 at 6:07:25 PM UTC+3, Frank Hossfeld wrote: >> >> That's not really true. There are a lot of people working on the GWT >> module, getting them out of GWT and moving them to standalone artifacts. >> Doing that, they replace JSNI with JsInterop, replace generators, etc. This >> is all done, to get GWT 2 ready for GWT 3. And if you want to see something >> existing in GWT 3, you can ask vertispan to do the job. >> >> With the knowledge about the things, that will change with GWT 3 / J2CL, >> I was able to make mvp4g ready for GWT 3 / J2CL. I replaced the generator >> with APT and remove the dependency to any GWT classes. I created a sample >> application based on the new version (mvp4g2) and Elemental 2. And yes, it >> works with J2CL. >> >> And, keep in mind, applications written in GWT in 2010 still work. What >> was the favorite JS framework at that time? I don't remember. >> > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/9ce474a1-e4cd-4629-960e-5177c4693067%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
