puffy i wouldn't get hyper excited.
people will be looking for certain things when using different plugins, firstly the ease of use ...
a good example of this is alot of people find TAToads plugins a little awekard to work with, and i've been asked several times now to remake some of thier features for an simpler setup from a few users.
this isn't to take away from Toad and say that my plugins are better because i know they're more unstable than his due to the time and experience i have put into them compared to him - however some people will use them over his simply for thier ease.
another factor is features ... it is nice to do a one upsmanship with someone if you choose to, however my approach to all of this is completely different - rather than trying to take the ideas of someone else and just extend on them, what i'm doing is making a complete system of what i feel the user will want.
it is obvious both of you are making some good plugins with alot of good features, a big difference in what we're all doing though is whilst you guys are adding support for additional systems ... i'm making mine exclusive for just DBP.
reason being is, i don't use any other language so really why should i create a plugin for a language i don't use ... second reason is, i'm creating it exclusively from the WindowsAPi not a third party APi which means it'll have to be used on a WindowsOS.
To prevent alot of bugs creaping in i'm using the Global Structure, this keeps the DLLs feet firmly planted allowing me to develop from that ... there are also alot of other goodies that quite frankly I can only achieve using VisualC++.
personally i'm not looking to make this a competition. I doubt my plugin will be greatly popular throughout the community, most of mine arn't - but for the select few who like how i set them up no doubt it'll be something they look forward to using.
especially now i've got the hang of the WM System
