On Mon, Aug 18, 2008 at 2:45 PM, <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I've written a library on top of django.form that adds support for
> highly dynamic forms, including removing and adding inline forms after
> page load-time. To do so, I subclassed forms.BaseForm and added the
> needed functionality to it. My problem is ,that I'd like to support
> the same declarative syntax as forms via Form and
> DeclarativeFieldsMetaclass. However, only BaseForm and Form are
> exposed from the forms module and I can't use
> DeclarativeFieldsMetaclass in my application. Would it be possible to
> change this? The same applies to BoundField. It's also hidden inside
> the module.
Huh?
$ ipython
In [1]: from django.newforms.forms import DeclarativeFieldsMetaclass
In [2]: DeclarativeFieldsMetaclass?
Type: type
Base Class: <type 'type'>
String Form: <class 'django.newforms.forms.DeclarativeFieldsMetaclass'>
Namespace: Interactive
File: /home/users/patrys/Desktop/web/django/newforms/forms.py
Docstring:
Metaclass that converts Field attributes to a dictionary called
'base_fields', taking into account parent class 'base_fields' as well.
In [3]: from django.newforms.forms import BoundField
In [4]: BoundField?
Type: type
Base Class: <type 'type'>
String Form: <class 'django.newforms.forms.BoundField'>
Namespace: Interactive
File: /home/users/patrys/Desktop/web/django/newforms/forms.py
Docstring:
A Field plus data
Constructor information:
Definition: BoundField(self, form, field, name)
--
Patryk Zawadzki
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
