Hi alistair I understand. If this is a useful combination my practice is to create a separate projects which loads both.
For Pillar and Magritte this is another story. When magritte is used deep down in the core of Magritte then you end up being forced to load magritte even when you do not need it. I was a naive design decision. Stef On Mon, Nov 27, 2017 at 11:02 AM, Alistair Grant <[email protected]> wrote: > Hi Stef, > > On 26 November 2017 at 22:39, Stephane Ducasse <[email protected]> > wrote: >> Hi Alistair >> >> If you want help I can add a baseline that automtically load DataFrame. >> Because users should not load by themselves external project. > > Thanks for the offer, but Pharo-Chrome isn't actually dependent on > DataFrame. I just used it in an example in the README as it makes > inspecting the results easy (it's possible to inspect the results > without DataFrame, you'll just be looking at an Array of Arrays). As > we've seen from Pillar and Magritte, the more dependencies the greater > the maintenance costs and potential for incompatibility. If there's a > compelling reason to automatically load DataFrame I'm happy to do > that, but at the moment I'm not seeing it. > > Cheers, > Alistair > > > >> Stef >> >> On Sat, Nov 25, 2017 at 3:57 PM, Sean P. DeNigris <[email protected]> >> wrote: >>> Alistair Grant wrote >>>> https://github.com/PolyMathOrg/DataFrame >>> >>> Cool, thanks! I didn't know about this project. >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >>> >> >
