[quoted text, click to view] Tom Leylan wrote:
> I'm so confused... :-)
>
> Perhaps somebody would point me in the right direction. I was planning to
> write a simple applet to display database records. It's a large database
> (in terms of number of rows) but it isn't complex. It only has a couple of
> tables and the data is read-only. I program for a living, I'm familiar with
> .Net and some time ago I wrote some Java applets so I thought rather than
> use ASP or ASP.Net I thought I would create an applet.
>
> Due to limitations on the website I have available I won't have SQL-Server.
> I can easily configure it (the site) to use MS-Access but if there is an
> alternative I'd like to hear about it. I might have MySQL available I'm
> going to check.
>
> If I write this thing in J# will the majority of people be able to run it?
> People using IE only? Do they have to download/install the .Net runtime?
> Would it run in Netscape or another browser? Am I doing the right thing :-)
>
> I can't quite figure out where J# fits into things. The application code
> will download from a website right? No direct installation required, etc.,
> etc.? Is it generally operating like Java?
>
> Thanks,
> Tom
>
>
>
In either case, the users may have to download software:
J# browser control:
- .net framework
- j# redistributable
- j# broswer control (not sure if this includes j# redistributable
As far as I know such an applet will only work in IE on Windows, I could
be wrong.
Java:
- Java runtime from sun (because MS won't/cannot distribute it anymore)
This will work on most any platform and most any browser.
In my opinion, J# is targeted at those who would like to migrate Java to
..net, but I think they are more thinking of back-end J2EE stuff. There
is no real evidence to me that J# is being really pushed as an applet
technology (although it is theoretically possible to make an applet in J#).
I think if you are looking for the least pain for your users, I would
say Java for an applet. The absolute least pain for users is not to use
an applet at all, but have the web server do all the work. Sounds like
you may not need an actual applet for what you are trying to do.
This may all change in a few years if all windows machines ship
pre-installed with .net. But until then, asking your users to install
..net is no more polite than asking them to install java.