||View All MessagesBack to WebFX|
Isn't a plugin truly just an OO thing regardless of where this design concept is implemented? A PLugin has to do with runtime type reflection, late binding to an object and interface implementation. Any application can be built to allow for a "plugin" to execute if that plugin implements appropriate interfaces and some how makes itself known to the calling application. Why would it matter what particular task the calling applicaton was performing or what type of information the calling application was passing to the "plugin" to process? So in the case of an IE behavior the behavior implementes a few know interfaces and gets a reference to the parent DOM. Why is this any different than me writing a plugin for an ecommerce site where I implement an interface that receives a reference to a shopping cart?
Sent: September 5, 2003
Subject: Re:Eoalas patent: the end of DHTML as component platform?
MS says it is going to have to change IE to comply with the Eolas patent case. Scriptlets have been targeted, so I assume element behaviors are in violation as well. So much for custom tags and HTML extensibility. Which is a shame, because this was (imo) dhtml's best shot at becoming a true application platform...