- 1
- 2
- < previous
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
- 1
- 2
- < previous
Latest on AJAX
- A future without programming
- Zend adds Flash links to PHP
- JavaFX RIA technology almost ready
- Aptana introduces AJAX servers
- Who needs an enterprise AJAX solution?
- OpenAjax moves on interoperability, security
- Mozilla Labs pursues Web development tools
- Open source identity: Horde lead developer Jan Schneider
- Nokia challenges developers to think outside the phone
- Coghead clicks for non-coders
Development Essentials
- Top 10 wicked cool algorithms
- Facebook app verification fee draws criticism
- Microsoft's openness stressed
- Yahoo's developer platform to launch this week
- Microsoft starts new developer portal
- Google API allows creating apps that can track laptops
- PHP, JavaScript, Ruby, Perl, Python, and Tcl Today: The State of the Scripting Universe
- Analyst: In-house app development fraught with waste
- Is unit testing doomed?
- Open source still the best way to develop software
TechWorld Jobs (beta)
Recent Jobs
TechWorld Blogs
-

TalkingTech
The view from the top of IT with TechWorld Editor Rodney Gedda
-

Entrenched
Cooking up better code, IDG's developers reveal some of their secrets
-

Broadband Voice
Darren Pauli digs in from the front line of Australia's broadband battleground
Recent blog posts
- A Novell approach to business
- An open storage stack? I like the sound of that
- The mobile clone wars: fighting for a better phone experience
- Stopping the "Clean Feed"
- Identifying web platforms
- Clean Feed ‘not technically possible’
- No Clean Feed - well duh!
- Conroy's content cops still on the cards
- Will open source ruin the economy? Please help
- Linux kernel 2.6.27 is out!
Recent comments
- A real alternative?
7 hours 36 min ago - Hello this is Brianna
1 day 17 hours ago - Turn any PC into a media center
2 days 7 hours ago - How About the Correct Title?
2 days 22 hours ago - who are you kidding?
3 days 3 hours ago - Seriously, how much did they pay for this advertisement
4 days 18 hours ago - SF Bay Area - free Seminar on Enterprise Cloud Computing
4 days 21 hours ago - video conferening but not telepresence...
5 days 4 hours ago - SAMSUNG OLED 40" TECHNOLOGY
5 days 13 hours ago - What was the question again, oh well this was prepared earlier
1 week 20 hours ago - Worldwide broadband prices continue to drop which means ? in AU
1 week 20 hours ago - Not a Problem Here in Australia and New Zealand
1 week 3 days ago - Clear the air
1 week 3 days ago - Tabbed browsing, Quick Find,
1 week 6 days ago - Microsoft details plans for new social bookmarking tool
2 weeks 19 hours ago - There is a 3rd party tool
2 weeks 2 days ago - Demise of Windows
2 weeks 2 days ago - new OS
2 weeks 2 days ago - Re: Favicon
2 weeks 3 days ago - Multi Camera Kino
2 weeks 4 days ago




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.