Patteryfly 4.0.0 Alpha.2 Release
crosspost from: https://blog.patternfly.org/patternfly-4-0-0-alpha-2-release/
In the PatternFly Roadmap we outlined our future plans for PatternFly and laid out the goals for the PatternFly 4 release:
Providing initial support for Angular 2 application development
Updating the libraries on which Angular-Patternfly is built
Making the dependence on jQuery optional when consuming Angular-PatternFly
Today, we are excited to announce our first PatternFly 4 alpha release, PatternFly 4.0.0-alpha.2 (we had to skip 4.0.0-alpha.1 due to some known issues). This blog provides some highlights of the release, please check the release notes for PatternFly and Angular-PatternFly for further details.
Directive to component migration
The primary driver for the PatternFly 4 release is to enable Angular 2 development through the re-factor of our Angular 1.x directives into Angular 1.5+ components. These components can be used in a “downgraded” Angular 2 application. All directives have been converted to components, except the pfRemainingCharsCount, pfFocused, pfValidation, and pfFixedAccordion directives. We have provided a Angular 2 quickstart that can be used as a starting point for your own PatternFly Angular 2 applications.
With PatternFly 4, we’ve refactored our Angular modules to enable development of Angular-PatternFly applications without bringing in the jQuery dependency. To take advantage of this, include the patternfly-settings.js file from the PatternFly dependency, rather than patternfly.js. More details can be found in the associated Github Pull Request.
Table View Component
New common component work has landed in PatternFly 4 with the introduction of the Angular-PatternFly Table View component. The table view component leverages the angular-datables port of the datatables.net library we are using in PatternFly 4. It brings the highly requested table view pattern implementation to Angular. Check out the Angular-PatternFly docs for more details on using the table view in your Angular applications.
jQuery component split
We’ve refactored the monolithic patternfly.js file into a number of separate source files with this PatternFly 4 release. The goal was to better enable developers to locate functionality and contribute to PatternFly. The individual files are still packaged into a single file at build time, mimicking the PatternFly 3 distribution, as such there is no migration step required in this regard for your applications.
Ruby now optional for building PatternFly
We will follow up with additional PatternFly 4 alpha releases as we solidify our API and component changes. Once we are API stable and feature complete we will have a Beta release, followed by a final 4.0.0 release. We will continue with PatternFly 3 releases until PatternFly 4.0.0 is ready. After the 4.0.0 release, we do not plan to have anymore PatternFly 3 releases.
PatternFly 5 development has continued concurrent to the Patternfly 4 effort. We are planning a 5.0.0-alpha.1 release in the coming weeks. Stay tuned for blogs and announcements detailing what we’ve been up to with PatternFly 5.