Today we're excited to share the next major version of Tyler Forge™ components! It has been a monumental effort, and we're extremely happy with where the final product ended up. This new version modernizes the library, and opens the door to many new possibilities for developers building applications with Forge. We're looking forward to seeing what you build with it!
As we near completion of development work on Forge 3.0, we wanted to give everyone a brief update about what this next major version is, what you can expect from it, and when you can start using it. We know many of you are eager to get your hands on it, and hopefully this post will help answer any questions you may have.
The split view component arrived with Forge 2.9.0 a few months ago, finally giving us a way to develop resizable layouts without relying on third party libraries. This is a powerful tool that's been a long time in the making. It also has the potential to be a little confusing to use up front. This post will be an introduction to the split view, showing how you can use it and some of the thought that went into its development.
How to upgrade applications & libraries from TCW (1.x) to Forge 2.x.
Welcome to the TCW/Forge upgrade guide! If you're looking for information about how to upgrade from TCW v1.x to Forge 2.0, you've come to the right place.
With the next generation version of Tyler Components Web (TCW) now being generally available, you probably have a lot of questions about how to upgrade, what is happening with the previous version, what has changed... etc. This guide is intended to walk you through the process of upgrading your applications and libraries, and answer all of the questions above and much more.
Yes, there are breaking changes that come with this upgrade, but we can assure you the process is not as daunting as it may seem.
Please let us know if you run into any problems that are not documented in this guide!
Let's get started!
In order to optimize Forge use, teams should avoid creating libraries from Forge components and should ensure that the components are kept up to date.
It's worth noting that this concept applies to any package that you want as a dependency of your library, but you want to allow for the consumer/dependent to control the version for compatibility with multiple versions of the library in question.