Re: Form customization

[Confi Yobo]

I kind of support what you are saying Alex Scott, I think the form should
be simplified at currently it takes a lot of time to setup a simple contact
form.

My suggestion is that upon creation of every form there should be
properties and methods to allows you to customize the form. Simplifying the
form will eliminate the need for using third party library like
DJANGO-CRISPY-FORMS
.

On Sun, Oct 6, 2019 at 12:11 AM Alex Scott  wrote:

> Hi all,
>
> Are there any current plans or developments to allow better customization
> of forms?  I've browsed several old Stack Overflow, django-users and Django
> ticket requests and it seems common enough to want to say, add a class to
> every form field or field label, or change the label suffix from ":" to "".
>
> The current "solutions" seem hacky and non-DRY, usually requiring custom
> code for every form used in a site.
>
> Would it be a terrible idea to allow these to be set in settings or in a
> base form that gets inherited by everything else?
>
> Thanks,
> Alex
>
> --
> 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/CAMiVppbh%2BOAWa6z0k0m2uQj0ZrguCAzgz3tt3yhWa6_FjMO_ow%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/CAD9uRzdagVtR-VZA9TqweCHyk0uPujAnJYkELNiS-_0zrGDdDw%40mail.gmail.com.

Re: Django Websocket Implementation Request

[Confi Yobo]

Ok

On Sat, Aug 10, 2019 at 6:07 PM Carlton Gibson 
wrote:

>
> On 10 Aug 2019, at 18:51, Confi Yobo  wrote:
>
> So it should not be expected in 3.0? @ Carlton Gibson
>
>
> No. As per the previous comments, it’s not something likely to be included
> in core. Certainly not for 3.0.
>
> --
> 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/DF029827-57FD-4F88-8145-E5AB9A438355%40gmail.com
> <https://groups.google.com/d/msgid/django-developers/DF029827-57FD-4F88-8145-E5AB9A438355%40gmail.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/CAD9uRzc1GsR3Qs9JMv7AhvaCx-%3D2pbOYmwqTHhV9_a_XyeuE5g%40mail.gmail.com.

Re: Django Websocket Implementation Request

[Confi Yobo]

So it should not be expected in 3.0? @ Carlton Gibson

On Thursday, August 1, 2019 at 2:09:21 PM UTC+1, Confi Yobo wrote:
>
> This might be a little redundant as you would say but i see importance in 
> it.
>
> Django should come chipped in with websocket implementation rather 
> developers using third party libraries like django-channels which are 
> difficult and most at times have poor documentation. I have seen many cases 
> where developers want to build an application that requires websocket they 
> use another web framework.
>
> So in my opinion and that of few other developers i'v  seen i think 
> websocket feature should be added to django out of the box(something like 
> socket.io would make a lot of sense).
>

-- 
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/c3480723-f659-4ab0-9ca6-6389834b2d0f%40googlegroups.com.

Re: retriving all table from database

[Confi Yobo]

Like Adam Johnson has said, i think you should use stackoverflow or any
django facebook group for this post.

On Wed, Aug 7, 2019 at 5:16 PM vishal singh 
wrote:

> please anyone help me out its urgent..
>
> On Tue, 6 Aug 2019 at 19:56, vishal singh 
> wrote:
>
>> can anyone help me to pull all table name(schema wise ) from database
>> into  a dropdown.
>>
>> it will be best if someone give codesnippits or examples , how to do??
>>
> --
> 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/CAMSP2acrz51WLRuiiE5J3%2BbbFjd3f77BQi%3DP1%2B2Q8Zf5C4fegg%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/CAD9uRzc81vXNddgnw0%2BzLpvfmT5XEjT3%3DmbN%3DR-eyo5mswO6rA%40mail.gmail.com.

Re: Django Websocket Implementation Request

[Confi Yobo]

So it should not be expected in future release?

On Thu, Aug 1, 2019 at 9:14 PM Andrew Godwin  wrote:

> Unfortunately, from my perspective, websocket support is tricky enough
> that it's at least not on the short-term plan to bake into Django; it's
> used by only a small fraction of our users, and the Channels project is an
> official Django project, so it's as close as we can get so far. Future
> Django versions with async support will shrink Channels down significantly,
> and remove the need for it to be hosted differently, but the plan is still
> to have it as a separate package - we may write about it in the official
> docs, though.
>
> socket.io is even harder as it's fundamentally hard to scale - it needs
> stateful storage to aid in transferring connections, and this means it's
> really hard to have a single method that will work for everyone. Having
> "one right way to do it" is sort of a necessary prerequisite to having
> something in Django, and I just don't feel like it's there.
>
> Andrew
>
> On Fri, Aug 2, 2019 at 6:00 AM Confi Yobo  wrote:
>
>> And socket.io kind of implementation is one thing developers from js
>> like us are missing in django.
>>
>> On Thu, Aug 1, 2019 at 8:58 PM Confi Yobo  wrote:
>>
>>> Please consider it, cause the procedures of using third party websocket
>>> library (mostly for production) is cumbersome
>>>
>>> On Thu, Aug 1, 2019 at 2:22 PM Carlton Gibson 
>>> wrote:
>>>
>>>> Hmmm. I guess Channel is doing more than just websockets, but I've
>>>> always thought it had good docs... Anyhow...
>>>>
>>>> We'll see how the Async work goes, but a lot of channel will end up
>>>> being absorbed into Django itself. What, at this point, I guess that will
>>>> leave is "just" the websocket bit. (Maybe the Channel Layers bit... too but
>>>> maybe that would/could be separate.) Hopefully this'll make it more focused
>>>> and easier to follow
>>>>
>>>> But... I think websockets haven't turned out to be the One True Hammer
>>>> people thought. (They're not that popular actually, it seems...) So I'm not
>>>> sure we'd include support in core (vs keeping it in the third-party
>>>> package.)
>>>>
>>>> I guess something to revisit after 3.0.
>>>>
>>>> Kind Regards,
>>>>
>>>> Carlton
>>>>
>>>>
>>>> On Thursday, 1 August 2019 15:09:21 UTC+2, Confi Yobo wrote:
>>>>>
>>>>> This might be a little redundant as you would say but i see importance
>>>>> in it.
>>>>>
>>>>> Django should come chipped in with websocket implementation rather
>>>>> developers using third party libraries like django-channels which are
>>>>> difficult and most at times have poor documentation. I have seen many 
>>>>> cases
>>>>> where developers want to build an application that requires websocket they
>>>>> use another web framework.
>>>>>
>>>>> So in my opinion and that of few other developers i'v  seen i think
>>>>> websocket feature should be added to django out of the box(something like
>>>>> socket.io would make a lot of sense).
>>>>>
>>>> --
>>>> 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/c561814d-941c-446f-8707-c2ef1ce8170e%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/django-developers/c561814d-941c-446f-8707-c2ef1ce8170e%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/CAD9uRzdwK6Luj9cKZN70FgRRRO%2BtrybZ16XwB-FjWiPXZu9Eqw%40mail.gmail.com
>> <https://gro

Re: Django Websocket Implementation Request

[Confi Yobo]

And socket.io kind of implementation is one thing developers from js like
us are missing in django.

On Thu, Aug 1, 2019 at 8:58 PM Confi Yobo  wrote:

> Please consider it, cause the procedures of using third party websocket
> library (mostly for production) is cumbersome
>
> On Thu, Aug 1, 2019 at 2:22 PM Carlton Gibson 
> wrote:
>
>> Hmmm. I guess Channel is doing more than just websockets, but I've always
>> thought it had good docs... Anyhow...
>>
>> We'll see how the Async work goes, but a lot of channel will end up being
>> absorbed into Django itself. What, at this point, I guess that will leave
>> is "just" the websocket bit. (Maybe the Channel Layers bit... too but maybe
>> that would/could be separate.) Hopefully this'll make it more focused and
>> easier to follow
>>
>> But... I think websockets haven't turned out to be the One True Hammer
>> people thought. (They're not that popular actually, it seems...) So I'm not
>> sure we'd include support in core (vs keeping it in the third-party
>> package.)
>>
>> I guess something to revisit after 3.0.
>>
>> Kind Regards,
>>
>> Carlton
>>
>>
>> On Thursday, 1 August 2019 15:09:21 UTC+2, Confi Yobo wrote:
>>>
>>> This might be a little redundant as you would say but i see importance
>>> in it.
>>>
>>> Django should come chipped in with websocket implementation rather
>>> developers using third party libraries like django-channels which are
>>> difficult and most at times have poor documentation. I have seen many cases
>>> where developers want to build an application that requires websocket they
>>> use another web framework.
>>>
>>> So in my opinion and that of few other developers i'v  seen i think
>>> websocket feature should be added to django out of the box(something like
>>> socket.io would make a lot of sense).
>>>
>> --
>> 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/c561814d-941c-446f-8707-c2ef1ce8170e%40googlegroups.com
>> <https://groups.google.com/d/msgid/django-developers/c561814d-941c-446f-8707-c2ef1ce8170e%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/CAD9uRzdwK6Luj9cKZN70FgRRRO%2BtrybZ16XwB-FjWiPXZu9Eqw%40mail.gmail.com.

Re: Django Websocket Implementation Request

[Confi Yobo]

Please consider it, cause the procedures of using third party websocket
library (mostly for production) is cumbersome

On Thu, Aug 1, 2019 at 2:22 PM Carlton Gibson 
wrote:

> Hmmm. I guess Channel is doing more than just websockets, but I've always
> thought it had good docs... Anyhow...
>
> We'll see how the Async work goes, but a lot of channel will end up being
> absorbed into Django itself. What, at this point, I guess that will leave
> is "just" the websocket bit. (Maybe the Channel Layers bit... too but maybe
> that would/could be separate.) Hopefully this'll make it more focused and
> easier to follow
>
> But... I think websockets haven't turned out to be the One True Hammer
> people thought. (They're not that popular actually, it seems...) So I'm not
> sure we'd include support in core (vs keeping it in the third-party
> package.)
>
> I guess something to revisit after 3.0.
>
> Kind Regards,
>
> Carlton
>
>
> On Thursday, 1 August 2019 15:09:21 UTC+2, Confi Yobo wrote:
>>
>> This might be a little redundant as you would say but i see importance in
>> it.
>>
>> Django should come chipped in with websocket implementation rather
>> developers using third party libraries like django-channels which are
>> difficult and most at times have poor documentation. I have seen many cases
>> where developers want to build an application that requires websocket they
>> use another web framework.
>>
>> So in my opinion and that of few other developers i'v  seen i think
>> websocket feature should be added to django out of the box(something like
>> socket.io would make a lot of sense).
>>
> --
> 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/c561814d-941c-446f-8707-c2ef1ce8170e%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/c561814d-941c-446f-8707-c2ef1ce8170e%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/CAD9uRzcpxHkhZ5hNUu1xF73nTF%3DpR_qmyV8nJweEvQmivz57KQ%40mail.gmail.com.

Django Websocket Implementation Request

[Confi Yobo]

This might be a little redundant as you would say but i see importance in
it.

Django should come chipped in with websocket implementation rather
developers using third party libraries like django-channels which are
difficult and most at times have poor documentation. I have seen many cases
where developers want to build an application that requires websocket they
use another web framework.

So in my opinion and that of few other developers i'v  seen i think
websocket feature should be added to django out of the box(something like
socket.io would make a lot of sense).

-- 
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/CAD9uRzdHaQJdo3%2BBt%2BDzGfadvLTK%2B8gC7r2A75Q8a4L3dkN42Q%40mail.gmail.com.

Framework support suggestion

[Confi Yobo]

Please, I want to suggest a feature for django to have an eject
functionality just like laravel where a developer can use/change from one
webjs framework to another. And would have a package.json attached to each
project to ease development time.

My reason is that django is one of the best web development framework, the
only reasons I see people going with frameworks like laravel or ruby on
rails is them having flexibility; that is the ease of using webjs
frameworks.

-- 
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 post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAD9uRzdZxOUXzi%3DHwun50EXNaxW2JTN-ptEA68XbXhuc5TiTMA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: help regarding google summer of code

[Confi Yobo]

Sincerely, i really think django should have an integration for
frontend frameworks just like laravel(which with just eject you have
switched framework) or ruby. because the work around  is really
stressfull and sometimes hard to deploy.

On Sat, Mar 9, 2019 at 2:48 PM Muhammad Faraz
 wrote:
>
> in it its not clear that weather its worth working and also i agree to point 
> that django is lacking in integration  with frontend frameworks like laravel 
> and ruby and also i am not focusing on only vuejs it was only because right 
> now i have worked only on vuejs so what are your thoughts on this idea and a 
> little favor can i get guide to be accepted in django part of google summer 
> of code
>
> On Saturday, March 9, 2019 at 2:30:44 PM UTC+5, Carlton Gibson wrote:
>>
>> Hi Muhammad.
>>
>> There was a thread about this the other day:
>>
>> https://groups.google.com/d/topic/django-developers/KVAZkRCq9KU/discussion
>>
>> Have a read. (Check out Aymeric's blog post series linked in that thread.)
>>
>> Work around Django's staticfiles app would be good. It would ideally be 
>> general purpose, rather than just targeting one JS framework. (i.e. not just 
>> Vue.)
>>
>> Kind Regards,
>>
>> Carlton
>>
>>
>> On Saturday, 9 March 2019 04:05:56 UTC+1, Muhammad Faraz wrote:
>>>
>>> i am taking part first time in any open source project using summer of code 
>>> and i was think would the idea of integration django with front ends like 
>>> vuejs will it be acceptable front end support especially  for vuejs is 
>>> great in laravel due to watch package so i was thinking would proposal of 
>>> creating module that make the integration of font end frame works with 
>>> django easy will it be acceptable ?
>
> --
> 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 post to this group, send email to django-developers@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-developers.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/django-developers/5240ab50-ad65-4128-808c-4c60110b482c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 post to this group, send email to django-developers@googlegroups.com.
Visit this group at https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAD9uRzd7rOdKqjWzGLQanMbfxVSn1ukCvkciyS3Acnr23Q9-Qg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.