 |
XUI |
General
Interface |
Nexaweb |
Laszlo Systems |
| Standards-based Server Architecture (XML, J2EE) |
Yes. Framework-based solution with XML and Java-based Architecture within a J2EE platform; conforms and adheres to recognized standards and patterns such as MVC (Model-View-Controller) and other widely adopted technologies such as JSP, Struts, and JSTL. |
N/A. Client-based solution with JavaScript and XML-based architecture. |
No. Proprietary Nexaweb server that runs inside a J2EE server and routes client-side requests to the right Web application instance, serving much in the same manner as HTTP requests. |
Laszlo applications are written in XML and JavaScript and compiled by the Laszlo Presentation Server (LPS) into the bytecode format supported by the Flash Player. The LPS runs within a Java Servlet Container or Application Server. |
| Data Binding (backend source integration) |
Yes. Binding is done through standardized JSTL Expression Language and JSF Data Binding. Developers can bind UI components directly to existing bean values using the JSF Expression Language (EL). Data can also be in a form of pure XML generated from the server or passed through a web service. |
Unknown |
Yes. Through proprietary Nexaweb Messaging server that provides communication between clients and servers. |
User interface components can be filled in from the values in an XML data source. Uses XPath syntax for hierarchical data binding. |
| Client-to-Server Method Binding |
Yes. Through standardized JSF Method Binding. Developers can bind UI components directly to existing bean methods using the JSF Expression Language (EL). |
Unknown |
Unknown |
Done through Laszlo’s Java APIs that allow objects on the server to respond to client requests. |
| Support for stateful persistence of client and server sessions |
Yes. XUI supports synchronous client and server persistence which can be turned on or off. |
Unknown |
No |
No |
| Support for standard security approaches (data encryption, digital certificates, etc) |
Yes. XUI adheres to standard security protocols such as SSL using HTTPS. |
Yes |
Yes |
Yes. Runs over standard HTTP and HTTPS (port 80 and 443; configurable). |
| Development environment |
IDE Agnostic; Any text editor can work with XUI development. Since XUI works primarily with the presentation layer of a J2EE application, the development environment is the same as with any other application; no need for special environment. |
Proprietary General Interface Studio, a rapid application development (RAD) environment. |
Proprietary Nexaweb Studio, is an Eclipse-based, Internet Development Environment that makes it easy to quickly build and deploy Rich, Enterprise Internet Applications in J2EE. |
IDE Agnostic; Any text editor can work with development. |
| Pluggable Look-and-Feel |
Yes. Through standard CSS and XML configuration files. |
No |
No |
No |
| World-Ready |
Yes. With UNICODE support and other double-byte encoding such as Shift-JIS and BIG-5.
Internationalization is handled through the built-in Localized Content Manager or through standard Java Resource Bundles. |
N/A or Unknown; According to General Interface:
Q: Is there support for foreign alphabets and multi-byte characters?
A: General Interface Objects applications run natively inside a web browser and therefore inherit all the foreign alphabet and multi-byte character support of that browser. |
Unknown |
Unknown |
| Tag-based UI Component APIs |
Yes. Tag-based APIs with Object-Oriented approach; full support for browser scripting language when necessary.
Minimum skill-sets requirements:
• HTML
• XML (to create well-formed documents)
• Some JavaScript
|
No. APIs are written in Jscript/JavaScript 1.2. Developers need to have strong JavaScript and XML capabilities to create General Interface Screens |
Yes. Pages are written in XUL/SVG. |
Yes. Laszlo provides built-in tags using object-oriented programming.
Leverages developer’s skills in HTML, JavaScript. |
