Indeed; however as the difference is so small in practice, we thought
it worthwhile to pursue a solution based on the W3C work, rather than
use a proprietary solution. At the spec level, it only really requires
one extra API method.
S
On 28 Jan 2009, at 13:30, Marcos Caceres wrote:
Hi
On Thu, Jan 29, 2009 at 4:55 PM, Scott Wilson
scott.bradley.wil...@gmail.com wrote:
Indeed; however as the difference is so small in practice, we thought it
worthwhile to pursue a solution based on the W3C work, rather than use a
proprietary solution. At the spec level, it only really requires
Hi Marcos,
A widget engine, in our use of the term, is a server-side web
application that publishes widgets and implements the Widget API as a
web service accessible via AJAX. As it stands all browsers will block
any cross-domain Javascript requests, and this will apply in all cases
Hi Scott,
On Wed, Jan 28, 2009 at 9:51 AM, Scott Wilson
scott.bradley.wil...@gmail.com wrote:
Hi Marcos,
A widget engine, in our use of the term, is a server-side web application
that publishes widgets and implements the Widget API as a web service
accessible via AJAX. As it stands all
Hello Scott Marcos,
First I am pleased to hear that you are interested in the proxifying
mechanisms. When you say Marcos:
This might not be too much of an issue so long as the author
declares which domains they want to communicate with. That way, the
widget engine can allow access to the
Hi Stéphane,
On Tue, Jan 27, 2009 at 2:20 PM, Stéphane S. stephane.s...@epfl.ch wrote:
Hello Scott Marcos,
First I am pleased to hear that you are interested in the proxifying
mechanisms. When you say Marcos:
This might not be too much of an issue so long as the author declares
which
On Sat, Jan 17, 2009 at 8:02 PM, Scott Wilson
scott.bradley.wil...@gmail.com wrote:
Hi Marcos,
The engine/platform has to provide a means for a widget to access
externally-offered web services without breaking the same origin policy of
the browser. To do this both projects have implemented
Hi, Scott!
On 1/14/09 7:55 PM, Scott Wilson scott.bradley.wil...@gmail.com wrote:
All,
Two EU-funded projects have implemented the draft W3C Widgets
specifications, both the packaging and API parts.
This is fantastic to hear.
What is notable from these projects have been the
On 17 Jan 2009, at 05:26, Marcos Caceres wrote:
In addition, both projects wanted to add additional functionality to
the API; this has included state coupling and shared states to enable
richer interaction between (a) widgets in the same user context and
(b) instances of the same widget from
All,
Two EU-funded projects have implemented the draft W3C Widgets
specifications, both the packaging and API parts.
What is notable from these projects have been the adaptations used to
enable widgets conforming to the draft to be used in a web environment
rather than in a dedicated
10 matches
Mail list logo
