#RevCon13 – The OI Console using Git


Revelation Software 2013 Conference LogoNo, we don’t have some idiot out there using the OpenInsight Console, only well informed, intelligent and upstanding people – I digress.

As the Revelation 2013 Conference attendees head off to the second set of breakout sessions of this year’s event, they will be making their way to sessions presented by Bob Catalano and David Goddard.

The OI Console Overview
Bob Catalano (Revelation, US)
OpenInsight version 10 is scheduled to include a new OI Console and during this presentation Bob will provide his audience with an overview of what developers can expect to receive in the new version.  The OI Console is a browser-based Database Management utility with numerous features that include: Database Statistical Dashboards, Indexing, User Management Tools, Table Re-Sizing Tools, Lock Management, Base filing System Management and Configuration Record Maintenance.

With a list of customer requested features that long, this will be a session that will appeal to anyone who is responsible for, or who administers a Revelation based system.

Source Management Using Git
David Goddard (Revelation, Aus)
Despite the title of this session and this blog posting, Revelation really do love and appreciate their developers and users.  However, Git is a free and Open Source distributed version control system that is designed to handle everything from small to very large projects with speed and efficiency.  Git was built to work on the Linux kernel, meaning that it has had to effectively handle large repositories from day one.  Speed and performance has been a primary goal of the Git from the start.

One of the nicest features of any Distributed SCM, Git included, is that it is distributed.  This means that each developer has a full copy of the repository locally on their laptop/pc.  this frees the developer to work remotely from a central server and still have full access to the source management repository.  Changes can easily be pushed/pulled to/from a central server or directly to another developer.

David’s presentation will demonstrate how Git can be used with OpenInsight.  With some sneaky repository hooks, 90% of the work is done for you, automatically, in the background, while you get on with creating great OpenInsight based software.  It really can’t get any easier than that.

But wait, there’s more…. if attendees like what they see, they can try the OpenInsight Git interface free in a copy of OpenInsight straight after the presentation.  I am assured that developers will wonder how they ever worked without (a) Git by their side.

Advertisements

One thought on “#RevCon13 – The OI Console using Git

  1. Some additional notes from David Goddard’s Git presentation:

    Source is human readable code, usually text, that is compiled.

    RBasic, inserts, windows, messages, popups, context menu’s are all source. openInsight is made up of source.

    External images and other items are not source code but are required by the system are considered source. These are compiled from source.

    Source management is a logical way to organize and control changes. Printed books are a simple method of source where resources are compiled into a specific version.

    Source management is not version management.

    Use source management to track changes over time, coordinate changes betweenmany developers, identify who broke it, and see what it looked like at a point in time.

    Developers often have clumber some methods to manage source, I.e. system backup, zip copies, directory copies, naming “save as” with an suffix.

    Developers are often hesitant to use a source control system because it requires additional steps…. Until now.

    In OI 9.4 the PRE and POST method have been added to the repository where all repository actions are recorded so actions can be hooked into the repository.

    With zero effort source assets can be written to a source system outside of OI when they are saved into the repository by using the repository hooks.

    Three different operating modes, locak only, centralized (subversion), de-centralized (git).

    Certralized, fine grain control over who can see what source code, only one person can access code at a time, only one copy of the repository exists.

    Decentralized, everyone has a copy of the repository to work locally. Patches can be sent between users of the server’s copy with impacting the server until the code is ready to be pushed to the server.

    Git is open source, free, distributed, fast, integrity checke by sha-a checksums , nearly all operations are performed locally, and it’s difficult to get git to do anything undoable.

    Git is very good at managing many changes in a single program / document.

    Google, Microsoft, Facebook all put money into the Git project.

    The OpenInsight interface to the source management tool, in this case git, can be used with other source tools.

    David walked through the source management tools for Git in openinsight by changing stored proceedures and forms and saving them to a new local repository and uploading it to a GitHub account. He then proceeded to show how changes made externally that are retrived from te GitHub are incorporated back into the OpenInsight repository.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s