Benjamin found the error. I should not add both ViewHelper and
UiWidgetElement!
Thanks again Benjamin!
Bart
Bart McLeod schreef:
I meant to write $form->removeElement('begin'); but that makes no
difference to the result...
Bart McLeod schreef:
*testcode to reproduce error:*
setView($view)
I meant to write $form->removeElement('begin'); but that makes no
difference to the result...
Bart McLeod schreef:
*testcode to reproduce error:*
setView($view);
$form->addElement(new ZendX_JQuery_Form_Element_DatePicker("begin",
array('label' => 'begin', 'value' => '10-03-2008')));
echo $fo
*testcode to reproduce error:*
setView($view);
$form->addElement(new ZendX_JQuery_Form_Element_DatePicker("begin",
array('label' => 'begin', 'value' => '10-03-2008')));
echo $form;
$element = $form->getElement('begin');
$decorator = $element->getDecorator('UiWidgetElement');
$element->setDecor
Hello Benjamin,
The problem is that I am NOT the one who is passing the NULL value. It
is done internally, somewhere where I can't find it. Otherwise, it would
have been very simple to solve.
I have tried preserving the original decorator and re-adding it, but
that does not work either. So i
Hello Bart,
the call signature for all jQuery helper mimics the dojo one:
$this->helper($id, $value, array $params=array(), array $attribs=array())
if you want to pass no value leave the parameter entry or put array() in it.
null leads to an error, this is desired behaviour.
regarding NULL and
It seems to be by design, if explicit null values are passed in, the
default value is of no use:
As and addition, I noticed that when putting
if(! is_array($attribs)){
var_dump($attribs);
//exit();
}
inside the function, is actually dumps NULL, while $at
As and addition, I noticed that when putting
if(! is_array($attribs)){
var_dump($attribs);
//exit();
}
inside the function, is actually dumps NULL, while $attribs should be
Array{}, because the default is array(). PHP 5.2.5 doesn't seem to
assing the default
Hi Matthew,
That's truly exciting news, to have the Cal overhere in the Netherlands.
Chances are that we get to see more of him then!
Regards,
Bart
Matthew Ratzloff schreef:
Ah, OK. Thanks for the response.
FYI, last month Cal accepted a job in the Netherlands. I'm sure
that's probably
Ah, OK. Thanks for the response.
FYI, last month Cal accepted a job in the Netherlands. I'm sure that's
probably holding up your proposal.
http://www.ibuildings.com/news/?story=111
-Matt
On Sun, Oct 26, 2008 at 6:29 AM, Bart McLeod <[EMAIL PROTECTED]> wrote:
> Sorry Matt, for seeing your que
Sorry Matt, for seeing your question so late.
I would like to write a tutorial on devzone about those tricks, but my
proposal about that is still under review (Matthew, Cal?).
It comes down to delegating the responsibility for adding decorators to
a small set of classes that know how to add d
Hi Benjamin,
I was able to remove the error by removing the type hints in your
interface. There is no point in having default values array() if you are
type hinting for array's. In that case, when the underlying system
passes in a null value, for whatever reason, the error will be fatal.
pub
Hello Benjamin,
Yes, the decorators is exactly where I will have to be looking. The
reason that the 'begin' id caused the error is that the 'begin' field is
grouped together with other form elements automagically, because I just
hate to set decorators every time. It is more than likely, that i
Hello Bart,
ok i'll close it. In my opinion using the view helpers is really easy, but the
form elements are a bit hard to wield since the Element Decorator structure
is quite complex which spills to the jQuery specific elements and decorators.
greetings,
Benjamin
On Thursday 23 October 2008 2
>
> It would have been nice if this element would have been completely
> compatible with all the tricks I play.
>
What tricks are those?
-Matt
On Thu, Oct 23, 2008 at 2:57 PM, Bart McLeod <[EMAIL PROTECTED]> wrote:
> Hi Benjamin,
>
> Yes and no. I know where to look to find out what is happenin
Hi Benjamin,
Yes and no. I know where to look to find out what is happening. It would
have been nice if this element would have been completely compatible
with all the tricks I play. For now, just close the bugreport. If I find
a compatibility issue later, that I can describe more properly, I
so this is not at all ZendX_JQuery related? its due to your own form
implementation? i have already created a bug report, i will close it then if
you can confirm that.
On Thursday 23 October 2008 23:31:41 Bart McLeod wrote:
> By now, I found that the error is due to some internal magic I use fo
By now, I found that the error is due to some internal magic I use for
my forms. Still a strange error.
I was able to use a ZendX_JQuery_Form_Element_Datepicker, named 'begin'
in a regular form that has no magic to it.
Bart
Bart McLeod schreef:
Hi all,
$elem = new ZendX_JQuery_Form_
Hi all,
$elem = new ZendX_JQuery_Form_Element_DatePicker("begin",
"12.12.2007", array(), array());
$elem->setJQueryParam('dateFormat', 'dd.mm.yy');
$this->addElement($elem);
yields:
*Catchable fatal error*: Argument 4 passed to
ZendX_JQuery_View_Helper_DatePicker::datePic
18 matches
Mail list logo
