I think this should be true for all plugins. A download manager for syntaxes, plugins and even updates/new versions would be great. Easy access to all the goodies, right in the program they were meant for. We could even make a small HTML interface by using a small mozilla engine. Same content, same websites, different CSS. The only thing we need then is for EE to know that when clicking a link to a plugin or SDD it should install it.
I hadn't originally figured on it being so widespread in its usage, but I think this would be a great feature. Not so sure about the Mozilla engine, though. I was thinking about having a dedicated XML parser (or something) in to interpret the raw output generated from the server, reducing the embedded components in EE.
Sounds like a great tool, not only for code you can't recognize but also for code you don't have the SDD for but don't want to browse for. Send the code, get the SDD automagically. Also, while this would probably take some time it wouldn't be a problem since people would be prepared to wait a short while for it.
Well, it's two tools really (although in a sense one does overlap over the other), but it is something I'd really push to have included, at least in browsable form.
If you're concerned about privacy, why not make it into a plugin instead? The code is analyzed client-side and the only connection made is the one to download the correct syntax. This way, the plugin could also be used to automagically select correct SDD when opening a file.
Well, the thing is, the plugin would be huge, since it would be analysing code against known profiles, and would be updated with new syntaxes every so often, the result is that the server would be able to make a reasonable guess based on all syntaxes available to it, not just the few that people decide to install.
I'm still not sure exactly how it would work, but I can't see any practical way of analysing it on the client side without knowing every syntax EE has available. As this could potentially run into the thousands it would be a massive plugin.
I would suggest some kind of encryption but since the code is open source, whatever we do will be visible and therefore tappable (OpenSSL is, at last count, an optional library for SFTP support purposes, not a required build-in)
Is the server-side file type detection worth considering, though? I think it's a good idea, but I am a bit biased
I can always try rigging up a miniversion and see how well that works out with file type detection.