- From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
- Date: Wed, 23 Sep 2009 15:22:28 +0200
- To: Arthur Barstow <art.barstow@nokia.com>, public-webapps <public-webapps@w3.org>
Hi Art, All, I would like to suggest to add to the agenda the point that appeared during the widgets testing event. It is related to the Widget Interface, View Modes and patterns. The comments below will be valid also as LC comments to the Widget Interface. The Widget Interface includes width and height attributes. On the other hand the View Modes Interfaces defines the ResolutionChangedEvent event. So we may have at least the following scenarios: Scenario 1: a) the dimensions of the viewport change. b) the ResolutionChangedEvent is fired. c) the widget gets the new dimensions from the event Scenario 2: a) the dimensions of the viewport change. b) the ResolutionChangedEvent is fired. c) the widget gets the new dimensions from the Widget interface (the widget object) Incorporating the onresize handler on the <body> element, we could have another scenarion: Scenario 2: a) the dimensions of the viewport change. b) the onresize handler is triggered. c) the widget gets the new dimensions from the Widget interface (the widget object) So we have 3 scenarios for 1 thing (notification about changed size and retrieval of the new dimensions). If we want to keep ResolutionChangedEvent, we have two methods of getting the new width/height: i) from the ResolutionChangedEvent ii) from the Widget interface Therefore I suggest picking up one of the following: 1. Drop the ResolutionChangedEvent, mandate onresize handler, keep width/height in the Widget interface. 2. Drop width/height from the ResolutionChangedEvent, ignore onresize handler, keep width/height in the Widget interface. 3. Keep the ResolutionChangedEvent, ignore onresize handler, drop width/height in the Widget interface. 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: public-webapps-request@w3.org [mailto:public-webapps-request@w3.org] On Behalf Of Arthur Barstow Sent: Wednesday, September 23, 2009 1:56 PM To: public-webapps Subject: [widgets] Draft Agenda for 24 September 2009 Voice Conf Below is the draft agenda for the September 24 Widgets Voice Conference (VC). Inputs and discussion before the VC on all of the agenda topics via public-webapps is encouraged). Please address Open/Raised Issues and Open Actions before the meeting: http://www.w3.org/2008/webapps/track/products/8 Minutes from the last VC: http://www.w3.org/2009/09/17-wam-minutes.html -Regards, Art Barstow Logistics: Time: 22:00 Tokyo; 16:00 Helsinki; 15:00 Paris; 14:00 London; 09:00 Boston; 06:00 Seattle Duration = 90 minutes Zakim Bridge = +1.617.761.6200, +33.4.89.06.34.99 or +44.117.370.6152 PIN = 9231 ("WAF1"); IRC channel = #wam; irc://irc.w3.org:6665 Confidentiality of minutes = Public Regrets: Marcos, Marcin, Josh Agenda: 1. Review and tweak agenda 2. Announcements a. News/summary from the Widget Testing event http://www.w3.org/2008/webapps/wiki/TestWorkshop2009 3. Widget Interface spec: proposal to publish LCWD #2 <http://dev.w3.org/2006/waf/widgets-api/> 4. Access Requests Policy (WARP) spec: comment period ended Sept 20; review comments <http://dev.w3.org/2006/waf/widgets-access/> <http://www.w3.org/2006/02/lc-comments-tracker/42538/WD-widgets- access-20090804/> 5. URI Scheme spec: status of LC publication <http://dev.w3.org/cvsweb/2006/waf/widgets-uri/> 6. View Modes Media Features spec: proposal to publish FPWD <http://dev.w3.org/2006/waf/widgets-vm/vm-mediafeature.src.html> 7. View Modes Interfaces spec: Arve (from IRC) "the bit that troubles me is rotation" <http://dev.w3.org/2006/waf/widgets-vm/vm-interfaces.src.html> 8. AOB ________________________________________ 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 Wednesday, 23 September 2009 13:23:19 UTC