Hi,
Okay. I merged in paj's branch, fixed all the tests and did a new
release:2.0b9
Awesome! Thanks for all your work on this.
It's probably best to keep my repository as the official one, as the issue
tracker is populated there.
Great to hear your baby is doing well. Our Alice is great, 5
Dan,
It all sounds completely reasonable to me. I say go for it and do it.
If you could (where possible) add and modify unit tests to cover any changes
you make, that would be fantastic.
A line or two in the docs about the render(...) method would be great too. If
you don't have the
Ok, great. I have much of this already implemented (in a WidgetAlt
mixin I've been using to override `display` and `validate` on my own
widgets); this weekend I'll merge the changes, see about updating the
tests and docs accordingly, and send a pull request.
Thanks!
Dan
On Thu, Oct 20, 2011 at
There seem to be three ways to include a function call with your
widget - create a JSFuncCall and add it to cls.resources, use the
add_call method (which seems to be a per-instance shorthand for the
first method), or add the call directly in your template (which is the
method used by e.g.
Hi,
True, though if I understand Widget correctly display() does a lot
more than just creating the output string - I'd also have to rewrite
the code for automatic instance creation and resource management. Is
there any reason we couldn't add a separate render() method that just
does the
Hi,
There seem to be three ways to include a function call with your
widget - create a JSFuncCall and add it to cls.resources, use the
add_call method (which seems to be a per-instance shorthand for the
first method), or add the call directly in your template (which is the
method used by e.g.
I'm looking at this, but I'm afraid this is a jscalendar bug (which
is used in a old version).
I'l let you know if I find a way to fix this.
Damien
On 10/18/2011 11:46 PM, Paul Johnston wrote:
Hi,
Sorry, that widget doesn't work
