> Am 21.10.2015 um 10:46 schrieb Marcus Denker <marcus.den...@inria.fr>:
> 
> 
>> On 21 Oct 2015, at 10:42, Norbert Hartl <norb...@hartl.name 
>> <mailto:norb...@hartl.name>> wrote:
>> 
>> Will Epicea be in pharo5? 
>> 
> 
> Yes.
> 
Oh well then it is time to move to pharo5 I think :)

thanks,

Norbert

>> Norbert
>> 
>>> Am 21.10.2015 um 07:57 schrieb Marcus Denker <marcus.den...@inria.fr 
>>> <mailto:marcus.den...@inria.fr>>:
>>> 
>>> 
>>>> On 20 Oct 2015, at 19:28, Jean Baptiste Arnaud <jbaptiste.arn...@gmail.com 
>>>> <mailto:jbaptiste.arn...@gmail.com>> wrote:
>>>> 
>>>> In addition clean, the .change before publish the files. Especially if you 
>>>> plan to keep this change browser.
>>> No, we plan not to. It is just a standin until we have Epicea. Which we 
>>> wanted to ship already in Pharo4.
>>> 
>>>> Useful, because the actual change browser do not have a lot of way to 
>>>> filter select/reject and load change. Not at all in fact.
>>>> But here I have 95% of the changes are just related to the image creation. 
>>>> I do not load Roassal, GT and everything.
>>>> Should not appear in my change of my application. 
>>>> 
>>>> It is not a troll question but there are a way to reload the old change 
>>>> browser ?
>>>> Where is it ?
>>>> 
>>> It was the last tool bases on the SringHolder/CodeHolder hierarchy. It is 
>>> not a modular thing.
>>> 
>>> All this was supposed to be replaced by Epicea ages (years?) ago.
>>> 
>>>> 
>>>>> On 20 Oct 2015, at 11:08, stepharo <steph...@free.fr 
>>>>> <mailto:steph...@free.fr>> wrote:
>>>>> 
>>>>> So far not 
>>>>> 
>>>>> For now with the old changes replay.
>>>>> What would be easy to do (that nobody did) is to prompt the user for 
>>>>> another image/change and read from there. 
>>>>> 
>>>>> 
>>>>> Le 20/10/15 14:45, Jean Baptiste Arnaud a écrit :
>>>>>> A question pop in my head ?
>>>>>> Epicea will help me to recover change from my old.changes ?
>>>>>> If not can have a link to Oz or something.
>>>>>> 
>>>>>>> On 20 Oct 2015, at 08:19, Marcus Denker < 
>>>>>>> <mailto:marcus.den...@inria.fr>marcus.den...@inria.fr 
>>>>>>> <mailto:marcus.den...@inria.fr>> wrote:
>>>>>>> 
>>>>>>> 
>>>>>>>> On 20 Oct 2015, at 12:59, Jean Baptiste Arnaud 
>>>>>>>> <jbaptiste.arn...@gmail.com <mailto:jbaptiste.arn...@gmail.com>> wrote:
>>>>>>>> 
>>>>>>>> 
>>>>>>>>> On 20 Oct 2015, at 05:03, Nicolai Hess <nicolaih...@gmail.com 
>>>>>>>>> <mailto:nicolaih...@gmail.com>> wrote:
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> 2015-10-20 7:27 GMT+02:00 Marcus Denker < 
>>>>>>>>> <mailto:marcus.den...@inria.fr>marcus.den...@inria.fr 
>>>>>>>>> <mailto:marcus.den...@inria.fr>>:
>>>>>>>>> 
>>>>>>>>> > On 20 Oct 2015, at 00:26, Jean Baptiste Arnaud < 
>>>>>>>>> > <mailto:jbaptiste.arn...@gmail.com>jbaptiste.arn...@gmail.com 
>>>>>>>>> > <mailto:jbaptiste.arn...@gmail.com>> wrote:
>>>>>>>>> >
>>>>>>>>> > Hi, maybe a useful question :-)
>>>>>>>>> >
>>>>>>>>> > I crashed a image :-)
>>>>>>>>> > And I ask myself:
>>>>>>>>> >       - There are a more advance (thinking bout maybe epicea) 
>>>>>>>>> > change browser ? Because a list of 1293801283 changes and just 1 
>>>>>>>>> > options select all (which is broken you should use shortcut) will 
>>>>>>>>> > not really helpmeet
>>>>>>>>> 
>>>>>>>>> We are in the process of integrating it. We tried saturday night, but 
>>>>>>>>> the resulting update did not finish running all tests and we had to 
>>>>>>>>> revert.
>>>>>>>> Can I have a link to the source ?
>>>>>>>> 
>>>>>>> 
>>>>>>> the issue tracker entry is
>>>>>>> 
>>>>>>>          
>>>>>>> <https://pharo.fogbugz.com/f/cases/14605/Integrate-Epicea>https://pharo.fogbugz.com/f/cases/14605/Integrate-Epicea
>>>>>>>  <https://pharo.fogbugz.com/f/cases/14605/Integrate-Epicea>
>>>>>>> 
>>>>>>>         Marcus
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> Best Regards
>>>>>> JB
>>>>>> jbaptiste.arn...@gmail.com <mailto:jbaptiste.arn...@gmail.com>
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>>> Best Regards
>>>> JB
>>>> jbaptiste.arn...@gmail.com <mailto:jbaptiste.arn...@gmail.com>
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>> 
>> 
> 

Reply via email to