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 scenarios and split projects up along those lines, but management (especially with the tooling available at that time) seemed to explode exponentially, so I went monolithic. After several years of experience, this is the first time someone expressed a pain point (that I remember anyway)! This seems to validate the current approach and my suspicion that preemptively creating multiple packages is akin to premature optimization. Tim Mackinnon wrote > I think what we have to do is submit pull requests to these projects such > that they create better baselines with Groups Yes! I will happily integrate. The tests may need to be promoted to a package if they are currently in a tag, but 'Core' without and 'Tests' with seems appropriate given your issue. I don't have a strong opinion on the default but my guess is to leave it as is (i.e. all packages) because newbies will get the tests (i.e. documentation) and advanced users will know enough to customize. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
