Environment

1. Environment https://store.theartofservice.com/the-environment-toolkit.html

2. Integrated development environment • An integrated development environment (IDE) or interactive development environment is a software application that provides comprehensive facilities to computer programmers for software development. An IDE normally consists of a source code editor, build automation tools and a debugger. Several modern IDEs integrate with Intelli-sense coding features. https://store.theartofservice.com/the-environment-toolkit.html

3. Integrated development environment • The boundary between an integrated development environment and other parts of the broader software development environment is not well-defined https://store.theartofservice.com/the-environment-toolkit.html

4. Integrated development environment Overview • IDEs are designed to maximize programmer productivity by providing tight-knit components with similar user interfaces. IDEs present a single program in which all development is done. This program typically provides many features for authoring, modifying, compiling, deploying and debugging software. This contrasts with software development using unrelated tools, such as vi, GCC or make. https://store.theartofservice.com/the-environment-toolkit.html

5. Integrated development environment Overview • One aim of the IDE is to reduce the configuration necessary to piece together multiple development utilities, instead providing the same set of capabilities as a cohesive unit https://store.theartofservice.com/the-environment-toolkit.html

6. Integrated development environment Overview • Some IDEs are dedicated to a specific programming language, allowing a feature set that most closely matches the programming paradigms of the language. However, there are many multiple-language IDEs, such as Eclipse, ActiveState Komodo, IntelliJ IDEA, Oracle JDeveloper, NetBeans, and Microsoft Visual Studio. Xcode, Xojo and Delphi are dedicated to a closed language or set of programming languages. https://store.theartofservice.com/the-environment-toolkit.html

7. Integrated development environment Overview • While most modern IDEs are graphical, text-based IDEs such as Turbo Pascal were in popular use before the widespread availability of windowing systems like Microsoft Windows and the X Window System (X11). They commonly use function keys or hotkeys to execute frequently used commands or macros. https://store.theartofservice.com/the-environment-toolkit.html

8. Integrated development environment History • IDEs initially became possible when developing via a console or terminal https://store.theartofservice.com/the-environment-toolkit.html

9. Integrated development environment History • Maestro I is a product from Softlab Munich and was the world's first integrated development environment 1975 for software. Maestro I was installed for 22,000 programmers worldwide. Until 1989, 6,000 installations existed in the Federal Republic of Germany. Maestro I was arguably the world leader in this field during the 1970s and 1980s. Today one of the last Maestro I can be found in the Museum of Information Technology at Arlington. https://store.theartofservice.com/the-environment-toolkit.html

10. Integrated development environment History • One of the first IDEs with a plug-in concept was Softbench. In 1995 Computerwoche commented that the use of an IDE was not well received by developers since it would fence in their creativity. https://store.theartofservice.com/the-environment-toolkit.html

11. Integrated development environment Visual programming • Visual programming is a usage scenario in which an IDE is generally required. Visual IDEs allow users to create new applications by moving programming, building blocks, or code nodes to create flowcharts or structure diagrams that are then compiled or interpreted. These flowcharts often are based on the Unified Modeling Language. https://store.theartofservice.com/the-environment-toolkit.html

12. Integrated development environment Visual programming • The graphical programming environment "Grape" is used to program qfix robot kits. https://store.theartofservice.com/the-environment-toolkit.html

13. Integrated development environment Visual programming • This approach is also used in specialist software such as Openlab, where the end users want the flexibility of a full programming language, without the traditional learning curve associated with one. https://store.theartofservice.com/the-environment-toolkit.html

14. Integrated development environment Language support • Some IDEs support multiple languages, such as Eclipse, IntelliJ IDEA, MyEclipse or NetBeans, all based on Java, or MonoDevelop, based on C#. https://store.theartofservice.com/the-environment-toolkit.html

15. Integrated development environment Language support • Support for alternative languages is often provided by plugins, allowing them to be installed on the same IDE at the same time. For example, Eclipse and Netbeans have plugins for C/C++, Ada, GNAT (for example AdaGIDE), Perl, Python, Ruby, and PHP, which are selected between automatically based on file extension, environment or project settings. https://store.theartofservice.com/the-environment-toolkit.html

16. Integrated development environment Attitudes across different computing platforms • Unix programmers can combine command-line POSIX tools into a complete development environment, capable of developing large programs such as the Linux kernel and its environment https://store.theartofservice.com/the-environment-toolkit.html

17. Integrated development environment Attitudes across different computing platforms • On the various Microsoft Windows platforms, command-line tools for development are seldom used. Accordingly, there are many commercial and non-commercial solutions, however each has a different design commonly creating incompatibilities. Most major compiler vendors for Windows still provide free copies of their command-line tools, including Microsoft (Visual C++, Platform SDK, .NET Framework SDK, nmake utility), Embarcadero Technologies (bcc32 compiler, make utility). https://store.theartofservice.com/the-environment-toolkit.html

18. Integrated development environment Attitudes across different computing platforms • IDEs have always been popular on the Apple Macintosh's Mac OS, dating back to Macintosh Programmer's Workshop, Turbo Pascal, THINK Pascal and THINK C environments of the mid-1980s. Currently Mac OS X programmers can choose between native IDEs like Xcode and open-source tools such as Eclipse and Netbeans. ActiveState Komodo is a proprietary IDE supported on the Mac OS. https://store.theartofservice.com/the-environment-toolkit.html

19. Integrated development environment Attitudes across different computing platforms • With the advent of cloud computing, some IDEs are available online and run within web browsers; example of this are Codeanywhere and Cloud9 IDE. https://store.theartofservice.com/the-environment-toolkit.html

20. Common Desktop Environment History • Sun contributed its ToolTalk application interaction framework and a port of its DeskSet productivity tools, including mail and calendar clients, from its OpenWindows environment. https://store.theartofservice.com/the-environment-toolkit.html

21. Common Desktop Environment History • In March 1994 CDE became the responsibility of the "new OSF", a merger of the Open Software Foundation and Unix International; in September 1995, the merger of Motif and CDE into a single project, CDE/Motif, was announced. OSF became part of the newly formed Open Group in 1996. https://store.theartofservice.com/the-environment-toolkit.html

22. Common Desktop Environment History • Until about 2000, users of Unix desktops regarded CDE as the de facto standard, but at that time, other desktop environments such as GNOME and K Desktop Environment 2 were quickly becoming mature, and became almost universal on the Linux platform, which already had a larger user base than most commercial Unixes in total. Red Hat is the only Linux distribution to which CDE has been ported, although it has since been phased out in favour of GNOME. https://store.theartofservice.com/the-environment-toolkit.html

23. Common Desktop Environment History • In 2001, Sun Microsystems announced that they would phase out CDE as the standard Solaris desktop environment in favor of GNOME https://store.theartofservice.com/the-environment-toolkit.html

24. Common Desktop Environment History • HP's OpenVMS uses CDE as its standard desktop environment. https://store.theartofservice.com/the-environment-toolkit.html

25. Common Desktop Environment Licensing • The Open Group released Motif in 2000 as Open Motif under a "revenue sharing" license that does not meet either the open source or free software definitions. (The Open Group had wished to make it open source, but did not quite succeed in achieving this.) https://store.theartofservice.com/the-environment-toolkit.html

26. Common Desktop Environment Licensing • In 2006, a petition was created asking The Open Group to release the source code for CDE and Motif under a free license. On August 6, 2012, CDE was open-sourced under the LGPL free software license. Its source code is available at SourceForge. On October 23, 2012, the Motif widget toolkit was released under the LGPL v2.1 as well, making CDE a completely free and open source desktop environment. https://store.theartofservice.com/the-environment-toolkit.html

27. Common Desktop Environment Licensing • OpenCDE, an open source project to replicate CDE, was started in early 2010. The project intended to reproduce the look and feel, organization, and feature set of CDE without using any CDE-derived code. With the release of CDE as open source, OpenCDE has been closed in its favour. https://store.theartofservice.com/the-environment-toolkit.html

28. Common Desktop Environment Operating systems using CDE • Digital UNIX / Tru64 UNIX (originally Digital Equipment Corporation, now Hewlett-Packard) https://store.theartofservice.com/the-environment-toolkit.html

29. Common Desktop Environment Operating systems using CDE • HP-UX (Hewlett-Packard) from version 10.10 https://store.theartofservice.com/the-environment-toolkit.html

30. Common Desktop Environment Operating systems using CDE • OpenVMS (originally Digital Equipment Corporation, now Hewlett-Packard) https://store.theartofservice.com/the-environment-toolkit.html

31. Common Desktop Environment Operating systems using CDE • Solaris (Sun Microsystems) available as an add on for 2.3 onwards, and as standard in 2.6 to 10. https://store.theartofservice.com/the-environment-toolkit.html

32. Common Desktop Environment Operating systems using CDE • CDEbian - a Linux distribution based on Debian Squeeze built to run CDE https://store.theartofservice.com/the-environment-toolkit.html

33. Batch processing Notable batch scheduling and execution environments • UNIX utilizes cron and at facilities to allow for scheduling of complex job scripts. Windows has a job scheduler. Most high-performance computing clusters use batch processing to maximize cluster usage. https://store.theartofservice.com/the-environment-toolkit.html

34. Batch processing Notable batch scheduling and execution environments • The IBM mainframe z/OS Operating System / platform has arguably the most highly refined and evolved set of batch processing facilities owing to its origins, long history, and continuing evolution, and today such systems commonly support hundreds or even thousands of concurrent online and batch tasks within a single Operating System image https://store.theartofservice.com/the-environment-toolkit.html

35. Applied Materials Energy and Environmental Solutions • In 2006 the company acquired Applied Films, a glass coating and web coating business. Also in 2006, Applied announced it was entering the solar manufacturing equipment business. The solar, glass and web businesses are now organized into the EES group of the Company. https://store.theartofservice.com/the-environment-toolkit.html

36. Applied Materials Energy and Environmental Solutions • In 2007, Applied announced the Applied SunFab thin film photovoltaic module production line, with single or tandem junction capability https://store.theartofservice.com/the-environment-toolkit.html

37. Applied Materials Energy and Environmental Solutions • Also in 2007 the company acquired privately held, Switzerland-based HCT Shaping Systems SA, a specialist in wafer sawing tools for both solar and semiconductor wafer manufacture, paying approximately $475 million. https://store.theartofservice.com/the-environment-toolkit.html

38. Applied Materials Energy and Environmental Solutions • In 2008, Applied acquired privately held, Italy-based Baccini SpA for $330M, company that worked in the metallization steps of solar cell manufacturing. https://store.theartofservice.com/the-environment-toolkit.html

39. Applied Materials Energy and Environmental Solutions • Also in 2008, the company was listed at the top of VLSI Research's list of supplier of photovoltaic manufacturing equipment for 2008, with sales of $797M. https://store.theartofservice.com/the-environment-toolkit.html

40. Applied Materials Energy and Environmental Solutions • Applied Materials also operates a venture investing arm called Applied Ventures. https://store.theartofservice.com/the-environment-toolkit.html

41. BlackBerry Ltd Environmental record • In November 2011, RIM was ranked 15th out of 15 electronics manufacturers in Greenpeace’s re-launched Guide to Greener Electronics https://store.theartofservice.com/the-environment-toolkit.html

42. BlackBerry Ltd Environmental record • RIM performed badly in the Products category, only scoring points for the energy efficiency of its products as it reports that its BlackBerry charger gets the European Commission IPP 4-star rating. Meanwhile on Sustainable Operations the company scored well for its stance on conflict minerals and received points for its Paper Procurement Policy and its mail-back programme for e-waste. Nevertheless, RIM was given no points for the management of GHG emissions from its supply chain. https://store.theartofservice.com/the-environment-toolkit.html

43. BlackBerry Ltd Environmental record • In its 2012 report on progress relating to conflict minerals, the Enough Project rated RIM the sixth highest of 24 consumer electronics companies. https://store.theartofservice.com/the-environment-toolkit.html

44. Debian Desktop environments • It was previously suggested that the default desktop environment of version 7.0 "Wheezy" may be switched to Xfce, because GNOME 3 might not fit on the first CD of the set https://store.theartofservice.com/the-environment-toolkit.html

45. Common Open Software Environment • The Common Open Software Environment or COSE was an initiative formed in March 1993 by the major Unix vendors of the time to create open, unified operating system (OS) standards. https://store.theartofservice.com/the-environment-toolkit.html

46. Common Open Software Environment Background • The COSE process was established during a time when the "Unix Wars" had become an impediment to the growth of Unix https://store.theartofservice.com/the-environment-toolkit.html

47. Common Open Software Environment Background • Unlike other Unix unification efforts that preceded it, COSE was notable in two ways: it was not formed in opposition to another set of Unix vendors, and it was more oriented toward making standards of existing technologies than creating new offerings from scratch. https://store.theartofservice.com/the-environment-toolkit.html

48. Common Open Software Environment Background • The initial members, (known as "The Big Six" or "SUUSHI"), were: https://store.theartofservice.com/the-environment-toolkit.html

49. Common Open Software Environment Background • The Santa Cruz Operation https://store.theartofservice.com/the-environment-toolkit.html

50. Common Open Software Environment Background • These represented the significant Unix system and OS vendors of the time, as well as the holders of the Unix brand and AT&T-derived source code. They also represented almost all the key players in the two major Unix factions of the late 1980s and early 1990s, the OSF and Unix International (UI). Notable in its absence was OSF co-founder Digital Equipment Corporation; Digital did finally announce its endorsement of the COSE process the following June. https://store.theartofservice.com/the-environment-toolkit.html