AUIML is an XML dialect that is a platform- and a technology-neutral representation of panels, wizards, property sheets, etc. AUIML captures relative positioning information of user interface components and delegates their display to a platform-specific renderer. Depending on the platform or device being used, the renderer decides the best way to present the user interface to the user and receive user input.
The AUIML XML is created using the Eclipse-based AUIML VisualBuilder, which allows a developer to quickly build and preview user interfaces in the Java Swing and Web Renderers. The AUIML VisualBuilder can also automatically create application launchers, data beans, event handlers, and help system skeletons for the user interface. Because it plugs into Eclipse, building the user interface and application code is an integrated process.
News: Abstract User Interface Markup Language 6.1 Released
The Abstract User Interface Markup Language toolkit is a rapid-development tool to assist developers in writing GUIs to run as either Swing applications or on the Web -- without any changes. Version 6.1 includes several new features and improvements, most notably support for Java logging and Java 2 Standard Edition 5.0.
- Posted by: gham Hamilton
- Posted on: March 20 2006 01:27 EST
- do it support ajax by Hank Li on March 20 2006 21:13 EST
- Abstract User Interface Markup Language 6.1 Released by Javier Paniza on March 21 2006 03:32 EST
- UI is too specific in its nature by Mileta Cekovic on March 21 2006 10:56 EST
- Abstract User Interface Markup Language 6.1 Released by Michael Jouravlev on March 22 2006 15:15 EST
Have not look into hte details, does it support ajax? compare to jsp files, how fast is the page loaded?
Only two questions:
- Which licence type? Open Source?
- What about portal integregations?
OpenXava: Business Component Application Framework
I do not believe in generic user interface toolkits that try to span multiple paradignms (desktop and web).
UIs are too specific in its nature and any attmpt to generify it leads to poor UIs. If you want good UI you have to invest your hard work in it and develop separate UI for every device you need, either desktop or browser or PDA/smartphone or something else.
Not even to mention the cost of browser-to-server communication, which every good UI MUST be aware of.
Can someone compare it with XAML?