Mailing-List: contact isis-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: isis-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of dkhaywood@gmail.com
 designates 74.125.82.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:reply-to:organization:user-agent:mime-version
         :to:subject:references:in-reply-to:content-type;
        b=tKo3bMaiL4V+L3ZZMCy2svxBL+aaa8VaOHZHQWrknoydx+obxpKvJUDWQi2Zr+WibH
         c5OIYh2AdTHp7Un8ooYdYfmiHeJ8MlLw8g7BKHZZbguV/l+wuypDFeVpq/Y+pP0/05/q
         7wk0X4Ix4hCHWXHetcjGvuETngb0ImHVWAEyY=
Message-ID: <4D07E97A.4090609@gmail.com>
Date: Tue, 14 Dec 2010 22:02:34 +0000
From: Dan Haywood <dkhaywood@gmail.com>
Reply-To: dan@haywood-associates.co.uk
Organization: Haywood Associates Ltd.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US;
 rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: isis-dev@incubator.apache.org
Subject: Re: Reports
References: <A8C4F876-FB1E-4004-B486-5E361FF7B253@mycosystems.co.uk>
 <4D07C3E0.4050907@gmail.com>
 <C8311AC6-F06B-4E00-9315-ACA2167529BC@mycosystems.co.uk>
In-Reply-To: <C8311AC6-F06B-4E00-9315-ACA2167529BC@mycosystems.co.uk>
Content-Type: multipart/mixed;
 boundary="------------060806020308090608070909"

--------------060806020308090608070909
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


On 14/12/2010 21:01, Mike Burton wrote:
> Many thanks Dan,
>
> My Report class does similar to PdfRenderService&  XlsGenerationService etc, I should probably spilt it into separate classes, with adapters for each platform (seam, jsf, servlet...) I could then see generation&  customisation of layouts working in a similar way to Facelets Views, so will give it more thought.
Looks like we're on the same page, interested to see what you come up with.


> Might there be a better name for it than "view model" btw?
I called it "process object" pattern in my book, though that was really 
only half the story since I was talking mostly about input of data for a 
specific use case, eg a wizard.  A name I had come up with for an object 
designed for output was "report object".

But the term "view model" seems to be catching on, at least in the .NET 
world, so I'd be happy to adopt it to instead of either of the above terms.


> Mike
> ( iPhone)
>
>

--------------060806020308090608070909--