Xotcl

xotcl@alice.wu.ac.at

2 participants
653 discussions

ANN Tloona 1.3.0 released
by Eckhard Lehmann 20 Apr '08

20 Apr '08

Version 1.3.0 of Tloona Tcl/Tk IDE is out. Here are the highlights for this release: * various bugfixes * client console is able to read stdin * code browser understands XOTcl meta classes and slots (via the -slot argument) * Added some files for creating Mac OS X bundles (more on this will follow on the blog at tloona.sourceforge.net) * code definitions can be sent to the client console: proc, method (Itcl), instproc, class proc, Class, meta Class (XOTcl) with <Control-Return> The latter makes it a pleasure to test your programs and procedures while you are developing them. Just load the program into the client console, then edit the procedures, classes etc. and repeatedly send them to the console with <Control-Return>. You can immediately try out what you have done... this makes you even more productive! There is a new screenshot, showing how Tloona is running Tclhttpd inside it's client console. Combined with the ability to send code definitions to the console this is a very pleasant way to develop and test web applications rapidly. Here you go: http://tloona.sourceforge.net/ http://sourceforge.net/projects/tloona -- Eckhard

1 0

Re: [Xotcl] Abstract class
by Stefan Sobernig 06 Apr '08

06 Apr '08

Victor, Kristoffer already provided you with a primer ... > I've been looking everywhere and can't find the info. I am wondering why you are looking for that concept in the XOTcl-verse? Out of curiosity? Or, because you assemble your arsenal against your Java, C#, C++ background? There is a prior thread on this issue which provides a pretty precise picture on that matter: http://alice.wu-wien.ac.at/pipermail/xotcl/2000-December/004148.html To sum it up, you won't find a direct equivalent of "abstract class" as you might know it from languages cited above. But the key message of the thread by Uwe Zdun is that you can approximate and, finally, build it on your own ... Abstract class can take the following semantics which are not mutually inclusive (!): ~ A class object that, at least partially, consists of /abstract methods/. Abstract methods do not provide an implementation (method body). ~ A class object that is constraint to participate only in superclass-subclass relationships, i.e. participate only as superclass/subclass in an object system. In other words, a class that can not be instantiated. ~ A class object that requires its subclasses to provide implementations (method bodies) for the set of its abstract methods. Any of the three aspects may be approximated in XOTcl (as shown in the thread), but still, the concept will differ. Many issues blur the picture, for instance, time of enforcement of the abstract class constraints (there is no compile time in XOTcl!). The notion of "abstract class" comes with many connotations, but its purpose has been prominently linked to their use in terms of OO frameworks as promoted by Ralph Johnson & Co. This is inherently linked to the need of /integrating/ a framework into a final application with integration meaning completion. Completion, in turn, realises as refining "abstract classes" into concrete subclasses provided by the framework. Another perspective is considering the need for a /type hierarchy/, on the one, and an /implementation hierarchy/, on the other hand. Note, that type here not necessarily means "behavioural type" in the Liskov sense of the term. Type hierarchies are commonly realised by the well-known "interface" constructs in languages such as Java and C#, and the importance of interface-oriented programming gained some momentum in recent years (while it was the default in years of CLU and Emerald, but anyway). Implementation hierarchies, on the contrary, are commonly realised by class-based inheritance hierarchies. The trade-offs of using inheritance for realising both type and implementation hierarchies is widely discussed in literature. Abstract classes somehow settle in the middle. With abstract classes meaning collections of abstract methods, methods that comes without a method body (=implementation), you can approximate the idea of interfaces (as member of a type hierarchy). Finally, at a higher level, abstract classes may help realise valuable forms of OO design, the most prominent example being the GoF TEMPLATE METHOD pattern. Hope it helps to clarify the picture a bit ... //stefan -- Stefan Sobernig Institute for Information Systems and New Media Vienna University of Economics Augasse 2-6 A - 1090 Vienna `- +43 - 1 - 31336 - 4878 [phone] `- +43 - 1 - 31336 - 746 [fax] `- stefan.sobernig(a)wu-wien.ac.at <mailto:stefan.sobernig@wu-wien.ac.at> `- ss(a)thinkersfoot.net <mailto:ss@thinkersfoot.net>

1 0

Abstract class
by Victor Mayevski 04 Apr '08

04 Apr '08

Can somebody please update the XOTcl tutorial/reference to explain in detail what abstract class is and how to use it (examples of usage)? I've been looking everywhere and can't find the info. Thanks.

2 1

Resurrecting XOTcl for Debian
by Stefan Sobernig 17 Mar '08

17 Mar '08

Dear XOTcl community! XOTcl is now available in the official Debian sid/unstable suite of packages, starting with the most recent release (1.6.0)! We are also confident that XOTcl will, therefore, be featured in upcoming Ubuntu releases (probably in the second half of the year, i.e. the post-8.04 release). You will find the following XOTcl Debian packages: xotcl (core) xotcl-shells (xotclsh, xowish + man pages) xotcl-dev (headers + static libs, i.e. stubs) xotcl-doc (language reference + manual) aolserver4-xotcl (AOLServer 4.0.10/4.5 module) They are about to be spreaded to the Debian mirror network within the next hours. For now, they can be found at: http://ftp.debian.org/debian/pool/main/x/xotcl/ Over the last couple of weeks, we packaged and contributed XOTcl to Debian sid/ unstable under the sponsorship of the Debian Tcl/Tk maintainers. We would like to express our gratitude to the two chief Debian Tcl/Tk maintainers, Sergei Golovan and Francesco Lovergine, who supported and reviewed our packaging efforts. Please, report package-related bugs through the Debian bug tracker system: see http://www.debian.org/Bugs/Reporting General requests should be send to the Debian Tcl/Tk mailing list: see http://lists.alioth.debian.org/mailman/listinfo/pkg-tcltk-devel Enjoy! //stefan -- Stefan Sobernig Institute for Information Systems and New Media Vienna University of Economics Augasse 2-6 A - 1090 Vienna `- +43 - 1 - 31336 - 4878 [phone] `- +43 - 1 - 31336 - 746 [fax] `- stefan.sobernig(a)wu-wien.ac.at <mailto:stefan.sobernig@wu-wien.ac.at> `- ss(a)thinkersfoot.net <mailto:ss@thinkersfoot.net>

5 5

XOTcl 1.6.0 issue with "Object info class"
by Edmond Ho 10 Mar '08

10 Mar '08

Hello all, I downloaded XOTcl 1.6.0 today, and I immediately ran into an issue in some of my existing code. The following example works in XOTcl 1.5.6, but is different in XOTcl 1.6.0 -- as I understand the documentation on the website, there should be no difference between versions. package require XOTcl namespace import ::xotcl::* Class Foo set f [Foo new] $f info Class ;# returns "::Foo", which seems correct $f info Class "Foo" ;# in 1.5.6, returns 1; in 1.6.0, returns an empty string To repeat, the issue is that "Object info class <classname>" returns a boolean value in XOTcl 1.5.6, but returns an empty string in 1.6.0 -- the current documentation on the website suggests that the 1.5.6 behavior is correct. Am I missing something? Should the documentation be changed, or is the behavior in 1.6.0 incorrect? I downloaded the package via ActiveState's teacup service; I'm working on Mac OS X 10.4 Intel. Thanks in advance for any help! Cheers, Edmond

2 2

XOTcl at sourceforge
by Gustaf Neumann 26 Feb '08

26 Feb '08

Hi everybody, XOTcl is now available from sourceforge, in additon to www.xotcl.org: SourceForge project page http://sourceforge.net/projects/xotcl Download link (with mirror and maxmind geo location): http://downloads.sourceforge.net/xotcl/xotcl-1.6.0.tar.gz best regards -gustaf neumann

1 0

XOTcl 1.6.0 for Windows and FreeBSD users
by Martin Matuska 25 Feb '08

25 Feb '08

*XOTcl ver. 1.6.0 is now available for Windows and FreeBSD users* ------------------------------------------------------------------------ For users of Microsoft Windows: WinTclTk distribution for Microsoft Windows, versions 8.5.1 and 8.4.18 URL: http://wintcltk.sourceforge.net Single-file Tkcon executable (no need to install anything, just run & try) based on Tcl/Tk 8.5.1 or 8.4.18 including XOTcl 1.6.0 can be downloaded from: URL: http://wintcltk.sourceforge.net/tkwrap.html ------------------------------------------------------------------------ For users of FreeBSD: FreeBSD ports tree (packages will be built in the next days) URL: http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/xotcl/

2 1

Announcement: XOTcl 1.6.0 available
by Gustaf Neumann 24 Feb '08

24 Feb '08

Dear XOTcl Community, XOTcl 1.6.0 is available. This release provides in short: - orthogonality improvements for introspection, - more introspection methods (one can now e.g. query, into which classes a mixin class is mixed into) and - performance improvements (some methods are significantly faster. e.g. by a factor of 1000 for larger systems). In addition, the XOTcl source code follows now closer the Tcl source code guidelines (e.g. variable naming), a few potential crashes have been fixed. See below for more details. Best regards -gustaf neumann =============================================== Announcing XOTcl 1.6.0 ************************* We are pleased to announce the availability of XOTcl 1.6.0. Major changes relative to 1.5.6 are: * Provide a uniform interface to the following info subcommands <class> info superclass ?-closure? ?pattern? <class> info subclass ?-closure? ?pattern? <class> info instances ?-closure? ?pattern? <class> info instmixin ?-closure? ?pattern? The new option "-closure" returns the transitive set of the relation (e.g. .. info subclass -closure) returns the subclasses and the subclasses of the subclasses. For "info instances -closure" the instances of the subclasses are returned as well. For more details, please see the language reference manual. In cases, where a pattern is specified, and the pattern contains meta-characters, a list of results is returned matching the pattern (like "string match"). When no matching value is found, an empty list is returned. In cases, where a pattern is specified, and the pattern contains no meta-characters, a single value is returned corresponding to the specified value. The pattern is used to lookup an object or class, such it is not necessary to provide fully qualified names). if there is no match, empty is returned. Previously, "info superclass" and "info subclass" returned a boolean value and performed always a transitive search. Returning "" is more consistent and more in line with Tcl. Note that "<class> info superclass -closure" is a replacement for "<class> info heritage", and "<class> info instances -closure" is a replacement for "<class> allinstances". The old commands will be marked as deprecated in the near future. Please note, that the behavior of the match pattern has changed and is therefor not completely compatible with prior versions. * New info subcommands: <class> info instmixinof ?-closure? ?pattern? <class> info mixinof ?pattern? These info subcommands are used to determine, into which classes a mixin class was mixed into. These inverse functions of mixin and instmixin are used as well internally. These functions help to speed certain operations (e.g. superclass, or registering a mixin class) up by a factor of 1000 (!) or more, when a large number of objects exist. This functionality was primarily implemented by Martin Matuska. Many thanks! * Made the behavior "pattern" in the following calls identical concerning wild cards and object lookups <object> mixin delete pattern <class> instmixin delete pattern <class> superclass delete pattern <object> info mixin ?pattern? * Fix to preserve var traces when copying objects (Many thanks to Florian Murr for reporting) * Fix problem in Tcl 8.5.* when setting variables from C (problem with Tcl_ObjSetVar2()?); many thanks to Florian Murr and Neophytos Demetriou for reporting) * Improved documentation * Extended regression tests For more details about the changes, please consult the ChangeLog and documentation. MORE INFO General and more detailed information about XOTcl and its components can be found at http://www.xotcl.org

1 0

Re: [Xotcl] Xotcl Digest, Vol 39, Issue 1
by Jade Rubick 06 Feb '08

06 Feb '08

Kristoffer: Can you post some more information about how the API looks and works? Your blog post doesn't have much information on how it works or looks. Jade Jade Rubick Acting Chief Technology Officer United eWay jade.rubick(a)uwa.unitedway.org w: 503.285.4963 f: 707.671.1333 http://www.UNITEDeWAY.org On Feb 6, 2008, at 3:00 AM, xotcl-request(a)alice.wu-wien.ac.at wrote:

2 1

Pre-release of a new XOTcl-based template system
by Kristoffer Lawson 05 Feb '08

05 Feb '08

Having become somewhat fed up with the Template Toolkit, built on Perl, I decided to create my own HTML/XML template system with the help of XOTcl. It takes a rather different approach to how to create templates, totally separating the actual HTML from the code that defines the contents. It's simple and easy, and there are things missing from it, but the model is something I'm pretty keen to explore further. Not an actual release, but you can fetch it to play around with it. Some more information plus a rant against Template Toolkit (and similar HTML template systems) at: http://blog.fishpool.fi/?p=17 / http://www.scred.com/ / http://www.fishpool.com/~setok/

1 0

← Newer
1
...
18
19
20
21
22
23
24
...
66
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

Xotcl