Re: [Pharo-dev] GTools merging configurations

To return to this conversation, I used more versioner, and, though it still can be improved, it makes creating new versions easier. So, all in all, for now, we can keep the current configurations as they are. Cheers, Andrei On Thu, Oct 15, 2015 at 8:49 PM, Tudor Girba

Re: [Pharo-dev] GTools merging configurations

In my opinion it depends on the project size. When it’s small and evolves fast you can have everything in one conf. If the projects get big and evolve more slowly, it makes sense to keep them in separate configurations… I think that it’s about time for managing configurations vs time for

Re: [Pharo-dev] GTools merging configurations

I can imagine that well. Up to you but I think that having modular parts is nice too. What we should is a way to automatically update configurations. Stef Le 14/10/15 22:20, Andrei Chis a écrit : Hi, For the GTInspector, GTPlayground and GTSpotter we now have distinct configurations.

Re: [Pharo-dev] GTools merging configurations

On 15-10-15 09:48, stepharo wrote: I can imagine that well. Up to you but I think that having modular parts is nice too. What we should is a way to automatically update configurations. I love modular parts. I see a ripple effect Stephan p.s. Alex: this breaks the normalizer

Re: [Pharo-dev] GTools merging configurations

That is one beautiful analysis :) Doru On Thu, Oct 15, 2015 at 6:24 PM, Stephan Eggermont wrote: > On 15-10-15 09:48, stepharo wrote: > >> I can imagine that well. >> Up to you but I think that having modular parts is nice too. >> What we should is a way to automatically

[Pharo-dev] GTools merging configurations

Hi, For the GTInspector, GTPlayground and GTSpotter we now have distinct configurations. However, this complicates the integration process with Pharo as a lot of configurations need to be updated. So we'd like to merge them in ConfigurationOfGToolkitCore. What do you think? This will simplify a