W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > April 2007

Re: Architectural Ideas

From: Sean Owen <srowen@google.com>
Date: Thu, 19 Apr 2007 12:44:15 -0400
Message-ID: <e920a71c0704190944u5ec1f334oa88f6742cdffb367@mail.gmail.com>
To: "Abel Rionda" <abel.rionda@fundacionctic.org>
Cc: public-mobileok-checker@w3.org

I virtually completely agree with what you describe here, if I
understand it correctly.

Jo's idea was to make every "real" mobileOK Basic test depend
completely on the preprocessor results document. While it adds a
little overhead it is a tidy design.

But yes the preprocessor has to do a lot of work to prepare for this.
It has to run tests which are not strictly mobileOK Basic tests, like,
parsing and verifying a CSS stylesheet. Is this what you mean by
GrammarTest and non-declarative tests?

Yes, I think all of this logic goes into the Preprocessor and related
classes like the HTTPXXXXResource classes. My intention was to only
subclass TestImplementation to implement the "real" mobileOK Basic
tests. That's why the one method that they all implement takes in the
PreprocessorResults object.

PS you are going to commit some code changes? I'm personally fine with
that as I believe we're very much in agreement and sometimes its
easiest to start looking at each others' changes to sync up on the
remaining details.

Sean

On 4/19/07, Abel Rionda <abel.rionda@fundacionctic.org> wrote:
>
>
>
>
>
>
>
>
> Hi,
>
>
>
> We have  attached a diagram about the architecture and
>
> given some ideas about Preprocessor task.
>
> We can review this during the call today.
>
>
>
> Regards
>
Received on Thursday, 19 April 2007 16:44:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:13:03 GMT