Bug 818408 - directory link enhancements
Summary: directory link enhancements
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Application Server
Classification: Retired
Component: jrefactory
Version: 2.0
Hardware: All
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Ted Ross
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-03 02:32 UTC by Brent
Modified: 2020-03-27 18:39 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-27 18:39:18 UTC
Embargoed:


Attachments (Terms of Use)

Description Brent 2012-05-03 02:32:25 UTC
Description of problem:

This is a suggestion or imagination of a new directory function which might fit in with F17+.  I'm not sure this is the correct place to post this but I hope the suggestion will get some attention here.

The concept is based on HTML/Ajax functionality and how that might be integrated into the shell or file manager.  When setting up a directory structure and using soft links, I thought it would be advantageous if the link file would contain a list of automatically generated links to actual directories of files rather than a straight link to the destination directory.

link file >

destination directory 1
destination directory 2
destination file 1 (click to load)
destination file 2 - size - permissions - etc


The link file would be at a lower level than an html based solution, at the OS level with a flat file backend.  It would allow a broken link, a soft fail if files are moved out of the directory or if the directory is disconnected and it would allow some idea of a disconnected drives content.

It seems like a fairly easy implementation with a minimal memory footprint, used only when creating a new link and all-around positive upgrade to the current link system.  If other OS's have that functionality, I am not aware of it.


Thanks for reading up on this enhancement suggestion.


Note You need to log in before you can comment on or make changes to this bug.