While the fix is simple, its not a minor thing just to change a preferences file external to the image. This is going to bite *everyone* who moves to 5.0-development, and when 5.0 is released its going to bite lots of general public.�� A debugger can't be presented at startup with any reasonable expectation that users think Pharo is a quality product.��First impressions count.��This should be handled more gracefully by presenting instructions on how to migrate to StartupPreferencesLoader using version specific folders."Yuriy, Did you log an issue already to cleanup the StartupLoader references?cheers -benOn Wed, Apr 22, 2015 at 2:34 PM, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:Yes, I know. But while I was trying to understand the problem, I���ve found places in StartupPreferencesLoader where code is generated with StartupLoader. It���s a minor thing, but do we really need a place with potential problems in our system?
Uko
> On 22 Apr 2015, at 08:13, Esteban Lorenzano <estebanlm@gmail.com> wrote:
>
>
>> On 21 Apr 2015, at 19:27, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
>>
>> Oh, it should be replaced by StartupPreferencesLoader. I���ll submit a slice
>
> a slice for what?
> the changes you need to do are in your preferences file, not inside the image.
>
> Esteban
>
>>> On 21 Apr 2015, at 19:20, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
>>>
>>> So now startup actions are not working because StartupLoader was removed. What are the plans about this?
>>>
>>>> On 21 Apr 2015, at 17:40, GitHub <noreply@github.com> wrote:
>>>> 15368 unload Deprecate40 in Pharo5
>>>>�� �� https://pharo.fogbugz.com/f/cases/15368