Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.softwaretools > #97 > unrolled thread
| Started by | Roedy Green <see_website@mindprod.com.invalid> |
|---|---|
| First post | 2012-03-18 16:31 -0700 |
| Last post | 2012-03-24 02:00 -0700 |
| Articles | 4 — 2 participants |
Back to article view | Back to comp.lang.java.softwaretools
IDE vocabulary Roedy Green <see_website@mindprod.com.invalid> - 2012-03-18 16:31 -0700
Re: IDE vocabulary Roedy Green <see_website@mindprod.com.invalid> - 2012-03-18 18:21 -0700
Re: IDE vocabulary John <stledger@lanl.gov> - 2012-03-19 14:52 -0700
Re: IDE vocabulary Roedy Green <see_website@mindprod.com.invalid> - 2012-03-24 02:00 -0700
| From | Roedy Green <see_website@mindprod.com.invalid> |
|---|---|
| Date | 2012-03-18 16:31 -0700 |
| Subject | IDE vocabulary |
| Message-ID | <qircm7hruo4sqo8kfqiur5vk2sokv2e66m@4ax.com> |
Like Eclipse and Netbeans, IntelliJ has its own vocabulary. Classes are grouped into packages. Packages are grouped into directories, reflecting the dot structure of the packages. Directories are grouped into modules. A module in a group of packages all compiled with a common source code target level. Modules are grouped into projects. All classes in a project must use a common code style. You recompile the project as a whole. Projects are usually more or less self-contained collections of code that share code. You might carve many distributables out of a single project. Classes in the same project can share code simply by using an import statement. To use code outside the project, you must specially configure library jars etc. to import that code into the project. What the equivalent vocabulary for other IDEs such as Netbeans and Eclipse? I would like to update the Java glossary. -- Roedy Green Canadian Mind Products http://mindprod.com It is almost impossible to keep things in synch manually. Instead: -Keep each fact in only one central database (not necessarily SQL), and access it as needed. Since there is only one copy of each fact, there is nothing to get out of synch. -Use some automated tool so that if you change a fact is one place, it automatically updates the others. -Write a sanity checker you run periodically to ensure all is consistent. This is the strategy compilers use. -Document the procedures needed to keep all in synch if you change something and rigidly and mechanically follow them.
[toc] | [next] | [standalone]
| From | Roedy Green <see_website@mindprod.com.invalid> |
|---|---|
| Date | 2012-03-18 18:21 -0700 |
| Message-ID | <9f2dm7lgjcj04a9otv0tunisqurssrg1h3@4ax.com> |
| In reply to | #97 |
On Sun, 18 Mar 2012 16:31:30 -0700, Roedy Green <see_website@mindprod.com.invalid> wrote, quoted or indirectly quoted someone who said : >What the equivalent vocabulary for other IDEs such as Netbeans and >Eclipse? I would like to update the Java glossary. In NetBeans, it seems a project produces one jar, and all must be compiled with the same source level. It seems to be something even smaller than a package, if your package generates several different jars. -- Roedy Green Canadian Mind Products http://mindprod.com It is almost impossible to keep things in synch manually. Instead: -Keep each fact in only one central database (not necessarily SQL), and access it as needed. Since there is only one copy of each fact, there is nothing to get out of synch. -Use some automated tool so that if you change a fact is one place, it automatically updates the others. -Write a sanity checker you run periodically to ensure all is consistent. This is the strategy compilers use. -Document the procedures needed to keep all in synch if you change something and rigidly and mechanically follow them.
[toc] | [prev] | [next] | [standalone]
| From | John <stledger@lanl.gov> |
|---|---|
| Date | 2012-03-19 14:52 -0700 |
| Message-ID | <cacd902a-83a1-4ba0-91b9-b6824b522b3b@cj6g2000vbb.googlegroups.com> |
| In reply to | #97 |
On Mar 18, 5:31 pm, Roedy Green <see_webs...@mindprod.com.invalid> wrote: > Like Eclipse and Netbeans, IntelliJ has its own vocabulary. Classes > are grouped into packages. Packages are grouped into directories, > reflecting the dot structure of the packages. Directories are grouped > into modules. A module in a group of packages all compiled with a > common source code target level. Modules are grouped into projects. > All classes in a project must use a common code style. You recompile > the project as a whole. Projects are usually more or less > self-contained collections of code that share code. You might carve > many distributables out of a single project. Classes in the same > project can share code simply by using an import statement. To use > code outside the project, you must specially configure library jars > etc. to import that code into the project. > > What the equivalent vocabulary for other IDEs such as Netbeans and > Eclipse? I would like to update the Java glossary. I'll try to answer for Eclipse. Eclipse has workspaces. A workspace is a directory that can contain multiple projects. When the IDE is opened, the user can select the which workspace to work within. Code is not shared between workspaces. A project contains the source code, compiled classfiles, and the paths to library jar files. The libraries can be included in the project, or may be external to the project. A project can also depend upon another project, so that the sources and libraries in the project that is depended upon are available to the dependent project. Source files are contained within packages. A project can have multiple package structures. Eclipse allows the user to set which files are source files, and which are not. The project is compiled as a whole. Multiple jar files can be created from a project. The jar can include just the class files, the source and class files, or the source files, class files, and library files. Each jar file is independent, and each source file within a project can be individually included in the jar file, or excluded from the jar file. Hope this is clear, John > -- > Roedy Green Canadian Mind Productshttp://mindprod.com > It is almost impossible to keep things in synch manually. Instead: > -Keep each fact in only one central database (not necessarily SQL), > and access it as needed. Since there is only one copy of each fact, > there is nothing to get out of synch. > -Use some automated tool so that if you change a fact is one place, > it automatically updates the others. > -Write a sanity checker you run periodically to ensure all is consistent. > This is the strategy compilers use. > -Document the procedures needed to keep all in synch if you change > something and rigidly and mechanically follow them.
[toc] | [prev] | [next] | [standalone]
| From | Roedy Green <see_website@mindprod.com.invalid> |
|---|---|
| Date | 2012-03-24 02:00 -0700 |
| Message-ID | <k83rm7toe0t7j2b0vjp1s8fsao351oq26b@4ax.com> |
| In reply to | #99 |
. > >Hope this is clear, > >John That is exactly what I wanted to know. Thank you. I included it verbatim in the entry at http://mindprod.com/jgloss/eclipse.html -- Roedy Green Canadian Mind Products http://mindprod.com When you were a child, if you did your own experiment to see if it was better to put to cocoa into your cup first or the hot milk first, then you likely have the programmer gene..
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.java.softwaretools
csiph-web