There are times when you need to add a lot of data into TACTIC through some custom code. This could be an ingest from the start of a project or some large delivery from an external source. Although you could go directly to the database and execute straight SQL commands Read more…
The TACTIC API is very flexible, allowing you to access almost any of its internal data stored and to execute any command on the system. However, as of TACTIC 4.7+, there are a number of low level stypes in TACTIC cannot normally be queried by users that are not the Read more…
SQL is problematic when it comes to data from querying complex relationships between tables. At first, SQL seems simple enough. If you just want to get all the column for a single row, you can use a simple select statement: SELECT name FROM shot WHERE code = ‘SHOT001’; Because SQL Read more…
The Workflow Engine is one of the key technology components of TACTIC. A workflow defines a set of connected process nodes. Each node represents some work that needs to be done within the entire workflow which constitutes a job. The workflow engine drives the entire work process forward. It is Read more…
TACTIC 4.6 just introduced a new generic REST API which implements most of the TACTIC API. This opens up the TACTIC API to almost all programming languages. There are still some advantages to using the client side libraries for Python and Javascript as there is some custom convenience and logic Read more…
Using the TACTIC 4.6 API from javascript is very simple. You just have to reference a single javascript file. You can either reference a local copy of this file: <script src=”js/tactic.js”> </script> Or you can reference it from TACTIC server itself: <script src=”http://<server>/context/spt_js/tactic.js”> </script> Replace with your own server IP Read more…
TACTIC provides a number of mechanism to Python code on the server. We can start with a widget in the Custom Layout Editor with the HTML definition: <div> <input type=”button press_me” name=”Press Me”/> </div> In the behaviors: var script_path = “my_scripts/press_me”; var kwargs = {}; var server = TacticServerStub.get(); server.execute_python_script(path, Read more…
TACTIC Plugins are a way of packaging up functionality and distributing them to other projects or other servers. The Plugin architecture is very flexible and almost any functionality, large or small can be packaged in as a plugin. A TACTIC Plugin can contain: data configuration python class Images and media Read more…
Dynamic updates allow any part of the page to update itself based on change occurring on the server. To illustrate, begin with a simple element that display the number of assets in the system. <div>${asset_count}</div> In Python, the asset count would be retrieved as follows. asset_count = server.eval(“@COUNT(example/asset)”) When the Read more…
Widgets are self-contained user interface elements. In TACTIC, they combine HTML layout and CSS styling with server-side Python processing, client side Javascript behaviors, all encapsulated in a single entity called a widget. Widgets are a fundamental building block to interfaces in TACTIC. Even the base HTML tags have been mapped Read more…