Program

First TIP #399 was developed and voted yes, which allows to preload multiple languages.

This is sufficient for the upper case but not satisfactory for TCL in general. Specially the clock command has a high demand on msgcat, which is currently implemented by internal tweeks.

• dynamically load and unload locales
• all operations also possible only on package level
• command to check if a translation is present (clock)
• callback on locale change (asked by aku)
• callback on required mcload (to support other sources like db)

• is the proposed tip wise
• should a compatibility mode be included
• how to deal with tcloo (I have no idea)

1. narray http://www.ncnr.nist.gov/staff/nickm/narray.html
2. NAP http://chiselapp.com/user/jima/repository/napcore/
3. blt::vector http://rbctoolkit.sourceforge.net/
4. tcl-tna https://github.com/jbroll/tcl-tna
5. tensor http://web.eecs.umich.edu/~mckay/computer/tensor4.0a1.tar.gz
6. http://www.tcl.tk/cgi-bin/tct/tip/363.html
7. http://www.tcl.tk/cgi-bin/tct/tip/420.html
8. VecTcl https:// https://github.com/auriocus/VecTcl

In my talk I want to show some applications using very simple interfaces and to demonstrate, how to control them with Tcl.
These interfaces are enabled e.g. simply by photo-resistors that detect light intensity of an area of the computer display or the microphone to detect sound pulses of an RC-oscillator.

It shows how this technology can deploy applications to over hundreds of customers in a multi platform environment using multiple tdbc and/or native dbms interfaces without any code change.

This talk will examine the difference between the intended use of SQLite versus client/server databases such as PostgreSQL, MySQL, SQL Server, Oracle, etc., and give examples of where SQLite is useful and where those other database engines might be a better fit. The concept of "application file format" will be defined and examined, and it will be argued that SQLite makes a superior application file format in many cases.

The objective of this talk is to give attendees new insights into how SQLite can aid in building ever more powerful applications in Tcl and Tcl/Tk.

It's about measuring and monitoring temperatures with a Raspberry Pi, programmed mostly in Tcl, which is included and pre-installed in Raspbian, the Raspberry Pi version of Debian. One little daemon in Tcl collects the values from all connected sensors on a regular basis and writes them to an SQLite database, plus is makes the current values available for other processes via TCP. Another little daemon in Tcl serves a whole web page with all temperatures which are updated regularly. It gets its data from the first daemon.

Plans are to write another server in Tcl which collects data from a whole bunch of Raspberry Pis distributed across a building complex (like a group of apartment buildings, a campus or the like), saving the data to an SQLite database, presenting them on an electronic dashboard grouped in panels. The monitoring will also include automatic alarms if temperatures leave certain ranges.

The overall goal is to make sure that centralised heating system run smoothly and to inform facility managers promptly, should a problem arise. By comparing temperatures, finding the problem is supposed to be a lot easier. Another benefit would be to accumulate knowledge about how much energy is being consumed where and at what times. This way, the controlling of the heating system can be optimised by hydraulic calibration in order to save enery and cost.