I've created an account on Google Code where those interested parties can collaborate on code discussed in the Code Repository In-Development Forum.

The lavacr project is here.

The LAVACR SVN can be used by any LAVA member. If you need an account to add or edit code in SVN, please send a personal message to me on the LAVA Forums and I will add your name. You also need to have a Google account and an associated linked email address (not necessarily Gmail).

You don't have to use the LAVACR SVN to submit code to the Code Repository on LAVA. The LAVACR SVN is provided as a service and a convenient place for collaboration. Also having code in LAVACR SVN does not guarantee that it will be accepted in the LAVA Code Repository.

Organizing Code
The code directory has been split up into several LabVIEW versions. This helps segregate development into the different LabVIEW versions and helps prevent accidental up-compiles of the code base. From the root SVN folder you will see LabVIEW version sub folders (8.2.x, 8.5.x, etc.). Please place your code into the appropriate LabVIEW version sub folder.

Code Discussions
It is recommended to discuss code issues on the LAVA Forums. This way we can bring the wider community into the discussions. Please post issues in the Code Repository In-Development Forum. Also, fell free to use the Issues system built into the Google Code tools.

Note, when requesting access via PM, please tell me your email address you are using with your Google account. This is all I really need to add you. You don't need a gmail address just a google account with any email address associated with it.

Ok, I've stuck in my Rusty Nails stuff - VI Scripting Tools and some XNodes, including my XNode for determing how a sub-vi is wired at runtime. In the process I've arbitarily established a directory structure that mimics the CR structure. It occurs to me that we might want to do something to indicate which LabVIEW version files are in... my stuff is all in 8.5.1 which I've switched to for primary development of new code.

Share and Enjoy™

Perhaps we should create folders at a higher level that break down the code based on LabVIEW version. I was thinking of doing this for the LAVA CR downloads but it is less important than during code development, since the LabVIEW version is indicated on the download page.

Would seem sensible to me. Do we create separate directories for every minor bug0fix version - how big is the binary difference between an 8.5 and 8.5.1 vi ? Is it worth it stop the reporistory filling up with trivial recompile differences ?

I don't think LabVIEW bugfix releases should be included. Mainly because bugfixes are supported by the major.minor released run-time engine. The revisions should be in the form: 7.0.x, 7.1.x, 8.0.x, 8.2.x, 8.5.x.
BTW Gavin, it's great to see your initiative in this!

Gavin, I've moved your code into the 8.5.x folder and created additional folders for the other LabVIEW versions.

Michael,

I am looking around in Google Code and I have yet to come up with a search, or find any pick, tab, link, or any intsructions on where any lavacr code is. I gather that Gavin put some things in that like "rusty nails" or v 8.5.1. I haven't happened upon the right lucky charm to bring that up. I must not have the referents to work this out easily. Hints?

Mike

If you go to the setting page, and select 'Source Code browsing', 'Directory tree'.

And than go to the source tab, you can easily browse the current data in the repository:


Good luck,

Ton

Thanks!

I guess the intention is NOT to use the WIKI function at gcode lavacr and to use instead the LAVA cr forum instead for discussing?

The gcode accounts will funcition as a storage and librarian utilities for works in progress and not much more?

Mike

This is evolving. Not sure about the final form. The lavacr project on Google code is there to provide source code control. This is the same as sourceforge, but LAVA likes Google code better. Are you familiar with SVN? SVN is a source code control backend. In order to edit and put code into SVN, you need a client. On the Windows platform, the best one out there is Tortoise SVN. TortoiseSVN needs to know the URL to point to the source folder. This is provided here. Then, once you have your local copy of the code checked out, you can then edit the code and commit back. I can go into more detail if you like but there is an assumption that you are familiar with SVN and using source code repositories. Ask a question and I will try to answer.

Google code provides issue trackers which we can use for specific bugs or feature requests on the code. I think that's fine however discussions on the new features or the code in general should happen on the LAVA forums because there are more eyes over here.


Edit: One addition thing to mention. If you just want to add code. At a minimum, you should tell someone about it. I think starting a thread on the forums with something like: "hey, I just added some 7.1 code under a folder called joe's code" what do y'all think, etc...". Hopefully it will be a little more than that but you get the idea. Otherwise, noone will know it exists.

Thanks. You seem to be guessing very well. I haven't a clue about SVN, so I may indeed be asking for help.

I have always wanted a place to put the tidbits I write to help people (sometimes years later I want them and they are on some old defunct box sent to on the production floor to do Excel duty or in some hard drive now at the bottom of a landfill), and since I am not usually interested in meeting the C-R standards I thought this might be useful. I had the impression from an earlier forum conversations that this might be one of the functions you envisioned for this. Also I am just curious what Google is up to here. I have found uses for a lot of their bits and gadgets.

Finally, I presume there is a long tail for stuff given to Google for safekeeping. Maybe this way I don't have to worry about transferring it from new PC to new PC, backing up, and so on. It is an act of faith, but I am hoping someone who wants to organize all of human knowledge can do the little bit that I want.

Mike