[Design] Import Export supported client versions
Davor Cubranic
cubranic at cs.ubc.ca
Tue Jun 19 21:53:42 PDT 2007
On Tuesday 19 June 2007 15:44:17 Mikeal Rogers wrote:
> Ecco Pro
> - Why are we supporting this? They seem to have one developer left
> and a fairly small user base.
One developer? The company that owns Ecco hasn't had any developers on
it for a decade. There is a number of third-party utilities that are
still maintained, mostly homebrew, and I know of one guy who has
apparently been hacking the binary to extend it with additional
functionality.
There is a Perl library for interfacing with Ecco using the API it
exposes through DDE (yes, it's that old) that could perhaps be used to
inspect the structure its documents and transfer their contents into
Chandler. But the mismatch in functionality is still too great for this
to really be useful, IMHO. The only thing that makes sense to transfer
is the calendar notebook. But this is just one small part of Ecco,
which many users don't even use because they are already forced to use
Outlook and other enterprise scheduling applications. I definitely
think there is no point transferring its address book until there isn't
an equivalent thing in Chandler, and especially not the rest of the
data if there is no a) outlining/dependent items, and b)
user-configurable attributes in table views.
Davor
More information about the Design
mailing list