Re: Improved ajax support idea

2012-11-24 Thread Ariel Arias
Hi!
I use a lot of Ajax with Django too, but I agree that this kind of
solutions should not be inside the core of Django. It can be very well
solved by third party projects and include it in the core can make Django
lose one of his better things : freedom. Because developers will
"understand" that Django is telling you how to manage that.

Regards!

On Fri, Nov 23, 2012 at 10:53 PM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:

>
> I use a lot of AJAX in my projects as well.
>
> However, it that doesn't mean that *Django* needs to include advanced AJAX
> support.
>
> I (and other members of the core team) have said this many times in the
> past -- the Django community benefits when Django isn't a monolithic core.
>
> From a technical perspective, I see no reason why the sort of features
> you're talking about need to be in Django's core.
>
> The only reason to put these views in Django's core would be social -- by
> putting them in core they get 'blessed' as a preferred approach. And
> there's a downside to doing this -- it means that the rate of development
> becomes tied to Django's own release cycle. It also means that maintenance
> is either limited to those in the core team, or we need to increase the
> size of the core team
>
> As a case in point - there are several tools out there for building ReST
> APIs - TastyPie, Piston, Django ReST framework, and probably others. They
> all thrive as third party projects, and the broader community benefits from
> having competition. None of them need to be in trunk to gain popular
> support. They have independent release cycles, and independent development
> teams. And the broader Django community benefits as a result of this
> diversity.
>
> So - from my perspective, I'd say a AJAX-enhanced generic views sounds
> like a great idea, and I'd love to see what you can develop. However, I
> don't think the core is the right place for those views to live.
>
> Yours,
> Russ Magee %-)
>
> On Fri, Nov 23, 2012 at 10:12 PM, rohit jangid wrote:
>
>> I really liked the idea of more advanced inbuilt support for ajax in
>> django . I use django for my work and more than 80% of our time we use
>> ajax. would really like to participate and work on it .
>> thanks
>> On 22-Nov-2012, at 4:09 PM, James Pic wrote:
>>
>> > Hi all,
>> >
>> > More projects use AJAX nowadays. Django could help them more.
>> >
>> > For example, FormView, could check if request.is_ajax_request(), and in
>> that case return a JSON dict for example:
>> >
>> > {
>> > 'html': ,
>> > 'messages': [> installed>],
>> > 'error_fields': [> validate>],
>> > }
>> >
>> > All generic views could do something like this. The point is to provide
>> a consistent API usable in AJAX.
>> >
>> > This doesn't seem like much work, but for some reason I like this idea
>> a lot.
>> >
>> > What do you think ?
>> >
>> > I could work on a complete design document and documentation if you
>> think it's worth it.
>> >
>> > Regards
>> >
>> > --
>> > 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.
>>
>> --
>> 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.
>>
>>
>  --
> 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.
>

-- 
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: Error with GET 200 and GET 304

2013-02-13 Thread Ariel Arias
Hi. You are getting problems with your static files.

There is a lot of posts and tutorials you can find on Google about this
topic.

Django manage static files only for Development (setting them correctly on
settings.py) , and on production you should use a server for them (apache
for example).

Google "managing static files with Django" and you will find a lot of data.

Ariel

On Wed, Feb 13, 2013 at 6:19 AM,  wrote:

> Hi
>
> I am new to Django. When i run my Django project i get 0 errors. But when
> i run my browser with the "http://127.0.0.1:8000/";, i get the following
> console log. Please help me and plenty thanks in advance.
>
> *Console log*
> 0 errors found
> Django version 1.4.3, using settings 'BroadcastApp.settings'
> Development server is running at http://127.0.0.1:8000/
> Quit the server with CONTROL-C.
> [13/Feb/2013 03:10:46] "GET / HTTP/1.1" 200 4741
> [13/Feb/2013 03:10:46] "GET /static/css/bootstrap.css HTTP/1.1" 304 0
> [13/Feb/2013 03:10:46] "GET /static/watchy/img/watchy_logo.png HTTP/1.1"
> 304 0
> [13/Feb/2013 03:10:46] "GET /static/watchy/css/watchy_main.css HTTP/1.1"
> 304 0
> [13/Feb/2013 03:10:46] "GET /static/css/bootstrap-responsive.css HTTP/1.1"
> 304 0
> [13/Feb/2013 03:10:46] "GET /static/datepicker/css/datepicker.css
> HTTP/1.1" 304 0
> [13/Feb/2013 03:10:46] "GET /static/broadcast/css/webrtc.css HTTP/1.1" 304
> 0
> [13/Feb/2013 03:10:46] "GET /static/jqueryjs/jquery-1.9.0.js HTTP/1.1" 304
> 0
> [13/Feb/2013 03:10:46] "GET /static/js/bootstrap.js HTTP/1.1" 304 0
> [13/Feb/2013 03:10:46] "GET /static/datepicker/js/bootstrap-datepicker.js
> HTTP/1.1" 304 0
> [13/Feb/2013 03:10:46] "GET /static/watchy/js/bootbox-300.js HTTP/1.1" 304
> 0
> [13/Feb/2013 03:10:46] "GET /static/js/jquery.cookie.js HTTP/1.1" 304 0
> [13/Feb/2013 03:10:46] "GET /static/broadcast/js/webrtc.js HTTP/1.1" 200
> 2576
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django developers" 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 http://groups.google.com/group/django-developers?hl=en
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" 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 http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.