What architecture and good practice should I use for a massive application.

[cbutcher]

---

@Yamaeda wrote:

---

@VinnyAstro wrote:

---

I've programmed a bit in C++ (and matlab, I'm in the "that's a language too" team 😛 ) so I have some experience in OO already. 

Don't we all know that feeling all too well, telling people that G is a real language. 🙂

/Y

---

But G is a real language 😉

Just kidding, Matlab seems to be ever more serious the last few versions.

Like LabVIEW, it perhaps suffers from the "but it's easier if I do it all here" problem - why bother with functions, right? 

[Mark_Yedinak]

---

@VinnyAstro wrote:

---

@Yamaeda wrote:

---

@VinnyAstro wrote:

---

I've programmed a bit in C++ (and matlab, I'm in the "that's a language too" team 😛 ) so I have some experience in OO already. 

Don't we all know that feeling all too well, telling people that G is a real language. 🙂

/Y

---

Hahaha yes exactly. Software engineers can be very close-minded sometimes ^^

---

Not all SW Engineers. My background is computer science and started my career in SW engineering working on embedded system in C and assembly. Switched to LabVIEW on test automation in the 90s and fell in love with the language. I think universities are doing a disservice to CS majors by avoiding graphical programming and data flow more generally. I also think that the influx of python is hurting since as a language it is very loose and encourages quick and dirty programming rather than good design.

[billko]

I am reminded of this:

[wiebe@CARYA]

[VinnyAstro]

I completely forgot that Labview features a Navigation pane, it's gonna save my life 😄

[crossrulz]

---

@VinnyAstro wrote:

I completely forgot that Labview features a Navigation pane, it's gonna save my life 😄

---

Just let me state that if you find yourself using the Navigation pane, 99% of the time you are doing stuff wrong.  Stuff wrong usually include the architecture (maybe use a State Machine or a Queued Message Handler) and/or not enough modularity (ie subVIs).

[VinnyAstro]

---

@crossrulz wrote:

---

@VinnyAstro wrote:

I completely forgot that Labview features a Navigation pane, it's gonna save my life 😄

---

Just let me state that if you find yourself using the Navigation pane, 99% of the time you are doing stuff wrong.  Stuff wrong usually include the architecture (maybe use a State Machine or a Queued Message Handler) and/or not enough modularity (ie subVIs).

---

That's a nice summary.

Unfortunately I am inheriting someone else's program, so I'll have to deal with it.

[Mark_Yedinak]

---

@VinnyAstro wrote:

---

@crossrulz wrote:

---

@VinnyAstro wrote:

I completely forgot that Labview features a Navigation pane, it's gonna save my life 😄

---

Just let me state that if you find yourself using the Navigation pane, 99% of the time you are doing stuff wrong.  Stuff wrong usually include the architecture (maybe use a State Machine or a Queued Message Handler) and/or not enough modularity (ie subVIs).

---

That's a nice summary.

Unfortunately I am inheriting someone else's program, so I'll have to deal with it.

---

I would have a very hard time keeping that code. I would most likely throw it away and rewrite it. Good luck to you. Sorry you have to deal with that.

[mcduff]

---

@VinnyAstro wrote:

I completely forgot that Labview features a Navigation pane, it's gonna save my life 😄

---

That some oxymoron code you got there. Bad because huge (among other things), Good because it is extremely neat, no crossed wires, etc.

mcduff

[VinnyAstro]

---

@mcduff wrote:

---

@VinnyAstro wrote:

I completely forgot that Labview features a Navigation pane, it's gonna save my life 😄

---

That some oxymoron code you got there. Bad because huge (among other things), Good because it is extremely neat, no crossed wires, etc.

mcduff

---

Ah but the resolution isn't good enough for seeing all the wires 😉 (And I wouldn't have shared the picture if it was, this is not a horror thread. #censored)