> -----Original Message----- > From: Peter L. Peres [SMTP:plp@ACTCOM.CO.IL] > Sent: Sunday, June 22, 2003 5:59 PM > To: PICLIST@MITVMA.MIT.EDU > Subject: Re: [OT] My version of visual programming > > >> And how does that compare with other rad tools like vc++ vtcl python > >> and more ? > > > Well from what I have seen of VC++ its easier to use in many ways, and I > > dont know about the vtcl python but I had a quick look around on google > > and VB seems to be a much more cohesive tool. > > Ah, cohesive ? What is cohesive ? You mean it has everything packed in it > and you do not need (nor can you) use external resources ? > > Borland C Builder has been around since before M$ had rad tools (I still > have Turbo C 2.0). Its user interface is correspondingly smooth. I am not > bashing VB but apart from a 'good' name aquired by volume and advertising, > what advantages does it have ? > How about considerably better debugging capabilities? Due to it's interpreted nature ( at least when running through the IDE), you can set the program pointer to an arbitrary location within a function, so you can make a change to a line of code and simply drag the execution pointer up to execute that line again, no re-compiling etc. There are some limitations to what you can change on the fly (constant variables and select case statement values primarily) but it really speeds up debugging over the typical C IDE. You can also execute lines of code in the immediate window at any time. For me, the fantastic debugging more than makes up for many of the other problems with VB. > It is well known that you can write > spaghetti code in any language, it need not be Basic. Nor is structured > Basic, like VB, very hard to maintain or use as a language. > > The problem I see (as an occasional compiled VB application user) is > libraries (VBRUNxxx.DLL). Somehow I never have the right version installed > and if you have several they tend to knock each other out (new library > overwrites old during install). I do not know the details but this > happened twice so far (while using maybe 4 applications that require > VBRUN.xxx). > I have never, ever seen this problem with the run time libraries. Each version of VB needs the relevant version of the run time but that's pretty much it. What is a huge PITA is the numerous versions of common OCX's around that can cause no end of headaches. Stuff like the common dialog control, or windows common controls etc. arte the worst offenders. Personaly I try very hard not to use OCX's unless really necessary. > As to others, esp. tcl, here is a pair of buttons in tcl/tk, done without > a gui (vtcl is a gui for making tcl apps, spectcl more so - also produces > java code): > > -- snip -- > ## simple tcl application (two buttons for the price of one) > # colors > set bg1 #FFD0B0 > set bg2 #D0FFD0 > # buttons > button .b1 -text "Push me!" -background $bg1 -command { puts "Ouch!" } > button .b2 -text "Exit" -background $bg2 -command { exit } > # show the buttons, one on top of the other > pack .b1 .b2 -side top -fill both > ## the end. Really, that's it. Plug: visit http://www.scriptics.com/ > -- snap -- > > How about that for ease of programming ? And it runs on many platforms as > is, including on Windows. Python uses Tcl/tk for graphics (more or less > directly). > Not bad, but I could still have done it more quickly in VB. As fopr being unable to learn other languages, I started with x86 assembly and worked up to C before using VB. I use C everyday for writing PIC code, and occaisionaly for writing windows stuff, but if I need to knock up a quick utility or need a nice GUI for something I'll reach for VB everytime. Mike ======================================================================= This e-mail is intended for the person it is addressed to only. The information contained in it may be confidential and/or protected by law. If you are not the intended recipient of this message, you must not make any use of this information, or copy or show it to any person. Please contact us immediately to tell us that you have received this e-mail, and return the original to us. Any use, forwarding, printing or copying of this message is strictly prohibited. No part of this message can be considered a request for goods or services. ======================================================================= Any questions about Bookham's E-Mail service should be directed to postmaster@bookham.com. -- http://www.piclist.com hint: The PICList is archived three different ways. See http://www.piclist.com/#archives for details.