omniomni/omni-engineering huggingface dataset:
Philip J. Carroll. Philip J. Carroll, Jr. (1937–2014) was an American businessman who was active in a variety of corporate and government roles. 
Carroll earned a Bachelor of Science in physics from Loyola University New Orleans in 1958 and a M.S. in physics from Tulane University in 1961, after which he joined the Shell Oil company as an engineer. He died in Houston, Texas, on October 6, 2014.

Carroll became the CEO of Shell Oil in 1993 and served in that position until July 1998, when he became the chairman and CEO of Fluor Corporation, an engineering and construction services firm. He retired from Fluor in February 2002.

He was a non-executive director of the British defense company BAE Systems. 
Carroll was a member of the board of directors of other companies, including Boise Cascade, Vulcan Materials, American Express, Scottish Power, and Texas Medical Center.

Carroll was an honorary life member of the board of the American Petroleum Institute, a member of the Tulane University advisory board, and the James A. Baker III Institute for Public Policy at Rice University and the University of Houston.

In the 1970s he briefly served as the director of the U.S. Department of Commerce's Energy Conservation Division and the Director of the National Industrial Energy Conservation Council. In 2003 he was appointed by the Bush administration to head the policy planning advisory board of the Iraqi Oil Ministry.
He opposed the neo conservative-backed plan to privatize Iraqi oil. He told Newsnight: "Many Neo-Conservatives are people who have certain ideological beliefs about markets, about democracy, about this, that and the other. International oil companies, without exception, are very pragmatic commercial organizations. They don't have a theology."

News 
An American and 2 Iraqis to Assume Key Oil Posts, New York Times, May 2, 2003.
BBC with Greg Palast

References

External links 
BAE Systems
Fluor Corporation
Vulcan Materials
Scottish Power, PLC
Boise Cascade
Texas Medical Center
Obituary

1937 births
2014 deaths
British businesspeople
BAE Systems people
Carroll, Philip
Rice University people
American Express people
University of Houston System regents
Widget toolkit. A widget toolkit, widget library, GUI toolkit, or UX library is a library or a collection of libraries containing a set of graphical control elements (called widgets) used to construct the graphical user interface (GUI) of programs.

Most widget toolkits additionally include their own rendering engine. This engine can be specific to a certain operating system or windowing system or contain back-ends to interface with multiple ones and also with rendering APIs such as OpenGL, OpenVG, or EGL.
The look and feel of the graphical control elements can be hard-coded or decoupled, allowing the graphical control elements to be themed/skinned.

Overview

Some toolkits may be used from other languages by employing language bindings. Graphical user interface builders such as e.g. Glade Interface Designer facilitate the authoring of GUIs in a WYSIWYG manner employing a user interface markup language such as in this case GtkBuilder.

The GUI of a program is commonly constructed in a cascading manner, with graphical control elements being added directly to on top of one another.

Most widget toolkits use event-driven programming as a model for interaction. The toolkit handles user events, for example when the user clicks on a button. When an event is detected, it is passed on to the application where it is dealt with. The design of those toolkits has been criticized for promoting an oversimplified model of event-action, leading programmers to create error-prone, difficult to extend and excessively complex application code. Finite-state machines and hierarchical state machines have been proposed as high-level models to represent the interactive state changes for reactive programs.

Windowing systems 
A window is considered to be a graphical control element. In some windowing systems, windows are added directly to the scene graph (canvas) by the window manager, and can be stacked and layered on top of each other through various means. Each window is associated with a particular application which controls the widgets added to its canvas, which can be watched and modified by their associated applications.

See also
 WIMP (computing)
 Layout manager
 List of widget toolkits

References 

 
Graphical user interfaces
VariCAD. VariCAD is a computer program for 3D/2D CAD and mechanical engineering which has been developed since 1988 in the Czech Republic. VariCAD runs on Windows and Linux. It features many  tools for 3D modeling and 2D drafting. VariCAD provides support for parameters and geometric constraints, tools for shells, pipelines, sheet metal unbending and crash tests, assembly support, mechanical part and symbol libraries, calculations, bills of materials, and more.

The program includes a standard part library with screws, nuts, bearings etc. Additionally, it offers many calculation modules for, e.g., springs, beam torsion, volume, mass and center of gravity.

VariCAD allows editing of DWG files without conversion using the Open Design Alliance DWGdirect libraries. VariCAD also supports the ISO industrial product data exchange format STEP/STP. A list of notable supported file formats is listed in the Comparison of CAD software article.

VariCAD is available for both Windows and for some time on the Linux OS. With the addition of support for Unicode user interface now also supports non Latin character sets such as those used in the Japanese, Chinese and Russian languages.

VariCAD is available in English, German, Portuguese and Japanese languages.

VariCAD Viewer is a free proprietary computer program for viewing of 3D/2D CAD files. It runs on the Windows and Linux operating systems. Notable supported file formats are listed in the Comparison of CAD, CAM and CAE file viewers article.

See also 
 Comparison of CAD, CAM and CAE file viewers
 Comparison of CAD editors for AEC

References

External links 
VariCAD Homepage
CNC1 - 3D hobby cnc base machine (free design project made with VariCAD)

Computer-aided design software
Computer-aided design software for Linux
Ravi Sethi. Ravi Sethi (born 1947) is an Indian computer scientist retired from executive roles at Bell Labs and Avaya Labs. He also serves as a member of the National Science Foundation's Computer and Information Science and Engineering (CISE) Advisory Committee.  He is best known as one of four authors of the classic computer science textbook Compilers: Principles, Techniques, and Tools, also known as the Dragon Book. He also authored Software Engineering: Basic Principles and Best Practices and Programming Languages: Concepts & Constructs (1989, 1996) textbooks.

Sethi was born in 1947 in Murdana, Punjab. He attended the Indian Institute of Technology, Kanpur (IITK) and went on to obtain a Ph.D. at Princeton University. He worked as an assistant professor at Penn State University, before joining Bell Labs in 1976.

While working for Bell Labs he was awarded the "Distinguished Technical Staff award", and in 1996 he was named a Fellow of the Association for Computing Machinery. Also in 1996 he was named research vice president in charge of computing and mathematical sciences and, additionally, in 1997, chief technical officer for Lucent’s Communications Software Group.

In 2014, Sethi joined the department of computer science at the University of Arizona.

References

External links
Home page (University of Arizona)
Autobiographical note at Avaya website 
Publication list on DBLP

1947 births
1996 fellows of the Association for Computing Machinery
Indian computer scientists
Living people
Avaya employees
Scientists at Bell Labs
IIT Kanpur alumni
Princeton University alumni
People from Punjab, India
Zephyr (protocol). Created at MIT as part of Project Athena, Zephyr was designed as an instant messaging protocol and application-suite with a heavy Unix background. Using the "do one thing, do it well" philosophy of Unix, it was made up of several separate programs working together to make a complete messaging system. Zephyr and IRC were the first widely used IP-based instant-messaging systems.

Creation
Zephyr is the invention of Ciarán Anthony DellaFera who was, at that time, an employee of Digital Equipment Corporation and a Visiting Research Scientist at Project Athena. The design originated as a solution to the "reverse Remote Procedure Call (RPC)" problem: how can service providers (servers in a client–server system) locate and communicate with service users. The initial concept emerged from conversations between Ciarán and Michael R. Gretzinger, another systems engineer at Project Athena, in early 1986. By mid to late 1986 Ciarán had distilled the problem to two specific issues: the ability to locate users in a distributed computing environment (known today as "presence detection"), and the ability to deliver scalable, light-weight, and authentic messages in a distributed computing environment. The Zephyr Development Team (Mark W. Eichin, Robert S. French, David C. Jedlinsky, John T. Kohl, William E. Sommerfeld) was responsible for the creation of the initial code-base and the subsequent releases that were issued throughout the late 1980s.

Application
Zephyr is still in use today at a few university environments such as Carnegie Mellon, Iowa State, University of Maryland, College Park, Brown University and MIT. It has been largely replaced by modern and more popular instant messenger systems such as XMPP. MIT currently operates both Zephyr and XMPP.

Points of interest
Zephyr uses UDP datagrams sent between ports 2102, 2103, and 2104. It is incompatible with most routers doing NAT because it reports the internal IP address and so returning datagrams are incorrectly routed. Most sites have deployed Zephyr using Kerberos 4 authentication exclusively, though in late 2007, some sites, including Iowa State, deployed Zephyr using Kerberos 5.

Client support
 BarnOwl has always had Zephyr protocol support.
 Pidgin supports the Zephyr protocol since version 0.11.0-pre10 (April 13, 2001).
 Adium added support for Zephyr in Version 0.70 (October 18, 2004), but dropped in version 1.4b6 (June 3, 2009).

See also
 Comparison of instant messaging clients

References

External links
 Zephyr 3.0
 The 1988 Usenix paper on Zephyr
 Zephyr on Athena
 MIT Q&A about Zephyr
 Zephyr's Source Code

Free instant messaging clients
Instant messaging protocols
Massachusetts Institute of Technology software
Slack. Slack or Slacks may refer to:

Places
 Slack, West Yorkshire, a village in Calderdale, England
 The Slack, a village in County Durham, England
 Slack (river), a river in Pas-de-Calais department, France
 Slacks Creek, Queensland, Australia, a suburb of Logan City

Science and technology
 File slack, a kind of computer internal fragmentation
 Slack bus, an electrical power regulating system used to conduct load flow studies
 Slack (project management), the time that a task in a project network can be delayed without delaying subsequent tasks or the overall project
 Slack (software), a team communication tool that can be used for collaboration
 Slack variable, a mathematical concept
 Slack tub, used by a blacksmith to quench hot metal

People
 Slack (surname), a list of people

Other uses
 Slacks, another name for trousers
 Slack Technologies, an American software company responsible for Slack software
 Resource slack, the level of availability of a resource to a business
 Slack, the central belief of the parody religion Church of the SubGenius
 Slack coal, fragments of coal and coal dust; for example used in the Birchills Power Station
 Slack, the valley or trough between dunes
 Slack, not having tension (physics)
 Slack action, free movement due to loose couplings between railway cars

See also

 SLAC (disambiguation)
 Slak (disambiguation)
 Slacker, a person who habitually avoids work or lacks work ethic
 Slackness (Jamaican music), a crude or bawdy subgenre of dancehall music
 Slackware, a Linux distribution
FreeGEM. FreeGEM released in 1999 is a windowing system based on Digital Research's GEM which was first released in 1985. GEM stands for "Graphics Environment Manager".

Overview
FreeGEM is the free software/open source version of GEM developed after Caldera Thin Clients released the GEM code under the terms of the GNU GPL-2.0-only free software license in April 1999. Caldera Thin Clients owned the source code to GEM through Caldera's purchase of the remaining Digital Research assets from Novell on 23 July 1996, who had acquired Digital Research in June 1991.

FreeGEM code works on almost every version of DOS, and runs on almost every IBM compatible PC. One can download all the FreeGEM binaries and source code in one package through the OpenGEM SDK. The OpenGEM SDK also contains language bindings, documentation, and compilers. There are additional FreeGEM resources available through John C. Elliott's GEM website.

OpenGEM is a popular FreeGEM distribution. Other distributions include Owen's FreeGEM Distribution.

OpenGEM
OpenGEM is a non-multitasking 16-bit graphical user interface (GUI) for DOS. It is an extended distribution of FreeGEM that includes features of the original Digital Research GEM.

OpenGEM is intended to provide a simple to install and use GUI system and windowing framework for the FreeDOS operating system.

Caldera Thin Clients (later known as Lineo), who owned the source code to GEM through Caldera's purchase of the remaining Digital Research assets from Novell on 23 July 1996, released the source to GEM under the terms of GPL-2.0-only in April 1999. OpenGEM was developed by Shane Martin Coughlan in collaboration with the FreeGEM Developer team, and is free software released under the terms of the GPL-2.0-only. OpenGEM versions 3 through 6 are hosted on SourceForge and on the FreeDOS website.

OpenGEM has not been actively developed since 2008 but is feature-complete as a basic GUI and includes a full SDK for future third-party development or extension.

Compatibility 
OpenGEM works with FreeDOS Beta 9 and above, DR DOS 5.0 and above, MS-DOS 3.3 and above, PC DOS 3.3 and above, REAL/32, and DOSBox 0.65. OpenGEM will function on Windows 95, Windows 98, Windows 98SE, and Windows ME. It is not known to work with Windows NT, Windows 2000 and Windows XP or later.

See also 

 ViewMAX
 QEMU
 GEM character set

References

External links
 GEM Development mailing list 
 John C. Elliott's GEM site
 FreeGEM file site
 Owen's FreeGEM Distribution
 OpenGEM on the FreeDOS site
 OpenGEM on Github
 OpenGEM on the SourceForge site
 
 FreeGEM/XM on Github

1985 software
DOS software
File managers
Free windowing systems
GEM software
Windowing systems
Thomas Davenport (inventor). Thomas Davenport (July 9, 1802 – July 6, 1851) was a Vermont blacksmith who, with his wife Emily, constructed the first American DC electric motor in 1834.

Biography
Davenport was born in Williamstown, Vermont. He lived in Forest Dale, a village in the town of Brandon.

As early as 1834, he developed a battery-powered electric motor, along with his wife Emily Davenport. They used it to operate a small model car on a short section of track, paving the way for the later electrification of streetcars. It is the first attempt to apply electrification to locomotion.

Davenport's 1833 visit to the Penfield and Taft iron works at Crown Point, New York, where an electromagnet was operating, based on the design of Joseph Henry, was an impetus for his electromagnetic undertakings.  Davenport bought an electromagnet from the Crown Point factory and took it apart to see how it worked.  Then he forged a better iron core and redid the wiring, using silk from his wife's wedding gown.

With his wife Emily and colleague Orange Smalley, Davenport received the first American patent on an electric machine in 1837, U. S. Patent No. 132. In 1840, he printed The Electro-Magnetic and Mechanics Intelligencer, making it the first magazine to be printed with electricity.

In 1849, Charles Grafton Page, the Washington scientist and inventor, commenced a project to build an electromagnetically powered locomotive, with substantial funds appropriated by the US Senate.  Davenport challenged the expenditure of public funds, arguing for the motors he had already invented.  In 1851, Page's full sized electromagnetically operated locomotive was put to a calamity-laden test on the rail line between Washington and Baltimore.

References

Further reading
Post, R. C. (1976). Physics, Patents, and Politics:  A Biography of Charles Grafton Page.  New York:  Science History Publications.
Michael Brian Schiffer, 2008.  Power Struggles:  Scientific Authority and the Creation of Practical Electricity Before Edison, Cambridge MA:  MIT Press.
Frank Wicks.  "The Blacksmith's Motor.  Electricity, magnetism, and motion:  A self-taught Vermonter pointed the direction for lighting the world."   Mechanical Engineering, July 1999.
Davenport's patent for the electric motor, issued in early 1837, Today in Technology History February 25 (direct link)
Smalley and Davenport's shop
The invention of the electric motor 1800–1854: Thomas Davenport

External links

1802 births
1851 deaths
19th-century American inventors
American blacksmiths
Vermont culture
American railroad pioneers
People associated with electricity
People from Williamstown, Vermont
People from Salisbury, Vermont
Emily Davenport. Emily Goss Davenport Weeks  (April 29, 1810October 5, 1862) was an American inventor from Vermont. Together with her husband Thomas Davenport, they invented an electric motor and electric locomotive around 1834.

Davenport kept detailed notes and actively contributed to the process of the inventions. Needing to insulate the motor's iron core, Davenport cut her wedding dress into strips of silk to insulate the wire windings. She is also credited with the idea of using mercury as a conductor, enabling the motor to function for the first time. With her husband Thomas, and colleague Orange Smalley, she received the first American patent on an electric machine in 1837, U. S. Patent No. 132. This electric motor was used in 1840 to print The Electro-Magnet, and Mechanics Intelligencer - the first newspaper printed using electricity.

She was born Emily Goss in Brandon Vermont, one of five children born to Rufus Goss a local merchant and Anna Green. She and Thomas Davenport lived in Salisbury, Vermont and had two children, George Daniel Davenport and Willard Goss Davenport. Thomas Davenport died in 1851 and Emily moved to Middlebury. On January 6, 1856 she married John Mosely Weeks in Salisbury, the inventor of the Vermont beehive. She died in 1862 and is buried in Pine Hill Cemetery in Brandon, Vermont.

Further reading

References

1810 births
1862 deaths
People from Brandon, Vermont
19th-century American inventors
American women inventors
19th-century American women
Disruptor. Disruptor may refer to:

Disruptor (software), an open-source software technology 
Disruptor (Star Trek), a weapon in the Star Trek franchise
Disruptor (video game), is a video game for the Sony PlayStation
Disruptor Beam, a game company started by Jon Radoff
Disruptor Conductor, an episode of CBC Docs POV
Disruptor Records, an American record label
Endocrine disruptor, chemicals that interfere with endocrine systems
Photonic Disruptor, a model of the dazzler non-lethal directed radiation weapon
Projected water disruptor, a type of bomb disposal equipment
A catalyst of disruptive innovation

See also
Disruption
XUnit. xUnit is a label used for an automated testing software framework that shares significant structure and functionality that is traceable to a common progenitor SUnit.

The SUnit framework was ported to Java by Kent Beck and Erich Gamma as JUnit which gained wide popularity. Adaptations to other languages were also popular which led some to claim that the structured, object-oriented style works well with popular languages including Java and C#. 

The name of an adaptation is often a variation of "SUnit" with the "S" replaced with an abbreviation of the target language name. For example, JUnit for Java and RUnit for R. The term "xUnit" refers to any such adaptation where "x" is a placeholder for the language-specific prefix.

The xUnit frameworks are often used for unit testing  testing an isolated unit of code  but can be used for any level of software testing including integration and system.

Architecture 

An xUnit framework has the following general architecture.

Test case 

A test case is the smallest part of a test that generally encodes a simple path through the software under test. The test case code prepares input data and environmental state, invokes the software under test and verifies expected results.

A programmer writes the code for each test case.

Assertions 

A test case is implemented with one or more assertions that validate expected results. 

Generally, the framework provides assertion functionality. A framework may provide a way to use custom assertions.

Test suite 

A test suite is a collection of related test cases. They share a framework which allows for reuse of environment setup and cleanup code.

Generally, a test runner may run the cases of a suite in any order so the programmer should not depend on top-to-bottom execution order.

Test fixture 

A test fixture (also known as a test context) provides the environment for each test case of a suite. Generally, a fixture is configured to setup a known, good, runtime environment before tests run, and to cleanup the environment after.

The fixture is configured with one or more functions that setup and cleanup state. The test runner runs each setup function before each case and runs each cleanup function after.

Test runner 

A test runner is a program that runs tests and reports results. The program is often part of a framework.

A test runner may produce results in various formats. Often, a common and default format is human-readable, plain-text. Additionally, the runner may produce structured output. Some xUnit adaptations (i.e. JUnit) can output XML that can be used by a continuous integration system such as Jenkins and Atlassian Bamboo.

See also

References

External links
 
 
 
 

Unit testing frameworks
Amiga 3000UX. The Amiga 3000UX is a model of the Amiga computer family that was released with Amiga Unix, a full port of AT&T Unix System V Release 4 (SVR4), installed along with AmigaOS. The system is otherwise equivalent to the standard A3000, once a right-click initiates a boot to Kickstart (Amiga's kernel).

Sun Microsystems and Unix International featured the Amiga 3000UX on their stands at the 1991 Uniforum event, ostensibly to promote Commodore's adoption of those exhibitors' technologies, specifically OPEN LOOK and SVR4. This may have led to unsubstantiated rumours about Sun potentially incorporating the model into its workstation range, sustained by persistent community perceptions of Commodore's managerial incompetence.

It is possible that Commodore (or a third party) repurposed A3000UX machines for standard AmigaOS, as some standard A3000 models have been found with labeling suggesting they were originally to be sold as A3000UX machines.

See also

 Amiga models and variants

References

Amiga
Computer-related introductions in 1990