![]() | |
#51
| |||
| |||
|
|
Tony Gravagno wrote: Luke Webber <luke (AT) webber (DOT) com.au> wrote: But I suppose you're right about one thing-if you use an applet, it would work on all browsers? Or not? If not, what's the advantage? If so, I guess I should look into it. Yes, the advantage is that they work on all browsers. The disadvantage is that Microsoft shipped a lot of copies of IE with no JVM, so any client without Java needs to download it. The other disadvantage is that Microsoft also shipped a lot of copies of IE with their own, ageing JVM. I'm not sure which is worse, no Java or Microsoft Java. Give me a break. MS Java is v1.4.x of the Sun JVM. That's 1.1.4. I don't like it and try not to use it as much as possible, but it's either there or it's easy to get. It's either there or it's /not/ so easy to get. It's easier to get the Sun JVM these days, because Microsoft have made changes. or a while there the Microsoft JVM download was withdrawn entirely. (Use Sun whenever possible!) In an app, you let the browser detect if there is a Java, which level it's at, and then you either tell the user to upgrade or you support what's there - just like with any app. If you want to use Java, do what everyone else does, provide a link to the Sun download page, say "click here" to install, etc. The typical Jane Internet user will download and install all sorts of crap on to their systems, it's not unreasonable to ask them to install Java. And if they don't have the ability to install Java of all things then give them a plain browser-independent web page and skip the glitz entirely. People waste entirely too much time the absolute lowest common denominator. I think the best use of applets is for rich GUIs for clients using a service that they actually need. It's a mist to bung applets into web pages that are going to be hit by a lot of casual drop-ins, because they /won't/ install a plugin just to view your site. I know I wouldn't. Luke |
#52
| |||
| |||
|
|
"murthi" <c_xyz_murthi (AT) seeing_xyz_green (DOT) net> wrote: Didn't make myself clear. This is an artist's website, no server, no database, just a set of pages with "thumbnails"... ... I have now spent 19 hours on finally getting it to work on 5 browsers. Wish someone were paying. Some artist is paying $5 per month for a website so that you can spend 19 hours of your time writing client-side code that's cross-browswer compatible. Chandru, you're brighter than this but maybe you just need to be reminded. (I think many of us get caught thinking inside the box when we let end-users define the box dimensions for us.) Don't cater to someone who wants everything from you on a zero budget. If the task is to get a dynamic site then the solution is at least to have some dynamics on the web server. Almost every web host on the planet supports Perl and PHP, maybe with free MySQL. The Win32 hosts cost much less than they used to and they support ASP, ASP.NET, SQL Server, etc. These services are not expensive, as little as $8/month for an excellent *nix/BSD host or maybe $15/month for Win32. I wouldn't be surprised at all if your artist friend is paying a lot more and utilizing none of the features available... Good luck. T |
![]() |
| Thread Tools | |
| Display Modes | |
| |