Welcome to Brasato

News

23.03.2007 We implement the CaveatEmptor example from Hibernate with Brasato

Get Brasato
Download Brasato (14Mb)

5-minutes Install

Brasato Screenshots

Events

Controller

SOA GUI

2009

Please visit the OLAT website for everthing concerning the brasato gui framework (it is actively used and enhanced by the Olat community)

Sept 17th, 2007

Stay tuned: After the release of OLAT 5.2.2 we are soon going to release a new version of Brasato with many improvements which we learned while running OLAT.



Brasato is an advanced open-source Web 2.0 framework written in Java.

Brasato is the destillation of three years of developing the large open-source e-learning project OLAT

We were nominated for the JAX Innovation Award. It was an honor to be nominated together with such great projects as Groovy, openArchitectureWare and others. See the well-deserved winners.

We will show you three reasons why we think this framework could become your favorite.





1. Automatic Accessibility mode

cited from wikipedia AJAX#Accessibility
Accessibility Using without incurring the cost of re-rendering the entire page in the web browser. Non-Ajax users would ideally continue to load and manipulate the whole page as a fallback, allowing the developers to preserve the experience of users in non-Ajax environments (including all relevant accessibility concerns) while giving those with capable browsers a much more responsive experience.


With Brasato, you are programming with a modern, ajaxified, event-based, partial screen updating, fast framework.

And you don't need to worry about providing an HTML output which is suitable for screenreaders... it is done automatically in most cases



2. SOA GUI

While taking only a little bit longer than normal coding, it gives you the chance to create truly reusable gui flows which can be used with two lines of code.

Everybody is talking about SOA for business integration and orchestration.

On the GUI side, most frameworks only focus on reusable components.

However, the workflows on the GUI side with transactions to the business side (aka business logic) can be seen as reusable services.

When GUI workflows are used, this allows for true code reuse which goes far beyond having standard components. (As an example, a complete user search is plugged into the screen with two lines of code). GUI SOA could be seen as a very advanced form of portlets.

With GUI SOA, you can delegate your task to a Service and plug the visual part of the service into your screen

The rest is automatically handled for you - until you are notified of the results of the service. A service, in order to execute it tasks, can ask for help by calling other visual and non-visual services.

For example, in OLAT, there are learning groups, which can have a forum. In order to use that forum all you need to do is to ask the collaborative service to generate a forum. You provide a callback implementation to determine who can read, post, and moderate the forum, and you then receive from the service a so-called controller with an initial component.

You put this component into your screen (attach it to the component tree). The controller does then handle the complete forum for you.



Another, simpler example is a user search service, consisting of a search mask, a results table, and the capability to show/hide results column, and save those as preferences.

To use the service, you call the service to receive a controller and register as listener, so that you will later receive either a "user-chosen" event, or a "cancel" event.

3. Debug mode

See behind the scenes of your web pages like you have never seen before.

No searching for config files, no mapping files. Even complete foreign code of your fellow programmer that happens to be in vacation for four weeks when your release is tomorrow and you have a critical bug... Never mind - see here

Let's better do a hands-on experience: Download the Code