q2K BHP
Black History Portal
THE BHP WIRE —
HIDDEN TRUTHS
What's New!
THE JOURNEY THROUGH TIME

Explore Black History

Explore the people, places, events, achievements, struggles and stories that shaped our journey.

✊🏾

Civil Rights

Movements, leaders, victories and the continuing fight for equality.

⚙️

Black Inventors

Innovation, patents, science, technology and world-changing contributions.

🏆

Sports

Pioneers, champions, Negro Leagues, records, activism and excellence.

♟️

People

Meet the people whose lives, choices and achievements shaped the journey.

📍

Places

Black towns, communities, institutions and places where history happened.

📜

Events

Moments that changed communities, movements, institutions and the nation.

Enter a person, place, event, or topic.
MY'STORY

The MOVE Fire

This is a personal recollection on the Move fire on May 13, 1985 Philadelphia police fired thousands of rounds at the MOVE house, city officials approved dropping an explosive device on the roof, the resulting fire was allowed to burn, 11 people—including five children—died, and 61 homes were destroyed. Philadelphia City Council later called it a “brutal attack carried out by the City of Philadelphia on its own citizens” and acknowledged that no individual faced criminal consequences for the bombing. One timeline correction worth preserving for the BHP record: the major previous MOVE-police confrontation was August 8, 1978, about seven years before the bombing, not a year or two earlier. Officer James Ramp was killed, other police and firefighters were wounded, nine MOVE members were later convicted, and television cameras recorded police beating Delbert Africa during his arrest. The 1985 MOVE Commission later specifically criticized city planners for failing to adequately use lessons from that 1978 confrontation. And that actually strengthens the point you’re making: 1985 did not happen without precedent or institutional memory. There had already been a deadly confrontation with MOVE, years of conflict, negotiations and police involvement before Osage Avenue.

MORE →
BLACK FACTS
The Truths They Never Taught You...

Wilmington 1898 — An American Coup

Wilmington, North Carolina once had a thriving Black middle class and an elected interracial government. In 1898 white supremacists used violence to overthrow that government, kill Black residents and drive many others from the city.

MORE →
BHP gathered finds from its connected research sources. Showing the 4 strongest Black History matches.
← BACK TO RESULTS
Wikipedia

Vector-based graphical user interface

A vector-based graphical user interface is a mostly conceptual type of graphical user interface where elements are drawn using vector information instead of raster information.

An example of a vector-based window, found in a privately funded vector-based graphical user interface research project.
2D GUI. All window decorations and elements inside them are vector-based, the background is generated from multiple sine waves and the shapes are defined in-runtime. The final image is rasterized, anti-aliased and optionally composited, here the compositing is disabled.

Pros and cons

[edit]

The benefits of a completely vector-based graphical user interface would include:

  • more efficient, independent scalability; The resolution (measured in dots per inch or DPI) could be set higher or lower than 1px:1px without causing pixelation, enabling better use of high resolution monitors.

Cons might include:

  • Difficulty integrating raster-based applications. With some effort, this could be accomplished by texturing the entire raster-based application to a vector-based plane (though the disadvantages of raster-based graphics would still stand).
  • Slower rendering, greater system requirements. Because today's monitors display only raster-based information, the vector information would have to be rasterized (and optionally anti-aliased) before appearing.

Usage in 3D graphical user interfaces

[edit]

Since current 3D Graphics are usually vector-based, rather than raster-based, vector-based graphical user interfaces would be suitable for 3D graphical user interfaces. This is because raster-based 3D models take up an enormous amount of memory, as they are stored and displayed using voxels. Current operating systems such as Windows Vista, Mac OS X, and UNIX-based operating systems (including Linux) have enjoyed much benefit from using 3D graphical user interfaces. In Windows Vista, for example, Flip3D textures each window to a 3D plane based on vector graphics. Even though the window itself is still raster-based, the plane onto which it is textured is vector-based. As a result, the windows, when rotated, appear flat. In Linux desktops, Compiz Fusion can texture each raster-based workspace onto a 3D vector-based cube. As operating systems evolve, eventually the entire window would be made from 3D vector graphics, so that when rotated, it does not appear "flat". Also, advanced lighting may make 3D graphical user interfaces more aesthetically pleasing.

Usage in 2D graphical user interfaces

[edit]

As most computer monitors become more and more high resolution, everything displayed would be smaller. However, if the screen resolution were turned down, everything would appear pixelated. Thus, resolution independence is currently being designed to solve this problem. With raster graphics, all icons need to be extremely high resolution, so as to not appear pixelated on higher resolution screens. This may take up enormous amounts of memory, and hard disk space.[citation needed] If vector graphics were used instead, it could be easily scalable and never lose data nor appear pixelated.

Some graphical user interfaces on operating systems such as IRIX use vector-based icons. A number of vector-based icon sets are also available for window managers such as GNOME and KDE.

With Windows, applications built using Windows Presentation Foundation (which is native[citation needed] to Windows Vista, but can be downloaded for Windows XP and Server 2003) are vector-based and scale losslessly based on Windows DPI settings. However, even without this, it has always been possible to build applications to be DPI-aware.[1] Additionally, in Vista, the Desktop Window Manager detects when an app is not DPI aware and, if the computer is set to a different DPI than normal, uses bitmap scaling to render the window at a larger size.[2]

New version of AmigaOS 4.1 enhanced in 2008 its Workbench with 2D vector graphical interface based on Cairo libraries, but pragmatically integrated it with a 3D Compositing Engine based on Porter-Duff Routines.

See also

[edit]

References

[edit]

Source: Wikipedia. Article content is retrieved live through the MediaWiki API.

Wikipedia

Vector-based graphical user interface

A vector-based graphical user interface is a mostly conceptual type of graphical user interface where elements are drawn using vector information instead of raster information.

MORE →
Wikipedia

Graphical user interface

A graphical user interface, or GUI, is a form of user interface that allows users to interact with electronic devices through graphical icons and visual indicators such as secondary notation. In many applications, GUIs are used instead of text-based UIs, which are based on typed command labels or text navigation. GUIs were introduced in reaction to the perceived steep learning curve of command-line interfaces (CLIs), which require commands to be typed on a computer keyboard. The actions in a GUI are usually performed through direct manipulation of the graphical elements. Beyond computers, GUIs are used in many handheld mobile devices such as MP3 players, portable media players, gaming devices, smartphones and smaller household, office and industrial controls. The term GUI tends not to be applied to other lower-display resolution types of interfaces, such as video games (where heads-up displays (HUDs) are preferred), or not including flat screens like volumetric displays because the term is restricted to the scope of 2D display screens able to describe generic information, in the tradition of the computer science research at the Xerox Palo Alto Research Center.

MORE →
Wikipedia

Zooming user interface

In computing, a zooming user interface or zoomable user interface (ZUI, pronounced zoo-ee) is a type of graphical user interface (GUI) on which users can change the scale of the viewed area in order to see more detail or less, and browse through different documents. Information elements appear directly on an infinite virtual desktop (usually created using vector graphics), instead of in windows. Users can pan across the virtual surface in two dimensions and zoom into objects of interest. For example, as the user zooms into a text object, it may be represented as a small dot, then a page thumbnail, then a full-size page, and finally a magnified view of the page. ZUIs use zooming as the main metaphor for browsing through hyperlinked or multivariate information. Objects present inside a zoomed page can, in turn, be zoomed themselves to reveal further detail, allowing for recursive nesting and an arbitrary level of zoom. Researchers have described the ZUI paradigm as a Post-WIMP interface and potential successor to the traditional windowing GUI. The term ZUI was coined by Franklin Servan-Schreiber while working at Sony Research Laboratories, in partnership with Ben Bederson and Ken Perlin of New York University.

MORE →
No preview image
Wikipedia

User interface markup language

A user interface markup language is a markup language that renders and describes graphical user interfaces and controls. Many of these markup languages are dialects of XML and are dependent upon a pre-existing scripting language engine, usually a JavaScript engine, for rendering of controls and extra scriptability. The concept of the user interface markup languages is primarily based upon the desire to prevent the "re-invention of the wheel" in the design, development and function of a user interface; such re-invention comes in the form of coding a script for the entire user interface. The typical user interface markup language solidifies often re-used program or script code in the form of markup, making it easier to focus upon design of a user interface in an understandable dialect as opposed to focus on function. User interface markup languages, like most markup and programming languages, rely upon sub-application runtimes to interpret and render the markup code as program code that can be processed and put out in the desired form. In XML-based user interface markup languages, the markup is usually interpreted and represented as a tree of nodes that may be manipulated at runtime by the application's code or dynamically loaded user script.

MORE →
TOPIC OF THE DAY

Greenwood / Black Wall Street

Before the 1921 destruction of Tulsa’s Greenwood District, Black residents had created a remarkable center of business and community life. The district included stores, professional offices, entertainment venues and homes owned by Black citizens. Understanding Greenwood means learning what was built—not only what was burned.

MORE →
TRIVIA QUESTION OF THE DAY

Which Supreme Court case ruled state-sponsored public-school segregation unconstitutional?

Brown v. Board of Education in 1954.