LoomScript TextMate/SublimeText Bundle

Hey all,

This bundle adds some support for LoomScript in TextMate or Sublime Text.

http://dl.dropbox.com/u/41430608/bundles.zip

Give it a shot and feel free to share back any improvements!

Ben

Thanks for posting this. We have been using this bundle internally with Sublime Text for all of our LoomScript development.

What sort of functionality does this provide?

It's primarily syntax highlighting.

This is the syntax file for EditPlus:

http://pub.bitgap.com/loom/loomscript-stx.zip

Last updated: Feb 21, 2013

I didn't want to start a whole new thread for this question, as it is Sublime Text related, but has anyone bothered setting up a custom build system for LS in Sublime Text 2? I managed to get it going (basically, just get ST to run "loom run" for me...), but once I ran my project with it one, subsequent "loom run" calls, either via ST or via the Terminal give me the following error:

[loom.asset] assetAgent is already running; you only want one instance at a time.
Error: end of file reached.

My build script in ST is just this simple little guy:

{
"cmd": ["loom", "run"],
"path": "/usr/bin",
"working_dir": "$project_path"
}

For sublime text I would reccommend running a loom run --noconsole as loom run uses some terminal features for console input and cleaning itself up

Thanks Jeremy, that worked perfectly :)

Hey guys, this is bundle that we use for TextMate/SublimeText:

https://dl.dropbox.com/u/9150007/loom/ls_bundle.zip

Cheers,
Nate

Hi,

so do I understand this correct: if I develop under windows, I should use http://www.sublimetext.com/2 and the bundle linked here?

What has to be done, such that I can debug my scripts?
I though I read something somewhere, but can't find it anymore ...

Thanks!

To Debug your scripts, you can use to commandline debugger, ldb.
You can invoke the debugger with the following command:

loom debug

And Invoke the help:

LDB>help

Thanks for the quick reply!

Hmm ... looks like I have to get used to the command line (as a UI-spoiled Windows user, this is quite a task ;) )

Just a side question: do you use this a lot, or do you start logging vars to the console when working actively?
I could imagine that with the live update, this could be more comfortable ^{^}

I also installed the LoomScript bundle for Sublime. Reading the above posts, this is still "only" for syntax highlighting, right?

Here is another post on using SublimeText2 in more of an IDE setup

http://theengine.co/forums/loom-with-loomscript/topics/setting-up-sublime-text-2-as-an-ide-for-loom

You can use Console.print() styled debugging, there is also a loom debug command which allows you to set breakpoints and inspect local variables

loom debug (and once it is running) type help

We do have a proper IDE in development.

You should submit the LoomScript package to the Package Control repo (http://wbond.net/sublime_packages/package_control). Then it's just a keystroke away!

Whoops, here's how to submit: http://wbond.net/sublime_packages/package_control/package_developers#Submitting_a_Package