This is a programmatic mapping from closure externs https://github.com/google/closure-compiler/tree/master/contrib/externs so, at the end if it changes it will change the same in every place, so fixing it should not be very difficult. Anyways, this super awesome project 😜 is going to expose a user-friendly and type safe API (manual work) over raw elemental2 https://github.com/hal/elemento (code example here https://github.com/ibaca/rxtodo-gwt/blob/master/src/main/java/todo/client/ApplicationElement.java#L53), IMO pretty promising! RxGWT will be using elemento typed events to make it also Rx typed events just over elemental2!
Code example here, this is always nice...
root = li().data(ITEM, item.id).css("completed", item.completed)
.add(div().css("view")
.add(toggle = input(checkbox).css("toggle").checked(item.completed).asElement())
.add(msg = label().textContent(item.text).asElement())
.add(destroy = button().css("destroy").asElement()))
.add(summary = input(text).css("edit").asElement())
.asElement();
bind(toggle, change, ev -> {
root.classList.toggle("completed", toggle.checked);
repository.complete(item, toggle.checked);
application.update();
});
All these fields are typed so, root is a HTMLLiElement, toggle is a HTMLInputElement or ev in the bind method is an InputEvent.
On Wed, Jun 7, 2017 at 10:14 PM Vassilis Virvilis <vasvir2@gmail.com> wrote:
Who knows?Or maybe this a bad idea that will lead to a new KDE4 fiasco.Something like this: We will try really hard to not rename all methods and move all packages around in the next week commits. However we may introduce incompatible changes as we are evolving the API. So no you can't use __this__ in __production__.thanks for the clarification.Maybe a sufficiently strong wording in the compatibility guarantees is enough.Vassilis--On Wed, Jun 7, 2017 at 10:14 PM, Daniel Kurka <kurka.daniel@gmail.com> wrote:There is some reasoning behind us not broadly announcing elemental2 and the jsinteorp generator:They are both still beta software in the sense that we know there are existing problems, but we already want feedback on them.There are still no guarantees on APIs / compat but if you are brave and want to be part of evolving them and turning them into a finished and polished product, you can do that.We will announce them broadly once we consider them ready for general use and have a compatibility guarantee in place.--On Wed, Jun 7, 2017 at 11:48 AM Vassilis Virvilis <vasvir2@gmail.com> wrote:VassilisAh yes that explains it. It was j2cl that I remembered.Thanks for the clarification.On Wed, Jun 7, 2017 at 9:40 PM, Colin Alworth <niloc132@gmail.com> wrote:I think you may be misremembering - the jars were released to maven as experimental last summer, then as beta in April, and only after that were they on github.
J2CL is not expected to be dropped until it is "ready", but as with elemental2, this isn't going to mean "bugfree" but more like "complete enough to be reviewed and used".
On Wednesday, June 7, 2017 at 1:10:37 PM UTC-5, Vassilis Virvilis wrote:Looks like they are also here in source formI thought google didn't want to release them before they were "ready". So either they changed their mind, or they feel it is ready or I don't remember correctly :-)VassilisOn Wed, Jun 7, 2017 at 7:17 PM, Colin Alworth <nilo...@gmail.com> wrote:The groupId has changed - using the mvnrepository site, try https://mvnrepository.com/artifact/com.google.elemental2 to see all of the jars now available.
On Wednesday, June 7, 2017 at 11:14:33 AM UTC-5, Bruno Salmon wrote:
Additionally, this supports the recent beta release of jsinterop.base and elemental2, available from Maven Central.
Where can we find that elemental2 beta release (I can see only the June 2016 version on that page)?Thanks for all your amazing work.--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
----Vassilis Virvilis
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
--Vassilis Virvilis
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment