Saturday 22 November, 2008
Revving up once:radix for RAD Web apps
GUI RAD development moves to the Web
Rodney Gedda 23/07/2008 12:21:42
Once:radix editing the properties of a form field
Once:radix editing the properties of a form field

Once:radix is really RAD

With the little hurdles behind me, it was time to get my hands dirty with once:radix.

The first thing that impressed me was the level of separation between data presentation and code logic. Fields and forms can be presented on a page with ease and then drilled down into for data types and scripting.

Database connectivity - done, CSS - done, HTML - done. It's all just there ready to be moulded to your specific requirements.

So presenting forms on a blank page is like using Filemaker or Access without the flair associated with client GUI applications.

See the screen shots for what to expect when developing with once:radix. I was quite excited at how easy it is to begin building a Web application.

Applications built with once:radix can be open source or commercial and the application itself is dual-licensed.

Integration and hacking

Once:technologies insists once:radix is not a framework in the traditional sense, but it does have a lot in common with the Web application frameworks like Django, Ruby on Rails, and Spring.

The basic integration between components is done for you, but any Java coder can hack up servlets for once:radix to perform other repetitive tasks.

Conversely, once:radix differs from other open source Web application frameworks in the sense that it's a complete Web-based GUI RAD tool and not a set of standard components that used by developers to create a custom application.

According to Napier, once:radix is a complete development and delivery environment with "most of the hard work done for you".

"That's why people with less Web and database experience can build advanced business applications with our system."

Without the need to develop security or design database schema developers can focus purely on the end-user application.

For external communication once:radix has its own Web API, and the company is keen to get the open source community building servlets for easy integration of popular online services like Facebook.

There is already a range of Web API functions, from database connectivity to user management, and for Web services there is a SOAP-like API. Better servlet documentation is coming.

Other features include Rhino support for server-side scripting, caching, and two levels of native debugging.

Once:technologies claims applications developed with once:radix are as scalable as Java, Tomcat and PostgreSQL will allow them to be and an average server should be able to cater for 200 users.

What's good
Intuitive user interface
All Web-based
Reduced development complexity

What needs work
Dependent upon Firefox only
Browser needs to be configured

Comments

once:radix

Rodney Gedda's review provided a fair and balanced analysis of some of the features of once:radix.

The issue of configuring the browser is due to the lock-down of some features in Firefox. But to make some once:radix functions available (e.g. file uploads) signed.applets.codebase_principal_support must be enabled. Alternatively, an SSL signed certificate (e.g. from Verisign) is needed. Both solutions are simple and a matter of choice when developing an application.

The need to delete Rodney's prefs.js file is a problem that occurs infrequently. In fact, it is only the second time I have seen the need to do it, in the many thousands of installations performed. But then, in accordance with Murphy's Law, software is most likely to go wrong during an important product review!

Cross browser support is an important issue. At our last attempt, Internet Explorer was 16 times slower than Firefox 2. With the speed improvements achieved in Firefox 3, the difference would be even more dramatic.

We face the same issues with browser compatibility as other RIA technologies, though it may be more acute with once:radix, due to the sophistication of our client.

We have seen extraordinary changes in all of the associated technologies over the life of this project and expect this will continue. Nevertheless, the rewards far outweigh the small challenges we face. The key platform of our design strategy is to conform to W3C and other standards. If that means, failing to achieve Microsoft compatibility in the short term, so be it. However we are in discussion with Microsoft to develop a strategy to achieve full compatibility without loss of performance. Hopefully, this will be resolved soon.

Market Place
 

Techworld Australia Member Login

c