Just go to Zkoss.org and do a search on HTML5. You'll see a lot about how it is increasing support for HTML5. Here is one neat "small talk" for example:
http://books.zkoss.org/wiki/Small_Talks/2011/October/ZK_Html5_Canvas_Charts Also, if you download the source for ZK, and browse through it, you'll see its heavy reliance on jQuery on the client side. Ron --- In [email protected], "Merrill, Jason" <jason.merrill@...> wrote: > > >> Out of interest... why does ZK marketing material never mention HTML5? > > Speculating here, but probably because it doesn't use HTML 5 tags at all, - > everything I saw on their site indicates it's an AJAX solution using an older > version of HTML. > > Jason Merrill > Instructional Technology Architect II > Bank of America Global Learning > > > > > > _______________________ > > From: [email protected] [mailto:[email protected]] On > Behalf Of John Fletcher > Sent: Tuesday, January 17, 2012 3:59 AM > To: [email protected] > Subject: Re: [flexcoders] Re: Flex alternatives > > > Out of interest... why does ZK marketing material never mention HTML5? They > used to say "direct RIA" though I can't see that on the site anymore. I > thought HTML5 was the new buzzword and that it would make sense to state it > at least 3 times on every page? > John > 2012/1/17 Ron G <rgrimes@...<mailto:rgrimes@...>> > > > Hi Joaoak: > > You can make the coupling as tight or loose as you want. Each UI object can > have a client side widget that is primarily the appearance, and a server side > component that should contain the more complex logic. So, you can hide as > much as want by placing it in the server side component as Java code, or keep > in the client side widget as JS. In fact, since you indicate you are moving > to HTML5, ZKoss actually might be a good choice, since it relies heavily on > jQuery, which is considered a favorite HTML5 library. The difference is ZK > lets you choose where client side logic is stored - as JS on the client or > Java on the server. Another type of HTML5 approach won't offer that. > > Ron > > > ---------------------------------------------------------------------- > 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. >
