Re: Re: JavaScript Question relating to netWindows
Alex Russell <[email protected]> Mon, 19 Jan 2004 12:08:37 -0800
| Newsgroups | gmane.comp.windows.devel.netwindows |
|---|---|
| Organization | netWindows.org |
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 19 January 2004 8:43 am, Roy Weston wrote: > I was thinking more about supporting multiple markups at the same > time such that if netWindows detected a browser that supported XUL, > it would render what it could in XUL, otherwise 'degrade' to > netWindows decorated DOM Nodes, and finally 'degrade' to the > original page markup. The same with SVG, i.e. XUL renderer -> SVG > renderer -> netWindows Decorated renderer -> plain old page. I guess this is a logical extension of what I'd been considering. Right now, most NW widgets have a "degradeable" inline constructor which allows them to be rendered as workable (if not pretty) parts of a UI when NW isn't avaialable because of whatever limitation. For things like SVG and XUL , I really see the big benefits there being angled lines (think ER diagrams). Beyond that, there are interesting applications to our object model, but I don't think any of them are quite as pressing. What you're talking about would require some detection engine to figure out what rendering we'd use at any given time. Not hard I'd think, and we could easily extend the __widget__ registration mechanism to support it...hrm...I think I'm starting to see a plan = ) - -- Alex Russell [email protected] BD10 7AFC 87F6 63F9 1691 83FA 9884 3A15 AFC9 61B7 [email protected] F687 1964 1EF6 453E 9BD0 5148 A15D 1D43 AB92 9A46 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (Darwin) iD8DBQFADDlFoV0dQ6uSmkYRApVKAJ9yAKQ2ypCxtVKa0lvfgj4qBle0nQCdHF42 +iC72LxehcWPGz99FVerkVg= =cnrG -----END PGP SIGNATURE----- _______________________________________________ The netWindows developers list: [email protected] http://netwindows.org/mailman/listinfo/devel_netwindows.org