I have plans on creating an ExtJS version of Zend_Form. I have a need
to get it out soon so will be working on it this week. Do you have a
specific interface planned out. My plan was to layout the form as a
Zend_Form, add any extra extjs config that might be needed. And let
the extjs form render the form to and extjs json config object. Even
though the extjs will do most of the same validations as Zend_Form, I
will re-instantiate the form when the extjs form submits and validate on
server side also.
Matthew Weier O'Phinney wrote:
-- Rob Allen <[EMAIL PROTECTED]> wrote
(on Wednesday, 21 May 2008, 08:35 PM +0100):
On 21 May 2008, at 20:15, P draic Brady wrote:
It's really great news! And once the Dojo implementation is in place as a
template it's an open field for someone to step up and do something similar
for the lighter libraries like jQuery.
I wonder if this will actually happen long term?
There is talk on #zftalk already by a number of developers who are
interested in doing so. :-)
I think you can essentially assume that most other JS/Ajax libraries
won't be used with ZF by the majority of developers once the new
Zend-Dojo stuff is released. There just won't be the same level of
documentation, mailing list or irc help on how to do stuff compared to
using Dojo.
Even if the relevant components are written for another JS library, to
adopt them you have to decide if they will be keep up with the
official Zend-Dojo components over the years that follow. Who will
maintain them and update them through ZF 2.0, 3.0 etc? This is the
bit that would worry me about adopting something other than Dojo for
use with ZF over the long term.
Any integration other than Dojo will be part of extras, and will need to
be maintained by the community. Hopefully, this will mean that if one
developer is unable to continue, another can pick up where they left
off. But it is a good point to keep in mind, particularly if your
company is in need of official support channels.
I'm planning on telling my developers at work that we need to migrate
to Dojo over the next 6 months. I had a look at the Dojo docs and at
first glance they don't look as comprehensive as we've been used to,
but I'm sure we'll manage.
The 1.0 docs have been greatly improved, and they have also added API
documentation. You should also look at Dojo
Campus (http://dojocampus.org/), which has a lot of concrete use cases
_with_ code to demonstrate the various features of Dojo. Between the
official documentation, API docs, and Dojo Campus, there's a lot of
material.
Additionally, both O'Reilly and Pragmatic Programmers are publishing
books in the next month covering Dojo. Basically, if there is a time to
learn it, now is that time.
