On Wednesday 06 June 2007 11:11, Hermann Himmelbauer wrote:
I'm currently studying your doctests in z3c.form and I have to say, they
are really nice to read and understandable! Thanks!
Great! I am glad you like it.
I'm through with forms.txt and found some minor issues, so I attached a
It would be very interesting to see RDBMS interaction. Formlib for
example is not trivial to use with RDBMS especially because of a lack
of documentation and because everything seems to be written with ZODB
objects in mind.
It works together with a mapper like SQLAlchemy (and
It works together with a mapper like SQLAlchemy (and z3c.zalchemy).
IMHO, it is not formlib's task to do mappings like that.
Not sure what mappings you're talking about. I just want to
know how can I get some data from somewhere (it may be a
file, RDBMS or other external source) and
On Thursday 31 May 2007 02:25, Nikolay Kim wrote:
Not sure what mappings you're talking about. I just want to
know how can I get some data from somewhere (it may be a
file, RDBMS or other external source) and display it in a form,
then edit this data etc. Formlib default forms (EditForm,
Am Donnerstag, 31. Mai 2007 08:09 schrieb Maciej Wisniowski:
It would be very interesting to see RDBMS interaction. Formlib for
example is not trivial to use with RDBMS especially because of a lack
of documentation and because everything seems to be written with ZODB
objects in mind.
On Thursday 31 May 2007 03:48, Hermann Himmelbauer wrote:
Anyway, in my case a decent ORM-integration with Zope3 forms is still a key
issue to me.
If you provide me with a simple hello world-like example of the ORM stuff
you are using, then I will give it a try to write a demo for z3c.form.
Am Donnerstag, 31. Mai 2007 10:16 schrieb Stephan Richter:
On Thursday 31 May 2007 03:48, Hermann Himmelbauer wrote:
Anyway, in my case a decent ORM-integration with Zope3 forms is still a
key issue to me.
If you provide me with a simple hello world-like example of the ORM stuff
you are
I also still struggle with this issue. In my case, I have the following
scenarios:
I currently try to solve these issues with a self-made Form class, which
descends from form.Form. In case you are interested, here is my docstring
which somehow explains the basic idea:
Thanks for the
On Wednesday 30 May 2007 11:06, David Pratt wrote:
1) An iteration of the wizard that will not allow show submit button or
allow submit until the end of all steps.
I have implemented this feature. The Finish button will now only show up
when all required fields are filled out. You can update
Hi Stephan. Thanks for your reply. For #2, the following excerpt from
django's documentation located here:
http://www.djangoproject.com/documentation/tutorial02/
snip
And speaking of forms with dozens of fields, you might want to split the
form up into fieldsets:
class Admin:
fields = (
Am Mittwoch, den 30.05.2007, 18:12 +0200 schrieb Maciej Wisniowski:
Thanks. BTW, I am still looking for 1-2 demos to write but I am out of
ideas.
Do have anything related to forms that you would like to see demoed?
It would be very interesting to see RDBMS interaction. Formlib for
On Wednesday 30 May 2007 15:07, David Pratt wrote:
class Admin:
fields = (
(None, {'fields': ('question',)}),
('Date information', {'fields': ('pub_date',)}),
)
This is s lame! We have this great OO language and they do such
simple C-like structures.
12 matches
Mail list logo
