Hi Andriy && Thiago,
thanks a lot for your comments and suggestions, and sorry for the late
reply :-( I'm still somewhat busy with getting things set up in my new
home and my new job, but it looks as if there is now some light at the
end of the tunnel :-)
From your posts, I see there is a general tendency to have Cohatoe as a
self-standing building block, and I'm also in favour of that (keeps
things more simple). I might also add that I think of Cohatoe as a
rather slim framework. The basics are in place, and apart from smaller
issues and some peripheral things (like better documentation and tool
support), I don't think there will be a lot of effort in developing
Cohatoe itself in the near future. Rather, I think most of the code that
will be created should be in EclipseFP, and it should use Cohatoe to
implement language-sensitive features.
> I agree with Andriy to a certain degree. Keeping a separate project will
> certainly demand more time from you, Leif, and it is much reasonable
> to keep Cohatoe inside EclipseFP for as long as it makes sense. But
> we need to make sure that Cohatoe and EclipseFP code bases (and
> ideas) are kept as untangled as possible. Being the excellent
> programmer that you are, I am sure you can do that. And I promise at
> least to be out of the way. :-)
Not at all, I'm very happy you are around :-))
As for the code bases, I think they should remain in separate Darcs
repos and they should also have separate build/release cycles. That's
mostly because I think that Cohatoe will be relatively quiet and have
not many updates (see above), and the main rock'n roll will go on the
EclipseFP side (and very hopefully mostly in Haskell ;-).
> Assuming you decide to go down this path, as first measures, I think
> we should set up a separate page for Cohatoe inside our site and make
> it very visible as Andriy pointed out and set up a separate repository for
> the cohatoe code. What do you guys think we also need to get started?
Well, for me the homework looks like:
- move the darcs repo to our sf server, put it next to the main
- move the download site for Cohatoe to the general EclipseFP download site
- point to the EclipseFP mailing list as primary mailing list for
Cohatoe discussion, both for using and developing it.
I suggest we use a tag such as '[cohatoe]' for posts that have to do
I don't think we need more for the moment. I think I'll leave my blog in
place and continue to use it the way I did so far (was a lot of fun at
least for me, I'll just have to reserve some time again for it :-). But
I will take some of the older articles, review them, and put them in the
help files for Cohatoe. Or maybe we could put them on a wiki page?
Thanks a lot && ciao,
> Thiago Arrais
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> eclipsefp-develop mailing list