-
What is GT's philosophy regarding Metacello baselines? Our project, is a collaboration between some people set on working in Squeak and some in Pharo and some in Smalltalk/X and some in Bee, and for a significant stretch of time I have been eyeing GT and now I am in a position where I have a bunch of really nice GT visualizations and I would like to merge those into the main branch of the project. Obviously the visualizations use some GT-specific classes so that code will not compile in a non-GT image. What is the correct way of telling Metacello "this baseline is for GT"? I would be expecting something along the lines of |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
We are not recommending using groups because they are half baked concepts (you can depend on them, but you cannot manipulate them). Instead, we use exclusively only baselines. So, in your case, I'd have a GT specific baseline that loads your other baseline + the extensions. We typically call these GToolkit4XYZ. For example, take a look here: https://github.com/feenkcom/gt4smacc |
Beta Was this translation helpful? Give feedback.
-
I think this addresses what you are trying to do: https://github.com/seandenigris/Computer-World/blob/005fd697fc9518d3d2f9d53d67f808d638c5bbb6/repository/BaselineOfComputerWorld/BaselineOfComputerWorld.class.st#L65 It’s from one of many projects that aims to be loadable in either GT or Pharo. It doesn’t use groups |
Beta Was this translation helpful? Give feedback.
We are not recommending using groups because they are half baked concepts (you can depend on them, but you cannot manipulate them). Instead, we use exclusively only baselines. So, in your case, I'd have a GT specific baseline that loads your other baseline + the extensions. We typically call these GToolkit4XYZ. For example, take a look here: https://github.com/feenkcom/gt4smacc