Fragment repository

[twolfson]

I still don't know the complexity of releasing small modules for Python but to stay as true to "One Thing Well" as possible, we should fragment this repo.

The utils seem like they each could be fragmented and optimized (selection is a perfect example of expanding scope for open source).

The base and TestCase could be separated into different repositories for specialized tests and quicker debugging.

[twolfson]

Fragmentation notes from a few nights back:

• Abstract sublime command harness
  • which has cmd to add file to dir hanress (at any relative subpath)
• The plan should be to namespace harness directories so we can have concurrent non-colliding plugins
  • The command.py will namespace the command too (i.e. the sublime_text --command trigger)
• The add file command will be used at all steps (e.g. command.py)

[twolfson]

The take away from the last comment: Fragment off a harness repo which allows for adding and running an arbitrary Python command in sublime from the command line. It should include namespacing of the command/directories so they can be run concurrently without the potential for conflict.

The testing framework would build on top of that with writing out results to a file then parsing them as if it were a test (current situation).

[twolfson]

Tests that we need with respect to the execfile fiasco:

• "import" picks up instantaneous changes (write file to disk, import)
• "import" retains imported file's globals at runtime

import sys

def main():
  # This should be retained, eval + compile lost them =(
  return sys

[twolfson]

Work for execfile + Sublime Text 3 can be found in 04dc0a5

[twolfson]

Sleep notes

Fragments:

• launcher
• TDD setup
• execfile junk
• sublime utils
  • split slection
  • second guessing this, maybe put it in a base wrapper which TDD extends?
  • also, it might be better to abstract interpolation into a library itself
  • maybe try jison/bison?

---

For fragmentation, a separate launcher/harness would make the most sense

• Run arbitrary Python in subl from Python
  • v1 = --command / init
  • v2 = http server (a la phantomjs node_module)
  • this has much more complexity but allows for a lot more actions
  • it should be considered an entirely different module and not a v2

---

Sublime info package which has:

• package dir
• CLI locations (e.g. is it subl or sublime_text)
• build number

[twolfson]

More notes from last night:

Installer - bash script to perform Travis installs

Info - ST locations, pkg dir

Launcher with namespace - Launch ST under a specific namespace

Assertion - Base layer of TDD and other testing implementations (provides try/catch/finally harness and wrapper)

TDD - Thin layer around unittest.TestCase to use all test cases under the Assertion layer

---

Make Sublime Text installer standalone and possibly python-less

curl | sh

---

Definitely semver the bash script