I'll try to keep it short...
> When I’m trying to find out why my presentation layer DOM element didn’t
> receive some DOM attribute as result of computation, this is bug in the
> presentation layer, which was abstracted together with browser in your
> approach
>
Yes, you can assert/debug against
> This community needs more people *doing* stuff.
Agreed (although I'm calling the kettle black here).
I think historically GWT was really hard to contribute to; as you said, it
was a single toolkit, and had a lot of complexity in it (non-trivial
optimizations, non-trivial old browser support, et
>
>
> Thank you, GWT people, for spending your time answering my thoughts.
>
>
> To summarize (and TLDR), these were responses in the thread:
>
>
> Ivan Markov: We should improve javascript-side debugging to match DevMode.
>
> Jens: Google is busy doing other things, so no hope with gwtromium.
>
>
Thank you, GWT people, for spending your time answering my thoughts.
To summarize (and TLDR), these were responses in the thread:
Ivan Markov: We should improve javascript-side debugging to match DevMode.
Jens: Google is busy doing other things, so no hope with gwtromium.
Jens: Change your a
