On Mon, 8 Dec 1997, Rick Macdonald wrote:

> Larry W. Virden, x2487 wrote:
> > 
> > Rick Macdonald <[EMAIL PROTECTED]> writes:
> > > Michael Rogers wrote:
> > > >
> > > >     I agree.
> > > >
> > > > Mike Rogers
> > > >
> > > > Munther M. Hindi writes:
> > > >  > This is a plea for the addition of some type of multifile/project
> > > >  > management support into vTcl.
> > >
> > > Stewart has said many times that this is an issue the next major release
> > > will address.
> > 
> > Oh Stewart, where aaaarrrreeee you....
> 
> Hopefully he's working on vTcl! That's why I jump in and answer the easy
> questions!  ;-)

 Now I feel really guilty. You've been getting a lot of "busy" signals
 from me recently so I guess it's only fair to let you know why I haven't
 been putting out new releases. Left to the imagination, one may come to
 the conclusion that I had lost interest - this is not the case.

 Starting in February of this year I took a job as VP Engineering for a
 startup software company in Fairfax, VA (www.webmethods.com). I was 
 thinking there might be some evening and weekends free that I could work
 on vtcl, but this has been the rare exception.

 I put out several messages of design goals for the next few releases
 of vtcl. Included in this were project and file management capabilities.
 I want to get away from the monolithic file format and "introspection"
 as a means of configuring widgets. The latter causes some of the problems
 with widget extensions (Tix) and variable evaluation in the properties
 editor. If anyone has used Symantec's Cafe, I think this is a good design
 to work towards.

 I never intended vtcl to be a one-man-show. However, I did want it to
 be as fully functional as possible before it's initial release. This
 signifies my willingness to devote substantial time to it instead of
 trying to get others to flesh out my idea.

 Areas where others could greatly help out are FAQs, tutorials, docs and
 demos. These are all pretty much thankless, but make the effort look much
 more professional and help new users get off the ground more quickly. I
 would also like help on the internals.  This is a much more daunting task
 - made even more so by my spartan commenting techniques in the code :) If
 there are enough takers, I will set up a vtcl-dev mailing list.

 -stewart-

---------------------------------------------------------------------------
To unsubscribe from the Visual Tcl mailing list, please send a message
to [EMAIL PROTECTED] with "unsubscribe vtcl [EMAIL PROTECTED]" in the
message body (where [EMAIL PROTECTED] is your e-mail address).

Reply via email to