Here is my take on it.
First, it's important to remember that it doesn't make a bit of difference to Rainmeter if you use the Measure=Plugin / Plugin=WebParser or the Measure=WebParser syntax. The result is exactly the same.
We could move the documentation for WebParser from ..Plugins\WebParser to ..Measures\WebParser. Then we can start reminding folks about the change when we help on the forums. Mind you, we have no right to bug people about this as long as our advice conflicts with the documentation.
The upside
1) It would technically be the correct thing to do.
2) It might eliminate some very rare confusion when WebParser doesn't work as expected and the user says "Oh, the .dll is missing from the ..Rainmeter\Plugins folder on my system! How do I get it back?"
The downside
1) There are probably 10,000 links in the forums, hundreds of links internally in the documentation, and an unknown number of links other places that all point to ..Plugins\WebParser. Every one of those will break if we don't do some work to deal with it.
2) When someone is learning Rainmeter, they almost always use existing skins as the starting point. Guess what the syntax is going to be in those?
3) Are we really going to nag every single new user, and virtually every existing user, who writes or changes a skin using WebParser?
4) Since the syntax for every existing skin a user tears apart is going to be ..Plugins\WebParser, where in the docs are they likely to look for it?
My suggestion
We have changed a handful of plugins into measures. There is some benefit internally in Rainmeter, both from an efficiency and code-maintenance standpoint. However, it doesn't matter either way to end-users.
It is our intention that eventually all "built-in" plugins will be changed to measures, and only "3rd-party" plugins will remain plugins. I agree that measures should be under measures and plugins under plugins in the documentation. However, this is an ongoing process. I'd rather do the work required to deal with the boatload of links in the forums, reddit, deviantART and everywhere else one time, not make it a career.
When we are done converting everything, I'd rather do one big push to make it clear that now plugins are ALWAYS about "3rd-party", and that is what the entire plugin idea is about. I'm not in favor of doing this piecemeal, nagging them about WebParser and NowPlaying now, and starting to nag them about the next one we change then. The forums are going to become annoying to the point of hostility.
I'm not even going to say which ones have been converted and which ones haven't, as I'd rather not add more chum to the water...
So I suggest that we ignore this entire issue, until we are ready to make the change, all at once, in a logical way.
It's not up to me, but personally, I still use Measure=Plugin / Plugin=WebParser any time I'm helping on the forums, and in any skins I distribute. It's just not a discussion I want to have every single time I'm helping someone, and I just find it distracting from the real problem I'm trying to help with. That is what I intend to continue doing until we complete the process of changing plugins to measures.
As I said, it's not up to me really, and if the majority want to attack this as the changes are made, changing the documentation, dealing with the links, and addressing this with users as we help them, then so be it. I can see the argument for doing that. I would vote against it myself.
