2 replies to this topic

[Cris D.]

I realize that cocoon is still a way off, but it seems that some progress has been made (hopefully enough to answer this question) which is...

How likely is it that existing Etomite API's will be compatible with the new Etomite release?
I'll make it multiple choice to make it easy for you
1) Don't be stupid, I'm re-writing the whole thing from scratch so it will be coincidence if anything is backward compatible.

2) There's some overlap in code classes and it's possible that some elements of the existing API's will work with tweaking.

3) I'm trying to make as much backward compatible as I can, it's quite likely that many existing API's will still work in the new release.

4) If you give me your snippets, I'll re-write cocoon so that they work ok on it. (I'm guessing it's not this one).

[Dean]

well i know you can scratch number 4 off that list...

[Ralph]

Well, to be honest, don't assume that any resources from Etomite Prelude will work with Cocoon without modifications... But don't let that be cause to stop developing for Prelude thinking that you'll be dead-ending your efforts... The current code base will be around for a while, probably for quite a while, even after Cocoon has been released... And conversions to the new code base won't be terrible - but there will be differences that will need to be addressed... And remember, there is always a possibility that a compatibility API could be integrated for legacy resources... All of this compatibility is being taken into consideration but one thing that I want to make clear is that the next release will be radically different than the current Etomite Prelude code base...