Xotcl May 2010

xotcl@alice.wu.ac.at

3 participants
4 discussions

XOTcl 1.6.6 available
by Gustaf Neumann 03 Nov '11

03 Nov '11

Announcing XOTcl 1.6.6 ************************* Dear XOTcl Community, We are pleased to announce the availability of XOTcl 1.6.6 Major changes relative to 1.6.5 are: * improved 64-bit compatibility (expat) * fixed minor memory leaks (info methods, forward error case) * fixed potential cyclic dependencies via namespace imports during cleanup * fixed potential crash with var-traces being fired twice * compatibility with Tcl 8.6b1 * fix for debian packaging For more details about the changes, please consult the ChangeLog and documentation. The planned next release will be 2.0.0 MORE INFORMATION General and more detailed information about XOTcl and its components can be found at http://www.xotcl.org best regards -gustaf neumann

1 1

Announcing: Spindle v0.1 — An MVC web framework for Tcl/XOTcl
by Kristoffer Lawson 22 May '10

22 May '10

I've grown to hate all the web frameworks I've used (non-Tcl), and OpenACS was always impenetrable for me, so I decided to create one that reflects how I think a framework should operate. It's very early development stuff, but it works and has some hopefully intriguing ideas. And yes, it's all XOTcl. Check it out: http://github.com/Setok/Spindle -- Kristoffer Lawson, Co-Founder, Scred // http://www.scred.com/

2 4

Announcing Storm v0.1 — A transparent queryable object storage for Tcl/XOTcl
by Kristoffer Lawson 17 May '10

17 May '10

Continuing on where Spindle leaves off, I created a system which again reflects how I believe storage should work. After endless problems with RDBMS and the object-relational mismatch, I decided to hell with that, and built a transparent persistence layer which can use a file or Sqlite backend (no reason why others could not be used too). The idea is that any class created from the basic PersistenceClass metaclass can be attached to storage. Changes are automatically written out. Even more interestingly objects which are referred to, but which do not exist in memory, are automatically loaded as well. You can even destroy them at will and, when required, they'll happily be loaded back in. There is also a simple query language for getting objects from their class. It's not perfect, and a lot could be done with it still, but I like the idea. For many things full blown direct RDBMS access is just not necessary, and can cause major headaches. I also think that a lot could be done to optimise the Storm system so that performance differences wouldn't be huge, for many cases. Spindle (the web framework) does not require Storm in any way, and you can use any storage backend you want with it. I did, however, create them simultaneously so perhaps they subconsciously share some fabric. http://github.com/Setok/Storm -- Kristoffer Lawson, Co-Founder, Scred // http://www.scred.com/

1 0

Bug in XOTcl documentation
by Kristoffer Lawson 17 May '10

17 May '10

For the [ob info class] it specifies: objName info class: Returns the name of the class of the current object. Undoubtedly that should say "Return the name of the class of the object". Ie. no "current". It is returning the class for objName, after all. -- Kristoffer Lawson, Co-Founder, Scred // http://www.scred.com/

1 0

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 May 2010