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
  • 4 years ago
  • 4 hours ago
  • 6 years ago

Installs

  • Total 601
  • Win 476
  • OS X 58
  • Linux 67
Aug 23 Aug 22 Aug 21 Aug 20 Aug 19 Aug 18 Aug 17 Aug 16 Aug 15 Aug 14 Aug 13 Aug 12 Aug 11 Aug 10 Aug 9 Aug 8 Aug 7 Aug 6 Aug 5 Aug 4 Aug 3 Aug 2 Aug 1 Jul 31 Jul 30 Jul 29 Jul 28 Jul 27 Jul 26 Jul 25 Jul 24 Jul 23 Jul 22 Jul 21 Jul 20 Jul 19 Jul 18 Jul 17 Jul 16 Jul 15 Jul 14 Jul 13 Jul 12 Jul 11 Jul 10
Windows 0 0 0 1 0 0 0 0 1 1 0 0 0 0 2 0 0 0 2 1 0 1 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 0 0 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 0 0 0 0 0 0 0
Linux 0 0 0 1 1 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