Aztec,

Just look in the dynamicforms/templates folder: all templates for input fields are built using this tag in its various forms. There's plenty of examples there. And yes, it's exactly what you asked for.

LP,
Jure

On 29. 01. 21 09:18, Aztec Rabbit wrote:
Curtis - This is nested block right? what i want is like tag include (can be called more than once) but with children.

Jure - I've read the documentation, can you give me a sample code? I am confused

Hmmm, but i think this feature is very useful (for card, container, wrapper, and anythink with different content) and each component can be included in other components, thats awesome. I think this feature should be in django core, but, yes, I understand.

On Friday, January 29, 2021 at 11:27:26 AM UTC+7 jure.er...@gmail.com wrote:

    Source is here
    
(https://github.com/velis74/DynamicForms/blob/master/dynamicforms/templatetags/dynamicforms.py
    
<https://github.com/velis74/DynamicForms/blob/master/dynamicforms/templatetags/dynamicforms.py>

    - see at end of file), documentation will follow shortly as we near
    1.0 release (right now it's pretty pathetic, but it is there at
    readthedocs), but there are examples & unit tests included showing
    most of the functionality.

    As far as I understood the feature wasn't perceived as something that
    would improve Django as a whole. There is that thing we need to be
    wary of - feature creep. Generally added features are preferred to be
    provided as third party libraries. Easier to maintain, easier to find
    that exact match you're looking for. Just look: Curtis also pointed
    you to his own version, a bit different that ours, but maybe it would
    suit you more?

    LP,
    Jure

    On Thu, Jan 28, 2021 at 6:52 PM Aztec Rabbit <ars...@gmail.com>
    wrote:
    >
    > Is there a link to the documentation or source code to the
    library you created? And can i know why it is not accepted?
    >
    > On Thursday, January 28, 2021 at 9:34:03 PM UTC+7
    jure.er...@gmail.com wrote:
    >>
    >> We have just created a tag like that in our dynamicforms
    library. It's called "extendtemplateblock". Feel free to use or
    copy, but it doesn't look like it's going to be accepted in Django
    itself.
    >>
    >> We tried to keep API similar to the "include" tag, so it should
    be easy to use.
    >>
    >> You can choose to only pull one block from your extended
    template ("block" parameter) or define any of the blocks in it
    using "block" nested blocks.
    >>
    >> LP,
    >> Jure
    >>
    >> On 28. 01. 21 07:33, Aztec Rabbit wrote:
    >>
    >> Hi,
    >>
    >> I think template tag like in JSX is very useful, for example:
    >>
    >> > card.html
    >>
    >> <div>
    >> <h1>{{ title }}</h1>
    >> <p>{{ component.children }}</p>
    >> </div>
    >>
    >> > index.html
    >>
    >> {% component './card.html' with title='Foo' %}
    >> Bar
    >> {% endcomponent %}
    >>
    >> --
    >> 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-develop...@googlegroups.com.
    >> To view this discussion on the web visit
    
https://groups.google.com/d/msgid/django-developers/ff75ddef-2267-44f5-89f7-9b8ebf1460efn%40googlegroups.com
    
<https://groups.google.com/d/msgid/django-developers/ff75ddef-2267-44f5-89f7-9b8ebf1460efn%40googlegroups.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-develop...@googlegroups.com.
    > To view this discussion on the web visit
    
https://groups.google.com/d/msgid/django-developers/0cb2a1f6-9070-4875-90e2-eb6da241ea82n%40googlegroups.com
    
<https://groups.google.com/d/msgid/django-developers/0cb2a1f6-9070-4875-90e2-eb6da241ea82n%40googlegroups.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 <mailto:django-developers+unsubscr...@googlegroups.com>. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/109df365-750f-483d-8043-cf8c7c360c5en%40googlegroups.com <https://groups.google.com/d/msgid/django-developers/109df365-750f-483d-8043-cf8c7c360c5en%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/9b8c9ecc-9a68-e346-0b98-8339002e9e5b%40gmail.com.

Reply via email to