• Manu <turkeyman gmail.com> Dec 10 2011

Manu <turkeyman gmail.com> writes:

--20cf303b41473703e704b3c6df29
Content-Type: text/plain; charset=UTF-8

Just another thought. Has anyone considered including VisualD in the
windows distribution, and the standard installer?
I think many windows users will want to install it at the same time as the
toolchain, and it could auto-configure the toolchain paths in the plugin
while installing, which would be nice.
I think it'd be a really good move for the windows distribution. Make the
whole experience a lot simpler and painless, the sort of things windows
users expect.

That said, VisualD seems it could do with some extra resources to get some
fundamental features in there. It's working well for what it is, but it's
lacking quite a few fundamental features that will make it a 'proper'
visual studio integration (ie. browse info and related features).

--20cf303b41473703e704b3c6df29
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Just another thought. Has anyone considered including VisualD in the window=
s distribution, and the standard installer?<div>I think many windows users =
will want to install it at the same time as the toolchain, and it could aut=
o-configure the toolchain paths in the plugin while installing, which would=
 be nice.<br>
<div>I think it&#39;d be a really good move for the windows distribution. M=
ake the whole experience a lot simpler and painless, the sort of things win=
dows users expect.</div><div><br></div><div>That said, VisualD seems it cou=
ld do with some extra resources to get some fundamental features in there. =
It&#39;s working well for what it is, but it&#39;s lacking quite a few fund=
amental features that will make it a &#39;proper&#39; visual studio integra=
tion (ie. browse info and related features).</div>
</div>

--20cf303b41473703e704b3c6df29--