You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
it would be nice if sailfish could be used to build reusable parent containers that are completely independent of their child html. This would require a new token to start a block which accepts child elements, a new token to end the block of child elements and a new token to actually insert the children. In my examples i'm just going to use [ for start of "child block" ] for end of child block and ^ for insert children here (these tokens might be problematic, but that's mainly bikeshedding)
Something along the lines of:
In the file main.stpl:
is there interest for this feature? This seems as something very useful to make sailfish a lot more flexible. If there is interest for this i would be willing to try implementing this. There are obviously some questions left on how this should be implemented, but i already have some ideas for this.
Thanks :)
The text was updated successfully, but these errors were encountered:
Hi,
it would be nice if sailfish could be used to build reusable parent containers that are completely independent of their child html. This would require a new token to start a block which accepts child elements, a new token to end the block of child elements and a new token to actually insert the children. In my examples i'm just going to use
[
for start of "child block"]
for end of child block and^
for insert children here (these tokens might be problematic, but that's mainly bikeshedding)Something along the lines of:
In the file
main.stpl
:In the file
template_with_children.stpl
which is used to render TemplateWithChildren:This would then render:
is there interest for this feature? This seems as something very useful to make sailfish a lot more flexible. If there is interest for this i would be willing to try implementing this. There are obviously some questions left on how this should be implemented, but i already have some ideas for this.
Thanks :)
The text was updated successfully, but these errors were encountered: