In 1984, Apple debuted the operating system that is now known as the 'Classic' Mac OS with its release of the original Macintosh System Software. The system, rebranded 'Mac OS' in 1996, was preinstalled on every Macintosh until 2002 and offered on Macintosh clones for a short time in the 1990s. Noted for its ease of use, it was also criticized for its lack of modern technologies compared to its competitors. The current Mac operating system is macOS, originally named 'Mac OS. Requiring a big budget to create beautiful looking games is now a thing of the past. GameMaker allows you to implement AAA game features hassle-free. Bring your games to life with 2D physics, create a thriving player base with cross-platform network play, and create stunning visual effects using shaders.

This is a sub-page of Roblox (Windows, Mac OS X).

• 1Graphics
• 3Text

Graphics

Early Moon Texture

Before 2007, this moon texture was used.

Early Builders Club Icons

Builders Club was the membership service that originally granted the additional perks that Roblox Premium gives to players who subscribed to it. These icons were used by previous versions of the game's UI on the player list to indicate which level of Builders Club players had, they later became unused when they were replaced with newer icons that lasted until Roblox Premium replaced this membership on September 23, 2019.

Platformer Prototype (digifox08) Mac Os Sierra

The icons that were for the regular Builders Club, 'Turbo' Builders Club, and 'Outrageous' Builders Club, respectively.

Early Dialog Bubble Textures

There were a bunch of images that were previously used for the NPC dialog bubbles but were left unused when the UI was redone.

Glue Surface Texture

In 2014, Roblox removed the Glue surface, this was its texture. When it was removed, all of the Glue used in the games were affected by getting replaced with the Welds.

Sun Rays Texture

Although sun rays are present in the game, this texture isn't used. In older versions of the game from 2012, the sun rays appeared when the time was exactly 6:00 A.M.

Here are the sun rays in action.

2011 UI Elements

When the In-Game Video Capture was first introduced, this was the button to stop recording, and it was located in the bottom right corner next to a camera icon.

This button, as it clearly says, used to be a shortcut to exiting a game, it was located in the bottom left corner. The first variant was used when the player was at the confirmation screen for leaving a game. The second variant was used when the cursor hovered over the button.

Character

Character.png was a small graphic of an early Robloxian.

Test Textures

test_texture.jpg and test2_texture.jpg were two unused textures meant for testing something, most likely Materials or Decals. The textures were made in 1998.

Detonator

Detonator.png was a clip art image of a detonator.

2005 Leftovers

• SurfacePanel.png

• VelocityTool.png

• VelocityTool_ovr.png

• VelocityTool_ds.png

• VelocityTool_dn.png

• FlatTool.png

• FlatTool_dn.png

• ControllerPanel.png

• DropperTool.png

• DopperTool_dn.png

• FillTool.png

• FillTool_dn.png

Roblox had a different UI in 2005, and there were plenty of leftovers from it.

Misc.

• FireWand.png

• Gun.png

• MissingCursor.png

• ControllerAI1Tool.png

• ControllerAI2Tool.png

• ControllerNoneTool.png

Supersafe Chat Buttons

For a while, Roblox had a feature called 'Supersafe Chat' that any player could use, but in the case of users that were under the age of 13 and Guests, it was their only method of communicating as they could not use the regular chat. It replaced the regular chat's ability to type anything with preset messages instead. Although the feature was removed in April 2014, allowing any user to talk regularly (except Guests, who lost the ability to talk altogether), the code and images for Supersafe Chat still existed for a while.

The blue icon was used as the regular state, green was for when the cursor hovered over the button, and red was for when you were in the Supersafe Chat menu, the gray button was never used.

Platformer Prototype (digifox08) Mac Os 7

Early 2.0 Textures

Before the 2.0 package was released, a prototype was released. These textures were meant to go with the model used in the promotional render.

The textures of the old 2.0 head and body, used for the promotion. Their file names were JohnHead.png and JohnTex.png, respectively.

Oddly enough, it doesn't have a singular texture, which may have been because they planned to have full head and body replacement textures, similar to how pants and shirts work if the pants meant the entire body and the shirt meant the head. Furthermore, there's something in the top left corner that seems to resemble hair texturing (which the promotion render did not have), but it could be something completely unrelated that managed to find its way into the texture, either by pure accident or on purpose.Also noticeable is the drastic changes in pixel quality between JohnHead.png and JohnTex.png. This is quite unusual, seeing as these two textures were supposed to go together, and therefore would imply that they should have the same pixel quality, but they are not the same quality.

2007 Figure

Back in November of 2007, this image was used on the front page of the ROBLOX Website.

It was removed by 2008, being replaced by builderman.

Sounds

While these sounds were deleted, they can be accessed in the library, and so people can use them in their own games.

Text

An XML file for the Supersafe Chat chat options.

Development Related

characterControlScript.rbxmx contains commented out metadata.

This guide provides information on how to download and install JavaFX Scene Builder 2.0 on a Windows, Linux, or Mac OS X system. Download information for the JavaFX Scene Builder samples is also included.

JavaFX Scene Builder is a design tool that enables you to drag and drop graphical user interface (GUI) components onto a JavaFX scene. It can help you to quickly prototype interactive applications that connect GUI components to the application logic. It automatically generates the FXML source code as you define the GUI layout for your application.

System Requirements

Use the following information to help you get set up and successfully start using JavaFX Scene Builder.

• Ensure that your system meets the requirements listed in the JDK Certified System Configurations section of the Java SE Downloads page. JavaFX Scene Builder 2.0 supports the same Java 8, Standard Edition (Java SE 8) platforms that support JavaFX, with the exception of Linux ARM.

• Download JDK 8 from http://www.oracle.com/technetwork/java/javase/downloads/index.html and install it to successfully run the JavaFX Scene Builder 2.0 samples.

• Download and install the latest NetBeans IDE 8.0 software to successfully complete the JavaFX Scene Builder Getting Started tutorial. The tight integration that NetBeans IDE has with JavaFX Scene Builder allows you to easily create a new FXML file, edit it using JavaFX Scene Builder, modify and compile your Java controller source files, and run the sample application used in the tutorial. Download the NetBeans IDE 8.0 software from http://netbeans.org/downloads/.

  However, there are also instructions in the JavaFX Scene Builder Getting Started tutorial that guide you to complete the sample application using only a standalone JavaFX Scene Builder tool and the ANT utility. You can also use Using JavaFX Scene Builder with Java IDEs to get information about how to use other Java IDEs to create JavaFX projects and use Scene Builder to work on the FXML file for your application's GUI layout.

Installation

The JavaFX Scene Builder is available as a Windows package (.msi) for the Windows platform, as a Debian package (.deb) or .tar.gz file for the Linux platform, and as a disk image (.dmg) for the Mac OS X platform.

To install:

1. Download JavaFX Scene Builder from the Additional Resources section of the Java SE Downloads page at http://www.oracle.com/technetwork/java/javase/downloads/index.html.

2. In the JavaFX Scene Builder 2.0 section, accept the license agreement, if you agree to its terms.

3. Click the link for your operating system and follow the prompts to save the installer file.

4. Use the following information to install in your specific platform.

   • (Windows platform) Run the
     javafx_scenebuilder-2_0-windows.msi installer file. Respond to the prompts as indicated in the installation wizard.

     By default, the JavaFX Scene Builder software is installed at
     C:Program FilesOracleJavaFX Scene Builder 2.0 on a Windows platform. If you install JavaFX Scene Builder on a 64-bit Windows machine, the default installation location is C:Program Files (x86)OracleJavaFX Scene Builder 2.0.

   • (Linux platform) Extract the Scene Builder 2.0 files from the javafx_scenebuilder-2_0-linux-<platform>.tar.gz to a directory on your local file system, or double-click the javafx_scenebuilder-2_0-linux-<platform>.deb file to open it with Ubuntu Software Center, where <platform> is either x64 or i586. By default, the Scene Builder application is installed at /opt/JavaFXSceneBuilder2.0/.

   • (Mac OS X platform) Open the
javafx_scenebuilder-2_0-macosx-universal.dmg file and drag the JavaFX Scene Builder 2.0.app application into the Applications folder.

   For any of the supported platforms, the installed software contains the files similar to or a subset of what is shown in Figure 1-1, which shows the installation layout on a Windows platform.

   Figure 1-1 Contents of a JavaFX Scene Builder 2.0 Installation on a Windows Platform

   
   Description of 'Figure 1-1 Contents of a JavaFX Scene Builder 2.0 Installation on a Windows Platform'
   

   /app - Contains the JavaFX Scene Builder properties files and libraries.

   /runtime - Contains a copy of the Java Runtime Environment (JRE), which includes executable files and libraries that enable JavaFX Scene Builder to run standalone.

   COPYRIGHT.html - Contains the copyright information for JavaFX Scene Builder.

   JavaFX Scene Builder 2.0.exe - JavaFX Scene Builder executable file.

   JavaFX Scene Builder 2.0.ico - JavaFX Scene Builder icon file.

   msvcr100.dll - Microsoft runtime library.

   README.html - Contains a pointer to the JavaFX Scene Builder README page.

   THIRDPARTYLICENSEREADME.txt - Contains the list of third-party licenses.

Getting Started

To get started with Scene Builder, read through the following documentation:

• JavaFX Scene Builder Overview - A high level overview of the JavaFX Scene Builder 2.0 tool

• JavaFX Scene Builder User Guide - An introduction to the user interface and features of JavaFX Scene Builder 2.0

• Getting Started with JavaFX Scene Builder - A step-by-step tutorial for creating the FXML file that defines the user interface of a simple issue tracking application

• Using JavaFX Scene Builder with Java IDEs - A tutorial that gives information about how to configure the NetBeans, Eclipse, or IntelliJ IDEs to use with Scene Builder.

Running the JavaFX Scene Builder Samples

Download the JavaFX Scene Builder samples to see some applications you can build using the Scene Builder tool.

1. Go to the Additional Resources section of the download page at http://www.oracle.com/technetwork/java/javase/downloads/index.html.

2. Locate the JavaFX Scene Builder section, click the Samples link, and follow the prompts to save the javafx_scenebuilder_samples-2_0.zip file to your local file system.

3. Extract the sample files from the zip file to a directory on your local file system.

Each sample is a NetBeans project and also includes at least one JavaFX layout stored as an FXML file. The <sample>.fxml file can be loaded and edited using the JavaFX Scene Builder.

To run the samples, you must have the JDK 8 software. Since the samples include the corresponding NetBeans projects files, using the NetBeans IDE is the simplest way to run the sample applications. However, you can also run them using the Ant utility, Eclipse, or IntelliJ IDEA. See below for more information.

Using NetBeans IDE

Use NetBeans 8 or later to run the JavaFX Scene Builder 8.0 samples.

1. Go to the javafx_scenebuilder_samples-2_0-install directory in which you extracted the sample files.

2. Run a sample by opening the project in the NetBeans IDE, compiling it, and then running it. For example, to run the Login application, open the Login project in NetBeans IDE, right-click the project node in the Projects window, and select Run.
   Source code for each sample is in the src folder for each NetBeans project.

Using Eclipse or IntelliJ IDEA

See Using JavaFX Scene Builder with Java IDEs for information on how to run the samples in either the Eclipse or IntelliJ IDEA environment.

Using the Ant Utility

If you choose not to run the samples in NetBeans or any other IDE, you can use the Apache Ant utility (version 1.8 or later) to build and run the sample application on the command line. Enter a command similar to that in Example 1-1. Note that the examples shown use JDK 8.

Example 1-1 Ant Command to Run the Sample Application

The main values for <TARGET> are clean, jar, and run. You can set <TARGET> with the value of -projecthelp to get a list of available targets. For example, to run the Login application on the Windows or Mac OS platform, type something similar to that in Example 1-2.

Uninstalling JavaFX Scene Builder

To uninstall JavaFX Scene Builder, use the standard uninstall process for your operating system.