+ 1 :)
We are planning to integrate GT tools but this is at another level and
the future is bright and shinning :)
Stef
On 28/8/14 21:39, kilon alios wrote:
Well as the discussion was in another thread , Spec is licensed as MIT
inside Pharo , the new GPL license seems to affect any present and
future contributions from Ben. So I will say yes it looks like Spec is
here to stay, I may not be a fan of Spec design but they are many
Pharoers out there that they are and since Pharo community is quite
democratic looks like Spec is here to stay. The Pharo team wont be
able to add in Pharo any GPL affected contributions of Ben ( assuming
Ben continuous to develop Spec which I doubt) but Pharoers can
continue to contribute to the Pharo MIT Spec . So it looks like the
effect is minimum if you exclude the fact we lost the most major
contributor to Spec.
So far the idea is to push forward both Spec and Morphic and
personally I really like this idea as it lets people more options on
the GUI front which can be only good thing since anyone this way can
use the right tool for his or her own needs. It would also be a lot of
shame if Ben's hard work goes to waste even though he decided to give
up pharo, we have to respect his choice but also his work make sure
his effort don't go wasted as he built a tool that many people find
useful.
So yes you can keep using Spec and I am sure we will all appreciate
any contribution you make to Spec :)
On Thu, Aug 28, 2014 at 10:15 PM, Martin Saurer
<[email protected] <mailto:[email protected]>> wrote:
Dear all,
A few weeks ago, I read about the dispute on Spec, which has
escalated, and as a result of that, Ben has left the
Pharo/Smalltalk community. It's always sad when a long term member
leaves, but live is going on.
>From my (somewhat business minded) point of view one question is
currently unanswered:
Is there a future of Spec (without Ben)?
I'm asking this because I'm the author of a web frontend engine
which can be bound to a programming language (like Pharo) to
create desktop-like web applications. Currently there is an
implementation for the J programming language as well as a rough
(but working) implementation for Pharo. My plans for the (far)
future is to bind the frontend engine to Pharo in a more elegant
way probably by extending Spec. So one may write a desktop
application in Spec, and a corresponding web GUI is automatically
created as well.
So I'm currently a little unsure whether to go with Spec or going
back to the good old Polymorph.
Is somebody of the core team able to clarify the situation?
Many thanks in advance.
Martin
