-- Bernd Matzner <[EMAIL PROTECTED]> wrote (on Friday, 22 August 2008, 12:58 PM -0700): > Bernd Matzner wrote: > > using 1.6 RC2, I see no JS generated with Zend_Dojo's Programmatic mode, > > but perhaps I'm missing something from the documentation - only if the > > (-1) param value is passed to setUseProgrammatic, there should be no > > script generation. > > > > Here's what I do: in my controller, I > > > > <snip> > > Zend_Dojo::enableView($this->view); > > Zend_Dojo_View_Helper_Dojo::setUseDeclarative(); > > $this->view->dojo()->enable(); > > (... options) > > </snip> > > > > Then create a form > > > > $myForm = new Zend_Form(); > > Zend_Dojo::enableForm($myForm); > > > > with some dijit controls. In this case, how would the programmatic code be > > pushed to dojo()?
I'm not understanding the issue at this point. What are you expecting, and what is actually happening? By default, ZF produces programmatic JS. With Dojo, there's very little to be done, and the bulk of our support involves creating an object that maps nodes to desired dijit properties, and then a one or two liner that actually does the processing. Passing the "-1" value to setUseProgrammatic() simply tells the dojo() view helper not to actually spit out anything. The assumption is that you're doing all your own processing. It has very limited use. > > I wonder how this is supposed to work when adding BorderContainer and > > ContentPane to a view (as described in the documentation), where dojo() > > object is already echoed to the page before this actually happens. You would need to capture the content prior to echoing the dojo() view helper. I've gone over this countless times on the list and issue tracker at this point. > > Thanks for any insight on best practice here. > > > > Declarative works fine except for a few glitches. What glitches are you seeing? If you could, please open issues in the tracker for them, so we can improve the offering. > > Also, there are a few attributes still added (tooltipPosition) to the HTML > > code, will create a report in the issue tracker. Hmmm? When describing an issue, please always provide the following: * Code to reproduce the issue/anomaly * Expected result * Actual result This makes my life easier as I then have a reproduce case and a test basically written -- which I'm going to need to do eventually anyways. -- Matthew Weier O'Phinney Software Architect | [EMAIL PROTECTED] Zend Framework | http://framework.zend.com/
