Re: Regarding Google Season of Docs

[Kranthi Kotagiri]

Hey hi,
Your profile looks good. I really like the way you designed it and the
format matter you insert really explains well.


On Thu, Jul 9, 2020 at 9:49 AM kaka bisht  wrote:

> Good morning,
> For the previous month and this month, I spent a lot of time in Django
> documentation by Django and Mozilla community, and I would like to thank
> the Django community for it.
>
> My Cv has been attached to this email, but along with this, I tried to
> write a basic Django blog to demonstrate my theoretical knowledge along
> with the series of projects I have completed.
> https://programmerprodigy.code.blog/2020/07/09/basics-of-django-framework/
>
> My suggestion for this season for docs was to give basic introductory
> information as we give in project urls.py file, we could perhaps add
> similar basic introductory information in-app directories, such as give
> away to link models.py file to views.py file and from that to app urls.py
> or project urls.py file
> The second suggestion was to better the context insertion into the HTML
> files, as in improve our context dictionary
> The third suggestion was to include Django-debug toolbar along with basic
> information about it, as a layer over the standard Django debugs.
>
> Hoping to hear back from the community over the feedback for the blog
> along with the suggestions made,
> --
> regards,
> Hridyesh Singh Bisht
> kakabish...@gmail.com
> https://kakabisht.github.io./
>
> --
> 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/CANZicOT8p2KpU898m7ViGisAqAJZ%3DtvB7008QUW%3DW2pNGFiJDg%40mail.gmail.com
> 
> .
>

-- 
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/CAEytwOYtGQJyoog8-wP-UDHrUc81V7kvB%2B%2BFkZRAYa-KpPnR8w%40mail.gmail.com.

Re: Admin webcomponents

[Carlton Gibson]

Hi Both. 

Jon Dufresne (mainly just him) had been doing a super job removing the 
jQuery dependencies in the admin, and modernising the JS whilst he's at it. 
It's approaching just "vanilla" JavaScript, all nice and modern, and 
linted. 

The blocker here will be Select2 -- we're not going to rewrite that 
ourselves. (Anyone know if they´re rewriting without jQuery?)

Leaving Select2 aside though, what are the advantages to components that 
the JavaScript we have doesn't satisfy? The Admin JS is not THAT complex... 
what more do we need? 

This (obviously) needs someone to step forward to write the code. I'd guess 
a prototype mini-project demonstrating one bit would be good to see. Then 
we could compare the code and see what the gains are. 

I recall seeing various articles complaining about web component 
accessibility. I presume this would be addressable, but it's something to 
bear in mind. 

Kind regards, 
Carlton


On Saturday, 11 July 2020 14:04:44 UTC+2, 1337 Shadow Hacker wrote:
>
> I cannot state how excited I am to see such as seasoned Django hacker as 
> Jacob being up for the task. I believe I'm not the only one who have had, 
> for a long time now, a vision for Django where the effort in the 
> django.contrib.admin becomes usable outside the admin and end up beating 
> Rails on generic views and stuff.
>
> As much as I have a fantastic experience with StencilJS as an avid TDD and 
> Unit Testing fan myself, I don't see jQuery going anywhere in any kind of 
> future. While you don't need it so much anymore for basic things, but for 
> some advanced usages it does provide a friendlier API than the DOM. And if 
> you're going to pull it for a reason or another, why would you want to 
> write document.querySelectorAll instead of $() ...
>
> Also, keeping jQuery in the first iteration will force figuring out 
> dependency management, how Django wants to leverage the browser import 
> calls. So, as long as we have something else to tackle this, then removing 
> jQuery would be fine. But keep in mind a lot of stuff uses it, such as 
> select2, however, we might also decide to use other autocomplete 
> webcomponents.
>
> > Many years ago, I wrote a Django app to integrate client-side form 
> validation with Django's server side logic.
>
> Well that looks really good, we're also undergoing efforts in the ryzom 
> library, and also had another interesting pattern proven in a library 
> called facond, both of which might be worth to take a look at if you also 
> get your kicks from this kind of stuff.
>
> https://facond.readthedocs.io/en/master/index.html
> https://yourlabs.io/oss/ryzom 
>
> > I'm very much interested in this topic, because I already implemented 
> parts of this in AngularJS, although this now is
> > an obsolete technology.
>
> Well the fast deprecation of JS frameworks has been a problem for Django 
> for years, and for a good reason.
>
> This is why I believe we can see salvation in the webcomponents standards, 
> living since 2017 and now available in every browser engine, the time has 
> come for Django to keep up with the W3C standards.
>

-- 
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/bc9a8cb5-3a4e-47a5-b233-56010c4a7d70o%40googlegroups.com.

Re: Admin webcomponents

['1337 Shadow Hacker' via Django developers (Contributions to Django itself)]

I cannot state how excited I am to see such as seasoned Django hacker as Jacob 
being up for the task. I believe I'm not the only one who have had, for a long 
time now, a vision for Django where the effort in the django.contrib.admin 
becomes usable outside the admin and end up beating Rails on generic views and 
stuff.

As much as I have a fantastic experience with StencilJS as an avid TDD and Unit 
Testing fan myself, I don't see jQuery going anywhere in any kind of future. 
While you don't need it so much anymore for basic things, but for some advanced 
usages it does provide a friendlier API than the DOM. And if you're going to 
pull it for a reason or another, why would you want to write 
document.querySelectorAll instead of $() ...

Also, keeping jQuery in the first iteration will force figuring out dependency 
management, how Django wants to leverage the browser import calls. So, as long 
as we have something else to tackle this, then removing jQuery would be fine. 
But keep in mind a lot of stuff uses it, such as select2, however, we might 
also decide to use other autocomplete webcomponents.

> Many years ago, I wrote a Django app to integrate client-side form validation 
> with Django's server side logic.

Well that looks really good, we're also undergoing efforts in the ryzom 
library, and also had another interesting pattern proven in a library called 
facond, both of which might be worth to take a look at if you also get your 
kicks from this kind of stuff.

https://facond.readthedocs.io/en/master/index.html
[https://yourlabs.io/oss/ryzom](http://yourlabs.io/oss/ryzom)

> I'm very much interested in this topic, because I already implemented parts 
> of this in AngularJS, although this now is
> an obsolete technology.

Well the fast deprecation of JS frameworks has been a problem for Django for 
years, and for a good reason.

This is why I believe we can see salvation in the webcomponents standards, 
living since 2017 and now available in every browser engine, the time has come 
for Django to keep up with the W3C standards.

-- 
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/co4AO24VjvnGZ9_bD9o165F2KQhfZOU-ugaeS_fX2nEiHBJzWsd25QrXdDIvZRV-RiO2-88Qmb8262lUQWjxoYnGcebhWaPSlRE-xxvlTfM%3D%40protonmail.com.