Dear List,
for localizing an Application I would like to translate the constants in the Chronology-Core. What's the best way to do this? I file my changes for my application in a Monticello package. I could just overwrite the definitions with my own, but I would love to do this in a less destructive way.
Any ideas?
Thanks!
Christian
There has always been a problem of keeping the core source of Smalltalk separate from project code. The best way I know of is to make an new object with an instance variable containing the object you want to modify, then make the mods on your seperate object instead of cluttering up the original object.
On Sun, Mar 24, 2019 at 6:07 AM Christian Kellermann ckeen@pestilenz.org wrote:
Dear List,
for localizing an Application I would like to translate the constants in the Chronology-Core. What's the best way to do this? I file my changes for my application in a Monticello package. I could just overwrite the definitions with my own, but I would love to do this in a less destructive way.
Any ideas?
Thanks!
Christian
-- May you be peaceful, may you live in safety, may you be free from suffering, and may you live with ease. _______________________________________________ Beginners mailing list Beginners@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/beginners
Hi Kirk!
* Kirk Fraser overcomer.man@gmail.com [190324 14:46]:
There has always been a problem of keeping the core source of Smalltalk separate from project code. The best way I know of is to make an new object with an instance variable containing the object you want to modify, then make the mods on your seperate object instead of cluttering up the original object.
In this case, it's a SharedPool. While I could inherit and override its initialization method, how would I make the rest of the Timespan hierarchy use my version instead of the in-system one?
Thanks!
Christian
beginners@lists.squeakfoundation.org