Open Source Omnis library to integrate other Open Source libraries

Hi, Paul —

Thanks for your thoughts and comments.

One thing I had hoped for in this was to come up with a way to track the version of a particular library that was required. In Python you can indicate in the requirements.txt document that you want “omniscli 1.2.3” or better. Perhaps even a way to pull directly from GitHub via their API.

> On Mar 25, 2018, at 6:34 PM, Paul Mulroney <pmulroney@logicaldevelopments.com.au> wrote:
>
> Hi Scotte,
>
> I had a quick look at your project Integrity.
>
>>> github.com/SpoMacGuy/Integrity <github.com/SpoMacGuy/Integrity>
>
> This reminds me of some of the Linux package managers that the various distros use to maintain software on the operating system. The concept of “this module requires X”, and “this module provides X” is a great idea – the thought that we could pool the various open source projects together, and have some way of managing it easily has a lot of appeal. The strength of the package managers is the maintenance of the database of packages. On CentOS, they use “yum”, so you can say eg “yum install X”, and it finds the appropriate package from the database, and picks from a number of mirror sites to download the package.
>
> Years ago I was fascinated with the concept of CORBA (en.wikipedia.org/wiki/Common_Object_Request_Broker_Architecture <en.wikipedia.org/wiki/Common_Object_Request_Broker_Architecture>), and the idea that multiple libraries could “advertise” feature sets that could then be drawn together to form the basis of the complete application. Using that idea, we created our own system where we have a modular system, and each module (library) advertises the features that it offers, and the common library (broker) manages that list. When a window/menu/function needs a certain feature, it requests it of the broker, which returns an item reference for use. We built a hierarchy system up, so that if we wanted to do customisation for a particular client, you could advertise the feature set with a higher priority over the “standard” features.
>
> Your idea of an open source utility sounds like that, but on a much grander scale!
>
> Regards,
> Paul.
>
>
>
>> On 25 Mar 2018, at 10:10 am, Scotte Meredith <spomacguy@gmail.com> wrote:
>>
>> I’m not totally sure either, so thought I’d run the flag up the flagpole and see if anyone would salute.
>>
>> The idea is someone has an Open Source utility for Omnis that you have incorporated into your library. Maybe it was a library that connects to Trello API or some other API. There are a few utility classes in the library that you have integrated into your library instead of using the whole library. Then the utility library gets updated and you sync your local Git repository for that library with yours. Now you have the JSON version locally. You could build the library from JSON, then copy each of the classes into your local library.
>>
>> Instead, this copies from one repository to the other directly.
>>
>> Anyway that’s the idea. Open to other ideas anyone has.
>>
>>
>>
>>> On Mar 24, 2018, at 4:12 PM, Mike Matthews <omnis@lineal.co.uk> wrote:
>>>
>>> That sounds good, but I don’t really understand why we would need it, but maybe we do.
>>>
>>>
>>> Mike Matthews, Managing Director, Lineal Software Solutions Ltd
>>>
>>> Apple Reseller, Microsoft Partner, SQLWorks Business Partner
>>> phone: 01271 375999 | web: lineal.co.uk | email: mike.matthews@lineal.co.uk
>>>
>>>> On 24 Mar 2018, at 18:44, Scotte Meredith <spomacguy@gmail.com> wrote:
>>>>
>>>> Hey, folks —
>>>>
>>>> I put together a small Open Source project to help integrate other Open Source projects for Omnis and keep them up to date.
>>>>
>>>> The purpose of Integrity is to make it easy to integrate Open Source projects into your Omnis Studio library.
>>>>
>>>> Once you have included particular clases into your library, if there are changes made to the included library, how to you integrate them back into your library? As you have more and more Open Source projects included in your work, this becomes more difficult.
>>>>
>>>> It’s my first Omnis 8.1 Open Source library, so let me know if there are any problems.
>>>>
>>>> Since open sourcing Omnis libraries in Git is new to all of us, I’m open to suggestions on whether this project is worth pursuing and any ideas people have to make it more useful.
>>>>
>>>> Thanks to Alex Clay for getting things started, for his initial input, and for his GitHub sharing guide (omnis.ci/guides/sharing-omnis-libraries-on-github.html)
>>>>
>>>> Integrity
>>>> github.com/SpoMacGuy/Integrity
>>>>
>
>
> No matter how much you push the envelope, it’ll still be stationery.
> —
> Paul W. Mulroney We Don’t Do Simple Pty Ltd
> pmulroney@logicaldevelopments.com.au <mailto:pmulroney@logicaldevelopments.com.au> Trading as Logical Developments
> www.logicaldevelopments.com.au <www.logicaldevelopments.com.au/> ACN 161 009 374
> Ph: +61 8 9458 3889 86 Coolgardie Street
> BENTLEY WA 6102
>
>
>
> _____________________________________________________________
> Manage your list subscriptions at lists.omnis-dev.com <lists.omnis-dev.com/>
> Start a new message -> mailto:omnisdev-en@lists.omnis-dev.com <mailto:omnisdev-en@lists.omnis-dev.com>

Scotte Meredith
SpoMacGuy@gmail.com

_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com
Start a new message -> mailto:omnisdev-en@lists.omnis-dev.com