Michael Aivaliotis

Note: Detailed submission procedure can be found here. LAVA Certified All LAVAcr content is LAVA Certified - a certification that insists on appropriate quality, support and usefulness. Members cannot simply upload any type of code to the LAVAcr - it must adhere to specific standards and rules before it is considered for inclusion. All code submitted is moderated by a group of well-respected LabVIEW professionals, all of whom are also respected premium members of LAVA. What is LAVA Certified? All LAVAcr submissions are assessed based on LAVA Certified criteria, including appropriateness for the LAVAcr environment. Although this may sound daunting, making sure your submissions are LAVA Certified is really just a matter of common sense and the standard practices we have all come to expect from competent LabVIEW developers. For code to become LAVA Certified, it must adhere to the following requirements: All custom VIs must include an appropriate level of documentation: including the use of the VI Documentation, free text on the Front Panel and/or Block Diagram. You don't need to include a novel, but please consider the average level of knowledge of a LabVIEW programmer that has never seen your code before. A verbose description is expected on the submission web page: this will form part of the page where your code will reside. Error handling must be appropriate: If your code has an error in cluster, then chain errors through your code to an error out cluster. If you're providing code that may be used as a subVI, then enclose all of your code in an error case structure. Your style does not need to be perfect: but consider those who will be trying to understand and perhaps modify your code. Keep crazy wiring to a minimum, try to line subVIs up, give VIs meaningful icons, use the 4-2-2-4 connector layout when you can, etc. All submissions must be versioned. Incomplete or secure code will not be accepted: including code with locked diagrams, missing diagrams or password protection. You must take reasonable steps to confirm that your code conforms to the functionality you submit it under. You are the primary support vehicle for your submitted code: and you must stand behind it. If another LAVA member has questions and/or comments, you must make yourself available within a reasonable amount of time to help out. Each portion of code will have a dedicated support thread, and other LAVA members may try to assist too, but you own the code, so it's your responsibility. LAVA Certified assessors will not alter your code to make it meet the requirements: If a submission does not meet the requirements when it is assessed, it will be returned to the member with a short description on the requirements it failed to address. Submissions must state the LabVIEW version it was created with: If you would like your code to be listed under more than one version of LabVIEW, then you must provide an extra copy in the appropriate version. You must confirm that your code works appropriately under each version of LabVIEW that you submit it for. LAVA Certified code hosted in the LAVAcr must be bound by a software license of your choosing. A description of the license used must be included in the readme file of the submission. You must also include your contact and ownership information. Currently, we only accept code licensed under an Open Source License. The submissions form currently supports the following licenses which you can chose from: BSD GNU Public Lesser GNU Public Creative Commons Attribution 3.0 Creative Commons Attribution-Share Alike 3.0 Creative Commons Attribution-No Derivative Works 3.0 Creative Commons Attribution-Noncommercial 3.0 Creative Commons Attribution-Noncommercial-Share Alike 3.0 Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 MIT Other (included with download) What is the Process for Submitting my Code? Code is submitted by filling out a dedicated web form here. This form requires some information from you (including a functionality description, image, desired distribution license), as well as a place to upload you code. More information about the submission procedure with a video can be found here. Once you have submitted the code, it will automatically get placed in the uncertified category and is immeadiatly available for download on LAVA. Once the review process is complete, you will receive notification whether you submission has been accepted and included in the certified LAVAcr categories, or if it has been denied based on the LAVA Certified requirements. How long does it take for my submitted code to be considered "certified"? That's an easy one: it depends The LAVA Certified assessment team are donating their time to this cause, so it may take a while (we aim to average next-business day). Try to find comfort in that good things come to those who wait. What Happens if my Code is Denied? We here at LAVA are people, just like you, and we don't want to exclude anyone, but making the LAVA Code Repository a free-for-all defeats the purpose of having a premium resource where other users can be confident that the contents are of a high quality. If one of the LAVAcr assessors deems that your submission doesn't meet all of the LAVA Certified requirements, then you will be emailed with a list of items that are considered erroneous. You are more than welcome to address the issues and resubmit the code. If you believe that your code is compliant with the LAVA Certified requirements and it is still rejected, please contact the assessor directly with your concerns.

That's very insightful.

As mentioned in this topic. LAVA has a new feature that can be used to embed media into forum posts. We can add more media types but are not sure what you all need. Also, we would like you to help us formulate the replacement script for these new media types. Media Replacement Match: You can use {1}, {2}, etc as a variable replacements or any regex statement: Ex: http://www.test.com/23423/Match: http://www.test.com/{1}/ For YouTube: http://(|www.)youtube.com/watch?v={2} Media Replacement HTML You can use $1, $2, etc as a variable replacements or any regex statement. Ex: <a href="http://www.testm.com/$1/">$1</a>Result: <a href="http://www.testm.com/23423/">23423</a> For YouTube: <object type="application/x-shockwave-flash" height="355" width="425" data="http://www.youtube.com/v/$2"><param name="movie" value="http://www.youtube.com/v/$2"><param name="allowScriptAcess" value="sameDomain"><param name="quality" value="best"><param name="bgcolor" value="#FFFFFF"><param name="scale" value="noScale"><param name="salign" value="TL"><param name="FlashVars" value="playerMode=embedded" /><param name="wmode" value="transparent"/></object> Let us know what media embed you want and what the replacement match and replacement HTML should be.

You have the ability to embed media onto any page on LAVA. Watch the video to see how. <object width="724" height="612"> <param name="movie" value="http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/1a04afba-8c8d-4023-af12-01f83891d135/jingswfplayer.swf"></param>'>http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/1a04afba-8c8d-4023-af12-01f83891d135/jingswfplayer.swf"></param> <param name="quality" value="high"></param> <param name="bgcolor" value="#FFFFFF"></param> <param name="flashVars" value="thumb=http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/1a04afba-8c8d-4023-af12-01f83891d135/FirstFrame.jpg&containerwidth=724&containerheight=612&loaderstyle=jing&content=http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/1a04afba-8c8d-4023-af12-01f83891d135/2009-07-05_1609.swf"></param> <param name="allowFullScreen" value="true"></param> <param name="scale" value="showall"></param> <param name="allowScriptAccess" value="always"></param> <param name="base" value="http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/1a04afba-8c8d-4023-af12-01f83891d135/"></param>'>http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/1a04afba-8c8d-4023-af12-01f83891d135/"></param> <embed src="http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/1a04afba-8c8d-4023-af12-01f83891d135/jingswfplayer.swf" quality="high" bgcolor="#FFFFFF" width="724" height="612" type="application/x-shockwave-flash" allowScriptAccess="always" flashVars="thumb=http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/1a04afba-8c8d-4023-af12-01f83891d135/FirstFrame.jpg&containerwidth=724&containerheight=612&loaderstyle=jing&content=http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/1a04afba-8c8d-4023-af12-01f83891d135/2009-07-05_1609.swf" allowFullScreen="true" base="http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/1a04afba-8c8d-4023-af12-01f83891d135/" scale="showall"></embed> </object> The following media types are currently supported: Flickr Image Set (http://www.flickr.com) GameTrailers (http://www.gametrailers.com) Google Video (http://video.google.com) MySpace Video (http://vids.myspace.com) YouTube (http://youtube.com) Do you know of any other videos or media types LAVA should support with this feature? Let us know here.

I've filed a support ticket with IPS on this. It appears to be a bug in the forums. Will let you know when it's resolved.

I fixed the link, click on it again.

Do you see an edit button on your submission page? I think there should be some file editing buttons on your settings panel but I think they're missing because of a bug. I've reported this to IPS to see if it can be fixed. Edit: I just saw Mark posted on the Admin forum that he's confirmed that there is no editing even on the submission page. We'll look into it some more and possibly file a bug report with IPS.

Omar, that was awesome. "watching the ads is almost like paying"

Sorry, no.

Why would you ever want to log out of LAVA? I realize it's different, and I appreaciate your feedback. We're not in a position to go editing the forum skin anytime soon. When and if we do, we'll collate all feedback over the next few months and then make decisions based on the information at hand. The important thing is now you know where everything is so you should be good to go. Keep sending us feedback!

You might want to leave this as it stands for those that only have LV 8.2. Renaming it to [LV8.2]Array Function XNodes. Then create a new submission with the 8.6 version.

Your explanation makes no sense to me. I'm not following. If you've already read/skimmed it then it won't be in the New Content list. New content, means stuff you haven't read yet.

Yair, this functionality is still there, see image:

Yes, please re-upload your avatar and personal photo. Also fill in any other optional info you desire.

All the Code Repository files should now be restored.

I've reported this bug to IPS.

hey Ton, I can't reproduce this (I have IE8 and Vista) but I have a workaround which works. You can send a PM from your messanger instead: Or you can jump to your messenger by clicking from a users popup. See video: <object width="608" height="372"> <param name="movie" value="http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/fb9d9a22-a8d6-4a48-aa49-0441ba5acc3c/jingswfplayer.swf"></param>'>http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/fb9d9a22-a8d6-4a48-aa49-0441ba5acc3c/jingswfplayer.swf"></param> <param name="quality" value="high"></param> <param name="bgcolor" value="#FFFFFF"></param> <param name="flashVars" value="thumb=http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/fb9d9a22-a8d6-4a48-aa49-0441ba5acc3c/FirstFrame.jpg&containerwidth=608&containerheight=372&loaderstyle=jing&content=http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/fb9d9a22-a8d6-4a48-aa49-0441ba5acc3c/2009-07-04_0033.swf"></param> <param name="allowFullScreen" value="true"></param> <param name="scale" value="showall"></param> <param name="allowScriptAccess" value="always"></param> <param name="base" value="http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/fb9d9a22-a8d6-4a48-aa49-0441ba5acc3c/"></param>'>http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/fb9d9a22-a8d6-4a48-aa49-0441ba5acc3c/"></param> <embed src="http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/fb9d9a22-a8d6-4a48-aa49-0441ba5acc3c/jingswfplayer.swf" quality="high" bgcolor="#FFFFFF" width="608" height="372" type="application/x-shockwave-flash" allowScriptAccess="always" flashVars="thumb=http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/fb9d9a22-a8d6-4a48-aa49-0441ba5acc3c/FirstFrame.jpg&containerwidth=608&containerheight=372&loaderstyle=jing&content=http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/fb9d9a22-a8d6-4a48-aa49-0441ba5acc3c/2009-07-04_0033.swf" allowFullScreen="true" base="http://content.screencast.com/users/Michael_Aivaliotis/folders/Jing/media/fb9d9a22-a8d6-4a48-aa49-0441ba5acc3c/" scale="showall"></embed> </object> Ton, one more thing. Do you get the same problem if you click the PM link under the avatar? See image: I've reported this bug to IPS.

Hey Gavin, I transferred ownership to you. You should able to edit and update the submission.

It appears to be an issue only on my computer, very strange. Thanks everyone for your help. This topic is now closed.

I've changed it so it opens a new tab.

It's actually suppose to be a LabVIEW volcano from this shirt here:

It's a bug. Known issue on all browsers, thanks! This has been reported to IPS.

It's been tough going through the last month without our beloved LAVA site, but behold, it's back and better than ever. We're calling this version LAVA 2.0. Welcome back! How did we get to this point? Well, there was a serious crash on the LAVA server database and years worth of data was lost. I didn't have a very good backup and data recovery process in place, which meant I couldn't bring the site up the way it was before. There is good news however... keep reading. Just to step back a little to discuss the history of LAVA. LAVA started back in 2002 as an experiment by myself and mostly to provide a web based platform for LabVIEW discussions that could be on the same level as the then popular Info-LabVIEW mailing list. I wanted to host quality discussions where the tiniest detail and minutia of LabVIEW coding could be discussed at an advanced level using the latest web technology. Well, it was a slow start but after a few years it looked like LAVA was a hit. The member levels grew and along with that, more stress on the server and site. Throughout the life of LAVA I was the sole administrator of the back-end system. I managed my own server and performed custom modifications to the forums application framework. However, this could only be sustained for so long. I have a "real job" of course and spending time on LAVA administration is on an as-needed basis. So, after a few months of neglect and a few careless server maintenance actions on my part, the inevitable happened. Data was lost. I didn't know what to do at that point and decided to tap into a few trusted LAVA members and friends for help. Jim Kring and justin Goeres to name a few. It was decided that a more decentralized management of LAVA was necessary to avoid another catastrophe and allow more people the ability to manage and help with the workload. We also took this opportunity to experiment with a hosted community service called Ning. The Premium members and some key LAVA members were invited to try the site out for a week. That went ok at the start but we found that it lacked the power that LAVA users were acustomed to. We also had an issue with how much control they had of all the site data and with how limiting the system was to modifications. At the end of the day we concluded that it would serve the community better to keep the familiar experience of the original LAVA intact. We scrapped the Ning site and took what we learned to relaunch LAVA. Here's the good news part. It turns out I had an off-site backup of the data from Feb 2007. Also, it just so happened, that avid LAVA reader, Philippe Guerit, was keeping all the RSS feed content on his computer since after Feb 2007. What luck! Buy the man a beer! I've managed, using LabVIEW of all things, to extract the old database data. Jeff Plotzke wrote a program to parse through Philippe's RSS feed file. And together we were able to get all the old content imported (yes, the dreaded Alpha thread too). Chris Relf and Mark Balla have also worked hard to manually import the old CR code into the new site as well. That data had to be manually imported. The bright side of this restructuring is that now I have more people to help out in keeping LAVA alive. We now have 6 administrators instead of just one. We have moved LAVA to a hosted Invision (the company that makes the forum software) server account, making it more reliable with regular backups. I have found a new friend in Jeff, who knows PHP, (why didn't you say so a long time ago?). And I have learned how to ask for help I want to assure you that all of us who have worked on getting the site up and running are passionate about keeping LAVA alive. We hope that you welcome the new LAVA, along with some of the new cool features we've added, back into your daily workflow. I'll be creating a separate topic to describe some of the new features in LAVA 2.0. In the meantime, please post any questions or problems with the site here. Note that the only way to login to your account is using your email address. To get a new password click the forgotten password link and fill-in ONLY your email address. Thanks to Jim, Jeff, Justin, Chris, Mark, Philippe and all the Ning beta testers.

Here's what we've got so far: