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
  • 47 minutes ago
  • 4 years ago

Installs

  • Total 430
  • Win 327
  • OS X 51
  • Linux 52
Jan 21 Jan 20 Jan 19 Jan 18 Jan 17 Jan 16 Jan 15 Jan 14 Jan 13 Jan 12 Jan 11 Jan 10 Jan 9 Jan 8 Jan 7 Jan 6 Jan 5 Jan 4 Jan 3 Jan 2 Jan 1 Dec 31 Dec 30 Dec 29 Dec 28 Dec 27 Dec 26 Dec 25 Dec 24 Dec 23 Dec 22 Dec 21 Dec 20 Dec 19 Dec 18 Dec 17 Dec 16 Dec 15 Dec 14 Dec 13 Dec 12 Dec 11 Dec 10 Dec 9 Dec 8
Windows 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 0
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 1 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 1 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