Importing Builtin Repository Channels

Introduction

This page describes the process for importing channel(s) from our built in repositories for Iguana 6.0. We have included a short version of the procedure and a longer version with screenshots.

Note: The process for importing channels is the same for any connected repo (builtin or otherwise).

Tip: If you have not upgraded to Iguana 6, we highly recommend that you do so before starting any new projects.  Iguana 6.0 gives you easy access to all these built in repositories and all its other advantages.  It’s a free upgrade for any customer who has valid maintenance and support.

Import Procedure summary [top]

  1. Commit any code changes that you want to keep before importing.
  2. Go to the Iguana Dashboard, and click Add Channel.
  3. Click Import a channel.
    Note: If an imported channel already exists it will be updated unless you choose to import it as a new channel.
  4. Choose the desired Builtin Repository from the Showing Channels On listbox.
  5. Check Import for each channel to be imported, and click the Import Selected Channels button.
  6. Enter a meaningful Commit Message for the import.
  7. If you are updating existing channels you will get the “Channel Collision” dialog.
  8. Choose your import options:
    Note: Generally you should choose “Full Update” (or “Update Translators Only” to preserve local channel settings)
  9. Check Replace with import for any updated shared modules (or other files).
  10. Click Continue to complete the import.

Import Procedure with screenshots [top]

  1. Commit any code changes that you want to keep before importing.
  2. Go to the Iguana Dashboard, and click Add Channel:
  3. Click Import a channel:
    Note: If an imported channel already exists it will be updated unless you choose to import it as a new channel.
  4. Choose the desired Builtin Repository from the Showing Channels On listbox:
  5. Check Import for each channel to be imported, and click the Import Selected Channels button:
  6. Enter a meaningful Commit Message for the import:
  7. If you are updating existing channels you will get the “Channel Collision” dialog:
  8. Choose your import options:
    Note: Generally you should choose “2. Full Update” (or “3. Update Translators Only” to preserve local channel settings)

    • No Action: Do not import the channel
    • Full Update: Import the channel, including the channel settings
    • Update Translators Only: Import the channel, excluding the channel settings
    • Import As New Channel: Import a copy of the channel using a different name
    • Make your import choices:
  9. Check Replace with import for any updated shared modules (or other files):

    Warning: If you do not check Replace with import your code may not work correctly if it depends on shared module changes (that are not imported).

    But don’t worry! If you import and overwrite changes you can always restore the previous commit. Or if you choose not to import and the code fails, you can re-import the changes later.

    Tip: You can click the See what will change link to view the differences between the import and your current code.

  10. Click Continue to complete the import.

Troubleshooting [top]

  1. Problem: Your imported channel is not working correctly:
    • Cause: You did not import an updated file dependency, like a module, VMD, or other file.
    • Solution: Re-import the channel and be sure to check Replace with import for any updated shared modules (or other files) in step 9.
    • If the code is still not working as you desire it may that there is a problem with the update, or it simply does not match your requirements, please contact us at support@interfaceware.com for more information.
  2. Problem: You lost updates you made to a shared module (or other file):
    • Cause: The import overwrote your changes.
    • Solutions:
      • View differences in the commit history and integrate your changes manually.
      • Revert to your previous commit, and use view differences to integrate imported changes manually.

Leave a Reply