[Pharo-dev] Pharo3 issues
tudor at tudorgirba.com
Tue Dec 31 07:44:40 EST 2013
I do not understand this reaction :(
On Tue, Dec 31, 2013 at 12:01 PM, Marcus Denker <marcus.denker at inria.fr>wrote:
> On 31 Dec 2013, at 11:58, Tudor Girba <tudor at tudorgirba.com> wrote:
> I think this should not be a global preference at all. Most of the time,
> you actually want to commit in the same repository where you always do.
> Only from time to time do you need to switch and copy to another repo. So,
> the preference should be per browser, not global.
> consider that the issue was open since July. How likely is it that what
> you describe will ever be done?
> On Tue, Dec 31, 2013 at 11:55 AM, Marcus Denker <marcus.denker at inria.fr>wrote:
>> On 30 Dec 2013, at 14:42, Sean P. DeNigris <sean at clipperadams.com> wrote:
>> > Marcus Denker-4 wrote
>> >>> - In monticello browser: when I select my project, all the
>> >>> available in Pharo are shown. As in Pharo 2.0, it should show only the
>> >>> concerned repositories (2 or 3 max).
>> >> Yes, this was made on purpose and there is an issue that questions if
>> >> idea was good:
>> >> (this issue is from July)
>> > I commented in the issue:
>> > +1. I don't like this change at all. Would someone comment on whether
>> > is an unseen purpose or this is a bug?
>> I think we should set the default of the preference to be the opposite,
>> then it’s fixed with no
>> problems for those wanting the other behaviour.
> "Every thing has its own flow"
"Every thing has its own flow"
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pharo-dev