33 replies to this topic

[jgcode]

Hi

This is a thread posted on behalf of Fab to see who in the LAVA community is going to the 2012 CLA Summit and are interested in OpenG?

If you are going please post including whether:

• You do or don't use OpenG
  
• You have an interest in OpenG (whatever that interest may be)

Thanks guys - it will help with planning!

Cheers
-Jon

[crossrulz]

I'm assuming I'm supposed to reply here. I currently have permission to go and I just went ahead and registered. We'll see if I will really get to go. As far as OpenG, I currently am not using it for projects due to company rules about open source and third party code. I still find it to be a great resource though. I do have an interest in OpenG, whether using it or helping with development.

[Fab]

Crossrulz,

Thanks for taking the time to reply.
This year we are trying something new at the US CLA Summit. There is a third day devoted for us to have work sessions. For the most part the topics of the work sessions will be determined based on what we learn on the first two days. However, I would like for there to have some options before the CLA Summit, so people are encouraged to stay for that third day.

One idea I had was to have one of that work session be about OpenG. Crossrulz, would you be interested in such a session?

I hope you do get to go, it is a great time for us LabVIEW fans

Fab

[crossrulz]

I would definitely be interested. I'm mostly interested in how people get away with using OpenG in their projects since I'm planning on taking up that fight in the next year or so. Anything more would be bonus to me.

[John Lokanis]

I will be there! And I use OpenG in almost all of my projects. Have been using it for many years. I would like to learn more about the process of turning some of my reuse code into OpenG packages.

[neil]

I am in, however I am going to the Europe one.

I use OpenG in pretty much all my projects.

[Fab]

I will be at both CLA Summits.
However the work sessions will only take place at the US CLA Summit.
Neil, I can let you know what we discussed at the US Summit when we meet at the UK one

John and Crossrulz,
Thanks, I will keep you posted of what we would do on the third day for OpenG.

Thanks,
Fab

[jgcode]

Both? Sheesh!

[neil]

I will be at both CLA Summits.
However the work sessions will only take place at the US CLA Summit.
Neil, I can let you know what we discussed at the US Summit when we meet at the UK one

John and Crossrulz,
Thanks, I will keep you posted of what we would do on the third day for OpenG.

Thanks,
Fab

Thanks Fab, that would be nice.

[Fab]

Both? Sheesh!

Jealous? Maybe next year you can join us for both and for NI Week

[jgcode]

Jealous?

Definitely

Maybe next year you can join us for both and for NI Week

Hmm 2013. The '13' doesn't sit well with me. If they name it 2012b I am in!

[Jeffrey Habets]

I've booked flight and hotel two weeks ago, so I will be there in Austin!

I've been using OpenG for a long time and will keep on doing so. It is standard in our pallets! If I need to work on a customer's system without it, first thing I do is install VIPM & OpenG.

[Yair]

If they name it 2012b I am in!

Surely* if it's a beta it should be called 2014b.

Incidentally, here's a picture of an elevator control panel from China:




Can you spot the problem?




* crelf, don't even think about it.

[Aristos Queue]

I will be at both summits. I am interested in OpenG.

[Darren]

I will be at the Austin summit. I do not currently use OpenG.

[Fab]

I will be at both summits. I am interested in OpenG.

Great! What is your interest in OpenG? What type of discussion would you like to have?

I will be at the Austin summit. I do not currently use OpenG.

Do you want to use it? Would NI let you use it?

[jgcode]

Would NI let you use it?

With respect to the Community (I can't see it being used anywhere else) I have seen EK use it in an example with LVOOP design patterns - that was a first as far as I know.

[Darren]

Do you want to use it? Would NI let you use it?

Most VIs I write ship as the source code of NI product features. It's my understanding that including open-source VIs in those features would not be allowed.

[Aristos Queue]

My interest in OpenG is mostly as a "what is LV missing" point of view. For example, I have long coveted the OpenG array palette, wished that LV had those functions in vi.lib directly. Most of the OpenG palettes are better as add-on libraries, IMHO, but that one feels like core functionality, and I've certainly cobbled my own version of several of those functions. Some of the other OpenG tools/palettes I've seen over the years have highlighted places where you guys could have done an even better job if we had tweaked things a bit inside LV. If nothing else, they highlight the parts of LV that you guys are using the most, which are the areas we should probably be focusing on.

In the future, I may be more interested in OpenG as a user of the tools... I'm doing more G programming these days, and even a little bit on the side that isn't for NI projects. Just a smidge, but it's more than has been over the last decade.

Most VIs I write ship as the source code of NI product features. It's my understanding that including open-source VIs in those features would not be allowed.

Ah, that rules out the OpenG palettes, Darren, but not the OpenG tools, like some of their scripting accelerators.

Edited by Aristos Queue, 03 February 2012 - 05:11 AM.

[Antoine Châlons]

Surely* if it's a beta it should be called 2014b.

Incidentally, here's a picture of an elevator control panel from China:




Can you spot the problem?

Chinese people are apparently very superstitious and the sound "4" (pronounced in Chinese of course) is close to the sound for death (or dead) so you won't find many fours in China.
One funny extent of that is that non-Chinese people leaving in China have cell phone numbers full of 4, because Chinese people refuse to have a number containing a 4.
I also heard that on her fourth pregnancy a Chinese woman would automatically have twins, but I'm not too sure about that one...