Issue 65543 - read-only files do not appear in the "recent files" list
Summary: read-only files do not appear in the "recent files" list
Status: CONFIRMED
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: 680m99
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
: 83587 97473 (view as issue list)
Depends on:
Blocks:
 
Reported: 2006-05-18 13:38 UTC by Frank Schönheit
Modified: 2013-08-07 15:31 UTC (History)
4 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Frank Schönheit 2006-05-18 13:38:33 UTC
- start OOo
- open a file which you do not have write access to
- close the file
- quit OOo
- start OOo
=> the file you previously opened does not appear in the "File / Recent Documents"
   menu
Comment 1 Mathias_Bauer 2006-05-24 12:00:43 UTC
Until now this is "works as designed". In case we want to have r/o file in the
picklist someone needs to define how we should treat files loaded by plugin or
Active-X control.

IMHO the current treatment is better; as the picklist has a very limited size we
shouldn't pollute it with every possible file we have loaded. At the end OOo
still mainly is an editor for files, not a viewer.
Comment 2 Mathias_Bauer 2006-05-24 12:01:38 UTC
Changed type to "enhancement" because due to the history of the current feature
it is an RFE.
Comment 3 Frank Schönheit 2006-05-24 12:42:29 UTC
In the case where I encountered the problem, I opened a document which was
read-only, but contained a small "application" (vulgo: some useful Basic
scripts) which I needed to run. Next time I needed to run them, I had to
manually browse to the file, again, which took me unnecessary time.

I'd like to consider OOo an "application development platform". Not necessarily
as primary goal, but as an important one. Then, the case that somebody gives you
an "application" (i.e. a document) which you just use, without actually
modifiying the document itself, might be more common.
Comment 4 matthias.mueller-prove 2006-05-24 13:40:35 UTC
Bettina, this is an RFE to be evaluated.
Comment 5 carsten.driesner 2006-05-24 16:20:14 UTC
Added on CC.
Comment 6 Mathias_Bauer 2006-06-07 14:58:02 UTC
BTW: documents shouldn't be (mis)used as a deploment tool for macros. So this is
a not a use case I consider to be relevant. But YMMV.
Comment 7 Frank Schönheit 2006-06-07 15:05:17 UTC
Hmm? Ever seen the zillions of MS Office documents which implement small
applications? This, IMO, is part of what made MSO strong ....

(side note: besides everything else, I want to have the 10er test document in
the recent files :)
Comment 8 Mathias_Bauer 2006-06-07 15:14:41 UTC
Having a document with assigned macros to work on it IMHO is something
different. A readonly document containing macros to start is just a launch pad
for macros. They better should be deployed as basic libraries or UNO packages. 
Comment 9 Mathias_Bauer 2007-12-04 15:21:40 UTC
Bettina, any progress here? In case you have no strong sympathy for the RFE I
would like to opt for closing it.

The recent file list is a scarce resource and IMHO should be reserved for files
that are edited not for other files that have been opened just for browsing them.
Comment 10 Mathias_Bauer 2007-12-04 16:17:24 UTC
according to release status meeting -> target 3.x
Comment 11 Frank Schönheit 2008-06-17 20:49:49 UTC
*** Issue 83587 has been marked as a duplicate of this issue. ***
Comment 12 bettina.haberer 2010-05-21 15:01:41 UTC
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements". 
Comment 13 Olaf Felka 2010-09-09 06:42:21 UTC
*** Issue 97473 has been marked as a duplicate of this issue. ***