Sharing Omnis Libraries on GitHub – one per project?
What would you recommend if you had a library that relies on another library for it to run, or has other support files it requires (i.e. commercial external components). I guess one could add links within the read-me file or perhaps place additional support files and folders in the lib folder. How do you or would you (anyone else can jump in here) approach that?
> On 2 Feb 2018, at 10:48, Doug Easterbrook <email@example.com> wrote:
> I’d suggest one project per library.
> Doug Easterbrook
> Arts Management Systems Ltd.
> Phone (403) 650-1978
> see you at the third annual users conference
> tickets.proctors.org/TheatreManager/95/online?performance=29086 <tickets.proctors.org/TheatreManager/95/online?performance=29086>
>> On Feb 2, 2018, at 3:40 AM, Michael Monschau <firstname.lastname@example.org> wrote:
>> Hi $all,
>> I just created my account on github and I am ready to create my first project. I have a number of example libraries that I regularly use and update for EurOmnis and I thought it a good idea to upload these to github. My question is, should I have one project per library or should I upload all EurOmnis example libraries within one project?
>> In a bid to make Omnis a recognised language, I will also upload other example libraries suitable for sharing, including the demo libraries for our Brainy Data components.
>> Manage your list subscriptions at lists.omnis-dev.com
>> Start a new message -> mailto:email@example.com
> Manage your list subscriptions at lists.omnis-dev.com
> Start a new message -> mailto:firstname.lastname@example.org