Jump to content

PaulG.

Members
  • Posts

    822
  • Joined

  • Last visited

  • Days Won

    22

Posts posted by PaulG.

  1. Although it may take decades I see graphical programming as the future of virtually all programming. It is simply much easier, more powerful and more intuitive to present information and direct information and data visually. If that were not the case we would all still be typing print:doc

    As far as teaching graphical programming to children goes: the younger the better. Bring on the future. cool.gif

  2. I have never thought of the save often thing as being bad. I developed that habit back in DOS 3.1 and it has saved me a lot of potential lost work. Power ouatages are just an excuse to take a break.

    Quiet envirnment:

    Protective ear-mufs (like those worn wire shooting) combined with ear plugs give me a 6 db reduction in noise. Add an industrial PC chassis fan running and there is no sound distrations. My boss bought a bumper sticker that now hangs in my cube that reads;

    "You do not want me to take of these headphones." (AnEnginneringMind.com)

    Visitors have learned to approach gradually to avoid me jumping out of my seat (when you are in the zone, you are in the zone).

    Ben

    That would certainly have been a less expensive approach to what I did. One place I worked was so noisy that out of necessity I felt the need/excuse to buy noise cancelling headphones. Good and expensive ones. Music sounded incredible but they didn't work well enough in that environment if I wanted silence.

  3. I don't think it matters much if Wikileaks broke the law. The ones that clearly broke the law are the ones that provided classified information to them. There's not much question on this point. If one agrees to protect the information as a condition of having access, I don't think that an individual can then just decide not to abide by the law/his contract/etc. If there's a real specific instance of wrongdoing, the I might see releasing that information to an attorney in confidence who could then build a case. Just anonymously dumping massive amounts of classified and sensitive data to Wikileaks is the action of a disgruntled coward.

    I'm putting on my flame suit now.....

    Mark

    I can honestly say I'm on both sides of the fence on this issue. What Wilileaks has been doing, to their credit, is doing the job the media is supposed to be doing but refuses to do. Our Founding Fathers here in the US explicitly gave us freedom of speach for the specific job of keeping an eye on things and putting the word out when they thought something wasn't right. On the other hand, I can see where the individual who discloses classified information is a disgruntled coward. But I don't see where this is the fault of Wikileaks.

    • Like 1
  4. With that recursive irony in mind, an article that I actually dogfooded was Graham's artice on removing distractions, particularly cutting your dev machine off from the internet: http://www.paulgraha...istraction.html

    Remove distractions. All of them. I simply cannot "get into a zone" very easily in a cube farm or with a radio on or phones ringing in the din and giggles of a typical office. Music is hit or miss. Sometimes some jazz or something Jeff Beck-ish helps me concentrate. White noise (where I work now - total bliss) or total silence works best for me. As far as cutting off the internet goes, I simply cannot do that. I need THIS place too often. :worshippy:

  5. Hi all,

    does anybody know where I can find documentation about DSC? Somethig which explains deelpy concepts like items, channels, I/O points, BVE refnum (what is a BVE???!!!)... and stuff like that!

    Thanks.

    sassos

    Good luck with that. DSC is not well documented. The best you can do is read whatever you kind find searching "DSC" at NI. There are a few tutorials available as well but no in-depth info you might be looking for.

  6. My own approach for larger projects is documented here on the dark side.

    A very diffrent design pattern class, which is pretty useful on larger app's is dynamical calls via VI server. Currently I'm using (studying) this for recursion, but more commonly you'd see this implemented as 'plugins' and for 'lazy loading'. Going OOP, that'd be the factory design pattern.

    Felix

    My current app is looking a lot like this. I like the enum state machines as well. I only use the text-based state machine if I need something simple, fast and dirty.

  7. alright maybe I'll try and ask for a new trend in this thread..who has worked on the coolest project which they can disclose and what was it?

    -side question: Is it accurate to say that the majority of LabVIEW developers are freelancers/consultants rather than on salary in a permanent position?

    and congrats crelf; sorry I don't know who you are yet (or what you do with your mad LV skills) but you're reputation defnitely precedes you!

    I once worked for a company that built a device that collected very large volumes of air samples and concentrated the particulate matter of those air samples into a fluid. It had to work in a wide range of temperatures and humidities and the sample size had to be consistent. The hotter and drier the ambient air the more fluid had to be dumped into the device to get the correct sample size and vice-versa and every combination in-between. To determine the correct flow rate for each combination of temperature and humidity manually would have taken months. So I had LabVIEW, an environmental test chamber, the "blower" that collected the air sample, the "collector" (kind of looked like a small stainless steel horn with tubes running in and out of it), syringe pumps, feet and feet of teflon tubing wrapped in brass wire transferring fluids all over the place, lab stands and jacks holding everything together, a balance, a pump that emptied the sample cup sitting on the balance, etc. etc. My LabVIEW code ran it all unattended for days at a time. It looked like a prop from a science fiction B movie. She was a real beaut. I had a blast putting that thing together and even more fun just watching it run.

  8. My main application controls various tests in 18 different test cells. From my "Main" vi I call up a test cell, test type, parameters, etc. The test grabs a template vi, loads the parameters and this template copy becomes the display and control of that particular test. To reduce screen clutter users can close the running test front panel but can re-open it if they want to check the status of the test later.

    Problem: a couple of the managers want to monitor these tests from their desks. That does not sound like much of a problem except I want the managers to see the status only and not have any of the functionality of the test interface.

    What I want: I thought you could call a vi by it's reference and look at it's front panel remotely. No functioning, just display the front panel. But I can't seem to find exactly how to do this without getting into remote front panels which seem like overkill for what I am trying to do.

    Suggestions?

  9. I'm not motivated enough to carefully read whole the discussion, so maybe it was put already.

    What I like the most in LVOOP is custom colors for wires. The effect is worth the effort for implementing all these access methods...

    If you're being serious this is funny. Paragraphs of LVOOP dialog and all you have to say is: "I like the pretty colors". :lol:

    And if you're being funny, well, this is funny. :lol:

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.