public inbox for
 help / color / mirror / Atom feed
From: "Left Spin" <>
Subject: Re: Sorry, but... this project is still alive?
Date: Fri, 12 Apr 2002 07:19:00 -0000	[thread overview]
Message-ID: <> (raw)

I think the number one barrier to entry for working on this project is the 
lack of a good debug environment. Issuing messages to the log file is too 
slow and cumbersome. When I mentioned the TclPro debugger, which has a great 
interface, I got no response. When I'm able to, I'll work on building TclPro 
v1.5 for Windows so I can work on SN. I had previously used a trial period 
version of the Aspen release, and I was begining to figure out the SN code 
base. My trial period has expired, but I am convinced using log file 
deugging techniques will be too slow to work on SN with. Please keep in mind 
that people new to working on this product will have to learn tcl/tk, 
itcl/itk, the SN code base, and probably other packages I'm not even aware 
of yet. It's a very large task. A good debugging package is essential to 
getting more people to work on SN.


>From: "Emilio Riva" <>
>Subject: Re: Sorry, but... this project is still alive?
>Date: Fri, 12 Apr 2002 09:02:26 +0200
>I don't know if I'll be able to do something useful... sooner or later I'd
>like to join to an Open Source project: how do you organize your work? via
>Web CVS?
> > Hi,
> >
> > would you be interested in contributing any of
> > the features that you talked about in your email?
> >
> > Ian.

Chat with friends online, try MSN Messenger:

             reply	other threads:[~2002-04-12 14:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-12  7:19 Left Spin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-12  0:16 Emilio Riva
2002-04-12  0:03 Emilio Riva
     [not found] < m>
2002-04-11  8:29 ` Randall R Schulz
2002-04-11  2:45 Emilio Riva
2002-04-11  8:49 ` irox
2002-04-11  9:25 ` Bill Brune
2002-04-11 13:53 ` Khamis Abuelkomboz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).