Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Message from discussion <title>s and other non-component data
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
David King  
View profile  
 More options Nov 17 2007, 9:18 pm
From: David King <dk...@ketralnis.com>
Date: Sat, 17 Nov 2007 18:18:11 -0800
Local: Sat, Nov 17 2007 9:18 pm
Subject: Re: [erlyweb-list] Re: <title>s and other non-component data

>> Then what does my view function look like? [...]
> I don't think that the view function should receive the meta Vals. The
> purpose of the {meta, Val} feature is to pass values "up" to the
> 'phased' Fun. If you need to pass the same value to the view function
> (and I can't really think of a scenario where you would), you can add
> it again as a {data, Data} tuple. Maybe to make things clearer,
> instead of adding {meta, Val} values to the list you return from a
> controller function, you would return a tuple such as
> show(A) ->
>  ...
>  {meta, [Val1, Val2], [{data, Data}, {ewc, ..}... ]}.

I like it. But I'm starting to think that {meta} is a bad word for  
it. It's not very descriptive of what's actually happening. Of  
course, I don't have any better suggestions :) Maybe  
{with_properties} or {set_properties} or something?

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.