What if in django, we have a uniform way of handling server-side web
sockets, built-in, not relying on external libraries?
Django Channels would be a deal, but they are broad and endup making us
forget about the sockets alone, what-if? we have a way of emitting those
events which can be responde
I know this may not be necessary at the moment because we are comfortable
depending on front-end frameworks, but I have my two ideas here:
1. what if django alone without any framework can be used to design
progressive web apps, with routers that do not reload the page, we
currently have one of
Hello, if this was already discussed before, let me know otherwise, I have
experienced a problem formally faced with other languages where everyone
has their own of naming their application.
By default creating a django creates a boilerplate that includes apps.py,
admin.py, models.py, views.py
l sáb, 18 sept 2021 a las 17:12, Jet Ezra ()
> escribió:
>
>> What if in django, we have a uniform way of handling server-side web
>> sockets, built-in, not relying on external libraries?
>> Django Channels would be a deal, but they are broad and endup making us
>>
o
> applications: https://htmx.org/
>
> Example app: https://github.com/adamchainz/django-htmx
>
> On Sun, 19 Sept 2021 at 00:00, Jet Ezra wrote:
>
>> I know this may not be necessary at the moment because we are comfortable
>> depending on front-end frameworks, but I h
Hello team?
So how are we checking for ajax-based in django 4+ if is_ajax() was
deprecated??
--
jet
--
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 email
f you didn't detect this until Django 4.0 I would recommend reading the
> documentation on deprecation warnings so you can discover deprecations when
> they happen:
> https://docs.djangoproject.com/en/4.0/howto/upgrade-version/#resolving-deprecation-warnings
>
> On Thu, Feb 24,
