> - Moose depends on OSProcess, I think we do not want this. What are your opinion ? This is because of the wizard to load from inFusion. But, what is the problem here?

> - MoosePanel needs TreeMorph from Momo10, so I loaded latest Momo10, but I don't know the impact on the rest of system. (project Momo does not have TreeMorph) MorphTreeMorph should already be in Pharo 1.1. Now, I would like to have a final Moose in 1.0 and then start working on 1.1.

> When these three things are fixed, all Moose works with Pharo1.1. Did you also run the tests?

Ah... Moose on the iPhone. My dream! Is there a chance I can get it on my iPhone ? I had Pharo on some point, but the certificate expired. Alexandre On 20 Mar 2010, at 11:37, Laval Jannik wrote: > >> >> >>> - Moose depends on OSProcess, I think we do not want this. What are your opinion ? >> >> This is because of the wizard to load from inFusion. But, what is the problem here? >> > > No real problem, but it sucks when I load it on iPod..... > Because there is no OSProcessForIPhone. > > >>> - MoosePanel needs TreeMorph from Momo10, so I loaded latest Momo10, but I don't know the impact on the rest of system. (project Momo does not have TreeMorph) >> >> MorphTreeMorph should already be in Pharo 1.1. Now, I would like to have a final Moose in 1.0 and then start working on 1.1. >> > Nice :), > At Lille, we will work for that. > > >>> When these three things are fixed, all Moose works with Pharo1.1. >> >> Did you also run the tests? >> > Yes, so results: > > There are some deprecations. or:or: should be replaced. > Then, there are 75 errors ans 16 failures. > > <1.jpeg> > So, we need to concentrate efforts on 1.0, then we will see these bugs. > For now, I try Moose on 1.1 to make eDSM on Pharo. > > Cheers, > Jannik >> > > --- > Jannik Laval > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Thanks, I will check. It appears to be free. Cheers, Alexandre On 20 Mar 2010, at 13:59, Laval Jannik wrote: > Hi Alex, > > If you are in a university, you can ask a Iphone dev account. > It is the easier for future (no problem of expired certificate), but it takes time (1 month). > http://developer.apple.com/support/iphone/university.html > > Cheers, > Jannik > > On Mar 20, 2010, at 17:52 , Alexandre Bergel wrote: > >> Ah... Moose on the iPhone. My dream! >> Is there a chance I can get it on my iPhone ? >> I had Pharo on some point, but the certificate expired. >> >> Alexandre >> >> >> On 20 Mar 2010, at 11:37, Laval Jannik wrote: >> >>> >>>> >>>> >>>>> - Moose depends on OSProcess, I think we do not want this. What are your opinion ? >>>> >>>> This is because of the wizard to load from inFusion. But, what is the problem here? >>>> >>> >>> No real problem, but it sucks when I load it on iPod..... >>> Because there is no OSProcessForIPhone. >>> >>> >>>>> - MoosePanel needs TreeMorph from Momo10, so I loaded latest Momo10, but I don't know the impact on the rest of system. (project Momo does not have TreeMorph) >>>> >>>> MorphTreeMorph should already be in Pharo 1.1. Now, I would like to have a final Moose in 1.0 and then start working on 1.1. >>>> >>> Nice :), >>> At Lille, we will work for that. >>> >>> >>>>> When these three things are fixed, all Moose works with Pharo1.1. >>>> >>>> Did you also run the tests? >>>> >>> Yes, so results: >>> >>> There are some deprecations. or:or: should be replaced. >>> Then, there are 75 errors ans 16 failures. >>> >>> <1.jpeg> >>> So, we need to concentrate efforts on 1.0, then we will see these bugs. >>> For now, I try Moose on 1.1 to make eDSM on Pharo. >>> >>> Cheers, >>> Jannik >>>> >>> >>> --- >>> Jannik Laval >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > --- > Jannik Laval > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

> > >> - Moose depends on OSProcess, I think we do not want this. What are your opinion ? > > This is because of the wizard to load from inFusion. But, what is the problem here? > No real problem, but it sucks when I load it on iPod..... Because there is no OSProcessForIPhone.

>> - MoosePanel needs TreeMorph from Momo10, so I loaded latest Momo10, but I don't know the impact on the rest of system. (project Momo does not have TreeMorph) > > MorphTreeMorph should already be in Pharo 1.1. Now, I would like to have a final Moose in 1.0 and then start working on 1.1. > Nice :), At Lille, we will work for that. >> When these three things are fixed, all Moose works with Pharo1.1. > > Did you also run the tests? > Yes, so results: There are some deprecations. or:or: should be replaced. Then, there are 75 errors ans 16 failures. <1.jpeg> So, we need to concentrate efforts on 1.0, then we will see these bugs. For now, I try Moose on 1.1 to make eDSM on Pharo. Cheers, Jannik > --- Jannik Laval _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev