On 3 April 2016 at 14:37, Aliaksei Syrel <alex.syrel@gmail.com> wrote:

I completely agree with you now, Igor :)

The idea that I proposed during Pharo days is to make BlShape polymorphic with what athens have. I did not implement it yet I work on it just right now.

I suppose that I explained me wrong to Stef and he started thinking that it is already implemented. On my road back from Pharo days I started working on what Stef wanted to do yesterday.

I my example I just wanted to show Stef how he can solve his problem just right now, without saying "Oh, Stef, you know, please wait one more week".

Also that was the idea why I started implementing own implementation of Athens Api and named it Sparta. Specifically to remove amount of shapes/pathes/paints used in Bloc. I was planning to finish it before I send an announcement email to pharo mailing list saying officially that bloc is released to alpha.

Can you shed more light on this? I need your motivation/reasoning behind it.��

I tried in Athens to keep a minimal set of protocol(s), so that there's no need to learn numerous methods to start using it.

The shapes/paints thing is central in Athens.. so, if you see how it can be made even simpler, i am all ears to hear details.

In any case, what i can tell from your statement above is to remove unnecessary bloat.. which is always welcome. But why that requires changes in Athens API, instead of changes in Bloc?

��

I discussed it on Pharo days and we agreed to wait until announcement.
And now I'm frustrated that people don't listen to me and try to use product before official release just in the middle of refactoring.

No, i am not using it, yet.. The only 'people' was Stef himself :)

��

What you are stating in this discussion will be implemented early or later.

Best regards,
Igor Stasenko.