Weblog Page

From: Marc Spitzer <mspitze1_at_optonline.net>
Date: Sun, 30 Nov 2003 19:02:33 -0500

The --with-tclinclude did not work for --with-actiweb, before in my config line I had a typo(activeweb). Also when looking through
/unix/tcl.m4 I noticed that you use TCL_SRC_DIR instead of TCL_INCLUDE_SPEC(both are defined in tclConfig.sh) for generating the configure script, near as I can tell TCL_INCLUDE_SPEC has all the private include files that xotcl needs. On my box TCL_INCLUDE_SPEC points to /usr/local/include/tcl8.4 and generic/ and unix/ are subdirectories of it.

Thanks again

marc

From: Kristoffer Lawson <setok_at_fishpool.com>
Date: Mon, 6 Sep 2004 16:05:22 +0300 (EEST)

Still looking for an official explanation for the operations of [eval]
(and other stuff I posted), but here's another one. The code follows:

package require XOTcl 1.3
namespace import xotcl::*

Class Foo -parameter doors

Foo instproc init {req} {
     puts $req
}


Object ob

set newOb [Foo new -childof ob hello -doors 4]
puts "Doors: [$newOb doors]"

$newOb proc doStuff {} {
     puts "class: [self class]"
     set newOb [[self class] new -childof [self] whatevah -doors 3]
     puts "Doors: [$newOb doors]"
}


$newOb doStuff

#$newOb eval {
# doStuff
#}

This version correctly states that the class for [self class] is an empty
string. However, if I comment out the "eval" version and use it instead,
[self class] gives me "::xotcl::Object".

                               / http://www.fishpool.com/~setok/

From: Uwe Zdun <uwe.zdun_at_uni-essen.de>
Date: Tue, 27 Feb 2001 17:28:33 +0100

Hi all,

FYI, we'll have a XOTcl Tutorial scheduled at the 2. European Tcl
Conference.

There are still some open slot ... so there's still a chance to
present your XOTcl applications :) Just send an abstract to Carsten Zerbst
(zerbst_at_tu-harburg.de).

Greetings,

Uwe

---------- Fwd ----------
Subject: European Tcl/Tk User Meeting
Date: Tue, 27 Feb 2001 17:17:52 +0100
From: Carsten Zerbst <zerbst_at_tu-harburg.de>


Dear Ladies and Gentleman,

this is the a preliminary schedule for the Tcl/Tk User Meeting. I still
need some papers and a speaker for the keynote.

Bye, Carsten

--
Dipl. Ing. Carsten Zerbst         |   Come to the
                                  |   2. European Tcl Conference 2001 !
zerbst_at_tu-harburg.de              |
http://www.tu-harburg.de/~skfcz   |   http://www.tu-harburg.de/skf/tcltk
-------------------------------------------------------
-- 
Uwe Zdun
Specification of Software Systems, University of Essen
Phone: +49 201 81 00 332, Fax: +49 201 81 00 398
zdun_at_xotcl.org, uwe.zdun_at_uni-essen.de

	07.06.01		08.06.01
09:00	Welcome		Stefan Finzel, ???
09:15		00:30
09:30	Keynote			00:45
09:45	Missing Speaker !!!	00:30	Jochen Lower, Update tdom
10:00	Discussion Future Development
10:15		00:30		00:45
10:30	Break		Break
10:45	Andrej Vckovski, Why using Tcl as a strategic development platform?		Carsten Orthbrandt, Wiggles
11:00
11:15		00:45		00:45
11:30	???		Markus Arjen, Testmake
11:45
12:00		00:45		00:45
12:15	Lunch		Lunch
12:30
12:45
13:00	Uwe Zdun, XOTcl Tutorial		Vogeler, Database Access with Tcl
13:15
13:30				00:45
13:45			M. Giordano and M. Mango Furnari, USING TCL AS MIDDLEWARE FOR A PARALLELIZING ENVIRONMENT DEVELOPMENT
14:00
14:15				00:45
14:30			Break
14:45		02:00
15:00	Break		???
15:15
15:30	Andrej Vckovski, Tcl Web			00:45
15:45			???
16:00
16:15				00:45
16:30			???
16:45
17:00				00:45
17:15		02:00

From: Scott Gargash <scottg_at_atc.creative.com>
Date: Tue, 21 Mar 2006 10:20:26 -0700

xotcl-bounces_at_alice.wu-wien.ac.at wrote on 03/21/2006 02:28:15 AM:

> i do not like the &-suggestions for the xotcl-core, since it looks
> like an operator, not like a name. The &-operator is not
> about fully qualifying a name, but about providing a reference
> in general.

What's the difference (in tcl) between a name and an operator or a name and a reference?

I'm not being sarcastic, you're making a distinction I don't see. The problem here is needing an
external reference to an XOTcl member. In Tcl, that means you need the name of the variable.

> i get the impression that adding these cmds/methods do not reduce
> significantly the clarity. myvar/myvarname makes sense for the
> snitters.

While that may be true for an experienced user, as a new user trying to use XOTcl I find the way
XOTcl uses namespaces (created on demand) to be pretty confusing. Anything that keeps me from
needing to understand that is a good thing. And leaving aside the new user issue, having a
documented access mechanism for clients instead of knowledge of the implementation seems like a good
thing.

Just my opinion.

      Scott

From: Kristoffer Lawson <setok_at_fishpool.com>
Date: Thu, 1 Apr 2004 12:18:41 +0300 (EEST)

On Thu, 1 Apr 2004, Catherine Letondal wrote:

>
> Kristoffer Lawson wrote:
> > On Wed, 31 Mar 2004, Alexandre Dehne wrote:
> >
> > > In order to use biok, I have to install xotcl. My problem with xotcl
> > > installation is that my system is under Fedora and there is no tclInt.h
> > > file under this distribution (even with the tcl-devel package). Of
> > > course, I can uninstall the tcl package and install tcl manually but, by
> > > uninstalling tcl package, other packages are going out and that put me
> > > in trouble ...
> >
> > Well tclInt.h is internal Tcl stuff (unfortunately still required by
> > XOTcl). Does Fedora have a Tcl source package? Would be in that.
> >
> > I think Debian is now clever enough to include tclInt.h in the tcl dev
> > package, although naturally the best would be if external packages no
> > longer needed tclInt.h
>
> Dear Kristoffer,
>
> I don't understand your answer : do you mean that there should be no
> problem at all? But the file tclInt.h does not exist on alexander's disk
> although he has a tcl dev installed.

The second paragraph was about Debian, not Fedora. On Debian I believe
tclInt.h is now included in the dev package. With Fedora I guess he has to
install the source. With any luck, Fedora may have source packages for Tcl
in addition to the normal dev package, but I'm not familiar with it.

                              / http://www.fishpool.com/~setok/

From: Artur Trzewik <mail_at_xdobry.de>
Date: Tue, 06 Nov 2007 20:15:56 +0000

Hello!

Using nested objects to represent graphs could be good solution if you
do not plan to move objects (change graph connection after creating).
Consider that the "rename" method create new objects by copy (see some
old messages in this mailing group)

The standard approach is using association as reference.
The biggest problem is synchronizing references (but there are also
standard solution for this problem from another languages)

Class Node
Node n1
Node n2
Node n2
n2 set parent n1
# use list to store N side of association
n3 set children [list n1 n2]

You can design same helper methods, parameters or even slots to manage it.

# using nested objects

Class Node
Node parent
Node parent::child_for_ever

Using nested objects is good because of simply object lifetime management.
I prefer nested objects when I want to have some control about
destroying groups of objects.

parent destroy
# all children were destroyed too

Artur

> Hi,
> I have a need to represent a directed graph in XoTcl.
>
> '-childof' functionality seems to work well to represent trees.
> Unless I misunderstand, it seems this will force an class-object to
> belong to a single parent (1-to-many relationship).
> Is there a way to represent multiple parents (many-to-many
> relationship) without making multiple copies of nodes along the way?
>
> Any help is appreciated.
>
> thanks,
> -shishir
> ------------------------------------------------------------------------
>
> _______________________________________________
> Xotcl mailing list
> Xotcl_at_alice.wu-wien.ac.at
> http://alice.wu-wien.ac.at/mailman/listinfo/xotcl
>

From: Andreas Kupries <andreask_at_activestate.com>
Date: Mon, 04 Feb 2013 12:13:18 -0800

20'th Annual Tcl/Tk Conference (Tcl'2013)
http://www.tcl.tk/community/tcl2013/

September 23 - 27, 2013
Bourbon Orleans Hotel
New Orleans, Louisiana, USA

Important Dates:

Abstracts and proposals due June 22, 2013
Notification to authors August 5, 2013
Author materials due September 2, 2013
Tutorials Start September 23, 2013
Conference starts September 25, 2013

Email Contact: tclconference_at_googlegroups.com

Submission of Summaries

Tcl/Tk 2013 will be held in New Orleans, Louisiana, USA from September
23 - 27, 2013. The program committee is asking for papers and
presentation proposals from anyone using or developing with Tcl/Tk
(and extensions). Past conferences have seen submissions covering a
wide variety of topics including:

* Scientific and engineering applications
* Industrial controls
* Distributed applications and Network Managment
* Object oriented extensions to Tcl/Tk
* New widgets for Tk
* Simulation and application steering with Tcl/Tk
* Tcl/Tk-centric operating environments
* Tcl/Tk on small and embedded devices
* Medical applications and visualization
* Use of different programming paradigms in Tcl/Tk and proposals for new
  directions.
* New areas of exploration for the Tcl/Tk language

Submissions should consist of an abstract of about 100 words and a
summary of not more than two pages, and should be sent as plain text
to <tclconference AT googlegroups DOT com> no later than August 5,
2013. Authors of accepted abstracts will have until September 2, 2013
to submit their final paper for the inclusion in the conference
proceedings. The proceedings will be made available on digital media,
so extra materials such as presentation slides, code examples, code
for extensions etc. are encouraged.

Printed proceedings will be produced as an on-demand book at lulu.com

The authors will have 25 minutes to present their paper at the
conference.

The program committee will review and evaluate papers according to the
following criteria:

* Quantity and quality of novel content
* Relevance and interest to the Tcl/Tk community
* Suitability of content for presentation at the conference

Proposals may report on commercial or non-commercial systems, but
those with only blatant marketing content will not be accepted.

Application and experience papers need to strike a balance between
background on the application domain and the relevance of Tcl/Tk to
the application. Application and experience papers should clearly
explain how the application or experience illustrates a novel use of
Tcl/Tk, and what lessons the Tcl/Tk community can derive from the
application or experience to apply to their own development efforts.

Papers accompanied by non-disclosure agreements will be returned to
the author(s) unread. All submissions are held in the highest
confidentiality prior to publication in the Proceedings, both as a
matter of policy and in accord with the U. S. Copyright Act of 1976.

The primary author for each accepted paper will receive registration
to the Technical Sessions portion of the conference at a reduced rate.

Other Forms of Participation

The program committee also welcomes proposals for panel discussions of
up to 90 minutes. Proposals should include a list of confirmed
panelists, a title and format, and a panel description with position
statements from each panelist. Panels should have no more than four
speakers, including the panel moderator, and should allow time for
substantial interaction with attendees. Panels are not presentations
of related research papers.

Slots for Works-in-Progress (WIP) presentations and Birds-of-a-Feather
sessions (BOFs) are available on a first-come, first-served basis
starting in August 5, 2013. Specific instructions for reserving WIP
and BOF time slots will be provided in the registration information
available in June 3, 2013. Some WIP and BOF time slots will be held open
for on-site reservation. All attendees with an interesting work in
progress should consider reserving a WIP slot.

Registration Information

More information on the conference is available the conference Web
site (http://www.tcl.tk/community/tcl2013/) and will be published on
various Tcl/Tk-related information channels.

To keep in touch with news regarding the conference and Tcl events in
general, subscribe to the tcl-announce list. See:
http://code.activestate.com/lists/tcl-announce to subscribe to the
tcl-announce mailing list.


Conference Committee

Clif Flynt Noumena Corp General Chair, Website Admin
Andreas Kupries ActiveState Software Inc. Program Chair
Gerald Lester KnG Consulting, LLC Site/Facilities Chair
Arjen Markus Deltares
Brian Griffin Mentor Graphics
Cyndy Lilagan Nat. Museum of Health & Medicine, Chicago
Donal Fellows University of Manchester
Jeffrey Hobbs ActiveState Software Inc.
Kevin Kenny GE Global Research Center
Larry Virden
Mike Doyle National Museum of Health & Medicine, Chicago
Ron Fox NSCL/FRIB Michigan State University
Steve Landers Digital Smarties

Contact Information tclconference_at_googlegroups.com


Tcl'2013 would like to thank those who are sponsoring the conference:

ActiveState Software Inc.
Buonacorsi Foundation
Mentor Graphics
Noumena Corp.
SR Technology
Tcl Community Association

From: Kristoffer Lawson <setok_at_fishpool.com>
Date: Tue, 8 Feb 2005 01:41:35 +0200

On Feb 7, 2005, at 10:20 PM, Gustaf Neumann wrote:

> There are two fixes for that, one simple (don't allow reclassing of
> objects to classes)
> or a more complex one (do more or less a recreate automatically when
> this happens;
> it tries to keep the object information as far as possible).

I don't know the internals really of XOTcl but basically making an
object a class would mean giving it the methods 'instproc' and 'new'
and various other stuff, thus allowing an instance of it to be created.
I guess it's some internal thing if it has to be recreated? In some
sense it would be 'pure' if this was possible.

I wonder if this has any relevance to changing the meta-class of a
class?

                                / http://www.fishpool.com/~setok/

From: Scott Gargash <scottg_at_atc.creative.com>
Date: Fri, 17 Mar 2006 15:13:01 -0700

xotcl-bounces_at_alice.wu-wien.ac.at wrote on 03/17/2006 08:25:37 AM:

>
>
> A double-reference would solve this. In that way the handle returned
> by [new] and [self] would always be a valid command for the object,
> throughout its whole lifetime. If it is moved to be a child of
> another object the handle remains the same (or at least can be used),
> but the ownership is changed. Whether this is workable in XOTcl or
> not is, of course, something you would be better at deciding.

I've been thinking along somewhat different lines, the classic "extra level of indirection" that
solves all problems. What about using interpreter aliases as an indirection? What would happen if
all objects were created as anonymous commands inside (say) the xotcl namespace, and the object name
was just an alias to the anonymous object?

This would let move be straightforward, drop the old alias and create a new one. From what I've
inferred of xotcl's implementation, I think xotcl would be (mostly) unaffected by the change. The
one thing that I think might be busted would be is parent/child relationships. Rather than
introspecting into the commands, you'd have to introspect the aliases (relationships would be
inferred by alias location instead of command location). That might be difficult, Tcl aliases are
surprisingly hard to introspect.

I also don't know what the performance implications would be (I think an alias introduces some
overhead). But if objects didn't ever move, there might be some potential optimizations available
too.

Just a thought...

      Scott

From: Artur Trzewik <mail_at_xdobry.de>
Date: Sun, 19 Nov 2006 18:53:54 +0100

Hi XOTcl friends!

I have found some small incompatibility between XOTcl 1.4 and 1.5 by
using XOTclIDE.
It considers tk binding

I use code as follow

bind $twin <KeyPress-Tab> [list [self] tabPress]

IDE::TclModeEdit instproc tabPress {} {
    # .....
    return -code break
}

the "return -code break" have caused that the event is not propagated more.
See more in Tk bind command manual.

It does not work with XOTcl 1.5.2.
I use small work around by wrapping XOTcl method in Tcl proc now.
XOTcl Method returns a boolean value.

bind $twin <KeyPress-Tab> [list tabPressHandler [self]]

proc tabPressHandler object {
      if {[$object tabPress]} {
          return -code break
     }
}

This incompatibility causes bad behavior in XOTclIDE editor.
(Code completion and automatic indenting).
I plan to ship next XOTclIDE version in some time without this problem.

Artur Trzewik