Hello Sir, On Thursday, March 15, 2018 at 11:29:46 PM UTC+5:30, Aymeric Augustin wrote: > > Hello, > > 2018-03-15 14:24 GMT+01:00 Manasvi Saxena <[email protected] <javascript:> > >: > >> Think of this library as a bridge between Python and HTML, you don't need >> to know the syntax of HTML, just need to know which function of the library >> creates what output. After you have created the content of your page just >> pass it to a function in a list and you have your HTML page. >> Have a look at the prototype and let me know what you think of it. >> > > Thanks for the example. > > To be honest the sample.py file doesn't strike me as a convenient way to > write HTML. > > I think someone who's confortable writing Python code should be able to > learn the HTML syntax very quickly. > > <tag attr1="value1" attr2="value2">content</tag> isn't more complicated > than pyhtml.tag("content", attr1="value1", attr2="value2"), is it? > > This idea is not a good fit for Django. Perhaps it can be a learning > experiment for you, though? > > Best regards, > > -- > Aymeric. >
After keeping in mind your valuable feedback I have decided to change my project proposal. I'm halfway through my formal proposal which contains the details required as per the guidelines provided on Django GSoC page. But would like to discuss with you the idea first for your valuable feedback. Django templating engine and jinja2 while being very efficient in their way still have some drawbacks. 1)Not enough freedom to implement logic in a template. Python functions can't be called inside the template. 2)Once the templating language syntax is applied to the template it creates readability issues for the front-end developer. This leads to two different development branches. If a front-end developer changes some of the parts in his template then the back-end developer has to make amendments manually each time. His job is not finished even after he has generated the content of the page dynamically. 3)The time required by the engines to generate the HTML content is more for large data. First, the QRM fetches the data from the database, then templating engine populates it on the template. I intend to first generate the HTML content according to the requirements of the developer using his programming skills in an exact way required and then place it inside the template. The library will have functions exactly similar to the HTML tags so that a python developer can reproduce the HTML code made by the front-end developer. Or a person with some knowledge of HTML or following the documentation of the library can design the page according to his requirement. The main benefit of doing this is that freedom in generating any HTML content can be given to the developer. I'm not experienced enough to comment on any of the drawbacks of templating engine but I listed these points based on my own personal experience I got from some of my past projects. And hence I need to know your views on this and would really appreciate if you could suggest me anything from your side. 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/cfc4f1b6-25ed-42f6-81ca-b3cbf9133dce%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
