Unless I'm not understanding it right, ZKoss looks like it requires some web 
server configuration in order to run.  Flex doesn't, which is nice for people 
like me who work in server environments they can't control.  But it looks like 
awesome tech! Am I right about it needing server side configuration?

Jason Merrill
Instructional Technology Architect II
Bank of America  Global Learning





_______________________

From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf 
Of Ron G
Sent: Wednesday, January 11, 2012 9:15 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Flex alternatives



Yes, we have also abandoned Flex in favor of ZKoss. Since we are already a Java 
shop, on the server side, it seemed logical to use a Java based framework on 
the client-side.

The thing I really like about ZK or ZKoss is that it has equivalent components 
to Flex. In fact, it actually has more components than Flex.

It implements an approach that I really like of separating the UI into 
appearance and behavior - much like the Spark components of Flex. Well, not 
exactly, but sort of. :) Here's what I mean. For each UI object, it has a 
client side (widget) and server side (component). I won't go into further 
detail, but it gives you a nice separation of concerns that you can avail 
yourself of. This feature also greatly insulates the rendered pages from 
x-browser compatibility issues.

Check it out for yourself at their site (zkoss.org).

Ron

--- In flexcoders@yahoogroups.com<mailto:flexcoders%40yahoogroups.com>, "Sal" 
<sal.celli@...> wrote:
>
> hi,
> as i can sadly see from the message history bottom grid, many programmers are 
> leaving flex.
> So this thread is to ask you all, if you have already found a valid 
> alternative to flex for RIA development.
>


----------------------------------------------------------------------
This message w/attachments (message) is intended solely for the use of the 
intended recipient(s) and may contain information that is privileged, 
confidential or proprietary. If you are not an intended recipient, please 
notify the sender, and then please delete and destroy all copies and 
attachments, and be advised that any review or dissemination of, or the taking 
of any action in reliance on, the information contained in or attached to this 
message is prohibited. 
Unless specifically indicated, this message is not an offer to sell or a 
solicitation of any investment products or other financial product or service, 
an official confirmation of any transaction, or an official statement of 
Sender. Subject to applicable law, Sender may intercept, monitor, review and 
retain e-communications (EC) traveling through its networks/systems and may 
produce any such EC to regulators, law enforcement, in litigation and as 
required by law. 
The laws of the country of each sender/recipient may impact the handling of EC, 
and EC may be archived, supervised and produced in countries other than the 
country in which you are located. This message cannot be guaranteed to be 
secure or free of errors or viruses. 

References to "Sender" are references to any subsidiary of Bank of America 
Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are 
Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a 
Condition to Any Banking Service or Activity * Are Not Insured by Any Federal 
Government Agency. Attachments that are part of this EC may have additional 
important disclosures and disclaimers, which you should read. This message is 
subject to terms available at the following link: 
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you 
consent to the foregoing.

Reply via email to