Common classes with JSON library representation
I realize this question is probably a bit early as most of us aren’t yet
using the new JSON library export but I’ll ask it anyway. I probably
should have brought it up at EurOmnis but it has only just occurred to
me now I am back in the office.
Has anybody put thought into a satisfactory way to handle classes which
are common to more than one library/application? We have multiple
applications and an infrastructure library of common code in our Omnis
VCS. This library’s classes are linked to most of our applications and
this works very well in the context of building our libraries from the
VCS. But I don’t immediately see an obvious way to handle this in a
multiple repository setup like Git. It may just be that I don’t yet
have a full understanding of Git but I would appreciate any thoughts you
may have on the topic.
Thanks and best regards,
PS. It was great to see and catch up with everyone at the conference.
Manage your list subscriptions at lists.omnis-dev.com