Re: Help for GSoC proposal (Formset improvements)

[PARTH PATIL]

I researched a bit on FormWizards, and what I felt is that it is 
oriented more towards the idea of multiple form submission similar to that 
of Google forms where we have multiple pages. 

I was thinking of creating a *FormSetContainer* which would be like a 
collection instance of different Forms, FormSets. or FormSetContainers 
themselves. It would be oriented more towards how we handle it in the 
backend, like the saving process, validation, etc rather than the 
frontend side. And the FormWizard View may be revived to display the 
FormContainer.

This would be another level of abstraction over the FormSet and can be 
helpful in the case where the user needs to get data for different model 
objects at once.

Please comment on need and feasibility of this. 


On Monday, April 8, 2019 at 11:54:57 AM UTC+5:30, Carlton Gibson wrote:
>
> Hi Parth. 
>
> Well, the wizard (&co) got moved out to it's own app 
> https://django-formtools.readthedocs.io/en/latest/
> But yes, there's no reason why this sort of thing wouldn't potentially in 
> scope. 
>
> Kind Regards,
>
> Carlton
>
>
> On Sunday, 7 April 2019 23:47:23 UTC+2, PARTH PATIL wrote:
>>
>> (Sorry I typed the incomplete message in the last post)
>>
>> I came across this ticket while going over the feature list of Forms and 
>> Formsets (# 18830 )
>>
>> Feature requested in this thicket is something like
>>
>> *FormWizard:*
>> * It will be like a container which can have forms, formsets, and 
>> formwizards itself.*
>>  
>>
>>1. Is this kind of feature still required?
>>2. Will this be a good addition to the Form?
>>3. Should I mention this in my proposal, as there is few time left 
>>for the final submission I may not be able to draft it properly?
>>
>> The possible use of this will be to attach different forms in an HTML and 
>> this form wizard will handle saving, etc of the forms. I was thinking of 
>> keeping something like a management form similar to formset which will 
>> handle the individual object and ensure which fields correspond to which 
>> form/formset element within the wizard.
>>
>>
>>
>> On Tuesday, March 26, 2019 at 11:26:56 PM UTC+5:30, PARTH PATIL wrote:
>>>
>>> I was planning  to do the "Formset Improvements 
>>> " 
>>> project in GSoC. I would need some more explanation on what is expected as 
>>> nothing was clearly mentioned there.
>>> You can link the related tickets or elaborate on what is needed that 
>>> would be helpful.
>>>
>>> I dug a little bit deeper into this. and found some related issues 1 
>>> 
>>>  
>>> | 2. 
>>> 
>>>
>>> I'm planning to add a request variable in the BaseFormSet Class 
>>> 
>>>  
>>> and then handle it such that it will be available within every form (not 
>>> completely polished till now).
>>>
>>>1. Is this a good approach?
>>>2. Will this solve the problem? (If not please mention the problems 
>>>which will not be solved
>>>
>>> I am also looking for some additional features that maybe added to 
>>> formset so am open for suggestions.
>>> I'm currently in middle of making the abstract so before moving forward 
>>> i would like to get some confirmation that this is correct approach. Thank 
>>> you
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/1fbb3ac2-c66a-413b-b409-ba0856fa1cb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help for GSoC proposal (Formset improvements)

[Carlton Gibson]

Hi Parth. 

Well, the wizard (&co) got moved out to it's own 
app https://django-formtools.readthedocs.io/en/latest/
But yes, there's no reason why this sort of thing wouldn't potentially in 
scope. 

Kind Regards,

Carlton


On Sunday, 7 April 2019 23:47:23 UTC+2, PARTH PATIL wrote:
>
> (Sorry I typed the incomplete message in the last post)
>
> I came across this ticket while going over the feature list of Forms and 
> Formsets (# 18830 )
>
> Feature requested in this thicket is something like
>
> *FormWizard:*
> * It will be like a container which can have forms, formsets, and 
> formwizards itself.*
>  
>
>1. Is this kind of feature still required?
>2. Will this be a good addition to the Form?
>3. Should I mention this in my proposal, as there is few time left for 
>the final submission I may not be able to draft it properly?
>
> The possible use of this will be to attach different forms in an HTML and 
> this form wizard will handle saving, etc of the forms. I was thinking of 
> keeping something like a management form similar to formset which will 
> handle the individual object and ensure which fields correspond to which 
> form/formset element within the wizard.
>
>
>
> On Tuesday, March 26, 2019 at 11:26:56 PM UTC+5:30, PARTH PATIL wrote:
>>
>> I was planning  to do the "Formset Improvements 
>> " 
>> project in GSoC. I would need some more explanation on what is expected as 
>> nothing was clearly mentioned there.
>> You can link the related tickets or elaborate on what is needed that 
>> would be helpful.
>>
>> I dug a little bit deeper into this. and found some related issues 1 
>> 
>>  
>> | 2. 
>> 
>>
>> I'm planning to add a request variable in the BaseFormSet Class 
>> 
>>  
>> and then handle it such that it will be available within every form (not 
>> completely polished till now).
>>
>>1. Is this a good approach?
>>2. Will this solve the problem? (If not please mention the problems 
>>which will not be solved
>>
>> I am also looking for some additional features that maybe added to 
>> formset so am open for suggestions.
>> I'm currently in middle of making the abstract so before moving forward i 
>> would like to get some confirmation that this is correct approach. Thank you
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/519108f2-4030-49d3-8ce8-137f32a48743%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help for GSoC proposal (Formset improvements)

[PARTH PATIL]

(Sorry I typed the incomplete message in the last post)

I came across this ticket while going over the feature list of Forms and 
Formsets (# 18830 )

Feature requested in this thicket is something like

*FormWizard:*
* It will be like a container which can have forms, formsets, and 
formwizards itself.*
 

   1. Is this kind of feature still required?
   2. Will this be a good addition to the Form?
   3. Should I mention this in my proposal, as there is few time left for 
   the final submission I may not be able to draft it properly?

The possible use of this will be to attach different forms in an HTML and 
this form wizard will handle saving, etc of the forms. I was thinking of 
keeping something like a management form similar to formset which will 
handle the individual object and ensure which fields correspond to which 
form/formset element within the wizard.



On Tuesday, March 26, 2019 at 11:26:56 PM UTC+5:30, PARTH PATIL wrote:
>
> I was planning  to do the "Formset Improvements 
> " 
> project in GSoC. I would need some more explanation on what is expected as 
> nothing was clearly mentioned there.
> You can link the related tickets or elaborate on what is needed that would 
> be helpful.
>
> I dug a little bit deeper into this. and found some related issues 1 
> 
>  
> | 2. 
> 
>
> I'm planning to add a request variable in the BaseFormSet Class 
> 
>  
> and then handle it such that it will be available within every form (not 
> completely polished till now).
>
>1. Is this a good approach?
>2. Will this solve the problem? (If not please mention the problems 
>which will not be solved
>
> I am also looking for some additional features that maybe added to formset 
> so am open for suggestions.
> I'm currently in middle of making the abstract so before moving forward i 
> would like to get some confirmation that this is correct approach. Thank you
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/0e6fe881-ea44-41b4-99e5-190841e66e20%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help for GSoC proposal (Formset improvements)

[PARTH PATIL]

I came across this ticket while going over the feature list of Forms and 
Formsets (# 18830 )

Feature requested in this thicket is something like

*FormWizard:*
* It will be like a container which can have forms, formsets, and 
formwizards itself.*




On Tuesday, March 26, 2019 at 11:26:56 PM UTC+5:30, PARTH PATIL wrote:
>
> I was planning  to do the "Formset Improvements 
> " 
> project in GSoC. I would need some more explanation on what is expected as 
> nothing was clearly mentioned there.
> You can link the related tickets or elaborate on what is needed that would 
> be helpful.
>
> I dug a little bit deeper into this. and found some related issues 1 
> 
>  
> | 2. 
> 
>
> I'm planning to add a request variable in the BaseFormSet Class 
> 
>  
> and then handle it such that it will be available within every form (not 
> completely polished till now).
>
>1. Is this a good approach?
>2. Will this solve the problem? (If not please mention the problems 
>which will not be solved
>
> I am also looking for some additional features that maybe added to formset 
> so am open for suggestions.
> I'm currently in middle of making the abstract so before moving forward i 
> would like to get some confirmation that this is correct approach. Thank you
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/b5ed1b63-84f7-4acc-8633-6c72336f2f82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help for GSoC proposal (Formset improvements)

[PARTH PATIL]

Thanks for your help 😀

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/ad7f8ce0-454a-45a0-9401-df3a17e50848%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help for GSoC proposal (Formset improvements)

[Carlton Gibson]

Hi Parth, 

Yes, something along those lines will be right. 

First-off, what are the existing work-arounds (i.e. how are people handling 
this in the wild: overriding `__init__()` methods etc...) — can these be 
summarised and documented, where worth recommending?

Then, API changes to improve on that situation, like passing in request 
objects. (From experience with DRF and django-filter, making the request 
available solves **most** issues for **most** users — "But I need X! — But 
that's just `request.X`" 9 times out of 10.) 

THEN, look at open accepted issues on Forms 
.
 
There are ≈70. Begin with FormSets issues, then spread out. Which are 
related? (#10403?) Which can you target? You don't have to solve them all 
(!) but a good goal for a 12 week project would be to become a total expert 
on django.forms, and to have handled a number of issues as part of that. 

HTH.

Kind Regards,

Carlton


On Tuesday, 26 March 2019 18:56:56 UTC+1, PARTH PATIL wrote:
>
> I was planning  to do the "Formset Improvements 
> " 
> project in GSoC. I would need some more explanation on what is expected as 
> nothing was clearly mentioned there.
> You can link the related tickets or elaborate on what is needed that would 
> be helpful.
>
> I dug a little bit deeper into this. and found some related issues 1 
> 
>  
> | 2. 
> 
>
> I'm planning to add a request variable in the BaseFormSet Class 
> 
>  
> and then handle it such that it will be available within every form (not 
> completely polished till now).
>
>1. Is this a good approach?
>2. Will this solve the problem? (If not please mention the problems 
>which will not be solved
>
> I am also looking for some additional features that maybe added to formset 
> so am open for suggestions.
> I'm currently in middle of making the abstract so before moving forward i 
> would like to get some confirmation that this is correct approach. Thank you
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/739596dd-772d-42ac-808e-32c670b8b683%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help for GSoC proposal (Formset improvements)

[Dmitriy Sintsov]

It would be nice to have paginated formsets when there are lots of one to 
many relationships in the inline form, otherwise such rendered formset is 
slow and huge.

On Tuesday, March 26, 2019 at 8:56:56 PM UTC+3, PARTH PATIL wrote:
>
> I was planning  to do the "Formset Improvements 
> " 
> project in GSoC. I would need some more explanation on what is expected as 
> nothing was clearly mentioned there.
> You can link the related tickets or elaborate on what is needed that would 
> be helpful.
>
> I dug a little bit deeper into this. and found some related issues 1 
> 
>  
> | 2. 
> 
>
> I'm planning to add a request variable in the BaseFormSet Class 
> 
>  
> and then handle it such that it will be available within every form (not 
> completely polished till now).
>
>1. Is this a good approach?
>2. Will this solve the problem? (If not please mention the problems 
>which will not be solved
>
> I am also looking for some additional features that maybe added to formset 
> so am open for suggestions.
> I'm currently in middle of making the abstract so before moving forward i 
> would like to get some confirmation that this is correct approach. Thank you
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/4aa66060-b6a0-465d-acbf-9b31ac6a69a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Help for GSoC proposal (Formset improvements)

[PARTH PATIL]

I was planning  to do the "Formset Improvements 
" 
project in GSoC. I would need some more explanation on what is expected as 
nothing was clearly mentioned there.
You can link the related tickets or elaborate on what is needed that would 
be helpful.

I dug a little bit deeper into this. and found some related issues 1 

 
| 2. 


I'm planning to add a request variable in the BaseFormSet Class 

 
and then handle it such that it will be available within every form (not 
completely polished till now).

   1. Is this a good approach?
   2. Will this solve the problem? (If not please mention the problems 
   which will not be solved

I am also looking for some additional features that maybe added to formset 
so am open for suggestions.
I'm currently in middle of making the abstract so before moving forward i 
would like to get some confirmation that this is correct approach. Thank you

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/09458146-224c-44c5-8bb3-2560f47350e5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.