Studio – Github

Hi Andrea,

This is one of the benefits—two developers can modify the same class. When you’re ready to integrate your code with others’ work, you merge your changes together.

Alex

> On Oct 5, 2017, at 03:34, Andrea Zen <a.zen@athesiavr.it> wrote:
>
> How is simultaneous development managed? I mean what now is the locking of classes in the VCS, when you “check out to modify”, that prevents developers to work both on the same class.
>
> Andrea Zen
>
>
>> —–Original Message—–
>> From: omnisdev-en [mailto:omnisdev-en-bounces@lists.omnis-dev.com] On
>> Behalf Of Alex Clay
>> Sent: Wednesday, October 4, 2017 8:40 PM
>> To: OmnisDev List – English <omnisdev-en@lists.omnis-dev.com>
>> Subject: Re: Studio – Github
>>
>> Hi Andrew,
>>
>> Instead of checking out classes, you simply make the changes you need.
>> When ready, export the library to JSON. You then commit it like any other
>> code – add new files, remove deleted ones, and commit and push when
>> ready. When you need to integrate with another developer’s work, pull the
>> remote repository into your local copy. In Studio, import the JSON code into a
>> new library and voila, you have the latest copy!
>>
>> Mix this with feature branching and you have a slick setup for multiple
>> developers…and it’s handy for single devs, too.
>>
>> I’m covering how to do this at EurOmnis in 10 days or so in case you’ll be
>> there. 🙂
>>
>> Alex
>>
>>> On Oct 4, 2017, at 14:35, Andrew Stolarz <stolarz@gmail.com> wrote:
>>>
>>> Hi Alex,
>>>
>>> Thanks I will look into it.
>>>
>>> Im used to the old school omnis VCS process, check in – check out
>>> within Omnis.
>>>
>>>
>>> How does this work for you using GitHub and JSON exports? ie. what is
>>> the process like to “check in / check out” components?
>>>
>>>
>>>
>>>
>>> Andrew
>>>
>>>
>>>
>>> On Wed, Oct 4, 2017 at 2:26 PM, Alex Clay <aclay@mac.com> wrote:
>>>
>>>> Hi Andrew,
>>>>
>>>> Your best bet is to jump to Studio 8.1 so you can export your
>>>> libraries as JSON. We have a couple projects on GitHub that host both
>>>> this JSON source and then compiled .lbs files:
>>>>
>>>> github.com/suransys/omnistap
>>>> <github.com/suransys/omnistap
>>>>>
>>>> github.com/suransys/omniscli
>>>> <github.com/suransys/omniscli
>>>>>
>>>>
>>>> Alex
>>>>
>>>>> On Oct 4, 2017, at 14:21, Andrew Stolarz <stolarz@gmail.com> wrote:
>>>>>
>>>>> Just curious if anyone is using Omnis libraries with Github? if so, how?
>>>>>
>>>>> or we locked into using the Omnis VCS?
>>>>>
>>>>>
>>>>>
>>>>> Andrew
>>>>>
>> __________________________________________________________
>> ___
>>>>> Manage your list subscriptions at lists.omnis-dev.com
>>>>
>>>>
>> __________________________________________________________
>> ___
>>>> Manage your list subscriptions at lists.omnis-dev.com
>>>>
>>>
>> __________________________________________________________
>> ___
>>> Manage your list subscriptions at lists.omnis-dev.com
>>
>> __________________________________________________________
>> ___
>> Manage your list subscriptions at lists.omnis-dev.com
> _____________________________________________________________
> Manage your list subscriptions at lists.omnis-dev.com

_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com