Re: [gwt-contrib] Re: The elusive J2CL

[Slava Pankov]

@Ivan Markov For some reason I cannot edit my previous message :-( Just 
want to clarify that I'm extremely grateful for your SDBG tool, it's 
beautiful software, and it's really sad to hear that you have some doubts 
about it.

On Monday, June 11, 2018 at 7:35:47 PM UTC-7, Slava Pankov wrote:
>
> @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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/4018719f-3680-49d9-8e43-a4f00e9024b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: The elusive J2CL

[Slava Pankov]

@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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
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.

Re: [gwt-contrib] Re: The elusive J2CL

['Goktug Gokdogan' via GWT Contributors]

J2CL is yet-to-be open-sourced Google product, I'll post a separate update
on the state but that's why it wasn't developed openly.

GWT, which is community owned; there is nothing done in secrecy and people
in the community actively working on GWT 3.

On Sun, Jun 10, 2018 at 3:58 AM Norbert Sándor 
wrote:

> > it would be nice to have J2CL released separately as soon as it is ready
>
> I still don't get why the development of J2CL / GWT 3 cannot be done
> openly like any other open source project.
> Why this secrecy is necessary.
>
> This kind of project management type is very unusual in case of open
> source projects
> It will make many people to stay away from the project and to switch to
> (even worse) alternatives :(
>
> --
> Norbi
>
> On Saturday, 9 June 2018 22:47:48 UTC+2, Ming-Yee Iu wrote:
>>
>> Wow! It's great to see all that progress being made on GWT 3. That's a
>> lot more backwards compatibility than I was expecting.
>>
>> Still, it would be nice to have J2CL released separately as soon as it is
>> ready to do so because
>>
>>1. Based on past experience, it will take 1-2 years or more before
>>GWT 3 is released
>>2. J2CL is useful independent of GWT 3. Just recently, I wanted to
>>package up some Java code as node.js NPM packages for others to use, but
>>doing that really requires something like J2CL instead of GWT
>>3. It's good to have some time for people to develop best practices
>>for how J2CL code can be mixed with JS. Google's JS code style is very
>>clean, well-typed, and Java-like, so it will naturally work well with 
>> J2CL.
>>Much real-world JS code is ugly and makes use of horrible JS corner cases
>>and hacks, so it might take a while to figure out best practices for how 
>> to
>>deal with those.
>>
>> --
> 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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/9516f69a-62cc-4eb9-86e6-aaeec3a09366%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA1r39Pm3UWvFRwkAfKS%3DjRFX_VM%2BJ%2B92CxTnpS6%3Dts0xg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.