RE: [widgets] Draft Agenda for 24 September 2009 Voice Conf

Hi Marcos,

>>I'm still confused as to why we can't keep both. Is it because of redundancy?
Yes. My personal opinion is that one source of the same information would be enough. It could be a kind of optimization.

Thanks,
Marcin

Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452  |  Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanclik@access-company.com

-----Original Message-----
From: marcosscaceres@gmail.com [mailto:marcosscaceres@gmail.com] On Behalf Of Marcos Caceres
Sent: Wednesday, September 23, 2009 6:15 PM
To: Marcin Hanclik
Cc: Arthur Barstow; public-webapps
Subject: Re: [widgets] Draft Agenda for 24 September 2009 Voice Conf

On Wed, Sep 23, 2009 at 4:36 PM, Marcin Hanclik
<Marcin.Hanclik@access-company.com> wrote:
> Hi,
>
> One more comment to the below:
> There is one use case not handled by the below scenarios:
> In case the width/height are dropped on the Widget interface, the widget would not know the initial dimensions.
> E.g. in Win32 each new window get WM_SIZE event with the initial width/height.
> However, I am not sure whether we should mandate the ResolutionChangedEvent to be used for the initial viewport size.
>
> So I would opt for keeping the ResolutionChangedEvent, dropping width/height on the ResolutionChangedEvent, and keeping width/height in the Widget interface.
>

I'm still confused as to why we can't keep both. Is it because of redundancy?


--
Marcos Caceres
http://datadriven.com.au


________________________________________

Access Systems Germany GmbH
Essener Strasse 5  |  D-46047 Oberhausen
HRB 13548 Amtsgericht Duisburg
Geschaeftsfuehrer: Michel Piquemal, Tomonori Watanabe, Yusuke Kanda

www.access-company.com

CONFIDENTIALITY NOTICE
This e-mail and any attachments hereto may contain information that is privileged or confidential, and is intended for use only by the
individual or entity to which it is addressed. Any disclosure, copying or distribution of the information by anyone else is strictly prohibited.
If you have received this document in error, please notify us promptly by responding to this e-mail. Thank you.

Received on Thursday, 24 September 2009 07:03:07 UTC