11 Apr
2013
11 Apr
'13
9:53 p.m.
For your information igor spent 6 months of design and coding to develop athens + the
handle of cairo + improving nativeboost (fgting against bug in mac OSX in different
versions) to make it work. Now I think that be you should wait that 3.0 is out.
But do not expect athens to be good if nobody use it.
Stef
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.
I am a fierce advertiser of Athens. Thanks to Igor tutorial, my developing environment is
Athens-based. I would like to see Athens widely used, yes.
However, if I go a step further, such as making Roassal depends on Athens, 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
- telling where to download and how to install Igor's VM
- telling the world how to install the free type fonts else Roassal will lamentably
crash
- have to test myself cairo on Ubuntu
- 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.
- Answering complains that loading Roassal takes too much time
Alexandre
This should be pretty fast, too.
Cheers,
Doru
On Thu, Apr 11, 2013 at 2:50 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
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 I do not understand the problem.
Athens loads perfectly and all the VM are working.
Now if you prefer to wait for about a year, it simply means that you do not need vector
graphics.
Roassal needs to be loadable in a 1.4 image.
Alexandre
On Apr 10, 2013, at 10:48 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
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
--
www.tudorgirba.com
"Every thing has its own flow"
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi,
I do not quite understand your worries.
Athens-Cairo has two parts:
- the VM side: the plugin is already nicely bundled with the Pharo VM on all operating
systems.
- the image side: the Athens canvas and Cairo binding are essentially working, but were
not yet added to Pharo 2.0 because it was not tested enough at the time of the release.
To me, the largest problem is on the VM-side, and that was nicely solved. The image-side
is solid already and will get into Pharo 3.0. But, in the meantime, I do not want to wait
for another year until we can start to benefit from the nice capabilities of Athens.
Can you be more explicit as to why we should not make this default in Pharo Morphic?
Btw, it is not enough to just load Athens. Here is what I reverse engineered:
Gofer new
squeaksource: 'Athens';
package: 'ConfigurationOfAthens';
load.
(Smalltalk at: #ConfigurationOfAthens) loadVersion: '2.0'.
Gofer new
smalltalkhubUser: 'ObjectProfile' project: 'Roassal';
package: 'RoassalAthens';
load.
ROPlatform setCurrent: 'athens'.
Cheers,
Doru
On Apr 10, 2013, at 9:43 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:
>> I would like to start adopting Athens behind Roassal. I believe there already is
a binding. The question is what keeps us from adding Athens as a dependency to
RoassalMorphic?
>
> Well... The way I see this is slightly different. Athens should be part of the
runtime (i.e., included in Pharo) and not use as a library. I am not sure what we will
gain to consider Athens as a separate Library.
>
> The Roassal<-->Athens bindings works well I think. We haven't spotted any
problem. Just load Athens before loading Moose while Athens is not part of Pharo.
>
> Cheers,
> Alexandre
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> 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
--
www.tudorgirba.com
"There are no old things, there are only old ways of looking at them."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev