[EMAIL PROTECTED] wrote: >>The plugin module for MSIE is cool. And with the javascript access to the >>browser's DOM tree, interesting things can be done. >> >> >> > >Yes it is cool but MSIE is such a security sive that my company, and a >growing list of others, have banned the use of IE. I would really like to >see development of the Plugin module for Mozilla/FireFox take place. > >Paul > > Are you new here? :-) According to some ppl Mozilla simply does not work properly, nor does 50% of Flash work :-) Well - no need to start browser war here, RT's strategy is clear - start with IE, produce stable release and follow with NS type plug-in. In their announcement, they stated NS plug-in will follow, they just did not clarified when.
But - I share your sentiment ..... plug-in will not imo gain enough of acceptance if NS type plug-in don't come soon enough = at least imo this year. Most potential developers (not talking intranets here) will come from camps caring about alternatives pretty much. For many youg ppl IE as a browser is simply non-existant, but of course my pov is biased, as I come from computer related user camp, where alternatives are more often used than with average home user. Anyway - plug-in is cool even in its current form, just not stable for 1.0 release (still no working proxy support, random crashes reported). I think once RT solves such issues, they will start looking into NS plug-in once again, as we have some cool folks here who are fluent with C/C++ and who offered RT help to set-up Mozilla dev. environment, which according to some ppl on web is a bit chaotic sometimes ... One important issue which has to be solved in the future though is multiple plug-in instances per page, or banners are not possible. I hope RT keeps that request in mind to later not introduce incompatibilities once such support is added. -pekr- -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
