ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Dream Maker

by seiyria ST2/ST3

A Sublime Text 2 Theme/Build System for Dream Maker (http://byond.com)

Details

  • 2015.09.04.00.19.43
  • github.​com
  • github.​com
  • 2 years ago
  • 38 minutes ago
  • 4 years ago

Installs

  • Total 415
  • Win 316
  • OS X 50
  • Linux 49
Oct 23 Oct 22 Oct 21 Oct 20 Oct 19 Oct 18 Oct 17 Oct 16 Oct 15 Oct 14 Oct 13 Oct 12 Oct 11 Oct 10 Oct 9 Oct 8 Oct 7 Oct 6 Oct 5 Oct 4 Oct 3 Oct 2 Oct 1 Sep 30 Sep 29 Sep 28 Sep 27 Sep 26 Sep 25 Sep 24 Sep 23 Sep 22 Sep 21 Sep 20 Sep 19 Sep 18 Sep 17 Sep 16 Sep 15 Sep 14 Sep 13 Sep 12 Sep 11 Sep 10 Sep 9 Sep 8
Windows 1 0 0 0 2 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 1
OS X 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

sublime-dreams

A Sublime Text 2 Theme/Build System for Dream Maker (http://byond.com)

Highlighting

Currently correctly highlighting: * All language keywords * Pre-processor macros * Strings (single and double quote) * Proc names (including built-in procs) * Numeric variables * Built-in functions * Language constants * Embedded expressions * Operators (most themes ignore these) * DMF files

Autocompletion

Currently there is an autocompletion entry for every variable that I could glean out of the reference. I have also added this feature for procs. They can be tabbed through much like the snippets below.

Themes

We provide two themes: Dark Dreams and Light Dreams. Light Dreams is what a DM programmer is most familiar with - it's the exact same color scheme. Dark Dreams is a dark theme that matches DMs specific syntax, except in a dark theme.

Build System

The build system currently only has the option to build an individual file or an environment. It searches for an environment by checking each parent folder recursively until it finds a .dme file. If it does not find one, it will only compile the current file. If multiple environments are found in the same folder, the first one will be chosen.

There are options to launch the environment in Dream Seeker or Dream Daemon. By default, running a new Dream Seeker instance will kill a previous one. This helps prevent RSC locking and makes testing a bit easier.

Snippet Autocompletion

Currently supported are:

def<tab> expands to:

#ifndef SYMBOL
#define SYMBOL value
#endif

if<tab> expands to: “ if (/* condition /) / code */

do\<tab>
expands to:

do /* code / while (/ condition */);

for\<tab>
expands to:

for (var i = 0; i < count; ++i) /* code */

forin\<tab>
expands to:

for (var i in 1 to count) /* code */

forinstep\<tab>
expands to:

for (var i in 1 to count step 2) /* code */

To make the most of the snippet auto-completion, after the initial tab, keep hitting tab to change positions.

Got useful snippets? Send a pull request!

Potential Future Features
=========================
*  Auto-reboot DreamDaemon on build
*  Auto-join DreamDaemon as self
*  Auto-join DreamDaemon with x keys/guests
*  Update DME with new file entries