Directory and File Explorer  Directory and File Explorer

This essay does not describe an existing computer program, just one that should exist. This essay is about a suggested student project in Java programming. This essay gives a rough overview of how it might work. I have no source, object, specifications, file layouts or anything else useful to implementing this project.

This project outline is not like the artificial, tidy little problems you are spoon-fed in school, when all the facts you need are included, nothing extraneous is mentioned, the answer is fully specified, along with hints to nudge you toward a single expected canonical solution. This project is much more like the real world of messy problems where it is up to you to fully the define the end point, or a series of ever more difficult versions of this project, and research the information yourself to solve them.

Everything I have to say to help you with this project is written below. I am not prepared to help you implement it; or give you any additional materials. I have too many other projects of my own.

Though I am a programmer, I don’t do people’s homework for them. That just robs them of an education.

You have my full permission to implement this project in any way you please and to keep all the profits from your endeavour.

Please do not email me about this project without reading the disclaimer above.

Introduction

This student project aims to create something like Microsoft File Explorer, but that works on any Java platform. It aims to bring back some of the ease of the old Lotus Magellan or QDOS for DOS (Disk Operating System). This is more of a programmer’s tool than an end user’s tool. Some of the features:

Implementation

Quick Viewers implement an interface, and can be dynamically loaded. Slow viewers actually launch an app via exec. Each app has to be configured with exactly what that command looks like under each OS (Operating System). Users can write their own viewers to plug in for their own file formats. You might look at how the old Magellan interface worked to get an idea how to design a high performance viewer. It had file format reconinizers, scolling viewers and indexers. You might support a JDisplay-style interface that supplies tokens to render, only computing them if the user scrolls down far enough. That would give you colourised Java, HTML (Hypertext Markup Language) etc which is easier to understand.

You might tackle a stripped down version of this project. You feed it the program directory name or list of directory names. With a single click of up or down arrow you can view the previous or next document in the directory. By hitting Del you can delete a document. It only works on text documents. It displays the first page of the document, the date, size, and filename. You might optionally implement Page Down, Page Up. Even this mini-version would be very useful for rapidly pruning your disks of old junk.

For a more challenging project thing about how you could create tools to rapidly compare files in two directories, letting you see at a glance which files are in one directory but note the other, common to both, bigger, newer, and where matching files differ.

SUBST

In the meantime, until somebody writes this beast, there is a trick you can use in windows to simulate bookmarks. Use subst to create fake drives P: and Q: attached to whichever directories are important and the moment. You can then refer to them as P: and Q: in commands, though there are no jump-to buttons.
J Drive

CMP homejump to top

available on the web at:

http://mindprod.com/project/explorer.html
  

optional Replicator mirror
of mindprod.com
on local hard disk J:

J:\mindprod\project\explorer.html
logo
Please email your , letters to the editor, errors, omissions, typos, formatting errors, ambiguities, unclear wording, broken/redirected link reports, suggestions to improve this page or comments to Roedy Green : feedback email. If you want your message, your name or email kept confidential, not considered for public posting, please explicitly specify that. Unless you state otherwise, I will treat your message as a letter to the editor that I may or may not publish in the feedback section. After that, it will be too late to retract it. If you disagree with something I said, especially when sending an ad-hominem attack, a rant composed mainly of obscenities or a death threat, please quote the offending passage and cite the web page where you found it, tell me why you think it is wrong, and, if possible, provide some supporting evidence. I can’t very well fix erroneous or ambiguous text if I can’t find it.
Blog
IP:[65.110.21.43]
Your face IP:[54.234.126.92]
You are visitor number 25,562.