Part of the research conducted at the Luxembourg Institute of Science and Technology, and before that in the Public Research Centre Henri Tudor, probes the boundaries of current technologies. As we are oriented towards applied research, it is not uncommon to produce tools and frameworks that will help us in conducting our research and, hopefully, be useful to partners to implement their business plans.
TULIP is the result of such a process. The following paragraphs will give a brief history of the framework with the tale of how it came to be together with a brief presentation of team members. Later paragraphs will then deal with concepts and technical details.
TULIP was designed and implemented in an iterative process as of 2014. The bulk of the framework has been developed by @etobias with the help of and under the watchful eyes of @vmaquil who heads the research activities in the Natural User Interfaces domain. From January to June 2014 the framework saw the first major developments with some complementary implementation and bug fixing activity done during the Summer and Fall of 2014. In Fall 2014, @yrangoni added the first traces of a lightweight logging library.
In January 2015 the project was migrated to Git, using GitLab as a platform.
We currently develop an adapter for the computer vision framework and are in the stages of testing it. Similarly, we are developing adapters to address networked devices.
Libraries and Licenses
TULIP, as of July 2015 is available under an LGPL version 3. We are still actively developing and redesigning parts of the software but feel free to use and contribute TULIP. We welcome any feedback and would love to hear your inputs and experiences regarding TULIP.
We plan on developing an audio feedback dimension that functions similar to the coronas. We also plan to modularise the adapters and distribute them separately so adopters can import only the adapters they need.
The TULIP framework offers facilities that make it easier for new adopters to the world of tabletop Tangible User Interfaces (TUI) to start writing their applications without having to start from scratch. The framework itself drives a few activities and tracks some items that are needed by said interface while offering some configuration facilities that should allow the framework to be adopted to many tabletop set-ups. TULIP features a layered architecture: