Born 1972 in Uppland, Sweden. Studying Computer Science [L1 ] at Link�ping Institute of Technology, Linguistics [L2 ] at Link�ping University and finally Computational Linguistics [L3 ] at G�teborg University.
gpl @ nakawe.se veronical - Tcl'ers chat [http://mini.net/cgi-bin/chat.cgi] mindtrader - sourceforge [http://sourceforge.net] and savannah [http://savannah.gnu.org] mindtrader? Read Clifford D. Simak's Time is the Simplest Thing, and figure it out...
UIE - User Interface Engine A software architecture designed to provide a generic interface between different programming languages. UIE combines event driven, declarative, object oriented and functional programming with natural language and databases. And provides concurrent processing by means of message passing.
Mimers brunn [L4 ] will become part of the UIE toolbox.
UIE toolbox - UIE development for Tclkit [L5 ] - http:// coming soon
UIE administrator - stay organized with Wikit [L6 ] - http:// coming soon
UIE communicator - communicate with Tcllib [L7 ] - http:// coming soon
I will be talking about UIE and UIE toolbox at Spr�kteknologidagen http://www.cling.gu.se/sprakteknologidag 16 May 2003, 15:00 at G�teborg University, Sweden. The talk is open to the public but the seating is *very* limited. If you wish to attend please contact Christine Lundell, [email protected] as soon as possible so that she can make alternative arrangements if a lot of people wish to attend. The talk will also be published here on the 17th for anyone that is interested.
The UIE Architecture
Pending ... Definition:
A software architecture designed to provide a generic interface between different programming languages. UIE is based around the concept of selfcontained objects, just like in object oriented programming. Unlike OO where the functions are bound to one specific object, UIE's functions are also self- contained first order objects as in functional programming. UIE also separates the data from the rest of the application by using a database server. To add further isolation between the software components, the result of functions are treated like any other data, which leads to a combination of declarative and functional programming.
Implementation:
Programming in UIE is done top-down rather than bottom-up. Starting with abstract objects and functions, and working downwards towards the actual code base that is kept isolated in the bottom layer. Implementing the UIE architecture led directly to several additional features, such as compactness and stability, natural language (without) processing, portability and living user interfaces.
Veronica Loell, 10 may 2003.
See also Concepts of Architectural Design for Tcl Applications.