Weblog Page

From: Gustaf Neumann <neumann_at_wu-wien.ac.at>
Date: Mon, 04 Apr 2005 14:25:30 +0200

Ben,

i have not done anything with safe interps until now. But try the following:
Add these lines to the end of xotcl*/generic/xotcl.c and recompile:
============================================
extern int
Xotcl_SafeInit(Tcl_Interp *interp) {
  /*** dummy for now **/
  return Xotcl_Init(interp);
}
============================================

then you should be able to do the following:

============================================
~rlwrap /usr/bin/tclsh
% package req XOTcl
1.3.7
% interp create -safe slave
slave
% load "" xotcl slave
% slave eval ::xotcl::Object o1
::o1
============================================

Since xotcl uses ordinary tcl interps, i would assume, it
inherits the safetiness of save tcl interps. Since xotcl does
not do any socket handling, file-i/o, exec's, etc., i would think,
this is a good start. If you see commands that we should deactivate
in safe interps, please let me know.

If nobody objects, i will add these lines to 1.3.7....

best regards
-gustaf neumann


Ben Thomasson schrieb:

>Hi Gustaf,
>
>Is there a safe interp for xotcl, or does xotcl work with the safe
>interp in Tcl?
>
>Thanks,
>
>Ben
>
>

From: Uwe Zdun <uwe.zdun_at_wu-wien.ac.at>
Date: Fri, 16 May 2003 11:02:08 +0200

The SOAP integration on my homepage is a simple example how to
integrate TclSOAP (with tclhttpd ... it should be no problem to
use another web server) and XOTcl. This is not intended as production
code ... I prepared it for a student project. It worked for the
students (they have done a web calendar with it). Yet, it can only handle
generic invocations and more work would to be done to provide a more
complete integration. The disadvantage of this solution is that TclSOAP
is not the fastest variant ... I don't know in how far that matters
compared to other web service solutions, web services are slow anyway.

two other solutions are possible, writing a new SOAP implementation (as
Gustaf suggested e.g. with tdom) ... that's a lot of work ... the word
"simple" in SOAP should not be taken literaly.

or you integrate an existing solution in another language in Tcl or Tcl in it
respectively.

--uwe



On Thursday 15 May 2003 11:17, Nicolas Boretos wrote:
> Hello again,
>
> We are at the onset of a Web based project to be built on, at least the
> current thinking is,
> on XML/SOAP. Basically, a Web browser interface calling SOAP methods on
> a SOAP server.
> Initial trials using tcl soap along with the the package's SOAP::domain
> stuff under tclhttpd seem
> promising, if possibly a bit cludgey and slow...We also work with
> Aolserver, but have not looked at ns_soap..
>
> Most of the application are requests for Eurosta data (living in a
> postgres db), calculations, and
> generating charts, pies, graphs, XML reports etc.
>
> I was wondering as to what efforts, if any are being done along these
> lines. I found some tclhttpd/soap etc wrappings
> on Mr. Zdun's site, but could not really get these to work (cleanly, at
> least). I also found the link below but have not
>
> http://nm.wu-wien.ac.at/Lehre/oo2/04-39.html
>
> had a chance to look at it.
>
> Is there anything newer/other along these lines available? Most of our
> thinking is to eventually move towards your
> ActiWeb/Active Web Objects, but we are still in the exploration phase.
> I also have a gut feeling that tis project will grow/change as time
> goes, which infers maintainability issues, which is
> why we are shying away from our intial tcl/tclsoap approach and more
> towards XOTcl/objects....
>
> regards,
>
> nicolas boretos
>
>
>
> _______________________________________________
> Xotcl mailing list - Xotcl_at_alice.wu-wien.ac.at
> http://alice.wu-wien.ac.at/mailman/listinfo/xotcl

-- 
Uwe Zdun
Department of Information Systems, Vienna University of Economics
Phone: +43 1 313 36 4796, Fax: +43 1 313 36 746
zdun_at_{xotcl,computer,acm}.org, uwe.zdun_at_wu-wien.ac.at

From: Kurt Stoll <kstoll_at_echelon.com>
Date: Wed, 1 Mar 2006 22:28:24 -0000

 

I suppose this is a trivial question, but I find this annoying.

 

Is there an easy was of passing a switch non-positional argument to another
procedure based upon the value provided to the calling procedure? For
example, if both p1 and p2 take a switch non-positional argument -sw, and p2
calls p1, but wants to forward along the state of the -sw parameter, how is
that best expressed. The straightforward approach - testing the value of
-sw and then using the correct invocation - is ugly, and subject to
combinatorial explosion. To avoid the combinatorial problems, and make it a
little cleaner, I can collect the options in a list and then make the call
(using an eval). This works, and is certainly cleaner, but it still seams
that there should be an easier way to pass the value along; passing other
options along is simply a matter of calling the option and providing the
current value. The example below shows these options:

 

Object obj

 

obj proc p1 {{-sw:switch 0} {-opt 1}} {

    puts "sw: $sw"

    puts "opt: $opt"

}

 

obj proc p2 {{-sw:switch 0} {-opt 1}} {

    if { $sw } {

        my p1 -sw -opt $opt

    } else {

        my p1 -opt $opt

    }

}

 

obj proc p3 {{-sw:switch 0} {-opt 1}} {

    set options [list -opt $opt]

    if { $sw } { lappend options -sw }

    eval my p1 $options

}

 

Is there a better way to do this?

 

Thanks,

Kurt

 

From: Ben Thomasson <ben.thomasson_at_gmail.com>
Date: Fri, 21 Jul 2006 13:35:17 -0400

Thanks! I'll test it other browsers next time. So
http://xotclllib.sourceforge.net should work in IE and Firefox now.

If you are using linux or unix you can use the installer provided for quick
cvs checkout:


   1. wget http://xotcllib.sourceforge.net/install-xotcllib-anonymous.tcl
   2. chmod +x
   http://xotcllib.sourceforge.net/install-xotcllib-anonymous.tcl
   3. ./install-xotcllib-anonymous.tcl -bin bin -lib lib/tcl

If you are using Eclipse or another IDE on windows you can check-out the
code from the CVS:

http://sourceforge.net/cvs/?group_id=124495

Currently this project is linux/unix centric as I live in a linux/bsd
world. However the scripts could
be converted to run in windows with a few changes to the header or just run
through a tclsh.

Ben

On 21/07/06, Vinod Kurup <vinod_at_kurup.com> wrote:
>
>
>
> On 7/21/06, Kristoffer Lawson <setok_at_fishpool.com> wrote:
> >
> >
> > On 20 Jul 2006, at 23:58, Ben Thomasson wrote:
> >
> > > Hello all,
> > >
> > > Please that a look at http://xotcllib.sourceforge.net and reply
> > > with comments or critiques. XOTclLib is a library of debugging,
> > > logging, profiling, documentation, tracing, serialization, and unit-
> > > testing utilities.
> > > The documentation for the project is still in progress and will
> > > improve over time.
> >
> > I tried to access this URL but it didn't seem to work. I just got an
> > empty page.
>
>
> Yes, it works in Firefox, but not in IE.
>
> You have closed your <title> tag with </head>. Change it to </title> and
> you'll be back in business :)
>
> Vinod
>
> --
> Vinod Kurup, MD
> vinod_at_kurup.com
> http://kurup.org
>
> _______________________________________________
> Xotcl mailing list
> Xotcl_at_alice.wu-wien.ac.at
> http://alice.wu-wien.ac.at/mailman/listinfo/xotcl
>
>
>

From: Neil Madden <nem_at_cs.nott.ac.uk>
Date: Wed, 19 May 2004 17:12:10 +0100

On 19 May 2004, at 17:07, Michael Schlenker wrote:

> Kristoffer Lawson wrote:
>
>> On Wed, 19 May 2004, Michael Schlenker wrote:
>>
>>
>>> Its similar in tcl, where you have [info commands] and not a magic
>>> $commands variable as you might have in other languages.
>>>
>>> Using traces it should be possible to provide such an interface if
>>> anyone really wants it.
>>>
>>
>> So what is so problematic about just getting a list, manipulating it
>> and
>> then setting it back? Seems like a lot of copied effort for what is
>> basically just list manipulation.
>>
> Yep. I refer to Adam and Neil who both wanted to have mutable objects
> instead of accessor functions.
> Its the usual problem with mutable list objects and the tradional
> value based list operations in Tcl.

Woah there! I said nothing about mutable objects/values. Mutable
variables are all that is needed, and they exist already (in fact, you
have to go an extra step to get immutable variables). The idea is to
reuse things like [lappend], [linsert], [lreplace] etc, without
creating lots of [mixin_append], [mixin_replace] etc etc. That's the
duplication of effort.


Neil.

From: Jeff Hobbs <jeffh_at_activestate.com>
Date: Tue, 02 Dec 2003 08:04:53 -0800

Uwe Zdun wrote:
> Having everything in xotcl1.1/* (also the libs) is no problem ... its
> just removing a ".." from the generated pkgIndex.tcl file. It this an
> issue?

That's not really an issue. It's a little cleaner in that all
the library components are in one directory. That has become
the new TEA standard for compiled extensions. Either way the
cleaner build will make it easier to add into ActiveTcl.

-- 
     Jeff Hobbs, The Tcl Guy
     http://www.ActiveState.com/, a division of Sophos

From: Laurent Duperval <laurent.duperval_at_netergynet.com>
Date: Wed, 13 Dec 2000 09:14:21 -0500 (EST)

Hi,

When do you use instproc vs. proc? I'm looking at the code I've written so
far, and it's all instproc, I make no use of proc at all. So I'm wondering
if it's because proc isn't used often or because I'm missing out on
something really cool.

L

-- 
MY EMAIL ADDRESS HAS CHANGED --> UPDATE YOUR ADDRESSBOOK
Laurent Duperval                   "Montreal winters are an intelligence test,
Netergy Networks - Java Center            and we who are here have failed it."
Phone: (514) 282-8484 ext. 228                                   -Doug Camilli
mailto:laurent.duperval_at_netergynet.com           Penguin Power!

From: Gustaf Neumann <neumann_at_wu-wien.ac.at>
Date: Sun, 23 Oct 2005 12:53:15 +0200

Kristoffer Lawson schrieb:

> Well, the subject says it all. That Tcl option seems to be missing
> from the XOTcl equivalent.

hmm, somehow we missed the introduction of this flag to tcl's unset.

Fortunately, this is quite simple to get this working in current xotcl.
Add the following line
to your script, and you are set.

    ::xotcl::Object instforward unset -objscope

Performancewise, this seems fine as well. Unless i have done something
stupid in my timings, it looks to me that we can drop our c-implementation
of unset.

check the following code:

   ::xotcl::Object sample
   set cmd {time {time {sample set xxx 1; sample unset xxx} 100000} }

    puts "orig set+unset [eval $cmd]"

  ::xotcl::Object instforward unset -objscope

   puts "new set+unset [eval $cmd]"


on my mac os x notebook, the version based on instforward is constantly
slightly faster than the original c-implemented version, where i don't see
at the first sight the performance eater (using the nested
time to get more precise timings).

If noone complains and this version survives our testing, I'll drop the
c-code and add this version for the next release.

all the best
-gustaf

PS: for now, you can add the instforward line to predefined.xotcl.

From: Gustaf Neumann <neumann_at_wu.ac.at>
Date: Thu, 27 Oct 2011 21:29:39 +0200

Dear XOTcl community,

today, we presented the Next Scripting Framework (NSF) at the 8th Annual
Tcl/Tk Conference at Manassas, Virginia. We are proud to announce also
here the availability of nsf 2.0b2, available from the web-site below,
that went as well public today. The release plan is to gather in the
first round feedback from the inner community and to polish the website
and documentation in the meantime. The full public release will come out
without the beta-state and will be annouced to the wider public.

The distribution of the next scripting framework contains essentially
  - NSF, the low-level framework
  - XOTcl 2.0
  - NX (descendant of XOTcl)

While XOTcl 2.0 is primarily highly compatible with XOTcl 1.6, NX
provides more support for programming the larger, such as stronger
encapsulation, method protection, modular feature composition, etc. For
more details, consult the slides referenced below. The website contains
a more detailed NX migration guide comparing XOTcl idioms with NX
idoms, or an NX tutorial.

The Next Scripting Framework requires Tcl 8.5 or newer and is released
under an MIT license. For users bound for the time being to Tcl 8.4 we
will continue to release bug fixes for the XOTcl 1.6 series.

web-site: http://next-scripting.org/
slides: http://nm.wu-wien.ac.at/research/publications/b885.pdf

Gustaf Neumann
Stefan Sobernig

-- 
Univ.Prof. Dr. Gustaf Neumann
Institute of Information Systems and New Media
WU Vienna
Augasse 2-6, A-1090 Vienna, AUSTRIA

From: <MichaelL_at_frogware.com>
Date: Tue, 27 Apr 2004 17:47:00 -0400

I wasn't sure if you guys were still monitoring the thread.

----- Forwarded by Michael Lenaghan/frogware inc. on 04/27/2004 05:46 PM
-----

starkit-bounces_at_equi4.com wrote on 04/27/2004 02:40:21 PM:

> On Tuesday, April 27, 2004, at 11:29 AM, Tom Krehbiel wrote:
> >
> > My vision for the future is this:
> >
> > * The TCT invite both Uwe Zdun and Will Duquette to become members of
> > the TCT and give them the responsibility of adding an OO system to the

> > core.
> >
> > * A Tcl/Tk version number is established as the point of insertion for

> > the new OO capability.
> >
> > * XOtcl is selected as the base OO system and is added to core Tcl.
> >
> > * Will works with Uwe and developments an OO mega widget system for Tk

> > and it is added to core Tk.
>
> (stepping out of the shadows for a moment...)
>
> I think this is an awesome list of suggestions. OO-in-Tcl has been
> talked about seemingly forever. For a while it looked like ITcl would
> be the implementation that ended the debate, but it's obvious there is
> no longer a champion (with spare time, anyway) to make it happen.
>
> This situation reminds me of my Red Cross first aid training of many
> moons ago. The instructor taught that if you're surrounded by onlookers
> and need help, don't say "Hey, somebody call an ambulance" because
> everyone is hoping or expecting someone else will do it. Instead, point
> a finger directly at someone, look them in the eye and say "You! You
> call an ambulance!".
>
> I think we've been crying "Somebody call an ambulance" for quite some
> time now. If Will and Uwe are up to the task, I think they should be
> given the power to make it happen for 8.5. I'll even toss my hat into
> the ring. I don't have the time to dig into the XOTcl or SNIT internals
> to make it happen, but if XOTcl and SNIT or a SNIT successor made it
> into the core I'd find time to write a full blown, real world
> megawidget example using them and have it ready to ship at the same
> time.
>
> --
> Bryan Oakley
> bryan at bitmover dot com
>
> _____________________________________________
> Starkit mailing list - Starkit_at_equi4.com
> http://www.equi4.com/mailman/listinfo/starkit