Xotcl

xotcl@alice.wu.ac.at

2 participants
653 discussions

Git repository: Branch "master" was renamed to "main"
by Stefan Sobernig 14 Sep '23

14 Sep '23

Hi everyone! If you happen to maintain a local clone of the NSF/XOTcl repository, please mind the renaming. Rather than re-cloning, run the following: $ git checkout master $ git branch -m master main $ git fetch $ git branch --unset-upstream $ git branch -u origin/main $ git symbolic-ref refs/remotes/origin/HEAD refs/remotes/origin/main Thank you! Stefan

1 0

Re: [Xotcl] object method as (fileevent) callback
by Vladimir 04 Feb '23

04 Feb '23

Sorry for ugly formatting. I do not know what is happened. Source of example in attachment. От: Vladimir Отправлено: 1 февраля 2023 г. в 21:44 Кому: xotcl(a)alice.wu.ac.at Тема: object method as (fileevent) callback Hello, I have a question. It is a simple Server example TclOO implementaiton below. I mark with yellow two lines, where I can use mymethod command to set private methods of class as callbacks. Both of this callbacks execute in class instance context. Is it possible do same thing with nx? I want incapsulate server logic inside nx::Class and set private method as callback to accept connection and reading data. #!/usr/bin/env tclsh package require oo::util ;# for 'mymethod' command package require logger logger::initNamespace proj::Server debug oo::class create proj::mock::Server { constructor { port } { my variable projVersion_ my variable port_ my variable socket_ set projVersion_ "0.1" set port_ $port ::logger::tree::proj::Server::debug "Init mock Server $projVersion_" # it works! set socket_ [socket -server [mymethod Accept_clb] $port] } ;# constructor method Accept_clb { sock addr port } { my variable clients_ ::logger::tree::proj::Server::debug "Accepting connection with $addr $port" set clients_(addr,$sock) [list $addr $port] fconfigure $sock -translation binary -buffering none fileevent $sock readable [mymethod Echo_clb $sock] ;# it works too! ::logger::tree::proj::Server::debug "Setting callback private method" } ;# Accept_clb method Echo_clb { sock } { my variable clients_ ::logger::tree::proj::Server::debug "Readable callback call" if { [eof $sock] } { ::logger::tree::proj::Server::debug "No more data in socket" close $sock unset clients_(addr,$sock) } else { set binary_msg [read $sock 2] binary scan $binary_msg "H*" string_msg ::logger::tree::proj::Server::debug "Readed 2 bytes" if [string length $string_msg] { ::logger::tree::proj::Server::debug "Sending 2 bytes left" puts -nonewline $sock $binary_msg } } } ;# Echo_clb destructor { my variable socket_ close $socket_ ::logger::tree::proj::Server::debug "Destroing Server" } ;# destructor } ;# dms::mock::server set s [proj::mock::Server new 1950] vwait forever

2 1

object method as (fileevent) callback
by Vladimir 01 Feb '23

01 Feb '23

Hello, I have a question. It is a simple Server example TclOO implementaiton below. I mark with yellow two lines, where I can use mymethod command to set private methods of class as callbacks. Both of this callbacks execute in class instance context. Is it possible do same thing with nx? I want incapsulate server logic inside nx::Class and set private method as callback to accept connection and reading data. #!/usr/bin/env tclsh package require oo::util ;# for 'mymethod' command package require logger logger::initNamespace proj::Server debug oo::class create proj::mock::Server { constructor { port } { my variable projVersion_ my variable port_ my variable socket_ set projVersion_ "0.1" set port_ $port ::logger::tree::proj::Server::debug "Init mock Server $projVersion_" # it works! set socket_ [socket -server [mymethod Accept_clb] $port] } ;# constructor method Accept_clb { sock addr port } { my variable clients_ ::logger::tree::proj::Server::debug "Accepting connection with $addr $port" set clients_(addr,$sock) [list $addr $port] fconfigure $sock -translation binary -buffering none fileevent $sock readable [mymethod Echo_clb $sock] ;# it works too! ::logger::tree::proj::Server::debug "Setting callback private method" } ;# Accept_clb method Echo_clb { sock } { my variable clients_ ::logger::tree::proj::Server::debug "Readable callback call" if { [eof $sock] } { ::logger::tree::proj::Server::debug "No more data in socket" close $sock unset clients_(addr,$sock) } else { set binary_msg [read $sock 2] binary scan $binary_msg "H*" string_msg ::logger::tree::proj::Server::debug "Readed 2 bytes" if [string length $string_msg] { ::logger::tree::proj::Server::debug "Sending 2 bytes left" puts -nonewline $sock $binary_msg } } } ;# Echo_clb destructor { my variable socket_ close $socket_ ::logger::tree::proj::Server::debug "Destroing Server" } ;# destructor } ;# dms::mock::server set s [proj::mock::Server new 1950] vwait forever

1 0

Scripted Value Constraints
by Maksym Zinchenko 13 Jan '23

13 Jan '23

Hello, I have a question about Scripted Value Constraints. I want to create new type check for UUID value, like this: ::nx::Slot method name=uuid {name value} { if {[regexp {([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})} $value] != 1} { error "Value '$value' of parameter $name is not UUID" } } So the tutorial states: If the same checks are used in many places in the program, defining names for the value checker will be the better choice since it improves maintainability. This part is kinda blurry for me, what does it means define a name? For example, how can I use for example: nx::Class create myClass -superclass mySupaClass { :property {user:uuid,required} :property {client:object,required} :property {total 0} bla bla bla Thank you

2 1

NX objects and namespaces
by Maksym Zinchenko 29 Dec '22

29 Dec '22

Hello, first of all Happy new year for all! I have a doubt about an object as a parameter and namespaces. For example I have 2 classes: package require nx > > nx::Class create aClass { > : public method print {} { > puts "I'm an a object: [[self] info name] -> [[self] info parent] " > } > } > > nx::Class create bClass { > :property pr:object,required > > :method init {} { > puts "a_obj print result: " > ${:pr} print > } > } > > aClass create a_obj > bClass create b_obj -pr a_obj > It works the way it's supposed to work. Now inside the namespace: namespace eval testNameSpace { > aClass create a_obj1 > a_obj1 print > bClass create b_obj1 -pr a_obj1 > } > This will give me an error, because NX is trying to execute object passed as a parameter in global namespace: I'm an a object: a_obj1 -> ::testNameSpace > a_obj print result: > invalid command name "a_obj1" > My question is, I might be doing something wrong, what is the right way to do it? Or when I pass Object as parameter I need to add namespace manually, why it's not assuming [namespace current]? Thank you

3 2

Instance with Non-breaking space
by Maksym Zinchenko 19 Dec '22

19 Dec '22

Hello, I have an issue, and dont know whats going on, I have a class "ccClass": nx::Class create ccClass -superclass oodz_baseclass { .... }, when i try to use it from proc ccClass create cc1 -name code -db db It gives me an error, like that in the naviserver logs, instead of space UTF-8 chars: "invalid command name "ccClass\xc2\xa0create"" Strange thing I can create objects from nsshell without any issues. May be someone can help me, thank you

2 2

Certificate on web site
by Maksym Zinchenko 29 Aug '22

29 Aug '22

Hello, would be so kind as to renew the certificate on https://next-scripting.org/. I can't access the website, HTTP Strict Transport Securityis enabled. Thank you

2 1

Announcement: Next Scripting Framework 2.4.0 available
by Gustaf Neumann 14 Aug '22

14 Aug '22

Dear Community, We are pleased to announce the availability of the Next Scripting Framework (NSF) 2.4.0, including NX and XOTcl. The changes are mostly perfective improvements in terms of bug fixes, Tcl version compatibility, and API consistency. See below for the details. Diff stats since 2.3.0: 182 files changed, 26862 insertions(+), 20338 deletions(-) Major changes relative to 2.3.0 are: NSF now compiles and runs with Tcl 9 (core.tcl-lang.org/tcl main branch at the time of writing, August 2022). This way, NSF/NX/XOTcl can be used with the Tcl 8.5.* series, Tcl 8.6.*, and Tcl 8.7.* and Tcl 9.* on Linux/Windows/macOS. One can see the results of the compilations and test runs on https://github.com/nm-wu/nsf/actions https://ci.appveyor.com/project/mrcalvin/nsf-2ylk0/history Selected changes worth mentioning: - Maintenance & bug fixes: * Tcl 9: For the first time, NSF now compiles and its test suite completes with Tcl 9. Kudos to Jan Njitmans. * Tcl 8.7: o Support for the Tcl 8.7a5 release (core.tcl-lang.org/tcl branch "core-8-branch"). NSF compiles and its regression tests execute successfully (including TCL_NO_DEPRECATE). o NSF is now TIP-538 ready (Tcl starting relying on libtommath as an extrinsic dependency). * Fixed type name abbreviation bug: Previous versions did not handle cases correctly where an application type name starts with the same character sequence as a built-in type. So it was not possible to define a type "object_id", since a a spec of the form "x:object_id" was interpreted as "x:object" ("object" is a predefined type). Now, such type name abbreviations are not allowed. * Plugged a small memory leak when using mp_int (libtommath) data internally. * Fixed a crash when using volatile combined with method "configure" in XOTcl 2. * Fixed crashes due to internal cache mismanagement of flag names processed by configure/ cget. See https://groups.google.com/g/comp.lang.tcl/c/F9cn_Ah4js4/m/eL22xbQaCgAJ * Fixed exit from non-threaded NSF builds (will not hang anymore). * Added a warning when a slot name hints a typing error. - Build environments, automated builds: * Made "Makefile" more robust in light of file paths containing white-space characters * Due to Travis becoming unavailable, we moved to GitHub Actions for automated builds on Linux and macOS. Windows builds are still served by AppVeyor. - XOTcl: * "dict" is now available as a per-object method, similar to "array". - MongoDB: * Tested the NSF MongoDB binding against latest stable releases of MongoDB (5.0.9) and MongoDB-C driver (1.22.1). * Fixed test case for gridfs and file renaming - Documentation: * Improved wording and corrected spelling in man pages, tutorials, and examples. The detailed changelog is available at https://next-scripting.org/xowiki/download/file/ChangeLog-2.3.0-2.4.0.log The Next Scripting Framework 2.4.0 (containing NX 2.4.0 and XOTcl 2.4.0) can be obtained from https://next-scripting.org/. Please report issues and wishes by opening a ticket at https://sourceforge.net/p/next-scripting/tickets/. Best regards - Gustaf Neumann - Stefan Sobernig -- Univ.Prof. Dr. Gustaf Neumann Head of the Institute of Information Systems and New Media of Vienna University of Economics and Business Program Director of MSc "Information Systems"

1 0

Default-value substitution using substdefault
by Maksym Zinchenko 13 Aug '22

13 Aug '22

Hello, I'm having trouble to define "srv" property in my superclass with default value from Naviserver command, may be Im doing smth wrong, would be so kind to help: nx::Class create dz_superclass { > :property identifier > :property {srv,substdefault=0b111: {[ns_info server]}} > :method init {} { > set :uuid "" > if {[[current object] info vars identifier] eq ""} { > set :identifier "" > } else { > if {[is_uuid ${:identifier}] == 1} { > set :uuid ${:identifier} > } > } > } > } nx::Class create dz_class -superclass dz_superclass { > :method init {} { > if {${:identifier} ne ""} { > set :obj_data [dict getnull [select_all client * > uuid_client=\'${:identifier}\'] 0] > } > } > } > When I create object: > dz_class create o1 -identifier 67720c6d-d00f-479b-85cf-4edaa5a9cb1a > o1 cget -srv > Im getting literal "[ns_info server]" instead of my virtual server name > [ns_info server] > Thank you

2 5

Announcement & Call for Speakers (The SQLite & Tcl Conf 2021)
by conference＠tclcommunityassociation.org 27 Sep '21

27 Sep '21

Hello XOTcl Developers, fyi ... # The SQLite & Tcl Conference __Wednesday, November 17, 2021__ The 2nd annual SQLite & Tcl virtual conference will be held on Wednesday, November 17. The virtual event will feature a combination of curated talks and work in progress talks (WIPs). [Registration is open](https://www.eventbrite.com/e/the-sqlite-tcl-conference-st-2021-regist…! Please visit the [SQLite & TCL conference](https://conf.tcl-lang.org/) home page to stay informed. # Call for Speakers We've made it easier to contribute by asking for shorter, less formal talks rather than requiring formal papers. - Have you done interesting work that you would like to share? - How about a cool idea that's not yet baked or just in the prototype stage but seems like something others would be interested in? We are particularly interested in new ideas, to hear about novel solutions to problems you've faced, or to see your work in progress. ## To submit your talk: Please visit the [call for speakers page](https://conf.tcl-lang.org/callforspeakers/) for instructions. As a token of our appreciation, each speaker will be gifted with a video conferencing light kit to use while presenting. The call for speakers for S&T 2021 ends on __October 4, 2021 at 11:59 PM CT__. __Important dates:__ - October 4 - Call for speakers for S&T 2021 ends at 11:59 PM CT - October 8 - We will start notifying speakers with their status of their submission and scheduled talk. - October 18 - Agenda for S&T 2021 Announced - November 17 - S&T 2021 held digitally online

1 0

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