Re: Queries about the project idea Improving the Less Popular Backends

2019-04-08 Thread Asif Saif Uddin
yes, you can select some relevant issues which help to fix a much bigger 
problem. so try to understand the bigger ideas coming out of some of the 
related issues. deadline is very close. it would be better to have the 
draft submitted here and fix at least one or two related issues to convince 
the core team and the community that ypu are capable to complete what you 
are proposing.

Cheers!

Asif

On Monday, April 8, 2019 at 5:24:06 PM UTC+6, Dingfan Zhao wrote:
>
> Hello guys, 
>
> I am year 4 students in Singapore and I would like to contribute to Django 
> in GSoC this summer. The project idea that I am interested in is Improving 
> the less popular backends. However, the project description is kind of 
> vague and I am not able to catch the exact requirements for this project. 
>
> In my view, the key for this project is to build some features for less 
> popular backends to make it support equal operations with other backends. I 
> appreciate if someone can give me some advice. 
>
> For example, I did a search in Django raising ticket page and I set up 
> some filters: 
> https://code.djangoproject.com/query?status=new=Database+layer+(models%2C+ORM)=id=summary=status=owner=type=component=version=1=id
>
> May I understand it like I would select some issues from these tickets and 
> solve them in order to fulfill this project idea? 
>
> Any advice is appreciated in advance! Thanks a lot. 
>
> Regards
>

-- 
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/449e90b3-9665-4bdb-b8e6-a5f702587ae2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Help for GSoC proposal (Formset improvements)

2019-04-08 Thread 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 () 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: Feature request (API): Add QuerySet of viewable pages or page_ids

2019-04-08 Thread air-hand
Thanks, Peter.

I'm trying implement referring to 
cms.utils.page_permissions.user_can_view_page.

2019年4月4日木曜日 7時59分29秒 UTC+9 Peter Farrell:
>
> Hi, I think this is a grand idea.
>
> On Tuesday, March 26, 2019 at 10:08:27 AM UTC-5, air-hand wrote:
>>
>> Hi everyone.
>>
>> I'm working with django cms, and needed permissions.
>>
>> CMS_PERMISSION is worked nice, but there is no method of "get viewable 
>> pages".
>>
>> I need viewable pages for listing up pages (searched results, recent 
>> updated etc.)
>>
>> I found cms.utils.get_view_id_list, but this is return view restricted 
>> pages only.
>>
>> User can view not restricted pages, or if included in get_view_id_list. 
>> (this is not be perfect, roughly speaking)
>>
>> If interested, please let me now.
>>
>> Thanks.
>>
>>

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/243093a1-3773-4411-92aa-ae50e731fc90%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: GSOC Proposal (Bundler for Django)

2019-04-08 Thread Ashik Meerankutty
Ok thank you for your feedback I will check it 

On Mon, 8 Apr 2019 at 2:46 PM, Jamesie Pic  wrote:

> PS: also check how other python frameworks deal with static files,
> particularly the cubicweb framework.
>
> --
> 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/CAC6Op18N%3DfJnb5SKUUBgmgVMo33_6QpruBiOCpU8VTb8kh9pxg%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CALaZoZc1ET6AJ3hiJy-Dc3ToadaDUJLGD%3DmywroaJdZxOAzJSg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Queries about the project idea Improving the Less Popular Backends

2019-04-08 Thread Dingfan Zhao
Hello guys, 

I am year 4 students in Singapore and I would like to contribute to Django 
in GSoC this summer. The project idea that I am interested in is Improving 
the less popular backends. However, the project description is kind of 
vague and I am not able to catch the exact requirements for this project. 

In my view, the key for this project is to build some features for less 
popular backends to make it support equal operations with other backends. I 
appreciate if someone can give me some advice. 

For example, I did a search in Django raising ticket page and I set up some 
filters: 
https://code.djangoproject.com/query?status=new=Database+layer+(models%2C+ORM)=id=summary=status=owner=type=component=version=1=id

May I understand it like I would select some issues from these tickets and 
solve them in order to fulfill this project idea? 

Any advice is appreciated in advance! Thanks a lot. 

Regards

-- 
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/57e26ea3-8b6d-4d9f-96b5-04c3e487e085%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: GSOC Proposal (Bundler for Django)

2019-04-08 Thread Jamesie Pic
PS: also check how other python frameworks deal with static files,
particularly the cubicweb framework.

-- 
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/CAC6Op18N%3DfJnb5SKUUBgmgVMo33_6QpruBiOCpU8VTb8kh9pxg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: GSOC Proposal (Bundler for Django)

2019-04-08 Thread Jamesie Pic
Hi Ashik,
Thanks for your proposal that I find revelant because there needs to be a
new version of staticfiles.

Supporting NPM, one way or another, is the main way to enjoy the same
development workflow with frontend code as with pip. For me it would make
sense to support it, one way or another. {% block extra_js %} overrides
kind of works, but overriding frontend code delivered by an app is far from
convenient

when it involves copying a minified script from an app into an override
static dir and patching that minified code. Also dealing with {{ form.media
}} definitely doesn't cut it, ie. when if you load jquery in your base.html
and a form media also contains a jquery, this means we load the same script
twice, and that also causes issues ie. with plugin loading. So it doesn't
look like anybody would deny that static file management in Django needs an
upgrade.

However, the suggestion to contribute to other existing third party apps is
valid. Before contributing to Django you need to study the current state of
the art in the Django ecosystem, that lives in external projects.
Contribute to those, see why you believe they don't cut it, and make a
write up the existing django static file apps ecosystem, that would be a
great start.

Have a great day

-- 
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/CAC6Op18N1O6hFnwgrmnw28c_-warB-KMGO68S572xz--9SGGaQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Help for GSoC proposal (Formset improvements)

2019-04-08 Thread Carlton Gibson
Hi Parth. 

Well, the wizard () 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.