To further refine my question: is there any way to pass in a mix of
IOlists and rendered {ewc} tuples to a view function? Can we turn
{data} into this?
On 08 Nov 2007, at 20:22, David King wrote:
>
> What is the difference between returning this:
>
> ["SomeString",
> {ewc,...},
> [<<"Some">,["IO","List"]]]
>
> And this:
>
> {data,["SomeString",
> {ewc,...},
> [<<"Some">,["IO","List"]]]}
>
> (Other than that the latter doesn't work.) In either case, a view
> function like this should work:
>
> <%@ view([FirstString,RenderedComponent,SomeOtherString]) %>
> ...
>
> The problem is that I can't always just return a {data} tuple or a
> [{ewc}] list, I have to differentiate between one that includes
> rendered components and one that doesn't, and I worry that the
> "detection" between the two may fail when I mix them (for instance,
> maybe I want to render a page with a title and a list of items; the
> title is a literal string, but the items are rendered {ewc}s). Am I
> missing an overarching design that requires a difference between
> passing a view function a list of rendered components and a list of
> iolists? Is there any way that we can get {data} to look at its
> arguments and see if they are {ewc}s, and render them just like it
> would if I returned a [{ewc}], so that I can always return a {data}?
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"erlyweb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
