To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=81658
------- Additional comments from [EMAIL PROTECTED] Thu Oct 25 02:51:30 +0000 2007 ------- I would go along with pretty much everything msc2 had to say. An import implementation must have some way of showing the user which records, if any, where rejected. So from the stand point of the extension implementing this feature I would say it is a 5. I suppose that doesn't necessarily require that a callback be available, as the extension could implement a post import check to compare the source and the destination datasets. But having this callback function for an error state as part of the API would certainly be the cleanest and most desirable solution, IMO. So, if this one feature would be the difference between a realization of the api in say 12 months from now, versus 4 months. I'd say leave it out for now, but it really should be part of the overall plan, and if it could make into the first cut all the better. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
