The javascript deployment library is specifically meant to address applets that only work in some browsers. Lots of browsers have bugs in the way they interact with applets. Our deployment library is designed to work around these bugs. If you restrict your users to IE7/ FF3 + JavaSE 6u10 then you probably don't need this library. But to support anything outside of this matrix means dealing with the reality of modern browsers, and having a javascript library take care of this for you is much more desirable than doing it by hand. This is the same reason that libraries like jquery and prototype exist.
- J On Nov 25, 2008, at 8:44 AM, Casper Bang wrote: > > Well pardon me for wanting a clean, clear and consistent deployment > model in my browser, without necessarily needing JavaScript to > generate custom HTML - Flash doesn't need that after all. I can only > guess you never experienced an applet which only works in some > browser/ > OS configurations due to convoluted deployment? > > /Casper > > On Nov 25, 4:07 pm, BoD <[EMAIL PROTECTED]> wrote: >> mbien wrote: >>> On Nov 24, 7:53 pm, Casper Bang <[EMAIL PROTECTED]> wrote: >> >>>> What's the purpose of reviving the applet tag which was >>>> deprecated by >>>> W3C 9 years ago?http://jfx.wikia.com/wiki/Applet_Example >> >>> object tag works too... >> >> But more importantly: who cares ? :) >> <applet>, or <object>, or <whatever>... Is this really worth >> debating? >> >> BoD > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
