Sharing Omnis Libraries on GitHub – one per project?
I concur with one lib per project…
Regarding your plugins, maybe you can point to your website, where demo
versions are available, or one can buy the runtime versions…
ie the artsman OmnisXL, relies on an external lib (*LibXL.dll) *for the
latest excel communications…
so you go somewhere else to get the latest version of that…
Some dev person just trying things out, would likely appreciate the demo
They may only have the demo Studio anyway!
Based in Chester in the UK.
On 02/02/2018 12:09, Michael Monschau wrote:
> Hi Doug,
> 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
>>> 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.
>>> 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