We’re excited to announce the release of Sencha GXT 3.1 beta, available on our download page and from Maven Central. This latest release of GXT introduces Theme Builder, a new tool for theming GXT applications, as well as the Neptune theme built entirely with this tool, adds support for GWT 2.6, and fixes a variety of bugs reported by our users. We’d like to gather feedback from our community while we prepare for the general availability of GXT 3.1.
In this article, we’ll tell you how we used Sencha GXT at Datenwerke to build one of our products called ReportServer, an open source Business Intelligence platform. First, we’d like to share our vision of reporting and business intelligence, which has greatly influenced and continues to affect the development and design choices of our product.
From the attendees of SenchaCon 2013, and in the continuous feedback we receive from our GXT community, the single biggest question that we have been asked most number of times is, “What is the plan/roadmap for GXT?”. The feedback we have received from our customers has been overwhelming. Everyone wants more in the framework, especially a support for tablets. With this post, I am excited to reveal the roadmap we have put together for GXT. And yes, tablet support is coming!
Sencha Desktop Packager is a tool that enables you to wrap up your web applications and deliver them as native solutions. In this article, we’ll look at using it to package GWT applications. We will use three different sample applications — a simple hello world with native features, one based on the GXT Explorer, and one based on the Quake2 GWT Demo.
Logging can provide invaluable process information during and after development and while you’re debugging. It can be completely compiled out, or added back to assist you with debugging in production, and can be customized for your particular application to render exactly the details you need. In this article, you’ll learn about the three main logging mechanisms built into GWT.
Many developers use Sencha GXT and GWT to help their teams produce structured, powerful, and maintainable web applications. In this article, we’ll discuss several different ways to customize what the compiler is building for you, and how it can impact build times and output sizes.
In Ext GWT 2, component styles were defined in a single large CSS file. Developers could extend or redefine the styles in this file to control the appearance of a component or define a custom theme. Although this made it easy to give components a new look, it was hard to determine the relationship between the styles in the CSS file and the components in the library. Furthermore, there was no assurance that all of the styles in the CSS file were needed, or that the styles needed for a particular component were actually defined in the CSS file.
Extensions provide developers with valuable features beyond those that ship in Sencha’s frameworks, and are a very important part of the Sencha platform. At Sencha, we are investing to improve the ecosystem of extensions on our platform and I wanted to share an early look at our progress.
In a previous article, we discussed the charting library as a whole. However, there is far more to the Sencha GXT 3 charting library than was covered in that introduction. This article discusses a number of the more intermediate and advanced features that you can use — including tweaking the data store backing your chart. With some simple changes to the basic chart setup, you can make your visualizations even more explanatory and expressive.
We’re excited to announce the general availability of Sencha GXT 3.0! Sencha GXT, previously known as Ext GWT, is our Java based web application framework that leverages the Google Web Toolkit compiler. With the Sencha GXT 3.0 framework, developers can build high performance web applications with cross-browser compatibility across all desktop browsers.