Releases: hal/elemento
Elemento 1.0.7
Added
- Add dependabot
- License check
- Checkstyle rules
- Code format and import sorter
- Automate release process using GitHub actions
Changed
- Update documentation
- Update links to API documentation
- Move away from git flow
- Change default branch
develop
→main
- Adjust branch names in CONTRIBUTING.md
- Adjust URLs for distribution management
- Move samples to its own repository: https://github.com/hal/elemento-samples
Elemento 1.0.3
The only change is that the minimal Java version is now Java 1.8.
Elemento 1.0.2
Upgrades
- Upgrade gwt-safehtml to 1.0.0-RC1
Elemento 1.0.1
Upgrades
- Upgrade to Elemental2 1.1.0
- Downgrade minimal Java version to 1.8
Elemento 1.0.0
Elemento 1.0.0 introduces many breaking changes:
Naming
The maven coordinates, GWT module and the packages have changed.
Maven
Please use the following maven coordinates:
<dependency>
<groupId>org.jboss.elemento</groupId>
<artifactId>elemento-core</artifactId>
</dependency>
GWT module
Inherit this GWT module:
<module>
<inherits name="org.jboss.elemento.Core"/>
</module>
Packages
The packages have been flattened and renamed. All Elemento classes are now in the package org.jboss.elemento
.
J2CL / GWT3
Elemento works with both J2CL and GWT. No classes from com.google
are used. The only dependencies you'll need are:
com.google.elemental2:elemental2-core
version 1.1.0com.google.elemental2:elemental2-dom
version 1.1.0com.google.elemental2:elemental2-webstorage
version 1.1.0org.gwtproject.event:gwt-event
version 1.0.0-RC1 andorg.gwtproject.safehtml:gwt-safehtml
version 1.0.0-RC1
You can use Elemento with GWT 2.8, 2.9 or J2CL. See the samples for more details about how to setup your dependencies.
Templating
The templating part has been moved to crysknife. Crysknife is a CDI implementation for J2CL / GWT3. Crysknife already contains most of the templating code of Elemento, integrates nicely with CDI and offers some extra features like GSS support on top of that.
The motivation behind this is that we don't want to have two very similar and competing template solutions.
Deprecations
All classes and methods marked as @deprecated
have been removed:
Classes
org.jboss.gwt.elemento.core.Widgets
org.jboss.gwt.elemento.core.HasElements
Methods
org.jboss.gwt.elemento.core.builder.ElementsBuilder.get()
org.jboss.gwt.elemento.core.builder.ElementsBuilder.css(String, boolean)
org.jboss.gwt.elemento.core.builder.HtmlContent.addAll(HasElements)
org.jboss.gwt.elemento.core.LazyElement.asElement()
org.jboss.gwt.elemento.core.Elements.elements()
Backward Compatibility
Support for GWT widgets as defined by com.google.gwt:gwt-user
has been dropped. If you really need support for widgets, you have to stick with the latest 0.9.x-gwt2 version.
Elemento 0.9.6
Added
- New method to select multiple classnames
Fixed
- Fix endless loop for attachables
Removed
- Remove method to wrap a body element (there's only one body element)
Elemento 0.9.5
Added
Attachable
interface- Typesafe CSS selector API
- Wrap HTML elements as builders
- Generate unique IDs
- Overloaded methods for IsElement
Changed
- Unified API: All classes which represent an element implement
IsElement<E extends HTMLElement>
and have aE element()
method.
Elemento 0.9.3
Added
- PR #72: Add readOnly, disabled, required and placeholder methods in InputBuilder (thanks @alejandrocq)
Upgrades
- Fix #71: Upgrade npm dependencies for todomvc-app-css and todomvc-common (thanks @cristian-spiescu for reporting)
Elemento 0.9.2
Added
- Add methods to generate unique IDs
- Add search event type
Upgrades
- Upgrade to JUnit 5