> I have to admit that, when I first played with vtcl, my main criticism
was:
> "Why isn't there a manual.". Now (a few months later), I realise that I
didn't
> need a manual for vtcl, it actually was a Tcl/Tk tutorial, (and even
better: a
> Tcl/Tk book (I use the Brent Welch, and the Oosterhout book, and the man
> pages via Tkman)). Also the "Frequently made mistakes" is very usefull in
my
> case (I seem to be able to make them all...)
> So maybe the idea of just increasing the "Tips of the day" is a good one
(they
> were usefull to me), and the first tip to appear (in a hughe font) would
have
> to be: "please read this or that tutorial/book on Tcl/Tk first".
> A few more elaborate examples (as the help is now) can be usefull, but it
> won't be easy to write such examples without having to explain a lot about
> Tcl/Tk... I do agree that such examples might win more people to start
> experimenting with vtcl. But after a (short) while, they'll learn that
they
> have to read something about Tcl/Tk though...
>
> Just my 0.02,
>
> Stef.
I have read a few of the tutorials and references on the web and while some
of them have been useful (TclTutor in particular was pretty helpful), most
of them leave me wondering how to implement this or that in VTcl. I think
most of the confusion stems from the fact that there are certain things that
seem to be able to be done both by scripting with Tcl and by using commands
associated with the various widgets. I cited the example of opening and
saving files in my last message. While both ways apparently work I'd like to
know which is more standard when creating Tcl/Tk applications, or is it a
case of whichever you prefer? I also don't fully understand what VTcl does
for me. I presume its just the layout stuff thats done for me, but I really
don't know at the moment.
I'll keep playing with it, but the ability to look at someone elses code
would be helpful. If anybody's written an app with VTcl could they please
let me have a look at it so I can try to decipher for myself what is going
on?
Different people learn things different ways. I like to learn by taking
things apart to see how they work. Its just my way.
_______________________________________________
vtcl-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/vtcl-user
