Hi David,
Indeed, you should move it to another package.
However, this package should either:
be in its own repository
load it with the initial project
In this case, you'd have to clone the whole initial project and
load only the package that you want to share, which can be quite big.
Either way, you'll have to tweak the baseline, as you can read about
here:
https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/Baselines.md
Hope this helps.
Pierre
On 01/03/2021 21:49, da...@totallyobjects.com wrote:
I guess that the answer is to move the kv into its own package but I
don't know how to refer from one package to another. Can anyone
clarify for me.
Sent from my Huawei tablet
-------- Original Message --------
Subject: [Pharo-users] Sharing classes between packages
From: David Pennington
To: Any question about pharo is welcome
CC:
I have a small Key/Value database that I have written for my
Seaside apps. I have one Package - Family-Accounts which defines
the classes for this database. I am now writing a new Seaside app
(IPMSClacton) that will also need to use the database. How do I
share the code between the two packages?
David
Totally Objects
