Re: #14633 - organization of settings docs

2013-01-08 Thread Sam Lai 
Looks good. Adds a bit more structure for browsing but doesn't
significantly change how the page is used, which is probably through
CTRL-F.

As mentioned by others in the issue, the distinction current and
deprecated settings seems very arbitrary. I think it'll be better to
sort the deprecated settings like any other setting, but include a
better visual distinction to indicate that they're deprecated (at
least bold the word deprecated I think). When someone's looking for a
setting, they're not thinking about whether or not a setting is
deprecated; they're probably looking for what it means and how it can
be configured.



On 8 January 2013 08:02, Tim Graham  wrote:
> I'd appreciate feedback on #14633 - "Organize settings reference docs". So
> far I've broken out the settings for each contrib app into their own
> sections. The one comment on the pull request suggests further breaking up
> the settings listed in the "Core settings" section, e.g. logging, caches,
> globalization (i18n/l10n), email, file uploads/media, storages, and
> security. I don't feel strongly about this proposal: it could be useful, but
> it could also be ambiguous as to which section a particular settings belongs
> in.
>
> The pull request also suggests organizing the default settings.py in a
> similar fashion.  While it may be outside of the scope of this ticket, it
> could be worthwhile to discuss that suggestion as well.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-developers/-/Uku6Vo8oCvIJ.
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: #14633 - organization of settings docs

2013-01-08 Thread Tim Graham 
Agreed, I'm +1 to keeping deprecated settings inline rather than moving 
them to their own section, but I'd defer to whoever made the original 
decision.

On Tuesday, January 8, 2013 4:58:17 AM UTC-5, Sam Lai wrote:
>
> Looks good. Adds a bit more structure for browsing but doesn't 
> significantly change how the page is used, which is probably through 
> CTRL-F. 
>
> As mentioned by others in the issue, the distinction current and 
> deprecated settings seems very arbitrary. I think it'll be better to 
> sort the deprecated settings like any other setting, but include a 
> better visual distinction to indicate that they're deprecated (at 
> least bold the word deprecated I think). When someone's looking for a 
> setting, they're not thinking about whether or not a setting is 
> deprecated; they're probably looking for what it means and how it can 
> be configured. 
>
>
>
> On 8 January 2013 08:02, Tim Graham > 
> wrote: 
> > I'd appreciate feedback on #14633 - "Organize settings reference docs". 
> So 
> > far I've broken out the settings for each contrib app into their own 
> > sections. The one comment on the pull request suggests further breaking 
> up 
> > the settings listed in the "Core settings" section, e.g. logging, 
> caches, 
> > globalization (i18n/l10n), email, file uploads/media, storages, and 
> > security. I don't feel strongly about this proposal: it could be useful, 
> but 
> > it could also be ambiguous as to which section a particular settings 
> belongs 
> > in. 
> > 
> > The pull request also suggests organizing the default settings.py in a 
> > similar fashion.  While it may be outside of the scope of this ticket, 
> it 
> > could be worthwhile to discuss that suggestion as well. 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "Django developers" group. 
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msg/django-developers/-/Uku6Vo8oCvIJ. 
> > To post to this group, send email to 
> > django-d...@googlegroups.com. 
>
> > To unsubscribe from this group, send email to 
> > django-develop...@googlegroups.com . 
> > For more options, visit this group at 
> > http://groups.google.com/group/django-developers?hl=en. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/WZWRDsCUqFcJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: #14633 - organization of settings docs

2013-01-08 Thread ptone 
Looks good overall Tim - I do think that the primary reference should be 
kept alphabetical within core - this is most useful when you have a setting 
you need to look up.  But I do think that a 'by-topic' cross reference 
index could also be very useful for discovering or learning about all 
settings.  Such an index could be at the bottom of the page, and include 
the topics suggested, as well as the deprecated settings - settings that 
apply to more than one topic could be duplicated in such an index, and 
deprecated settings could be duplicated under a topic, and under a 
"deprecated" heading in such an index. This is a case where more 
organization is only good, and there is no reason we have to choose an 
either or.

-Preston


On Monday, January 7, 2013 1:02:49 PM UTC-8, Tim Graham wrote:
>
> I'd appreciate feedback on 
> #14633- "Organize settings 
> reference docs". So far I've broken out the settings 
> for each contrib app into their own sections. The one comment on the pull 
> request suggests further breaking up the settings listed in the "Core 
> settings" section, e.g. logging, caches, globalization (i18n/l10n), email, 
> file uploads/media, storages, and security. I don't feel strongly about 
> this proposal: it could be useful, but it could also be ambiguous as to 
> which section a particular settings belongs in.
>
> The pull request also suggests organizing the default settings.py in a 
> similar fashion.  While it may be outside of the scope of this ticket, it 
> could be worthwhile to discuss that suggestion as well.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/6cpcbfEsyzQJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: About Understanding of source code

2013-01-08 Thread ptone 
You might want to attempt to write a patch for an open issue - reading the 
source code is one thing and you may learn a bit. But dissecting the source 
code when you have the purpose to fix a problem, gives you a much better 
understanding of how things are working - as you NEED to understand them in 
order to properly fix/extend them. Just reading through it allows you to 
too easily skip over things you don't really understand.

FWIW,

-Preston


On Sunday, January 6, 2013 8:57:23 PM UTC-8, Mayur Patil wrote:
>
> Hello there,
>
>   I want to understand how to get deep insight into Django code?
>
>   Thank You.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/kV3hLOhjrwoJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: About Understanding of source code

2013-01-08 Thread Amirouche B. 


On Tuesday, January 8, 2013 6:54:41 PM UTC+1, ptone wrote:
>
> You might want to attempt to write a patch for an open issue - reading the 
> source code is one thing and you may learn a bit. But dissecting the source 
> code when you have the purpose to fix a problem, gives you a much better 
> understanding of how things are working - as you NEED to understand them in 
> order to properly fix/extend them. Just reading through it allows you to 
> too easily skip over things you don't really understand.


Also you can read the discussions that lead to the code, here is those that 
I know of:

- https://code.djangoproject.com/wiki/NewformsAdminBranch
- https://code.djangoproject.com/wiki/ClassBasedViews

To find easy bugs, check easy picking in trac custom 
query,
 you 
can also precise a component for instance if you are interested in the 
ORM
.

Also one way to learn little by little while still keeping an eye on what 
is coming is to watch django on github  (or 
subscribe using a feed 
reader
). Also there is mailling list for the 
tickets
 (prefered)

Regards,

Amirouche

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/142VK7-i_hkJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Tutorials

2013-01-08 Thread Lee Trout 
+1 for logging. It took me way too long to figure out how to get everything
working properly using a different (builtin) class. I agree with #19395
that an example (or two) would be great.

Here's what I'm currently using which makes use of a rotating file handler
and a custom date formatter (If it offers any inspiration or
clarification): https://gist.github.com/4489135

On Mon, Jan 7, 2013 at 3:59 PM, Tim Graham  wrote:

> Hi Daniele,
>
> I think additional tutorials would be welcome. My suggestion, before you
> dive in and start writing, would be to create a ticket with an outline of
> the proposed tutorial.  That will give the community a chance to take a
> look and provide feedback and suggestions before you spend time doing the
> actual writing.
>
> For some ideas, here is the list of "coming soon" tutorials that were at
> the end of tutorial 4 for a long time:
>
>- Advanced form processing
>- Using the RSS framework
>- Using the cache framework (see ticket below)
>- Using the comments framework (not sure about this, since I think
>comments may be removed from Django, see #18965)
>- Advanced admin features: Permissions
>- Advanced admin features: Custom JavaScript
>
> These may not be the best options at this point, but someone thought they
> were good ideas at one point.
>
> In addition, here are some tutorial tickets that have been "accepted":
>
> #16526  - Add a tutorial on
> caching
> #19106  - Add new tutorial
> on breaking templates into blocks
>
> I think your suggestion of logging is a good candidate -- you may want to
> take a look at #19395  as
> well.
>
> Thank-you for your contributions thus far, and I look forward to seeing
> what you come up with in the future. :-)
>
> Tim
>
> On Friday, January 4, 2013 5:42:44 PM UTC-5, Daniele Procida wrote:
>>
>> I am one of those people who can only learn things by doing them, and
>> finds it very hard to grasp things from reference materials. The Django
>> documentation is excellent on the latter, but not quite so good on the
>> tutorials that would guide me through doing things in a way that will help
>> me learn.
>>
>> I've made a couple of tutorial contributions so far (which if I am honest
>> simply reflect the steps I took when I was learning the topic). They are
>> the testing tutorial > com/en/1.5//intro/tutorial05/>
>> and a uWSGI/nginx tutorial, which though it may not be quite right for the
>> Django docs has gone into the uWSGI docs.
>>
>> I'd like to contribute more tutorials to the documentation, and since the
>> next thing I need to get to grips with is logging I will write my own notes
>> so I remember how to do it, and I could create a tutorial for it.
>>
>> Would that be useful for the documentation? I realise that a tutorial is
>> always going to be a partial and incomplete introduction to a subject, but
>> newcomers need to start with something concrete, and it gives them some
>> purchase on the reference material that is already provided.
>>
>> Are there other topics that really ought to have tutorials written for
>> them?
>>
>> Daniele
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-developers/-/vdn9xXpBvEAJ.
>
> To post to this group, send email to django-developers@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.