Sure, here's an example of what I mean. This is example code from the draft:
// Resize the widget to 400x300 px window.resizeTo( 400, 300 ); If you were to render a widget that used that code into a webpage inline it would resize the whole window, not itself. If you put it in an IFRAME or OBJECT element, you could not, as the rendering parent, know when it had called this and the call would do nothing. Either way it would not work. Just to clarify though -- is this draft actually more meant for the desktop world? Or is in-page online rendering (/webtop) also in the thought process? On 2/22/07, Marcos Caceres <[EMAIL PROTECTED]> wrote:
Hi Stephen, I don't see why you could not embed a widget into a page using, say, a HTML object element? In theory, the scope of the widget should not conflict with the window scope of the web page (same as an iframe or a flash movie). Could you please clarify your concerns a bit more? Kind regards, Marcos On 2/22/07, Stephen Paul Weber <[EMAIL PROTECTED]> wrote: > The Widgets draft <http://www.w3.org/TR/widgets/> seems to be meant for > offline widgets (ala Google Desktop). After inspection it does not seem > that it could even be 100% used because it defines a window object to be > accessible to the widget representing the widget's window (which conflicts > with the browser window object representing the browser window). > > -- > - Stephen Paul Weber, <http://webos.singpolyma.net/Widgets> -- Marcos Caceres http://datadriven.com.au
-- - Stephen Paul Weber, Amateur Writer
