Athens is an API, the rendering is actually done by the backends.
Currently Ballon and Cairo are supported.
So, the answer is that Athens is supported in all platforms using the
Ballon backend, (note that ballon does not have all the features of
Cairo, so some of the features in the demo wont work), and the Cairo
backend as well.
You just need to tell NativeBoos were to locate the cairo library
(built using MacPorts, so the path starts at /opt/...).
For now we just hardcoded the library path (you can change them by
hand for now, to point to your local Cairo lib)
TCairoLibrary class>>nbLibraryNameOrHandle
^ '/opt/local/lib/libcairo.2.dylib'
AthensSurface class>>nbLibraryNameOrHandle
^ '/opt/local/lib/libcairo.2.dylib'
This should be changed, perhaps a settings?
Fernando
On Fri, Apr 20, 2012 at 12:25 PM, Alexis Parseghian <[email protected]> wrote:
>> People should start to use Athens, apps around Pharo would start be
>> look waaaayyy cooler.
>
> About that.
>
> Is it supposed to work outside of the Mac platform ?
>
> Tried the demo, and AthensDemoMorph new openInWorld crashes on
> "function unavailable". That backtraces into Block in
> NBFFICallout>>generateCall:module: where module seems to be
> '/opt/local/lib/libcairo.2.dylib' which is obviously Mac-ish but makes
> no sense on Linux.
>
> Where is the library name and location set/picked up ? I guess this
> question could be generalized to how the platform-specific
> initialization happens.
>
> As an aside, all NativeBoost-Tests are green.
>
> Platform : debian testing 64-bit with ia32 libs installed. Latest
> NBCogVM from jenkins, blank Pharo 1.4 #14414 with Athens 1.0
> (explicitly) installed from SS:Athens/ConfigurationOfAthens.
>
> I also look forward to discovering whatever new, inventive stuff these
> new projects enable.
