(i am not subscribed to moose list , so my reply is on pharo list only).

On 11 April 2013 21:49, stephane ducasse <stephane.duca...@free.fr> wrote:
> Hi guys
>
> I crosspost because I hate when I get complains without having mails sent to 
> the right forum.
>
> On Apr 11, 2013, at 3:46 PM, Alexandre Bergel <alexandre.ber...@me.com> wrote:
>
>>> If I understand correctly, if we would get ConfigurationOfRoassal to load 
>>> Athens only in Pharo 2.0, you would be satisfied, right?
>>
>> No, because if I download the Pharo from http://www.pharo-project.org/home 
>> (by clicking on the download button), install Roassal, then errors will show 
>> up, and this is what I want to avoid above everything else.
>
> Sure do not report it to the mailing-list……. frankly I do not understand.
> How can we address problems if people do not report them?
>
>> I am a fierce advertiser of Athens. Thanks to Igor tutorial, my developing 
>> environment is Athens-based.
>
> you know everything was in the examples since months.
>

Yes, but only with release of Pharo 2.0 we got VMs fully ready for use
by Athens.
(yes VMs was available more than half of the year before, but you had
to use special VMs and know where to take it and other boring
details... and before you had to install cairo by yourself)..
But with 2.0 we got an integrated solution where VM and Image both
ready for Athens.
On all platformz.

>> I would like to see Athens widely used, yes.
>>
>> However, if I go a step further, such as making Roassal depends on Athens,
> sorry but I do not get how you can get roassal working with athens without 
> having it depend on it because
> it would solve a lot of our modularity problem.
>
AFAIK, Roassal provides own abstraction layer(s) and can use Athens as
one of backends..
I don't see compelling reasons why one cannot solve the modularity
problems by checking what is available on system before going and
blowing up with errors.

>> then we will have to deal with:
>>  - students who simply clicked on the download webpage and see bugs 
>> appearing because the lib are not installed
>
> we cannot do magic.
> May be then you should prepare a virtual image OS with the lib installed. We 
> cannot install lib on all the platform of earth.

That's not needed anymoar. VMs are Athens-ready since release of Pharo 2.0.

> Sorry but if there is not cairo installed what can we do? May be the install 
> of Damien will handle such case. But if you use an OS
> for your lecture or students you should also have a look at it. Or do not use 
> Pharo 2.0 but then you will use software that is one year old
> with around 1000 fixes not available.
>
>>  - telling where to download and how to install Igor's VM
>
> the DEFAULT Pharo VM works with cairo. so I do not get what you mean.
>
>>  - telling the world how to install the free type fonts else Roassal will 
>> lamentably crash
>
> On which platform? I do not get what you are saying. On mac I press the 
> settings and it works. Alain is developing on linux so it should
> work too.
>
Settings>>appearance>>enable freetype
(btw, why we do not enabling it by default??? i think it is time to
reconsider what is good
defaults for new Pharo release)

>>  - have to test myself cairo on Ubuntu
>
> May be damien will address your problem. but again why do not create a 
> virtualize image containing a well install OS?
>
>
>>  - fiddling ConfigurationOfRoassal to make it sure it works with 1.4 and 
>> trying to not get nervous because I will surely won't be able to save 
>> Roassal using Versionner anymore.
>
> For versionner again, even in 1.4 I cannot use it because most of the time I 
> need handling of projects.
>
>>  - Answering complains that loading Roassal takes too much time
>
> This will be fixed but not now.
> Really?
> Not the moose people.
> The moose people complain about the speed of roassal not its loading.
>
>
>> Alexandre
>>


-- 
Best regards,
Igor Stasenko.

Reply via email to