Even More Smartclient 11 | Smart Gwt 6 Features
Check out some of the new features in Smarclient 11 | Smart GWT 6.
Join the DZone community and get the full member experience.Join For Free
we blogged a few weeks ago ( click here ) about the first batch of features in smartclient 11 | smart gwt 6. below are a bunch more. enjoy!
beautiful input controls
first of all, we’ve overhauled the appearance of our form controls to match current design trends and take advantage of css3 features like box shadows and transitions, that are now supported across all common browsers.
to check it out for yourself, see examples here , and across many of our other samples in the pre-release sample site .
datasource navigator & dashboards in developer console
you will find the new “datasources” tab in the developer console to be an extremely useful tool. it enables developers & admins to view, search, and edit data for any datasource in your application, without being limited to the ui intended for normal end users. leverage it as a:
- development tool
- troubleshooting tool for live, deployed applications (admins only)
- security auditing tool (log in as an ordinary user and perform operations to test for correct server-side enforcement of security rules).
it even includes the ability to save a dashboard consisting of grids configured to show interesting data, allowing admins to quickly bring up key information such as recent orders, lapsed subscriptions or other metrics that may otherwise have required a dedicated reporting tool to make available.
min and max width for listgrid auto-sizing
space in tables is premium. you want to see as much of the data is possible at one time, but this is difficult when the size of returned data is dynamic. to resolve this, smartclient 11 | smart gwt 6 gives you precision control over column widths, making it possible to:
- autofit perfectly to typical data, but not expand for unusually long values
- impose a minimum size for a column that allows a title to be partially clipped (e.g. showing “desc” may be sufficient for “description”
let’s look at an example:
a) the description column in the table below only has short values. as such, the column width is narrow, taking up as little space as possible without truncating the values.
b) below, one of the values in the description column is very long. the column is wider than before, but rather than make the column unusually wide, that single long description is truncated.
here, all of the values in the description column are blank. the column is therefore made as small as possible, even clipping the column title to ‘ desc …’ to free up as much space as possible.
component min and max heights & widths
get more control over layouts with minheight and minwidth properties on components. this makes it easy to implement scenarios like:
- components that should start scrolling if they grow beyond a certain size
- preventing components from becoming too small to be usable
- modal dialogs that should fill the screen, but not become overly large
let’s look an example:
when space is not an issue, the description text and the complete table with all of the data is displayed in the layout as shown below.
as the amount of description text grows, there is less space for the table. the amount of space available for the table is reduced. the complete table is still displayed, but the user must scroll to see all rows of data.
as more description text is added, there comes a point where further decreasing the height of the table does not make sense. at this point, the table is pushed downwards and the right-hand scroll bar provides navigation to it.
this feature also provides the ability to control the size of modal dialogs. in the example below, the modal dialog has been set to take up 80% of the width of the screen. therefore, the size of the modal dialog changes as the screen is resized. however, we don’t want it to get too small, or too big. let’s look at the example:
- at first, the screen is very small. the dialog has to take up the full width of the screen to be readable, and it prevents the screen from being sized smaller.
- as the screen gets larger, the modal dialog takes up 80% of the width.
- as the screen gets larger still, there comes a point when it is no longer necessary for the modal dialog to grow further.
more miscellaneous features
use our pre-release features now!
download our cutting-edge development pre-releases to get started using our new features now!
as always, please send us any bug reports or feedback in the forums . please be clear about what product and version you’re using when reporting issues.
the isomorphic team
Published at DZone with permission of Jason Hardy-Smith, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Designing a New Framework for Ephemeral Resources
Implementing RBAC in Quarkus
5 Key Concepts for MQTT Broker in Sparkplug Specification
Creating Scalable OpenAI GPT Applications in Java