EuroTcl Logo
Home
Registration
Currently selected Program
Accomodation
Travel
Past Events
Sponsors
ICT Logo

Program

General information

There will be a come-together on Friday evening for those arriving in Eindhoven the day before the meeting.
We will meet in the Cafe Usine, which is in walking distance from the main station for eating, drinking and talking.
It will start at 17:00 and you can join anytime depending on your arrival time.

Program Schedule

To be filled soon.

Talks and Presentations

Steve Landers
Jan Nijtmans
René Zaumseil
Christian Werner
Christian Gollwitzer
Richard Hipp
Jayanta Majumder
Jos Decoster and Steve Landers
Nathan Coulter
Steve Landers
A Tcl-based Kanban board for Fossil tickets

Kanban is a scheduling technique originally developed at Toyota in the 1950s to support lean and just-in-time manufacturing.
The word Kanban means signboard or billboard in Japanese, and Kanban has become popular in so-called agile or lean development as a way to provide flexible visual planning with continuous delivery.
The Fossil Distributed Version Control System contains an integrated ticket system for tracking bugs and feature requests.

This talk describes the marriage of the two: a Kanban board built on the Fossil ticket system along with a set of conventions to allow visual monitoring and management of tasks within a software development team and an interface to the Slack messaging application for team communication.

Jan Nijtmans
Semantic Versioning

The current supported versions of Tcl are 8.6.5 and 8.5.19. But what do those numbers mean? The answer: Nothing.
Intuitively some could say that 8.6.5 has more features than 8.5.19, and that 8.5.19 was 19 releases after 8.5.0, but it doesn't say anything on whether some particular script which ran fine with Tcl 8.5.0 will still run fine on Tcl 8.5.19 and/or 8.6.5.

This presentation will explain the concept of "Semantic Versioning", which is an attempt to give a more precise meaning to version numbers.
What would be the consequences if Tcl would adopt that idea? What would be gained by that, and what would be lost? A TIP is currently in progress (TIP #439) outlining this. Feedback on this presentation will be used to finalize the TIP and prepare it for a vote.

René Zaumseil
Testing the limits - tcl/tk in power plant simulation

The talk will give a short overview of the simulator and then present the software structure and the used packages of the newly developed tcl applications.
Additionally will be a live presentation of the simulator and of some key applications.

Christian Werner
Title

Abstract

Christian Gollwitzer
Reflecting on EIAS

Everything is a string (EIAS) is one of the fundamental rules of the Tcl programming language.
Even though a value in Tcl can have an internal representation that differs from a pure string value since Tcl 8, a pure script program cannot decide between values that are stored as strings and others, leaving aside the debug APIs in tcl::unsupported. At the C level, the set of representations stored in a Tcl_Obj can be extended, which is widely used within the Tcl core itself.

In this talk, an extension is presented which reflects the Tcl_Obj API into the script level [1]. While this extension itself deliberately breaks EIAS, the scripted Tcl_Obj types can be implemented in a fully EIAS conforming way.
A number of applications is shown, comprising ordered sets, automatic garbage collection and generators, which could not be implemented efficiently at the script level without this extension. It is shown that breaking EIAS in a controlled way coud pave the way for interesting features in Tcl 9.

Richard Hipp
Title

Abstract

Jayanta Majumder
Title

Abstract

Jos Decoster and Steve Landers
The evolution of the Tcler’s Wiki

The Tclers Wiki has been around since 1999 and is arguably the second oldest wiki still running. During that time it evolved from a simple built-in web server using the Metakit database, to deploying as a starkit, to using the SQLite database via TDBC, to using the Wub web server. It has also had a couple of makeovers, the most recent being in 2008. The one constant during that time has been the markup language. Although it has itself evolved, a page authored in 1999 will still render today.

But the wiki is in serious need of improvement: it looks dated and doesn’t support the workflow needed to curate the contents. This has to be done without breaking any of the approximately 20,000 pages of content.

This presentation introduces Nikit, the system behind the next generation Tclers Wiki. It covers the architectural design, the choice of web server and database engine, the markup language, the performance features, the "look and feel" and the spam mitigation techniques designed to allow the Tclers Wiki to remain "open".

Nathan Coulter
coroutine is the new main

Since their introduction in Tcl 8.5, coroutines have slowly but surely worked their way into the standard repertoire of the modern Tcl script author. New patterns for the effective use of coroutines continue to evolve. One exciting prospect is a number of coroutines operating cooperatively using a client-server strategy.

{ycl coro relay} provides two commands, [order] and [receive], for clients, and two more commands, [accept] and [deliver], for servers. The Tcl event loop doubles as a sort of transport mechanism, with [accept] and [receive] functioning as synchronization points. Any main script that is written as a coroutine can take full advantage of this system and of the brave new world it portends.