To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=74415 Issue #|74415 Summary|organize file handling around open/save import/export Component|framework Version|OOo 2.1 Platform|All URL| OS/Version|All Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|ENHANCEMENT Priority|P3 Subcomponent|ui Assigned to|tm Reported by|jes
------- Additional comments from [EMAIL PROTECTED] Sat Feb 10 21:47:56 +0000 2007 ------- File handling is probably the single most commonly used part of OOo. Unfortunately it is often one of the most confusing and inconvenient parts as well. I believe this could be greatly improved by organizing the file handling around this basic framework: Open/Save -- no file format changes Import/Export -- full user control over source and destination This would streamline the use of native files and help avoid the confusion naive users currently experience when "saving" their document in a non-native format, because it uses different words and menus for different operations. The Export operation would not register the file as "saved", thus naturally encouraging users to also "save" their file, giving them a native-format version. Exporting a file would also not change the name or file type of the current document, allowing easy creation of foreign-format files, e.g. to send as an attachment. The import/export pathways would include a re-designed user interface for completely specifying the file types and access to all available options for the file translation. This would avoid current problems such as * Loss of data or work when a document is "saved" in a foreign format. E.g, creating a copy of a document, e.g. a spreadsheet, as CSV using "Save As", then exiting Calc to find that no native format file exists. * Inconvenience when saving in a foreign format. E.g, creating by "Save As" a copy of a Writer document as .doc--now the current document has it's name changed and the "Recent Documents" list points to the .doc, rather than the native file. * Mysterious behavior when "opening" foreign files. E.g. opening an "Excel file" from Calc and having the file open in Writer because it is actually a CSV or HTML file. Instead of opening such a file (since a file format change is needed), it would need to be imported, where the user could specifically request conversion from CSV to a Calc document. * Confusing UI issues. The import/export interface would include descriptive names for each file type, in place of the current file type drop-downs which have long lists of often cryptic format names. Access to options for the file transformation could be presented in a uniform way, rather than through ad hoc option dialogs. This would not introduce any new functionality, only re-organize and define a clear policy for the existing file-handling operations. If implemented carefully, I believe this could make OOo more robust and predictable, as well as easier to use. However, this is still a rather fundamental change, so I don't know if it is even practical to consider. If it would help, I can prepare a more detailed proposal. --------------------------------------------------------------------- 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]
