Tim Mackinnon wrote
> Yeah - I have a similar issue with ExternalWebBrowser... that drags in...
> [a] huge raft of tests
My workflow is to make every project one monolithic package until the need
to do otherwise is presented (like right now!). I used to carefully think
about theoretical use case
Yeah - I have a similar issue with ExternalWebBrowser, which I load as:
spec
baseline: 'ExternalWebBrowser'
with: [ spec
repository:
'github://seandenigris/Pharo-Web-Browser:master/repository' ];
import:
Hi,
I'm updating the the baseline of PharoJS to use the zinc websockets from the
github repo https://github.com/svenvc/zinc. I want to load package
Zinc-WebSocket-Core. So, in BaselineOfPharoJS>>#baseline: I've defined
spec baseline: 'ZincHTTPComponents' with: [
spec
