It began life under the name ARPANet in 1969. It was born in the U.S.A., created in the midst of the Cold War by the government as a strategic mechanism that would provide for the emission and reception of electronic communication signals in the event of a world catastrophe. Commissioned by the Department of Defense, four computers called nodes were connected using modems, telephone wires and satellites, one each at UCLA, UCSB, Stanford and University of Utah. ARPANet stands for Advanced Research Projects Agency Network. Its purpose was to share information and results of research among the various scientists involved in Department of Defense projects. Each node was specifically designed io be independent of the others in case of that aforementioned world catastrophe.
Read the rest of this entry »
Why do we write documentation? Silly question. Because we want others to be able to use our program, library function or whatever we have written and made available. But writing documentation is not all there is to it: Documentation must be accessible. If it’s hidden in some non?standard place where the documentation?related tools won’t find it ?? how can it serve its purpose?
Read the rest of this entry »
The Java language has revolutionized the way we program applications for the Internet. Two great ideas make this language so promising:
• Applications written using Java run on multiple different platforms.
• Automatic memory management or garbage collection (GC) comes as a great relief for developers.
Other than these two issues, most of the remaining Java features can be implemented using the majority of other languages. Since its first public release in 1995, the Java language has been maturing and consolidating its position in the market as an increasing number of organizations realize its built-in strengths.
Read the rest of this entry »
In the late 1990’s many ERP companies caught the web browser wave, undertaking projects to leverage the Internet and browser technology and even to convert their software to “lite-client” or web “portal” architectures. Unfortunately for some, .NET came on the scene too soon after this major overhaul. When .NET appeared, some were too technically exhausted, or inflexible, or still basking in the glow of their new “Internet-based architectures” to recognize and embrace .NET. Other ERP software companies were and continue to be simply too busy struggling to stay solvent during the devastating one-two-three punch of Y2K, the recession of 2000, and 9/11. They lack the resources to consider the complete restructuring of their products that .NET warrants.
Read the rest of this entry »
18 Sep
Posted by jj as Database
O*NET, the Occupational Information Network, is replacing the Dictionary of Occupational Titles (DOT) as a source of occupational information. O*NET is a database—not a book, like the DOT. This database has the qualities of both an interactive library and a language.
Serving as a library for information on the working world, O*NET allows everyone to access data on job characteristics and worker attributes. It includes information on the knowledge, skills, abilities, interests, preparation, contexts, and tasks associated with 1,122 O*NET occupations.
Read the rest of this entry »
17 Sep
Posted by jj as Development
Because the properties of aluminum alloys are dependent upon both the exposure temperature and also to the length of time of exposure, the prediction of design values for structures designed to last many years is a significant challenge. For relatively short-life structures, the need is addressed simply by planning ahead and carrying out a test plan that replicates the intended service conditions. This is feasible for structures whose design life might be as much as a year or even five years, but it is not very practical for structures for which the life expectancy is 10 years or more.
Read the rest of this entry »
22 Jul
Posted by jj as Design & Graphics
This tutorial is designed to show the user how to use ArcGIS software and the Districting extension to prepare and submit a plan for the Competition. Please refer to the document “FINAL Rules of the Competition” for details and rules about this project including the rules and procedures of the competition.
Read the rest of this entry »
The 1,000,000 plant specimens stored at the National Herbarium of New South Wales are a major resource used by scientific botanists to confirm the identification of plants. The Digital Imaging project will provide an Internet- accessible electronic image bank of the herbarium collections. These data will be managed in the NSW collections database system. The images will be accessible through PlantNET on the RBG website. The first phase of the project will include all NSW native (including rare and endangered) and weedy species, subspecies and varieties. This web based database will provide a resource that can be used to confirm plant identifications by the community. This project will link images and enhance the continuing development of the EucaLink, WattleWeb and other similar projects that are part of PlantNet. It is also closely coordinated with the national Australia’s Virtual Herbarium (AVH) project being undertaken by all herbaria in Australia.
Read the rest of this entry »