I made some test to see if Aaron request for a markup file with
fragments only can be supported. There doesn't seem to be a simple
solution. A page referencing fragments defined in a Panel which is
also added to the Page defnitely doesn't work. We'd need a more
flexible approach to get the fragments markup stream.

this is exactly the usecase for panels not fragments.


Yeah, but a good framework should not get in the way of what you are trying to do, right?  I spent 2-3 hours trying to figure out a way to do this with fragments :)
Others will probably hit the same wall someday.  Panels did work for my solution, but in this situation loading fragments as a "standalone component" would have been
a more elegant solution for me.

well, what you are really doing is abusing the api :) fragments arent meant to be standalone pieces of markup, they are a convinience feature for people to embed repeating but non-reusable pieces of markup into parent's markup file. they are really meant to express "child markup" relationship.

since you are not adding the panel whose markup the fragment's are in into the hiearachy you are breaking that child relationship.

-Igor

Reply via email to