Meeting 18th May 2015 12:00-14:00

[swatts]

Here's a place to put topic suggestions for the next meeting.

We already have these possibilities

*Distribution

*Error Handling

*Extending the discussion to best practices in testing, and signing off code at the end of a project. What level of documentation should accompany, or be included in, code that's deployed and signed off?

I'm thinking the subjects marked with an asterix could have several short 10 minute presentations (along the lines of Error Handling - This is what we do)

Confirmed Agenda (I'll add as the confirmations come in)

Mr Swinders has volunteered to show us his cDAQ looping application too.

Greg will show us interactive SSH

Peter will refresh us on assertions

Review of CLA Summit(s) <-- if no-one volunteers I'll do this

Framework Discussion <-- CRoebuck Confirmed

James Mac Will be Integrating LabVIEW with the Web

If we have time Quick-fire Talks on Database Connectivity, Distribution, Error Handling, Signing off

Message was edited by: swatts

[James_McN]

In the vein of bringing back CLA summit content, I will be presenting on integrating LabVIEW with the Web which will be something of a case study of a couple of web centric projects I'm working on if people are interested.

[swatts]

Fun fact: our little user group has 6 people presenting in Rome! I'm rather proud of that

[Lucy]

Should we plan a longer meeting, so you can share your holiday snaps?

[swatts]

You need to come too, I won't be happy until it is called the eCSLUG Summit!

[CRoebuck]

If there's time (and interest) I would be happy to demonstrate the forthcoming Delacor Queued Message Handler (DQMH). This framework (yes yes, I used the F-word) allows developers not familiar with LVOOP to create large "Actor oriented" applications.

Maybe you're interested in Actor oriented design or maybe you are interested to see what Team Delacor has been up to the past few months........

[drjdpowell]

I have a similar actor-QMH template stealing borrowing from the JKI design.  We could have a QMH shootout!

[swatts]

oooh interesting concept, I'd like to have a think about this.

So what are the judging criteria...

Ease of use

Speed of development

Chuck a task at it?

[CRoebuck]

Steve,

I think criteria when judging any framework should be;

Ease of use

Supportability (by others AND NI)

Overhead (prgrammatic and from a developer point of view)

Type safety / Dataflow safety

Compatability with other languages and technologies

Cross platform

Chris

[swatts]

Within overhead I think some consideration of system overhead, 5000 VIs to solve a simple problem loses points!

Good points to consider tho', now we need an acronym. ---> COSTEC!