Skip to content

Where we're going with this

campadrenalin edited this page Apr 20, 2012 · 3 revisions

Our intention is to create libraries that allow developers to easily integrate CTree technology into their own projects, as well as provide a reference implementation, and as much documentation as it takes to get people off the ground.

Orchard timeline

  • Orchard 1.0
    • Use a lightweight JS client connected to a Python backend.
    • Support BCP, and MCP.
  • Orchard 2.0
    • Move to a full JS/Titanium system.
    • Split from Python library into its own repository
    • Support mobile and desktop
    • No BCP, use MCP over public or personal mob_tunnel

ConcurrenTree timeline

  • libctree 1.0

    • Python Library (BCP & MCP)
  • libctree 2.0

    • Python Library (BCP & MCP)
    • JS Library (BCP & MCP)
    • C++ Library?
    • Comes with mob_tunnel, an MCP node daemon that runs in the background, providing BCP with only the MCP extension. Mob_tunnel is good for servers and regular users alike.
    • Does not come with Orchard, though Orchard uses the JS Library

Clone this wiki locally