Question: can I use widgets in combination with Elemento/templating ? about elemento HOT 7 CLOSED

Using widgets w/ HTML template should work. Take a look at https://github.com/hal/elemento#data-elements. You'll need a field w/ an initialiser, something like

@Templated("MyApp.html#root")
abstract class MyApp implements IsElement {

    @DataElement MyWidget myWidget = new MyWidget();
}

if a field initialiser doesn't work, you can also use methods.

Regarding binding and validation, I recommend to take a look at Errai. I designed Elemento to be only a small toolkit around Elemental. If you want more, you'll have to switch ;-)

from elemento.

from elemento.

Yes I agree with @dnouls, Errai should be much smaller and simpler (without the need to use EE server - Wildfly 10+ ?) in order to be attractive. The last time I looked into it, there was no easy way to run it on the Tomcat. There are some info that this should be possible ("somehow", "somebody did it" and made a github project, but that did not working when I tried), and even then you have to bring so much (EE) jars that it's way too complex. I think it should be possible to drop the war on the Tomcat by default, and if you really need EE stuff than you should be able to use "EE Errai". Simply put: Errai should be "SE" by default and not "EE" by default.

from elemento.

Errai is best when you want to implement bigger enterprise SPAs. It has advanced features such as data synchronisation, annotations based validation or two way data binding. However it comes with some dependencies (one of them is WildFly, EE APIs).

I designed Elemento as an alternative in case you're just want to use GWT Elemental and support for simple HTML templates. However you have to implement or integrate all other goodies on your own.

from elemento.

I know that @hpehl, but still my personal opinion is that "JPA in the Browser", "CDI in the Browser" and other "EE" stuff should be optional. You don't need them for validation and data binding. That's what I think when I say it's over complex by default. Errai is great product, but EE features should not be mandatory, they should be optional. BTW your work (Elemento) is great as well ! I will probably use it in the future with my own validation, binding and other stuff on top of it.

from elemento.

Thanks.

Feel free to open a discussion at [1] or file an issue at [2]. Usually the Errai devs are open for improvements and ideas from the community.

[1] https://developer.jboss.org/en/errai?view=discussions
[2] https://issues.jboss.org/projects/ERRAI/summary

from elemento.

I close this issue, after discussions about the different frameworks and their main focus. Please reopen if you disagree.

from elemento.