Wow, thanks a lot.
I would like to thanks everybody who answered. I have learned a lot from
this thread and thanks to you I believe I am a better programmer.
FTR, I've added an article to my blog which obsoletes the previous article.
Kind regards from Spain
On Tue, Nov 27, 2012 at 8:22 PM,
On Sun, Nov 25, 2012 at 12:04 PM, James Pic wrote:
> it would be great if we could make urls easier to reverse in Javascript.
you shouldn't have to.
good REST design means not using database IDs. any response that
references server resources should send a whole URL. no need
I understand what you mean, I realized my point of view was too
user-centric and not very conceptual. So, thanks for that and I'm still
totally up to make or help making an external app in my
next re-factor session.
Here's a single point I'd like the list's attention: it would be great if
we
On Saturday, November 24, 2012 9:11:17 AM UTC-8, is_null wrote:
>
> Hello everybody,
>
>
> I can understand most of the points made here, expect just one, please
> bare with me. Several hackers on this list stated that it has "obviously
> not its place in Django". I don't understand why
On Sun, Nov 25, 2012 at 1:10 AM, James Pic wrote:
> Hello everybody,
>
> Thank you for your feedback. And pretty soon I will tackle this problem in
> an external app - or consider joining the party if somebody else has
> started, in this case feel free to let me know.
>
> I
On Sat, Nov 24, 2012 at 7:10 PM, James Pic wrote:
> Hello everybody,
>
> Thank you for your feedback. And pretty soon I will tackle this problem in
> an external app - or consider joining the party if somebody else has
> started, in this case feel free to let me know.
>
> I
Hello everybody,
Thank you for your feedback. And pretty soon I will tackle this problem in
an external app - or consider joining the party if somebody else has
started, in this case feel free to let me know.
I can understand most of the points made here, expect just one, please bare
with me.
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
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
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
Hi,
On Thursday, November 22, 2012 11:39:54 AM UTC+1, is_null wrote:
>
> More projects use AJAX nowadays. Django could help them more.
Django somehow does that already: It doesn't stand in your way :)
> All generic views could do something like this. The point is to provide a
> consistent
I like the idea. Could you create a third party app so I could use it right
away?
On Thu, Nov 22, 2012 at 2:39 AM, James Pic wrote:
> Hi all,
>
> More projects use AJAX nowadays. Django could help them more.
>
> For example, FormView, could check if
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': [],
'error_fields': [],
}
All generic views could do something like this.
13 matches
Mail list logo