Apple

I may have misinterpreted the intention?

I was concerned with this rule:

smartAttribute.userInfo.d2wComponentType = displaySmallIntNumber => componentName = "ERD2WDisplaySmallInteger"

Which implies setting a component name in the model?

Apologies if I'm misinterpreting this.

--
Dr. Mark Wardle
Consultant Neurologist, Cardiff, UK
(Sent from my mobile)

On Saturday, 5 May 2012 at 16:42, Ramsey Gurley wrote:

I wouldn't put component names in the model. I hope no one thought I suggested it :-)

I think specifying what value the attribute holds when the actual attribute value is very broad (password vs regular string) is perfectly acceptable though.

Ramsey

On May 4, 2012, at 10:28 PM, Mark Wardle wrote:

Isn't there a difference between including additional information about a value (eg isLarge as in Anjo Krank's example) and putting in a pseudo-component name?

The former clearly belongs in the model, the latter in the view.

I'd tend to use the user info as hints to refine the description of the model so that the view's rule engine can make better defaults when the hints are provided in the model.

Doesn't anything else break MVC, even if you use pseudo-component names? Particularly if you have keys named d2w-xxxx in your model!

--
Dr. Mark Wardle
Consultant Neurologist, Cardiff, UK
(Sent from my mobile)

On Thursday, 3 May 2012 at 18:33, David Holt wrote:

References:
	>Default D2W Rules for Components (From: David Holt <email@hidden>)
	>Re: Default D2W Rules for Components (From: Mark Wardle <email@hidden>)
	>Re: Default D2W Rules for Components (From: Ramsey Gurley <email@hidden>)
	>Re: Default D2W Rules for Components (From: Mark Wardle <email@hidden>)