Making Tcl "legacy" code object oriented by Artur Trzewik
Man könnte es nennen: "XOTclIDE next steps" oder "Objectorientation with XOTclIDE". Die Objektorientierung mit Tcl wird letzte Zeit wieder heiß diskutiert. Interesant könnte sein, eine Darstellung wie man ein herkömmliches Tcl-Programm zu XOTcl umwandelt und welche Vorteile
oder Nachteile sich dadurch ergeben.
Biotcl - a framework for computing biology by Detlef Groth
* Tcl becomes was Perl, Python, Java, Ruby already have
* Snit, Metakit and minihttpd as the foundation for framework development
* Starkits as the delivery platform
* no install step
* biotcl.kit - one file - will contain applications, libraries, webserver and documentation
Abstract
Currently from the four most important scripting languages (Perl, Python, Tcl and Ruby) only Tcl is missing a structured framework of tools and applications for computational molecular biology. This is a surprising issue because its clear syntax, high portability and extensibility makes Tcl an ideal choice as a scripting language for biological problems. We will present the status of our ongoing biotcl project [1]. The principal suggestion it that we will restrict mostly to tcl only libraries in order to achieve maximum portability. The following libraries will be the basis for developing biotcl-applications and libraries:
* Snit as the object oriented extension
* Metakit as RDBMS possibly with tsql4mk as SQL-Layer on top
* a small embedded webserver based on minihttpd
Applications, Libraries and Documentation (Wiki/HTML format) will be
delivered as one single starkitfile only in order to simplify
installation, maintainance as much as possible.
Sharpen Up Your Act by Brian Passingham
+ Introduction
- Vignette and "TCL"
- Typical Vignette codebase characteristics
+ Tcl Tools
- Survey of available tools
(ActiveState/T-IDE/Nagelfar etc)
- Why they can't be used in the Vignette context
+ Sharpen Approach
- Design of parser and supporting XML "interface definitions"
+ Other Related Work
- All I've found so far is Stefan Vogel's TrapEd
+ Current Status
- A "lint" for Vignette
+ Future
- Design recovery
- Code transformation
- Refactoring editor for Tcl???
+ Q&A
VCRI by Marcel Broeken and Jos Jaspers
Background
In
the PRO-ICT project a groupware environment has been created, to
facilitate collaborative writing in project based learning assignments
in secondary schools. In this VCRI
(Virtual Collaborative Research
Institute). The base environment of VCRI included three tools: a
database of relevant historical information sources (Database), a chat
facility for deliberation between the students (Chat) and a shared text
processor (Co-writer). The Co-writer allows the students to
work on the texts of their assignments simultaneously. Visualization
of argumentative ideas (Diagram), selection within sources (Selector)
and publishing of intermediate results (Publisher) were supported by
cognitive tools. Meta-cognitive tools supported the planning (Planner),
monitoring (Logbook)
and reflective activities (Reflector) of the students. With the Coach
program,
the teachers could monitor the progress of their students and provide
feedback
to the group or to individual teams. Screen dumps of the tools can be
found
at the project website: http://edugate.fss.uu.nl/vcri.
Outline of the
presentation:
What is the VCRI?
A bit of history
Who uses it?
Architecture
Tools
Problems
Solutions
Future
Drawing diagrams by Arjen Markus
The "What you see is what you get" or WYSIWYG paradigm is so commonly
used in computer applications these days that you would almost forget
that there are other solutions too. The problem with WYSIWYG is twofold:
first of all it can lead to very complicated user-interfaces - all
functionality has to be reachable by a few mouse clicks. So we end up
with a myriad of menu options, dialgoues and toolbars just to fit them
all into the screen somewhere. The second troublesome aspect of WYSIWYG
is this: what happens if you are not satisified with what you see? You
go and try to make it look better. In other words: it distracts from the
contents. One type of application where this is very evident is drawing
diagrams.
Typical diagrams are: flow diagrams, UML-style diagrams, diagrams
showing some computer network or organograms. It is tedious to manually
align the rectangles and circles, to centre the text and so on. Instead
you need to draw a high-level object - a box with associated text, an
arrow that is attached to two such objects, location and orientation
should be relative to other objects.
This article describes a little package, loosely based on the once
famous PIC drawing package, that provides a command-driven approach to
drawing diagrams. It illustrates the use of this technique in several
practical cases.
Doing 3D with Tcl by Paul Obermeier
1. Overview of existing solutions
+ Light-weight solutions: OpenGL Tcl-Bindings (tkogl, togl, ...)
+ Heavy-weight solutions: Tcl-Bindings of graphic APIs (Nebula, iVRS,...)
2. My personal wish-list
+ Light-weight OpenGL binding
+ BSD License
+ Highly automated (Swig generated IF)
+ Full scriptable OpenGL interface
+ Expandable with C-modules
3. Implementation issues
+ Currently in work