Weblog Page

From: Artur Trzewik <mail_at_xdobry.de>
Date: Sat, 6 Oct 2001 14:24:27 +0200

Hallo

For XotclIDE I have built a Error Stack browser witch can parse
error messages (in errorInfo) a convert it to methods list.

I have following problem. Consider the example

Class TestA
TestA instproc fooA {} {
  [self] fooC
}
TestA instproc fooB {} {
  fooC
}
TestA instproc fooC {} {
   error {error from fooC}
}

TestA a
a fooA

generate following errorInfo
error from fooC
    while executing
"error {error hier}"
    (procedure "fooC" line 2)
    ::sample0 ::TestA->fooC
    invoked from within
"[self] fooC"
    (procedure "fooA" line 2)
    ::sample0 ::TestA->fooA
    invoked from within

a fooB # generate following message

error from fooC
    while executing
"error {error hier}"
    (procedure "fooC" line 2)
    invoked from within
"fooC"
    (procedure "fooB" line 2)
    ::sample0 ::TestA->fooB
    invoked from within

I the first example we have the lines
   (procedure "fooC" line 2)
    ::sample0 ::TestA->fooC
This can be good used for parsing errorInfo
I the second there are only
   (procedure "fooC" line 2)
The same bahavior is by method chains with "next" or filter methods.

Can the xotcl be changed for same dubug infos?

Artur Trzewik

From: Tuyen Hoang <tuyenqh_at_yahoo.com>
Date: Wed, 16 Mar 2011 05:40:45 -0700 (PDT)

Can anyone tell me how to refer an instvar from within a namespace defined inside a class constructor? With my attempt below the $iss in the tk_messageBox line is undefined. Class create MatlabInterface MatlabInterface instproc init {} { my instvar iss namespace eval MicWatch { proc add {} { tk_messageBox -type ok -icon info -title "MicWatch" -message "$iss" } } } I’m new to Tcl, let alone XOTcl, and don’t know how to search the posts in the mailing list so forgive me if the question has been asked before. Regards, Tuyen

From: Neil Madden <nem_at_cs.nott.ac.uk>
Date: Tue, 27 Sep 2005 02:04:53 +0100

Will Duquette wrote:
> The point of [define] is simply that we want to be able to
> create objects which have a limited set of subcommands. Note
> that there's a distinct difference between writing an OO-API
> using a particular OO-framework for other users of that
> framework, and writing an object-style API for general users,
> many of whom might not care about the OO-framework at all.
> In the first case, you want to include all of the OO-framework's
> bells and whistles, because you expect your users to want to
> take advantage of them. In the latter case, you want to keep
> the API simple, clean, and easily documented.

That's certainly a good goal.

>
> [define] lets us do both. With [define] "instproc" and its
> siblings aren't subcommands of our objects--but at the same time,
> "instproc" and its siblings are available to every user who
> cares about them.

OK. The essential thing being done here then is to break down the
grab-bag of methods defined in Class and Object into a bunch of
different interfaces, so that clients of an object don't have to worry
about a bunch of extra "proc" and "filter" etc methods that have nothing
to do with their problem domain. I can sympathise with that. However,
I'm not sure [define] is the right solution, as it just creates another
bag of methods elsewhere (somewhat like [info] has become). We could
simply change the methods to be class-methods of [class] and [object]
(i.e. procs that expect an explicit self argument, rather than
instance-methods). That way by default objects don't get lots of public
methods that aren't needed by clients, but you can still do, e.g.:

class method myclass someproc {args} { ... }
object method myobj ...
object mixin myobj ...

This also somewhat reduces the need for self.method/method (or
instproc/proc) distinction. Likewise, you could also use it for the
script-style of define:

class define myclass {
     method foo ...
     method bar ...
}

where these are interpreted as [class method myclass ...] and not
[object method myclass ...].

It sort of clashes with previous XOTcl usage, where [class instproc]
means define an instproc on the object "class", but if we change the
name to "method" anyway then this is less of an issue. You could even
leave access to the methods using the form:

myclass class method someproc ...
myobj object method ...

which leaves only one top-level method in objects (two in classes). That
seems a bit more OO-y, but I don't know if it really adds much.

-- Neil

From: Jim Lynch <jim_at_jam.sessionsnet.org>
Date: Fri, 9 Apr 2004 08:10:29 -0700

Hi,

Subject says just about all: (fuzzy, but:) some aolserver support
included even if configure determines no aolserver

Can't fix today; this will take a bit of digging to find all the aolserver
stuff in xotcl, and make it subject to non-inclusion when user says no.

-Jim

--
Jam sessions community web site: http://jam.sessionsnet.org

From: Catherine Letondal <letondal_at_pasteur.fr>
Date: Sat, 06 Jul 2002 10:22:48 +0200

Hi,

I get an error when compiling on Linux (debian potato):

make[1]: Entering directory `/usr/local/packages/xotcl-full-0.9.4/xotcl-0.9.4/unix'
cc -DUSE_TCL_STUBS -DVERSION=\"0.9\" -DXOTCL_LIBRARY=\"/usr/local/lib/xotcl0.9/library\" -I/usr/local/include/tcl8.2/generic -I/usr/local/include/tcl8.2/unix -I"./../generic" -I"./../unix" -I"/usr/local/include" -g -O2 -D__NO_STRING_INLINES -D__NO_MATH_INLINES -fPIC -g -DXOLIBPKG=\"/usr/local/lib/xotcl0.9\" -DXOTCLVERSION=\"0.9\" -DXOTCLPATCHLEVEL=\".4\" -c `echo ../generic/xotcl.c` -o so/xotcl.o
../generic/xotcl.c: In function `TclCommands':
../generic/xotcl.c:9271: syntax error before `initMutex'
../generic/xotcl.c:9275: `initMutex' undeclared (first use in this function)
../generic/xotcl.c:9275: (Each undeclared identifier is reported only once
../generic/xotcl.c:9275: for each function it appears in.)
../generic/xotcl.c:9278: `rc' undeclared (first use in this function)
make[1]: *** [so/xotcl.o] Error 1
make[1]: Leaving directory `/usr/local/packages/xotcl-full-0.9.4/xotcl-0.9.4/unix'
make: *** [libs] Error 1

Thanks in advance for any help,

-- 
Catherine Letondal -- Pasteur Institute Computing Center

From: Kristoffer Lawson <setok_at_fishpool.com>
Date: Thu, 24 May 2001 22:10:28 +0300 (EEST)

Did somebody have a package containing mappings of Tk commands to XOTcl
objects? Or if not that than at least a document or ideas about the things
I should take into account when designing Tk stuff with XOTcl? Maybe
even a TclWiki page? Just so I don't go stumbling across the same problems
others have already solved and thus waste time.

         - ---------- = = ---------//--+
         | / Kristoffer Lawson | www.fishpool.fi|.com
         +-> | setok_at_fishpool.com | - - --+------
             |-- Fishpool Creations Ltd - / |
             +-------- = - - - = --------- /~setok/

From: Artur Trzewik <mail_at_xdobry.de>
Date: Tue, 4 Dec 2001 20:31:00 +0100

Hallo!

The Integrated Development Environment for XOTcl
The new version of XOTclIDE is ready on
http://www.xdobry.de/xotclide

The Changes from last annouced Version 0.22

- tcl-mode editing
  automatic ident with braces search (by inserting new tcl code)
  selecting braces areas by double-cklick directly after open brace
  (good for understand tcl list structures)
- support of using xotclIDE without mouse (tabulator, better tk list support)
- mixin wizard by object inspector (customize object mixins per GUI)
- show all available methods in object inspector (by using info methods)
- class tracker updated for xotcl 0.9
- tracking of objects (method Object>trackOn)
- component rename function
- object browser extended
- automatic importing of xotcl project from source files
   (tested on xoRBAC)

have fun

Artur Trzewik

From: Michael Aram <michael_at_aram.at>
Date: Mon, 19 Oct 2015 13:20:05 +0200

...in response to "
http://alice.wu-wien.ac.at:8000/xotcl-mailing-list/2992.html"...

Dear Prof. Neumann,

thank you very much for the detailed answer; your "patch" seems to solve
the problem.
For the time being, I will leave it as it is; if I encounter other unwanted
side effects during testing I will have to delve deeper (which can be seen
as a precondition to being able to answer your questions).

All the best,
Michael




On Mon, Oct 12, 2015 at 5:10 PM, Michael Aram <michael_at_aram.at> wrote:

> Dear XOTcl/NX/NSF community,
>
> I am in the process of upgrading one of our OpenACS based systems to XOTcl
> 2 and stumbled over the following legacy code:
>
> Class create Person -slots {
> foreach e {username first_names last_name email etcetera} {
> Attribute $e -default "" -proc assign {o var value} {$o changed_var
> $var $value}
> }
> }
>
> Person ad_instproc -private changed_var {var value} {} {
> my instvar __changed_vars
> lappend __changed_vars $var
> my instvar $var
> set $var $value
> }
>
>
> The intention of this not-so-pretty code mainly seems to be that the
> Person->save method called by code like the following can recognize which
> attributes have actually changed during the last request, and update the
> database accordingly...
>
> Person john
> john last_name doe
> john save
>
>
> For some reason, now that I have upgraded the system to XOTcl 2, this does
> not work anymore. The list __changed_vars is not updated (in the example
> above, it would not contain last_name; for debugging purposes, I have put a
> log statement into the "assign" proc, it seems that it does not get called.)
>
> As the update process introduced many many other changes as well (compared
> to the old and adapted OpenACS we had there), including changes in
> xotcl-core, it could certainly be the case that this is simply a the
> side-effect of some other change / or messed-up merge. So, my question is,
> SHOULD this work anyway in the latest stable version of XOTcl 2, or did the
> interface change?
>
> Thanks for your help,
> Michael :-)
>

From: Gustaf Neumann <neumann_at_wu-wien.ac.at>
Date: Mon, 5 Apr 2004 21:03:29 +0200

On Friday 02 April 2004 09:54, Alexandre Dehne wrote:
> Hi,
>
> First, thank you all for answering me !
>
> I first try to install the rpm xotcl-1.2.0-0.i386.rpm but fedora return
> that this was not an available rpm package...? The rpm
> xotcl-1.1.0-0.i386.rpm is recognized as an available rpm package but was
> not accepted by fedora.

 hmm, just being under FC 1.0 (Yarrow)

   rpm -qpl xotcl-1.2.0-0.i386.rpm

 returns the content of the rpm-archive. Can it be that your download of the rpm binary
 was incomplete?

>md5sum xotcl-1.2.0-0.i386.rpm
  00a8c360a8b02f0e4fb44a0d6f47cbaf xotcl-1.2.0-0.i386.rpm

  ls -l xotcl-1.2.0-0.i386.rpm
  -rw-r--r-- 1 neumann neumann 1764951 Feb 21 16:47 xotcl-1.2.0-0.i386.rpm

> So, I copy tclInt.h and tclIntDecls.h files from the correponding
> sources of my distribution to the /usr/include directory and next
> configure and compile XOTcl without any problem.

 as others pointed out, when you want to compile the src rpm file of xotcl,
 you should install the appropriate tcl src rpm file on your machine,
 then it should work. This is at least the way, i built the xotcl binary
 on our system.

 best regards
-gustaf neumann

-- 
Univ.Prof. Dr.Gustaf Neumann
Abteilung für Wirtschaftsinformatik
WU-Wien, Augasse 2-6, 1090 Wien

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

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

> did you try this example out of curiosity or do you have an
> interesting example?

Mostly out of curiosity. I was also wondering if you could do a
prototype object system in XOTcl (where one can inherit from any
object) so then I started to wonder if it would possible in XOTcl to
promote any object to a class.

> -gustaf
> PS: i did not know that you are using a Mac...

Yup. Got myself a Powerbook a couple of months ago and am very pleased
with it (after the problems with a Linux laptop it has been very
refreshing). Great AquaTclTk package for it too which includes XOTcl.

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