[Kde-accessibility] [Bug 63749] import and export file format issues (usability)

[Pupeno]

------- You are receiving this mail because: -------
You are a voter for the bug, or are watching someone who is.
     
http://bugs.kde.org/show_bug.cgi?id=63749     




------- Additional Comments From pupeno at kde.org  2003-10-09 22:29 -------
I don't completly agree with Sander Devrieze but I think he has a point in that 
something should be done... I have a simpler idea... 
Document based applications, like KWord, KSpread or even Kate should have an 
export function, which is like save as but with a simple diference, the 
application goes on editing the initial document, so, if I'm editing file.kwd 
and I export file1.kwd I go on editing file.kwd, then I could export file2.kwd 
but I go one editing file.kwd, then I may export file.doc and file.txt, but 
kword is always editing the original file, file.kwd. 
Import would only make sense if open wouldn't open non-native files (in which 
case, save shouldn't save non-native files) but I don't think this is a good 
idea. 
Import would make sense in training based applications, that saves the current 
status of the training to an internal file in .kde but to allow more 
versatility, it also allows to import and export that status to a file. 
I think that import and export should then, be turned into standard actions and 
that the training based application or status based application (a game would 
be droped in the same category for example) should be well explained in the 
style guides as well as the behaviours of export and import. 
Thanks