Re: Admin webcomponents

[Jacob Rief]

I'm very much in favor of this. Getting rid of jQuery is a very important 
step to make Django future-prove.
In my other (non-legacy) projects, I currently replaced all JavaScript 
against webcomponents. I actually made good
experience with the StencilJS compiler. Compared to Svelte, I really 
appreciate the clean syntax and the readability
of the generated code of those components.

The big advantage of webcomponents is, that they play well together with 
all existing JavaScript frameworks
out there, hence embracing all developers using one of those. I recently 
found this article on Hackernews 

 
which
boils it down quite well.

Many years ago, I wrote a Django app to integrate client-side form 
validation with Django's server side logic.
See here  https://django-angular.awesto.com/combined_validation/
At that time it was based on AngularJS. The idea however remains the same 
and could well be applied to an
approach using webcomponents.

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

– Jacob

-- 
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/0575817c-1130-4638-8e90-caa4e1cd04ebo%40googlegroups.com.

Admin webcomponents

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

Hello everybody,

Currently, the admin site provides various form fields, and formsets, that 
depend on JS scripts.

These are loaded by form media.

Nowadays, webcomponents have made it into standard HTML, all browsers now 
support:

- Custom Elements: https://w3c.github.io/webcomponents/spec/custom/
- Shadow DOM: https://w3c.github.io/webcomponents/spec/shadow/
- ES Modules: 
https://html.spec.whatwg.org/multipage/webappapis.html#integration-with-the-javascript-module-system
- Template elements: 
https://html.spec.whatwg.org/multipage/scripting.html#the-template-element/

Proposal: upgrade the admin JS from Form.Media to webcomponents.

When/If this gets done, we will have the maturity to start extracting 
webcomponent code from the admin site into main Django, as such, I see this 
proposal as the required first step before trying to deprecate form media in 
future releases.

Needless to say, webcomponent support would be really good to have for Django 4.

Thank you in advance for your feedback

Have a beautiful day

-- 
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/m4h3LNOthoOnLAlJFGqMUNnaf6jOhZxK_J2egLNz9xThbMpp88bdSQS3-42Ual5rI0nUpRu2DGGtVpEHTeul7CO9vD1sCYalUPVBwbB1sik%3D%40protonmail.com.

Re: Making startproject's settings more 12-factor-y

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

All right, thank you for your feedback.

May I throw in the idea of using DJ_ instead of DJANGO_ as prefix ?

-- 
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/PBiCVsKC2UAJFHuD-tEkUh2063D7DgV1DcAxdlcFI2tSqpPxK-8XVWSPbSnyvG5spVf_1QYHZeyNN2dimPNPk7NrS0eh9zq-PhAQxSHAsMk%3D%40protonmail.com.

Re: Welcome email

[Jure Erznožnik]

I too volunteer for the screening job.

LP,
Jure

On 09/07/2020 16:10, Peter Inglesby wrote:

Hi folks,

Is there any moderation for posts from new users? It can be enabled 
, and I'd be 
willing to be part of a team that filters posts from new users.


All the best,

Peter.

On Thu, 9 Jul 2020 at 13:59, Adam Johnson > wrote:


I think that's a good improvement, not bikeshedding :)

On Thu, 9 Jul 2020 at 13:17, Shai Berger mailto:s...@platonix.com>> wrote:

Sorry for the bike-shedding, but I think the text should drop the
"using Django" language. The people who come here with these
questions
clearly think of themselves as developers, not users.

IMO It should go something like,

        Welcome to django-developers, the mailing list for
discussion
        of the development of Django itself.

        This mailing list is not for support developing apps and
        websites with Django. For support, please follow the
"Getting
        Help" page:
https://docs.djangoproject.com/en/3.0/faq/help/ .
        This page will direct you to the django-users mailing
list or
        other resources, so you can find people who are willing to
        support you, and to ask your question in a way that
makes it
        easy for them to answer.

Thanks,

The Django Community



On Wed, 8 Jul 2020 11:50:16 +0100
Adam Johnson mailto:m...@adamj.eu>> wrote:

> Okay I'm in favour. That said, there's already a banner on
the groups
> page:
>
> This group is for the discussion of the development of
Django itself.
> If
> > you want to ask questions about using Django, please post on
> > django-users.
> >
>
> Suggested wording, adapted from my templated reply:
>
> Welcome to django-developers, the mailing list for
discussion of the
> > development of Django itself.
> >
> > This mailing list is not for support using Django. For
support,
> > please follow the "Getting Help" page:
> > https://docs.djangoproject.com/en/3.0/faq/help/ . This
page will
> > direct you to the django-users mailing list or other
resources, so
> > you can find people who are willing to support you, and to
ask your
> > question in a way that makes it easy for them to answer.
> >
> > Thanks,
> >
> > The Django Community
> >
>
> Who has access to add this? Someone from the DSF board, the
ops team,
> or the fellows?
>
> On Mon, 6 Jul 2020 at 00:02, Ahmad A. Hussein
> mailto:ahmadahusse...@gmail.com>>
wrote:
>
> > +1 on this. Here's the relevant feature
> > 
I found.
> >
> >
> > Ahmad
> >
> > On Sun, Jul 5, 2020 at 7:58 PM Adam Johnson mailto:m...@adamj.eu>> wrote:
> >
> >> I can't find a google groups feature that would allow
this. Do you
> >> know of one? It might otherwise require a custom bot.
> >>
> >> On Sun, 5 Jul 2020 at 16:14, Arvind Nedumaran
> >> mailto:arvindamir...@gmail.com>> wrote:
> >>
> >>> Oh I understand. I meant we could include the
distinction in the
> >>> welcome email and possibly a link to the other list.
> >>>
> >>> That may reduce the number of people who may be looking
for help
> >>> but end up here mistakenly?
> >>>
> >>> Get Outlook for Android 
> >>>
> >>> --
> >>> *From:* django-developers@googlegroups.com
 <
> >>> django-developers@googlegroups.com
> on behalf of אורי
> >>> mailto:u...@speedy.net>> *Sent:* Sunday,
July 5, 2020 8:39:22 PM
> >>> *To:* Django developers (Contributions to Django itself) <
> >>> django-developers@googlegroups.com
>
> >>> *Subject:* Re: Welcome email
> >>>
> >>> I think because this list is called Django developers
and what we
> >>> call "Django users" are also developers who use Django.
But they
> >>> are developers.
> >>>
> >>> אורי
> >>> u...@speedy.net 
> >>>
> >>>
> >>> On Sun, Jul 5, 2020 at 5:59 PM Arvind Nedumaran
> >>> mailto:arvindamir...@gmail.com>> wrote: