Jump to content

Michael Aivaliotis

Administrators
  • Posts

    6,196
  • Joined

  • Last visited

  • Days Won

    104

Posts posted by Michael Aivaliotis

  1. QUOTE (mross @ Apr 23 2008, 11:02 AM)

    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.

  2. QUOTE (Gavin Burnell @ Apr 22 2008, 12:05 PM)

    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 LV 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 LV versions.

  3. QUOTE (Gavin Burnell @ Apr 21 2008, 01:53 PM)

    ...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.

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

  4. As an experiment, 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.

    If you give me your Google email address in a PM then I can add you as a project member. Google Code supports SVN. There is currently no source code in there. Feel free to grab any code from LAVA or new code and put it in there. Let's see where this thing goes. I'd like to keep discussions on the code on LAVA.

  5. QUOTE (Yen @ Apr 18 2008, 03:03 AM)

    I also think this is good. We have a program going on with a local school for both NXT and LabVIEW. If we can get the local NI office to help with cRIOs, I assume we can get even more out of it.

    Actually, Israel has a large presence here in the Atlanta finals. I've seen at least 4 teams from there. I suggest you locate the local teams in your area and become a mentor. That's the best start.

  6. QUOTE (tcplomp @ Apr 17 2008, 10:31 PM)

    Michael,

    it would be nice if the logo of LAVA is used in the group description.

    See the Benelux LabVIEW user group in my profile for an example.

    Ton

    Yes, I know. I just have my hands full at the moment. Something to do with robots...

×
×
  • Create New...

Important Information

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