writing plugs in VB....

kamikaze2112 · 9th March 2002, 02:21

Hi there

I'd like to learn how to write plugins in Visual Basic, and was wondering how to get started.

I know this is an extremely vague request, but i would really like to learn the basics of writing plugins, and was wondering as to the location of any docs that could help. i tried the docs offered on the NSDN page but can't seem to open them due to a lack of file extentions.

please feel free to catch me on MSN (kamikaze2112@hotmail.com), or on ICQ (98411969).

any insight is greatly appreciated.

kämïkäzë

BDA7DD · 12th March 2002, 07:19

Quote:

Originally posted by Sawg
VB is to slow and not good for I/O/DSP/Vis plug-ins.

Correction: VB isn't good for ANYTHING... unless you're a retarded scriptkiddie and aren't mentally capable of learning a better program to write your viruses in. Learn something that's actually USEFUL like C++, it's not as difficult as most people claim it is. I can guarantee that you'll never go back to VB once you know C++.

Ximo · 29th March 2002, 12:41

Quote:

VB isn't good for ANYTHING...

True, but..
Correction: VB sucks compared to C++ or Delphi, but if it's the only language you know and you simply don't have the time to learn C++, at least it's something

If Ximo.HaveTime = True Then
    Ximo.LearnLanguage(CGI)
Else
    Ximo.Language = VB
End If

simple as that

.. i always thought c++ was for programming gurus, but i guess it is possible to learn it if you go for it..

Gourou · 29th March 2002, 16:36

No offense, but I could write a plugin in VB. It's not as useless as ppl think, they just dont want to take the time to build the Methods and such to do it. They assume that it has no functionality outside of what is shown in the book Learn VB in a weekend. I have a reference book that is 1190 pages thick of nothing but calls and methods I can create, with nothing more than a sentence explaining each one. VB is NOT decrepit or useless, it's underestimated. You CAN very well write a I-O / DSP / VIS plugin if you want, it just takes some time to figure out how to write a dll that wont get compiled as ActiveX, it has been done, I've seen it, so dont say you cant. And C++ is only faster on functions when compared to VB's *INTERNAL* functions, doing the API calls required for a VIS plugin would be just as fast, and the math is comparable, meaning.. 10,000,000 operations of addition in c++ takes a given time, in the same time vb could do 9,500,000 of the same, so dont give me the B.S. that it's that much faster, it's crap, I've timed it myself. and compiling for small code versus fast code, and removing all the optimizations , show that you have to skew the results to achieve a noticeable gain of c++ over VB. A c++ compiler does the optimizations for you, every knows that, remove those and you'll get the same drop.

Gourou · 29th March 2002, 16:45

P.S. I could do that test, because I know them BOTH! and I still prefer VB over c++, I also know perl, php, html, and java script, but nothing is simpler to do some things in than VB. Why go to all the extra work of a c++ program when VB can do 9999/10000 of everything I want to do? there is only *1* thing I dont know how to do, and it has never stopped me before, so dont even say you'll never go back, it's not true.

9th March 2002, 02:21	#1
kamikaze2112 Junior Member Join Date: Mar 2002 Posts: 6	writing plugs in VB.... Hi there I'd like to learn how to write plugins in Visual Basic, and was wondering how to get started. I know this is an extremely vague request, but i would really like to learn the basics of writing plugins, and was wondering as to the location of any docs that could help. i tried the docs offered on the NSDN page but can't seem to open them due to a lack of file extentions. please feel free to catch me on MSN (kamikaze2112@hotmail.com), or on ICQ (98411969). any insight is greatly appreciated. kämïkäzë

29th March 2002, 16:36	#4
Gourou Senior Member Join Date: Feb 2002 Location: The backside of the universe on the trailing edge of eternity Posts: 238	No offense, but I could write a plugin in VB. It's not as useless as ppl think, they just dont want to take the time to build the Methods and such to do it. They assume that it has no functionality outside of what is shown in the book Learn VB in a weekend. I have a reference book that is 1190 pages thick of nothing but calls and methods I can create, with nothing more than a sentence explaining each one. VB is NOT decrepit or useless, it's underestimated. You CAN very well write a I-O / DSP / VIS plugin if you want, it just takes some time to figure out how to write a dll that wont get compiled as ActiveX, it has been done, I've seen it, so dont say you cant. And C++ is only faster on functions when compared to VB's INTERNAL functions, doing the API calls required for a VIS plugin would be just as fast, and the math is comparable, meaning.. 10,000,000 operations of addition in c++ takes a given time, in the same time vb could do 9,500,000 of the same, so dont give me the B.S. that it's that much faster, it's crap, I've timed it myself. and compiling for small code versus fast code, and removing all the optimizations , show that you have to skew the results to achieve a noticeable gain of c++ over VB. A c++ compiler does the optimizations for you, every knows that, remove those and you'll get the same drop. Last edited by Gourou; 29th March 2002 at 19:23.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

29th March 2002, 16:45	#5
Gourou Senior Member Join Date: Feb 2002 Location: The backside of the universe on the trailing edge of eternity Posts: 238	P.S. I could do that test, because I know them BOTH! and I still prefer VB over c++, I also know perl, php, html, and java script, but nothing is simpler to do some things in than VB. Why go to all the extra work of a c++ program when VB can do 9999/10000 of everything I want to do? there is only 1 thing I dont know how to do, and it has never stopped me before, so dont even say you'll never go back, it's not true.