Django Sockets Proposal
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 responded to by the front-end?? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/4695e446-011d-41c8-a52c-37cc3057d884n%40googlegroups.com.
Idea
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 the best routing but what if they support SPAs this time? 2. what if we could instead of Javascript in the templates, we write python, case in example is forexample how we write C# in .NET withing our templates not writing JavaScript. Currently Django is requiring its developer to again go ahead and learn JS too, what if we remove that?? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/bdefe58e-b26f-434e-a83f-36917b81f936n%40googlegroups.com.
More boilerplate, less confusion, more harmony.
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 and the rest but leaving out forms.py, signals.py, urls.py and modules.py but most developers endup creating these files for their specific uses. The problem comes in only one instance where someone names these differently from the convetional way, and it becomes hard to traceback their source code. I suggest they be added with some little docstring for begginers to know what can be done in these files just like in the main urls.py of the project. 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/e862c598-abf3-4695-9327-5c81a910f389n%40googlegroups.com.
Re: Django Sockets Proposal
Handle events, handle requests, update the DOM all with python, having this in place will enable us to even write SPAs easily If we can achieve those three there, then we would be starting to see JS out of python. It's quit absurd to find you write your project with django and sometimes django restframework, but github shows you that 0.2 % python was used and 75% JS was used, and you wonder whether its JS you wrote or python!! On Mon, Sep 20, 2021 at 7:38 PM PINEDO HUANSI LUCERO < luceropin...@egyg.edu.pe> wrote: > if you're right, but what would we do? > > > El 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 >> forget about the sockets alone, what-if? we have a way of emitting those >> events which can be responded to by the front-end?? >> >> -- >> 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 view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/4695e446-011d-41c8-a52c-37cc3057d884n%40googlegroups.com >> <https://groups.google.com/d/msgid/django-developers/4695e446-011d-41c8-a52c-37cc3057d884n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAOHi-%2B0QdH2V%3DxMzj_pBG_QUrHGrQdXWHCLY7EgGHRNqdV19gQ%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAOHi-%2B0QdH2V%3DxMzj_pBG_QUrHGrQdXWHCLY7EgGHRNqdV19gQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMjc0xWWxacY0C%3D%2BCGO-ve0r6UGmVV%3DJ2j6%3DyJtnRasipb80hw%40mail.gmail.com.
Re: Idea
Well, this looks like a cool attempt but still lacking the python part. I would like to update the DOM just with Python not anything like Javascript. >From what I have read from the links above, I have realised that we are writing HTML that has already been covered up with JS, but in my issue, we are trying to run independent of JS just like we see in C# where one writes C# instead of JS in .NET On Wed, Oct 20, 2021 at 6:16 PM 'Adam Johnson' via Django developers (Contributions to Django itself) wrote: > Check out htmx as a way to avoid needing JavaScript in your Django > 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 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 the best routing but what if they support SPAs this >> time? >> >> 2. what if we could instead of Javascript in the templates, we write >> python, case in example is forexample how we write C# in .NET withing our >> templates not writing JavaScript. Currently Django is requiring its >> developer to again go ahead and learn JS too, what if we remove that?? >> >> -- >> 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 view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/bdefe58e-b26f-434e-a83f-36917b81f936n%40googlegroups.com >> <https://groups.google.com/d/msgid/django-developers/bdefe58e-b26f-434e-a83f-36917b81f936n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAMyDDM2N6zFK7p0VA8e-Y-DwpCSsePH3O5q3g1P7O8O8-Vi5kA%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAMyDDM2N6zFK7p0VA8e-Y-DwpCSsePH3O5q3g1P7O8O8-Vi5kA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMjc0xUSKYUgJrrUOTscr0%2BT8xLABqwF%3DK9BmDANyLVTuNS%2BKQ%40mail.gmail.com.
Is_ajax replacement??
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 emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMjc0xVkfsJm90tD8Q4%2B5KpyD4Z2FFeXAntc3K08M8EYg3hyQw%40mail.gmail.com.
Re: Is_ajax replacement??
Thanks, I think I will always add small module when needed On Thursday, February 24, 2022 at 11:33:30 AM UTC+3 Adam Johnson wrote: > The feature was deprecated in Django 3.1 - the release note covers > alternatives: https://docs.djangoproject.com/en/3.1/releases/3.1/#id2 > > If 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, 2022 at 6:49 AM Jet Ezra wrote: > >> 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 emails from it, send an >> email to django-develop...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/CAMjc0xVkfsJm90tD8Q4%2B5KpyD4Z2FFeXAntc3K08M8EYg3hyQw%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/django-developers/CAMjc0xVkfsJm90tD8Q4%2B5KpyD4Z2FFeXAntc3K08M8EYg3hyQw%40mail.gmail.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/b485d334-4c7e-4e3a-8a34-d95539d66a35n%40googlegroups.com.
