Hello Sir, On Saturday, March 17, 2018 at 5:39:34 AM UTC+5:30, Tom Forbes wrote: > > Hey Manasvi, > I don't have any say in the choice of a GSOC student, but I'd like to add > my two cents nonetheless. > > I can see the logic behind your proposal, but I'm skeptical about the > usefulness of such a project. Libraries that implemented something similar > to this have come and gone, and got good reason, they where not very > practical and other solutions where much easier to use. > > In the time since frontend frameworks have proliferated and JavaScript has > become much more mature. Anything we do in this space seems like it will be > dead on arrival compared to something like React or Ember, which already do > this but with huge huge advantages over your approach. > > In my humble opinion anything in this space will have to treat JavaScript > as a first class citizen - i.e something that makes the interoperability > between a JavaScript frontend and a Django backed easier would have some > benefits, but generating HTML in pure python on the backend by writing > components in Python does not have a bright future IMO. > > Tom > > On 16 Mar 2018 22:36, "Manasvi Saxena" <[email protected] <javascript:>> > wrote: > >> Hello Sir, >> >> Okay, so the idea is to render HTML by generally defining it in Python. I >>> could've sworn that I'd seen something like this years ago, but I'm failing >>> to find it. That stated, I think this is basically a generating version of >>> BeautifulSoup (https://www.crummy.com/software/BeautifulSoup/bs4/doc/) >>> as opposed to a parsing version. >>> >>> It's roughly like the Storm ORM (https://storm.canonical.com/) but for >>> HTML instead of database queries. >>> >>> It's interesting, but I'll ask if one can get 90% of the functionality >>> from xml.etree, which is in the standard Python Library. >>> >>> import xml.etree.ElementTree as ET >>> >>> a = ET.Element('p', style='{color: red;}') >>> a.text = "hello world" >>> ET.dump(a) # will match yours >>> >>> Note that this gets even weirder with something like "<p>hello <i>ignore >>> this</i> world</p>". >>> >>> b = ET.Element('p') >>> b.text = "hello " >>> c = ET.Element('i') >>> c.text = "ignore this" >>> c.tail = " world" >>> b.append(c) >>> ET.dump(b) # will match above >>> >> >> >> I'm sure xml.etree has its drawbacks which I will improve in my library. >> The whole idea here is to bring python closer in the picture of >> generating HTML content. >> Its applications are vast and not only limited to this. If time permits I >> intend to write a complete framework like Bootstrap for python where things >> like cards, navbars etc will be inbuilt and purely written on the basis of >> my library. >> And that is the new feather I intend to add to Django's hat. >> Just like we have some inbuilt 'forms' in Django we'll have a lot of >> other front-end related objects written in python and easily manipulative. >> And thus I intend to extend Django's reign in the front-end domain as >> well. And make it a full-stack framework. >> Surely designing is something that changes very frequently in today's >> world but if this is successfully implemented we can bring developers from >> front-end world to contribute to it too. >> Logic + Design. >> >> Regards, >> Manasvi Saxena >> >> -- >> 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 [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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/2cf482cc-0f2e-4182-ae34-951a74b43731%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-developers/2cf482cc-0f2e-4182-ae34-951a74b43731%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >
I haven't fully submitted my GSoC proposal yet hence I understand your concern regarding javascript. For including javascript I intend to use libraries such as Brython and Pyjs in my project. The framework I'll be building in the end for aiding in front-end will comprise of this feature. Please let me know what you think of the proposal now. Regards, Manasvi Saxena -- 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 [email protected]. To post to this group, send email to [email protected]. 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/49cbb6f1-f93b-43ae-a1d3-20c085021c46%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
