On Thu, Apr 7, 2011 at 3:23 PM, akaariai wrote:
> About the read-only forms part of the proposal: read-only forms will
> be easy to implement if the template widget rendering idea will be
> included in core.
>
> For example for SelectMultiple widget the base template is probably
> something like t
About the read-only forms part of the proposal: read-only forms will
be easy to implement if the template widget rendering idea will be
included in core.
For example for SelectMultiple widget the base template is probably
something like this:
{% for choice in choices %}
{% if choice.selected
On Thursday, April 7, 2011 at 13:55 , Russell Keith-Magee wrote:
> On Thu, Apr 7, 2011 at 5:04 PM, igalarzab wrote:
> > [GSoC Proposal] Read-only forms and DataBrowse
> > ==
>
> >
> > Problem Description
> >
On Thu, Apr 7, 2011 at 5:04 PM, igalarzab wrote:
> [GSoC Proposal] Read-only forms and DataBrowse
> ==
>
> Problem Description
> --
> The addition of the `newforms` package to Django greatly improved the
>
[GSoC Proposal] Read-only forms and DataBrowse
==
About Me
--
I'm a college student of computer engineering at the
Universidad Politécnica de Madrid.
This will be my last year before I graduate.
I started programming web