Hi, Is anyone maintaining the Addresses framework at the moment? I ask because it is based on a very different core assumption to its OS X equivalent, which is likely to cause huge compatibility problems. The core issue is that Addresses requires the type of each element to be specified, while the OS X version infers types from the contents. There are two major problems with this approach:
1) It will break Cocoa code in strange and exciting ways. 2) It is incredibly fragile. AddressBook on OS X is expected to be used to store various different types of data without the expectation that it will all be displayable in the Address Book app, or understandable by all AddressBook-using applications. The only kind of data that can be added to the Addresses database without breaking things are values with well-defined types stored in the framework. Unfortunately, I can't see a good way of fixing this without a significant rewrite. Someone mentioned that this was going to happen anyway, to make the system based upon CollectionKit. If this is still going to happen then I won't bother. If it isn't, then I will try to think of the best way of doing it. David _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
