– .. At the time of freezing the document, you can freeze other document context such as one or more selections/highlights, the state of the app (eg, wordwrap, line number display, colorization, customizations made to the menu entries, etc).

– .. This can form a way to file documents in a more graphical way (to help add mental context): The chosen directory is like a scroll parchment that is unwrapped by large animated hands. The pinned document icon is then inserted there much as you could on the desktop. You also see past document states that were saved onto that parchment as other pinned icons. Then the scroll rolls up again.

– .. Additionally, at the time of pinning the document, you can add notes and metadata onto a smaller scroll animation that folds up into a small roll and gets thrown into the document. The number and type of notes can be seen by mousing over the pinned document icon or by opening the document.

– Have an app that allows you to pick files or parts of files (eg, by typing the file name, marking an existing open file, or by generating the file names/locations through some other app) and visually show where on the hard drive or CD these files lie (eg, it would be a fraction of one or more circles). You can zoom in all the way to actually see the words based on where they lie on that media.

– With a monitor that has speaker sections on its various sides, you can control the surround sound direction and intensity by, eg, scribbling with the mouse on the desktop to indicate the direction and strength of sound (so mousing back and forth various times near the top right of the screen and then quickly on the left side would have most sound come from the top left speakers but a little on the left side as well). [Many alternatives to mouse scribbling exist: eg, slider, button, text controls.]

– .. The type of scribbling (ie, the selected mode/options) can allow you to define the types of sounds, eg, background music, website flash advertisements, alarm of various types, "you've got mail" notices, results of various batch processing, etc. This way, you know based on where the sound is coming from, what application is putting forth that sound.

– ..You can add in effects (like delays, frequency envelop shaping, volume control) also on a per sound category and location basis.

– .. Allow the sounding controls to be scriptable, in particular, integrate such specifications into many types of apps and context menus. This would allow for a running application's periodic results to be brought to your attention in a specific way (ie, special effect, volume, and sound location) depending on the actual resulting values or progress.

– A new torrent protocol would allow you to specify which parts of files you want to be chunked out first (there would be something like a probability distribution). The distribution can vary with respect to properties of the time of day, of the downloader, etc. This distribution information can remain private and solely under the control of the torrent file owner.

[20] — .. A graphical mousing tool would allow you to scratch (ie, scribble) at an image of the torrent file to define this same distribution information. [You could use many other widgets to define the distribution manually.]

– .. Allow traversing of folders quickly by swinging the mouse to the (eg) top right corner of the screen to go to parent folder.

– .. Have a mode where all the subfolders are lined up at the bottom and you can quickly pass by the subfolders and then hit down in a fast motion right around the right vicinity (based on the sounds you hear). If a particular resolution is not met, then the first downward movement eliminates all but (eg) 2 or 3 of the subfolders which then appear spread out widely. A second downward jerk of the mouse at the right spot would be easier to be on target since the folders would be far from each other (eg, 3 at left, center, and right, rather than 20 subfolders all next to each other).

– .. As a special automatic mode, have the sound coming from each folder be a pitch that suggests the size of the total contents of the subfolder (or maybe only going in one level at a time, etc). As another blend mode, have the pitch sound be based on last access time. As a special blend mode, have the frequency distribution of the file types inside the folders (eg, picture or png or word document or spreadsheet..) help shape the frequency sound.

– .. Allow for the user to speak or type key words (of some metadata type) and then have the sound profile of the searching be tuned to folders/files based on those key words.

– A Live Distro (live distro examples can be dug up here: http://distrowatch.com/ ) where you can set a mode so that every menu item you select from the desktop menu or from an application menu gives a tutorial for that entry (eg, it could be a video or animation or picture or some text). This would be a quick way to learn how to use any part of the distro without having to manually look up help docs of any sort. When you want help, just switch to learn mode and click away.

– .. Create Live Distros to cater to hobbies and to social causes. This would allow all the tools necessary and already expertly set up to be shared freely (and legally, of course) and easily (eg, a CD) with others sharing the same goals. The Live Distro is ideal for this and conflicts are not a problem because the live environment defines a new environment entirely. [Note, virtualization can simulate this but it's not as likely to work because of multiple competing standards and because many people don't even have virtualization set up.]

– Build a distro and PC system that has all of the relevant source code in the hard drive. We tag all projects (all source code) with metadata describing "all" aspects of the project (eg, all the interfaces implemented, the source location and uuid, the license of every single line if necessary…). You then update the distro by picking the app interface you want rather than to install a pre-cooked package. Thus, by specifying the properties of what you want, the distro decides what to compile with which parameters and if to recompile other applications or move them around. This helps solve the conflict scenarios that exist when you package something with details (but no associated metadata description) that then conflict with other details chosen by other packagers. The metadata has to be extensive and thorough, eg, specifying (implicitly in most cases) how conflicts would be resolved (eg, move the server port or rename something, etc). The computer would cache past compilations.

– .. Allow applications to be downloaded simply by their metadata file. After security checks, the applications would get built automatically based on this metadata bundle (which of course, lists the source through a network uuid of its components (including of patches)). If necessary (based on priority rules or user manual input), rebuild parts of the existing system to accommodate the new application. Download any necessary patches and source. In short, a metadata file re-adjusts the state of the computer.

– .. Build an application for the source PC that allows you to click on any application and have pop up the relevant body of source code. Then you can change any lines in any of the files and hit a button and the app would be recompiled under a different name with relevant entries being created in menus for easy access to your fork. Essentially: click, type, click and you have a fork.

[40] — .. And also be able to click on running software and the source code pertaining to where the application was when clicked would be highlighted for you. [This is possible with apps created with debugging info.] A context menu would allow you to see not just the top window application but also the lines where the kernel, the window manager, etc, were at that point in time.

1. The fact that IBM supports software patents /now/ is undisputed but is irrelevant and no defence of your erroneous statements and fallacious reasoning.

2. & 3. More fallacious reasoning and false assertions.

Sorry but your whole argument is (grossly) ignorant and fallacious.

PS. FYI the FFT was invented in the middle of the twentieth century. I think perhaps you're confusing the algorithm with the mathematical (Fourier) theory.

“LOL, I thought the whole thrust of your earlier argument was.. "IBM king of patents" does not support software patents.”

I'm sure you did think that but in reality it serves merely as a refutation of your false assertion (in quotes) which it follows – as is obvious to anyone of ordinary intelligence (LOL).

“maybe I missing something”

Just about everything relevant to the question of whether software is justifiable as patent eligible subject matter or not.

“According to Cooley himself, the 1965 paper only led to a redisovery of FFT – not 'invented' FFT”.

So what? According to Cooley himself, writing in hindsight in 1987, “the FFT was re-discovered, developed extensively, and applied on electronic computers in 1965…”

IOW it was still a likely *patentable* invention in 1965.