Re: Output of form in Extjs

[Russell Keith-Magee]

Hi João,

Thanks for the suggestion, but this isn't something we're likely to
add to Django's core itself.

This is for two reasons. The first is that we have been specifically
avoiding any dependency on any particular database library. Django is
a server-side framework, so we don't want to impose any client-side
decisions on users.

The second is that we want to move away from the .as_* model, towards
a more flexible approach. There was a Summer of Code project last year
aimed at moving the forms library to a templates approach; that hasn't
come to completion yet, but the broader aim still stands -- rather
than try an encode every possible output format, we'd like to move to
a place where an end user can plug in any output format. To that end,
your ext2js renderer would be an end-user plugin, rather than
something built into Django itself.

Yours,
Russ Magee %-)

On Wed, Sep 5, 2012 at 3:05 AM, JJ <joaoju...@gmail.com> wrote:
> Hi all,
> I created parse django to extjs in modelforms and forms. Basically works as
> form.as_p but is form.extjs_output. I mapped all widgets fields to extjs. I
> would like to submit this code to django-project. What do you think?
> Thank you.
>
> João Júnior
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-users/-/h6rzplc6r3kJ.
> To post to this group, send email to django...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.

[JJ]

Hi Russell,

I would like to create was plugin, as you presentation. I would like to contribute with this code. How can it help you?

Thank's

[Sean]

Hi JJ,

I am very interested in the django form output in ExtJS style, has your code been upload somewhere I can have a look, such as github?

Also, my email address is liush...@gmail.com

Thanks,

Sean