The 2010.2 version of XAF will see improvements to the UI of ASP.Net applications. Below I have enumerated some of these changes so that you can see what we are planning. Don’t forget to let us know what you think in the comments.
1. The first thing we’ve done is to improve the general layout of elements on the page. Previously, XAF web apps looked more like a web page, you know, with elements just “floating around in the air”. However, an XAF web app isn’t really an informational web site, it’s actually a rich internet application and so we’ve decided to improve the UI. Now the layout is more compact with functional regions having clearly defined borders. As a result, we waste much less of the screen real estate.
Before
After
2. Next we added a splitter, which separates the left panel and working area. This splitter allows you to collapse the left panel, enlarging the working area, enabling you to view more data. The splitter also allows you to fine-tune the width of the left panel.
Before
After
3. Then we introduced support for informational panels that allow you to display data of any kind, wherever required.
4. We’ve also freed up some additional work area space by moving the breadcrumb navigation under the view title, thus consolidating two related items – the view and the path to it.
Before
After
5. We have removed the object navigation Actions from the main toolbar while at the same time compacting and accenting their appearance. As a result we have freed additional space on the toolbar for other Actions and visually separated a functional UI element.
Before
After
6. Actions from the Save category have been removed from the main toolbar and are now available in a separate Action group. This group is displayed at the top and bottom of a View. Doing this means:
a. We clearly notify a user when he enters edit mode, as the Save Actions only appear in this mode;
b. We have visually separated a functional Action group;
c. We have freed toolbar space for other Actions;
d. We have made control of modifications look more like other web applications where, generally, changes are saved or cancelled via buttons located at the bottom of a form.
Before
After
7. Support for all of the DevExpress ASP.NET themes has been introduced, so that a user can now choose a theme best suited to their way of using the application.
Well that’s all for this short blog post. Don’t forget to let us know what you think in the comments. Until next time, happy XAF’ing! 