Hi Sebastian,

On 02 Aug 2014, at 15:53, Sebastian Sastre <[email protected]> wrote:

> Hi Sven,
> 
> how are you doing?

I am fine, I hope you guys recovered from the football world cup hype ;-)

> Firstly let me ask you how should I load Zinc.
> 
> I’m doing it like this:
> 
> 
>       Gofer it
>               url: 'http://mc.stfx.eu/ZincHTTPComponents';
>               package: 'ConfigurationOfZincHTTPComponents';
>               load.
> 
>       (Smalltalk at:#ConfigurationOfZincHTTPComponents) project latestVersion 
> load: 'WebSocket'. 
>       (Smalltalk at:#ConfigurationOfZincHTTPComponents) project latestVersion 
> load: 'SSO'.
> 
>       Gofer it
>               url: 'http://mc.stfx.eu/Zodiac';
>               package: 'Zodiac-Core';
>               package: 'Zodiac-Tests';
>               load.   
> 
> 
> Is that the right source/way?

It is up to you to decide which version you want to load. Both Zinc & Zodiac 
are part of the base image, so for most users it is not necessary to load a 
newer version.

But you want more, I guess. I maintain two versions #stable and #bleedingEdge 
(as you can also see from the CI job: 
https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/). What I 
normally do in my images is loading #bleedingEdge over what is already there.

So that would be

Gofer it
  url: 'http://mc.stfx.eu/ZincHTTPComponents';
  configurationOf: #ZincHTTPComponents;
  loadVersion: #bleedingEdge.

Note that for 4.0 you need to proceed two warning about removed classes.

There is no separate configuration for Zodiac, it is part of Zinc's. When doing 
a #bleedingEdge load, you get those updates automatically (I think because 
these are present already and because only the baseline is used), else you need 
to load the 'Zinc' group too.

Next you want to load two specific groups

#('SSO' 'WebSocket') do: [ :each | 
  #ConfigurationOfZincHTTPComponents asClass project bleedingEdge load: each ].

Now, there was an error in Zinc-WebSocket-Core-SvenVanCaekenberghe.27 with 
respect to the superclass of ZnWebSocketLogEvent - although it was OK in my 
image with no dirty package. I committed a new version, 
Zinc-WebSocket-Core-SvenVanCaekenberghe.28. Please try again.

Thanks for the feedback !

HTH,

Sven

> Secondly, I’m experiencing this in the latest version:
> 
> 
> <Screen Shot 2014-08-02 at 10.50.00 AM.png>
> 
> What’s the package that has the missin ZnWebSocketControlFrameHandledEvent?
> 
> thanks!
> 
> sebastian
> 
> o/
> 
> blog: http://sebastianconcept.com
> LinkedIn: http://www.linkedin.com/in/sebastiansastre
> github: https://github.com/sebastianconcept
> 
> 
> 
> 
> 


Reply via email to