Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
File Viewer Interface
0 views
Skip to first unread message
Roedy Green
Dec 23, 2011, 2:09:38 PM12/23/11
to
Ironically, the best file viewer I ever used was created for DOS,
called Lotus Magellan. With a single keystroke you could view and
file and the viewing came up instantly. It let you use wildcards that
spanned multiple directories, and sort in various orders.
The to its success was a C interface you could use to implement a
viewer for any type of file. It was designed for speed.
What we need today is something similar for Java. The viewer
interface would let you write various types of file organiser/viewers,
and they would work with the entire library of submitted viewers. If
they did not, you could always write your own code to the viewer
interface.
Viewers are simpler and faster than editors, and can be stripped down
from what the full editor would display. A viewer only has to render
the top chunk of a file immediately. It can procrastinate the rest
till when the user scrolls down.
Such a tool would let you rapidly review files and delete the unwanted
files with a single keystroke, or move it off to some attic directory.
The hard part of writing a file organiser is the Viewers. With this
standard interface anyone could write one to their own particular
needs, or modify an existing one.
--
Roedy Green Canadian Mind Products
http://mindprod.com
If you can't remember the name of some method,
consider changing it to something you can remember.
called Lotus Magellan. With a single keystroke you could view and
file and the viewing came up instantly. It let you use wildcards that
spanned multiple directories, and sort in various orders.
The to its success was a C interface you could use to implement a
viewer for any type of file. It was designed for speed.
What we need today is something similar for Java. The viewer
interface would let you write various types of file organiser/viewers,
and they would work with the entire library of submitted viewers. If
they did not, you could always write your own code to the viewer
interface.
Viewers are simpler and faster than editors, and can be stripped down
from what the full editor would display. A viewer only has to render
the top chunk of a file immediately. It can procrastinate the rest
till when the user scrolls down.
Such a tool would let you rapidly review files and delete the unwanted
files with a single keystroke, or move it off to some attic directory.
The hard part of writing a file organiser is the Viewers. With this
standard interface anyone could write one to their own particular
needs, or modify an existing one.
--
Roedy Green Canadian Mind Products
http://mindprod.com
If you can't remember the name of some method,
consider changing it to something you can remember.
Roedy Green
Dec 23, 2011, 11:49:57 PM12/23/11
to
On Fri, 23 Dec 2011 11:09:38 -0800, Roedy Green
<see_w...@mindprod.com.invalid> wrote, quoted or indirectly quoted
someone who said :
>
>The hard part of writing a file organiser is the Viewers. With this
>standard interface anyone could write one to their own particular
>needs, or modify an existing one.
There may be several interfaces:
1. deliver vanilla text
2. deliver RTF or something similar.
3. deliver a bit map of rendered text.
<see_w...@mindprod.com.invalid> wrote, quoted or indirectly quoted
someone who said :
>
>The hard part of writing a file organiser is the Viewers. With this
>standard interface anyone could write one to their own particular
>needs, or modify an existing one.
1. deliver vanilla text
2. deliver RTF or something similar.
3. deliver a bit map of rendered text.
John B. Matthews
Dec 24, 2011, 1:15:19 AM12/24/11
to
In article <r3k9f79918g6iempv...@4ax.com>,
<http://codereview.stackexchange.com/q/4446/6692>
--
John B. Matthews
trashgod at gmail dot com
<http://sites.google.com/site/drjohnbmatthews>
Roedy Green <see_w...@mindprod.com.invalid> wrote:
> Ironically, the best file viewer I ever used was created for DOS,
> ...
> Ironically, the best file viewer I ever used was created for DOS,
> What we need today is something similar for Java. The viewer
> interface would let you write various types of file
> organiser/viewers, and they would work with the entire library of
> submitted viewers. If they did not, you could always write your own
> code to the viewer interface.
>
> Viewers are simpler and faster than editors, and can be stripped down
> from what the full editor would display. A viewer only has to render
> the top chunk of a file immediately. It can procrastinate the rest
> till when the user scrolls down.
>
> Such a tool would let you rapidly review files and delete the
> unwanted files with a single keystroke, or move it off to some attic
> directory.
>
> The hard part of writing a file organiser is the Viewers. With this
> standard interface anyone could write one to their own particular
> needs, or modify an existing one.
See also this Code Review entitled "File Browser GUI":
> interface would let you write various types of file
> organiser/viewers, and they would work with the entire library of
> submitted viewers. If they did not, you could always write your own
> code to the viewer interface.
>
> Viewers are simpler and faster than editors, and can be stripped down
> from what the full editor would display. A viewer only has to render
> the top chunk of a file immediately. It can procrastinate the rest
> till when the user scrolls down.
>
> Such a tool would let you rapidly review files and delete the
> unwanted files with a single keystroke, or move it off to some attic
> directory.
>
> The hard part of writing a file organiser is the Viewers. With this
> standard interface anyone could write one to their own particular
> needs, or modify an existing one.
<http://codereview.stackexchange.com/q/4446/6692>
--
John B. Matthews
trashgod at gmail dot com
<http://sites.google.com/site/drjohnbmatthews>
0 new messages