I can understand your point about not being informed that this was
being done. I have gone to several NI seminars, and they talked about
Bridgeview being integrated as an add-on toolkit for LabVIEW. What is
LabVIEW anyway--it is a subset of BridgeVIEW.
They actually anticipated some confusion among users of BridgeVIEW when
this change was made. However, much more people have used and seen
LabVIEW, so they figured that it would be better to market BridgeVIEW
as LabVIEW with more options. I myself figured they would have done a
better job of explaining this integration in the catalog.
Mark
In article ,
Andrew Johnson wrote:
> john_jarvis@usinternet.com wrote:
>
> > Hi all -
> >
> > I was looking to recommend some software for an upcoming process
> > automation project. I figured Bridgeview might be a good place to
> > start.
> >
> > I looked in my new 2001 NI catalog and couldn't find it any longer.
> > Looks to be a few more process automation modules for Labview since
the
> > last time I looked. Did the functionality of Bridgeview get rolled
> > into Labview?
>
> Yes, as an add-on toolkit, but you would never know this from reading
> NI's 2001 catalogue. For some reason known only to the Marketing
> department in Austin, the only mention of BridgeView in the new cat.
is
> in the Index, where it says "See LabView".
>
> It is frustrating talking with clients about BV when we turn aroud
and
> discover the product has "disappeared" without an explanation.
>
> - andrew johnson
> - Wireworks West
> - Berkekey CA US
>
Sent via Deja.com http://www.deja.com/
Before you buy.