Tim Nicholson wrote: >Ok, > >I have gotten a few replies on the question of as to how one can get a java >written program to run without having constantly to be tied up to the >software that compiles it. > >I should admit, I haven't had the time as yet to read some of the longer web >pages that I was referred to on this subject yet. So please forgive me for >that. > I don't think you should put people to the trouble of answering your questions without reading their replies to your questions. I've begun to think you're a troll.
>I am just wanting to know breifly the following :- > > >How do all of you get the software for this example system ready for the >client ? > This is not usually an issue when programs are written by staff programmers for use in house. Programs are 'released' into production from pre-production staging areas where they are tested by other programmers and examined by prospective users. In larger organizations, release into production and production control are job specialties. When a program is destined to be a product, the work of preparing programs for 'installation' from media is a specialty apart from the work of design, development and testing. A program is installed by special installation software that examines the environment, assures that the program can run in that environment without encountering conflicts, adjusts settings and places the program in a suitable location on the user's machine. It will be a while before you get to this point. Don't worry. You may never have to concern yourself with the issue. >Assuming you have written all the code in java, how do you get it so that it >is ready for the client ? I assume that the client is not going to have to >compile the code each time so that they can use it to run their business ? > Not necessarily. In the open source world, clients often prefer programs in source form that they can modify and compile. >>From what I know, when you compile the java program, it becomes a different >sort of file as a result of the process ? What file does it become ? > You are a troll. >The reason why I mentioned ".exe" files is because, it appears that this >sort of file is ready to go. In the old DOS system, you would just type in >the name of the file and push enter and teh file would run. > Exe files have two principal attributes (among others). The first is that they're loaded and linked by the DOS or Windows loader. The second is that they execute instructions directly against the computer's microprocessor. >So basically I am talking about the situation where the file or in fact the >whole system which you finished writing in java code for example, is "ready >to go". Now some of you have said that it is perhaps a "bad idea" to make a >jav file into an "executable" or a "native executable" , perhaps the biggest >reason being because that it makes the resulting file a much bigger one. > It's unconventional practice to compile a java program to exe format. Considerations of size are usually irrelevant in an era when RAM is so cheap, although the class file format is more compact. Yes, size does matter in programming for the Web, where there are considerations of bandwidth; but it is unthinkable in any case to deploy an exe file to run in a browser. >So then I would take it that usually this is not the way that all of you get >the file you have written to be ready for the client ? I only mentioned the >".exe" part because I was trying to get across the idea that I am wanting to >know what happens when you have completed writing your program/system for >the client in java code and now you want to get it so that the user (your >customer) is able, through the easiest way possible, and through the way >that you all normally do this (ie if you don't normally make java files into >.exe files for this then don't mention that) to run the program on their >computers and just get it to open ? > Now you know and, if you don't, you haven't been reading. >Like I suppose in a Windows operating system that usually how it works is >that you open Windows Explorer or perhaps you have an icon for this >particualr program that you have written in java, and either way you just >double click on the file that your arrow is on and that gets the file to >run. > Sounds good. >So how do you get a java written program so that it is ready to run and >ready for the client to use ? >In what form does the java written file need to be so that it is ready for >the client to use after you have finished writing it ? > Use either a jar file or a batch file. How many times do you have to read the same straighforward information over and over? >I have not been taught yet how to do this, but it is a question that I'm >sure is very important in the software development process. > No, it' a mechanical detail. >I have recieved a few emails from people on my previous email yesterday on >the subject of ".exe" files, but it would appear from some of the replies >that I got, that this is not the usual way people >go about getting the programs they have written ready for their customer. > Right! >So then how do you do this ? > See above. >And how would you do it if the program had been written in a different >language like C or C++ ? > > Exe or batch file. ____________________________________________________ To change your JDJList options, please visit: http://www.sys-con.com/java/list.cfm Be respectful! Clean up your posts before replying ____________________________________________________
