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
  • 3 years ago
  • 1 hour ago
  • 5 years ago

Installs

  • Total 470
  • Win 363
  • OS X 54
  • Linux 53
Apr 21 Apr 20 Apr 19 Apr 18 Apr 17 Apr 16 Apr 15 Apr 14 Apr 13 Apr 12 Apr 11 Apr 10 Apr 9 Apr 8 Apr 7 Apr 6 Apr 5 Apr 4 Apr 3 Apr 2 Apr 1 Mar 31 Mar 30 Mar 29 Mar 28 Mar 27 Mar 26 Mar 25 Mar 24 Mar 23 Mar 22 Mar 21 Mar 20 Mar 19 Mar 18 Mar 17 Mar 16 Mar 15 Mar 14 Mar 13 Mar 12 Mar 11 Mar 10 Mar 9 Mar 8
Windows 0 1 1 1 1 2 1 0 0 0 0 0 1 0 0 2 0 0 0 0 0 0 0 1 1 1 2 0 1 2 0 1 1 0 0 1 0 0 0 0 0 0 0 1 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 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 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

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