Configuration for Roassal 3D

>
> On Dec 19, 2013, at 20:03 , Ronie Salgado wrote:
>> ed the configuration of Roassal 3D so it loads the baseline version of NBOpenGL, with the changes I made. However, I have tested it only in Linux, so I don't know if its working in Windows or in Mac OS X. Any feedback is appreciated.
>
> Works on my mac. Thank you.
>
> Stephan
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

> Serge Stinckwich wrote:
>> Apparently there is no CI job on https://ci.inria.fr/pharo-contribution/
>>
>> in order to use PharoLauncher.
>>
>> Regards
>>
>> On Thu, Dec 19, 2013 at 4:17 PM, Stephan Eggermont
>> <[hidden email]>
>>  wrote:
>>  
>>
>>> Is there a configuration that works in Moose 5?
>>>
>>> Stephan
>>> _______________________________________________
>>> Moose-dev mailing list
>>>
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>>    
>>>
>>
>>
>>
>>  
>>
> You mean something other than [1] & [2].  The first builds immediately on any source or upstream change.  The latter is triggered manually for a significant release to turn it into a deployed application.
> [1] https://ci.inria.fr/pharo-contribution/job/PharoLauncher
> [2] https://ci.inria.fr/pharo-contribution/job/PharoLauncherFinalUserImage
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

> Serge Stinckwich wrote:
>
> Apparently there is no CI job on https://ci.inria.fr/pharo-contribution/
> in order to use PharoLauncher.
>
> Regards
>
> On Thu, Dec 19, 2013 at 4:17 PM, Stephan Eggermont <[hidden email]> wrote:
>
>
> Is there a configuration that works in Moose 5?
>
> Stephan
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
>
>
>
> You mean something other than [1] & [2].  The first builds immediately on
> any source or upstream change.  The latter is triggered manually for a
> significant release to turn it into a deployed application.
> [1] https://ci.inria.fr/pharo-contribution/job/PharoLauncher
> [2] https://ci.inria.fr/pharo-contribution/job/PharoLauncherFinalUserImage
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>

> Sorry Ben,
>
> I was talking about a ROASSAL 3D image that I can see under
> PharoLauncher list of images.
>
> Regards,
>
> On Mon, Dec 23, 2013 at 4:56 PM, Ben Coman <[hidden email]> wrote:
>> Serge Stinckwich wrote:
>>
>> Apparently there is no CI job on https://ci.inria.fr/pharo-contribution/
>> in order to use PharoLauncher.
>>
>> Regards
>>
>> On Thu, Dec 19, 2013 at 4:17 PM, Stephan Eggermont <[hidden email]> wrote:
>>
>>
>> Is there a configuration that works in Moose 5?
>>
>> Stephan
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>>
>>
>>
>> You mean something other than [1] & [2].  The first builds immediately on
>> any source or upstream change.  The latter is triggered manually for a
>> significant release to turn it into a deployed application.
>> [1] https://ci.inria.fr/pharo-contribution/job/PharoLauncher
>> [2] https://ci.inria.fr/pharo-contribution/job/PharoLauncherFinalUserImage
>>
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>
>
>
> --
> Serge Stinckwich
> UCBN & UMI UMMISCO 209 (IRD/UPMC)
> Every DSL ends up being Smalltalk
> http://www.doesnotunderstand.org/
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

> Currently we do not have it. But it would be great to have one. I will try to create one...
>
> Alexandre
>
>
> On Dec 24, 2013, at 12:12 PM, Serge Stinckwich <[hidden email]> wrote:
>
>> Sorry Ben,
>>
>> I was talking about a ROASSAL 3D image that I can see under
>> PharoLauncher list of images.
>>
>> Regards,
>>
>> On Mon, Dec 23, 2013 at 4:56 PM, Ben Coman <[hidden email]> wrote:
>>> Serge Stinckwich wrote:
>>>
>>> Apparently there is no CI job on https://ci.inria.fr/pharo-contribution/
>>> in order to use PharoLauncher.
>>>
>>> Regards
>>>
>>> On Thu, Dec 19, 2013 at 4:17 PM, Stephan Eggermont <[hidden email]> wrote:
>>>
>>>
>>> Is there a configuration that works in Moose 5?
>>>
>>> Stephan
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>>
>>>
>>>
>>> You mean something other than [1] & [2].  The first builds immediately on
>>> any source or upstream change.  The latter is triggered manually for a
>>> significant release to turn it into a deployed application.
>>> [1] https://ci.inria.fr/pharo-contribution/job/PharoLauncher
>>> [2] https://ci.inria.fr/pharo-contribution/job/PharoLauncherFinalUserImage
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> [hidden email]
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>
>>
>>
>> --
>> Serge Stinckwich
>> UCBN & UMI UMMISCO 209 (IRD/UPMC)
>> Every DSL ends up being Smalltalk
>> http://www.doesnotunderstand.org/
>> _______________________________________________
>> Moose-dev mailing list
>> [hidden email]
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev