BlueBrick: Difference between revisions
(correct links to RB site) |
mNo edit summary |
||
| (13 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
{{Software | |||
|logo = {{software/logo|BlueBrick icon.png|32px}} | |||
|developer = Alban Nanty | |||
|version = 1.8.2 | |||
|operating system = Windows 2000 and later<br>Mac OS X {{comment|using Mono}}<br>Linux {{comment|using Mono}} | |||
|language = English | |||
|genre = Train layout design | |||
|license = GNU GPL | |||
|website = [http://bluebrick.lswproject.com/ bluebrick.lswproject.com] | |||
}} | |||
It uses a layers paradigm, where elements can be placed on various layers, and layers made visible or invisible. There are | '''BlueBrick''', by Alban Nanty, is a software for designing LEGO Train layouts. It has an LDraw input and output mode, and can produce either .ldr or .mpd files. But since BlueBrick does not directly use the LDraw parts library, when reading a LDRAW file, BlueBrick may display unrecognized parts with a default "missing part" red cross image. | ||
BlueBrick also can read and create [[Track Designer]] files, and requires Dot Net 2.X to run on MS Windows, or Mono to run under Linux or Mac. | |||
BlueBrick uses a layers paradigm, where elements can be placed on various layers, and layers made visible or invisible. There are four different types of layers: Grid, Brick, Area Assignment and Annotation. Brick layers is actually a generic part layer that can contains table, baseplates, road or train tracks. Thus, one can do tables on a table layer, lay down roads and baseplates on a baseplate layer, and so forth. Layers can be reordered, and made visible or hidden as needed. Any layer can be made translucent using a slider scale, which is quite convenient for the area layers. | |||
Track and roads feature connection points to allow for easy alignment and there is an adjustable snap-to grid. | Track and roads feature connection points to allow for easy alignment and there is an adjustable snap-to grid. | ||
==External links== | ==External links== | ||
* [http://bluebrick.lswproject.com/ Alban's site] for more information. | * [http://bluebrick.lswproject.com/ Alban's site] for more information. | ||
* The [http://railbricks.com/ RailBricks] site, issue [http://www.railbricks.com/ | * The [http://railbricks.com/ RailBricks] site, issue [http://web.archive.org/web/20110716165737/http://www.railbricks.com/media/railbricks_3.pdf three] (web PDF link) has a review (page 6) and a writeup of what was determined about the Track Designer format (page 7). | ||
Latest revision as of 13:58, 4 May 2018
| BlueBrick | ||||||||||||||||||||
| ||||||||||||||||||||
| Software infobox | ||||||||||||||||||||
BlueBrick, by Alban Nanty, is a software for designing LEGO Train layouts. It has an LDraw input and output mode, and can produce either .ldr or .mpd files. But since BlueBrick does not directly use the LDraw parts library, when reading a LDRAW file, BlueBrick may display unrecognized parts with a default "missing part" red cross image.
BlueBrick also can read and create Track Designer files, and requires Dot Net 2.X to run on MS Windows, or Mono to run under Linux or Mac.
BlueBrick uses a layers paradigm, where elements can be placed on various layers, and layers made visible or invisible. There are four different types of layers: Grid, Brick, Area Assignment and Annotation. Brick layers is actually a generic part layer that can contains table, baseplates, road or train tracks. Thus, one can do tables on a table layer, lay down roads and baseplates on a baseplate layer, and so forth. Layers can be reordered, and made visible or hidden as needed. Any layer can be made translucent using a slider scale, which is quite convenient for the area layers.
Track and roads feature connection points to allow for easy alignment and there is an adjustable snap-to grid.
External links
- Alban's site for more information.
- The RailBricks site, issue three (web PDF link) has a review (page 6) and a writeup of what was determined about the Track Designer format (page 7).