To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=41370
------- Additional comments from [EMAIL PROTECTED] Wed Feb 2 04:54:25 -0800 2005 ------- Yes, a database is not a file. And what we display to the user in the data source browser (what an ancient name), and what she is editing when she chooses the menu item in question, is not a database. It is also *not* really the file she is editing, since of course she *can* manipulate the server-side data definition from within our application. That's exactly the terminology problem we have, with our concept of "files without the actual data": We cannot say "database" because it implies (to a significat percentage of our target audience) that it's a self-contained database - which it isn't. We cannot say "database file" because it's too techy. We cannot say "database document" because of whatever. We cannot say "Database connection file" or "Data source file" or so because it's definately too techy. We have a conceptual problem here, and the agreement in the iTeam, when we realized and discussed this, was that "database file" is the best compromise. I'm open to re-discussing this, but we should a) involve the whole iTeam on this and b) find arguments why the problem caused by "database" is better than the problem caused by "database file". In my opinion, I didn't see the latter, so far. --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
