Luke Plant wrote:
So I feel quite strongly that we should fix this code to use
salted_hmac. (Or fix salted_hmac if there is some problem with it, but
remembering that there is lots of data that depends on it).
I updated the patch and changed the way the hashes are generated. We now use
the sal
Jacob Kaplan-Moss wrote:
I'm +1 in theory. I need to spend some time going through your code,
and I'll need to see some documentation on porting existing wizards to
the new code (unless it's truly 100% backwards compatible). But in
general I think it's a fine idea and something I'd love to target
Hi everybody,
I want to continue the discussion on the replacement of
django.contrib.formtools.wizard (previous discussions can be found here:
http://bit.ly/eI5ZT5 and http://bit.ly/gVTRtr).
I worked on moving the currently external django-formwizard to use class
based views. The repository/
my pull
request: https://github.com/stephrdev/django-formwizard/pull/5
I will start soon writing a draft and trying to help you make
django-formwizard the official replacement.
Cheers,
Miguel Araujo
@maraujop
2010/12/31 Stephan Jäkel
Hi,
I just updated the cbv_refactor branch to use the gene
s,
Miguel Araujo
@maraujop
2010/12/26 Stephan Jäkel mailto:m...@sjaekel.com>>
Hi Miguel,
I saw your message on GitHub and I thought I had answered that I'll work
on the formwizard within the next weeks. But maybe I missed to press the
"send" button :-)
Hi Miguel,
I saw your message on GitHub and I thought I had answered that I'll work on
the formwizard within the next weeks. But maybe I missed to press the "send"
button :-)
Regarding your points, I had the same thoughts in 02/2010 and started to
write django-formwizard. There were also som
Another update on this proposal:
I just wrote a patch to make the described idea possible and recycled the
already existing ticket http://code.djangoproject.com/ticket/10497 for that.
You'll find a patch attached to the ticket.
Stephan Jäkel wrote:
Hi,
this proposal is about extendin
I forgot to mention the ticket for the "stat" method:
http://code.djangoproject.com/ticket/10497
Stephan Jäkel wrote:
FYI, there is a ticket in trac which recommends to add a "stat" method
but I think this maybe would be hard to implement on backends like S3.
Cheers,
Hi,
this proposal is about extending the storage backend api of Django.
The storage backend has already many helpful methods to get information
about stored files like:
- name
- size
- full path (for some backends).
I think it could be useful to have some more methods to get information
abou
Hi Scot,
shacker wrote:
Not all forms are completed in a single sitting. We have a form with
more than 100 fields, which takes at least two hours for the user to
complete. Therefore it's essential that the (authenticated) user be
able to save it and return later to edit or complete it. IOTW ther
Hi,
about 4 months ago, I started this thread. I want to give some news on
django-formwizard to keep you all up2date.
Stephan Jäkel wrote:
The last not solved problem is handling file uploads.
This problem is solved. The formwizard supports file uploads in any step. I
solved the problem
Hi,
Alex Gaynor wrote:
My one comment (and we discussed this on IRC) is that this really
should inherit from GenericView IMO, so it'd be nice if that landed
before this.
Agreed, many stuff in formwizard/classbased-views is duplicated. (I actually
got the thread-safety bit from there).
Cheer
Hi,
Harro wrote:
+1 on the storage backend. Can the current filestorage backend be
reused for this?
I think yes, but will need some extensions for invalidation of files. But
can be subclassed (already wrote a experimental backend for doing this)
Cheers,
--
You received this message because
Hi,
TiNo wrote:
On Sat, May 29, 2010 at 22:07, Stephan Jäkel mailto:m...@sjaekel.com>> wrote:
I already discussed this ticket with Jannis during the sprints and
hope to start a discussion here to find the right way to allow file
uploads and see if my approach takes the
Hi,
Harro wrote:
We had a site where we needed a wizard with the ability to go back and
forward and store files.
Only allowing files in the last step really isn't an option imho, that
just avoiding the problem ;-)
I totally agree. But it is _one_ option to get around the problem.
What we did
Hi,
Jacob Kaplan-Moss wrote:
I couldn't tell from my quick play, though, if there were any
backwards-incompatible changes. There's a fair bit of code churn (in a
good way :), so before we could merge this I'd like a sense of what
any backwards-compatibily concerns would be.
There are some back
Proposal: Replace django.contrib.formtools.wizard
This proposal is about replacing the current form wizard, because it is not
usable in many ways. According to ticket #9200, the new form wizard module
should
a) have multiple storage backends to save the form data for the single steps.
(The tic
17 matches
Mail list logo
