TclTalk is completely based on tclkit
(http://www.equi4.com/tclkit.html) and thus gets deployed as a single
writable starkit. All development with TclTalk stays within the file
borders of this starkit, unless you tell otherwise. Invent and test
code with interpretive workspaces, then use the browser to create an
appropriate namespace, create some variables and procedures for that
namespace and write one startup procedure. When you are done, simply
use the "Create turnkey starkit.." menu option, tell it the full name
of your startup procedure and a name for your new starkit. TclTalk will
then create a new starkit in your personal folder, containing your new
program.
TclTalk will stay resident within your new program, so you can use it
to develop it further later on. Just start your new program with the
command line argument "-ide".
Please, have a look at: hhtp://tcltalk.ath.cx !!!
Regards...
Shin The Gin - a.k.a. Thomas Braun
--
.-. .-. .---. .---. .-..-. |Experts in Linux: www.WildOpenSource.com
| |__ / | \| |-< | |-< > / |"Making the bazaar more commonplace"
`----'`-^-'`-'`-'`-'`-' `-' |Check out my new novel: "Cloud Realm":
http://www.smith-house.org:8000|<this+/books/Larry_Smith/CloudRealm.html
> I have been downloading and trying tcltalk with each new announcement,
> but I just cannot get it working. The latest tclkit packages work
> stand-along, but have weird problems with tcltalk, include "cannot
> find setup" and "segmentation violations". This is on linux, using
> the x86 and x86-static versions of tclkit.
> ...
Hi Larry, thank you for your interest. I have tested TclTalk 0.3.2 on
Linux with tclkit v.8.4.13, which I pulled from here
http://www.equi4.com/pub/tk/8.4.13/tclkit-linux-x86.gz and v.8.5a4,
which I pulled from here
http://www.equi4.com/pub/tk/8.5a4/tclkit-linux-x86.gz. Both tests where
successfull on Ubuntu 6.06 and SLAX 5.1.8. I just cannot test on
windows, as I don't use it.
> ...There is obviously some-
> thing not kosher in my environment, so what guesses are there?
>
Did you try any other starkit yet?
Have a look at http://mini.net/sdarchive/ and see if you can start some
of them.
Shin - a.k.a. Thomas Braun
> Hi Larry, thank you for your interest. I have tested TclTalk 0.3.2 on
> Linux with tclkit v.8.4.13, which I pulled from here
> http://www.equi4.com/pub/tk/8.4.13/tclkit-linux-x86.gz and v.8.5a4,
> which I pulled from here
> http://www.equi4.com/pub/tk/8.5a4/tclkit-linux-x86.gz. Both tests where
> successfull on Ubuntu 6.06 and SLAX 5.1.8. I just cannot test on
> windows, as I don't use it.
Using precisely those pointers:
> gunzip tclkit-linux-x86.gz
> chmod +x tclkit-linux-x86
> chmod +x tcltalk.kit
> tcltalk.kit
application-specific initialization failed: couldn't open "setup.tcl":
no such file or directory
can't find package starkit
while executing
"package require starkit"
(file "./tcltalk.kit" line 4)
On Jan 25, 1:39 am, Larry Smith <l...@wildopensource.com> wrote:
> application-specific initialization failed: couldn't open "setup.tcl":
> no such file or directory
> can't find package starkit
> while executing
> "package require starkit"
> (file "./tcltalk.kit" line 4)
>
To me this sounds like tclkit is incompatible with your system
libraries.
Your problem could be reproduced like:
- start tclkit
- Enter "pack req starkit"
Do you get more error information this way?
Shin
Here's what I get:
> tclkit
% package require starkit
1.3.1
> tclkit tcltalk.kit
application-specific initialization failed: couldn't open "setup.tcl":
no such file or directory
can't find package starkit
while executing
"package require starkit"
(file "tcltalk.kit" line 4)
Doing it manually:
> tclkit
% package require starkit
1.3.1
% source tcltalk.kit
XIO: fatal IO error 0 (Success) on X server ":0.0"
after 37 requests (34 known processed) with 1 events remaining.
I may have some sort of library mismatch though. On an unrelated
problem I've had tclkits barf for lack of stdc++ - which IS present.
Just for the records:
it seems like your installation is somewhat hosed...
tcltalk works ok for me under debian(sarge), with a
tclkit-8.5a4
One feature-request: those windows (where you can type code,
select it, and eval it) should have some margin at the
left side, where one could easier select whole lines.
(currently one must target a rather small target - about
half a character cell - to start the drag for selecting
whole lines) I don't know, if the text-widget gives
any help in that direction..., so it might actually be a
feature request (read: TIP) for tk's(& perhaps tile's)
text-widget rather than for tcltalk.
On Jan 25, 9:05 pm, Andreas Leitgeb <a...@gamma.logic.tuwien.ac.at>
wrote:
...
> One feature-request: those windows (where you can type code,
> select it, and eval it) should have some margin at the
> left side, where one could easier select whole lines.
> (currently one must target a rather small target - about
> half a character cell - to start the drag for selecting
> whole lines) I don't know, if the text-widget gives
> any help in that direction..., so it might actually be a
> feature request (read: TIP) for tk's(& perhaps tile's)
> text-widget rather than for tcltalk.
Have you tried a triple-button-1 on a certain line of code?
OTOH:
- Use the browser to navigate to ::tcltalk::ws::create
- Find the line saying: "eval text $path ..." (line 2 or 3)
- Insert " -relief flat -borderwidth 2" right behind $path
- Choose "Accept" from the context menu
This should give you 2 more pixels around the text widget :)
Shin
On Jan 26, 12:06 am, "Shin" <t...@tcltalk.ath.cx> wrote:
> OTOH:
> - Use the browser to navigate to ::tcltalk::ws::create
> - Find the line saying: "eval text $path ..." (line 2 or 3)
DON'T
> - Insert " -relief flat -borderwidth 2" right behind $path
BUT
- Append " -relief flat -borderwidth 2" to that line
> - Choose "Accept" from the context menu
>
Sorry :(
Shn
ok, tripleclicking works, but is almost as clumsy as targetting
that small area between margin and middle of first char.
> OTOH:
> - Insert " -relief flat -borderwidth 2" right behind $path
> This should give you 2 more pixels around the text widget :)
That also works principially, but adds the margin all around,
not just to left side. I'd have fancied a larger margin on left side
than on the other sides.
But your two suggestions are probably already the best that is
possible with current text widget, so the critique is probably
misplaced in this thread. (should rather be in a new TIP for the
text-widget)
You only fell victim for my general rambling about "text" widget,
because I hadn't had a tk-app for some time, where I would select
whole lines as commonly as in TclTalk ;-)
On Jan 26, 9:00 am, Andreas Leitgeb <a...@gamma.logic.tuwien.ac.at>
wrote:
...
> You only fell victim for my general rambling about "text" widget,
> because I hadn't had a tk-app for some time, where I would select
> whole lines as commonly as in TclTalk ;-)
...
Well, the more keyboard oriented programmer doesn't benefit from
TclTalk as much yet. There's a potential for traversing menus and
special keyboard bindings for "Do it", "Print it" and "Report It".
If you like, you can change ::tcltalk::ws::create to add a binding to
$path on <control-return> like:
bind $path <Control-Return> "::tcltalk::ws::execLine $path"
and add a new procedure to ::tclktalk:ws
proc ::tcltalk::ws::execLine {w} {
set cmd [$w get "insert linestart" insert]
$w insert "insert linestart + 1 lines" "\"[eval $cmd]\""
update idletasks
}
The next new workspace would handle <control-return> at the end of a
line to execute that line and print the result behind the insertion
cursor into that workspace.
Regards...
Shin