"Tore Hatlen" wrote in message
news:ae3cc15a.0111131715.7d29f568@posting.google.com...
> We are investigating whether to continue use and development of
> LabView within out system. I've been asked to see if there are other
> products out there that offer the same kind of functionality as
> LabView. Does anyone know of any? I came onto this project part way
> through so I don't know why LabView was chosen to start with. I know
> of Vlab from Mentor but what about others? are they good, better,
> worse or the same?
>
> Thanks
If the functionality you want is to make a program, LabVIEW is just another
programming environment. You might as well use anything from Assembler to
Delphi.
If you what an program that:
is easy to maintain,
can be build in team
effort,
is reasonable fast to develop,
is portable to other OS,
then LabVIEW is pefect. If you are questioning whether to stick with LabVIEW
or not, you must have some problems with LV (if so, please specify; someone
might have a solution).
Ofter this is the result off skipping the engineering phase of software
development.
First an engineer starts building some VI's to get some experience with LV.
Then, an application is build with these experiments by two, four, or any
number of people.
The result, an unfinished program, that cannot be finished because it is not
documented...
Planning is the keyword here! It is needed in LabVIEW programming, just as
it is needed in any other part of engineering.
Ironicaly the reason for why this is often skipped, is because LabVIEW is so
*easy*. Not because it is to difficult!
Anyway, if you're looking for reasons not to use LabVIEW this might not be
the place...
Regards,
Wiebe.