Microsoft Patents Grouped Taskbar Buttons
I_am_Rambi writes "According to the US Patent office, patent #6,756,999 belongs to Microsoft. The patent this time is grouping taskbar icons processes. This is included in Windows XP, and some prior art in X. Looks like it was accepted two days ago."
Was the prior art in X prior to Windows XP's release and/or wide beta?
THERE IS prior art.
BeOS' Tracker had that in 1999 before anyone else. All windows/instances from the same application are showing grouped in the BeOS Deskbar, under the same sub-menu.
It seems the big difference is in the 'time threshold' part:
"The system organizes like application files and clusters the corresponding taskbar buttons and, upon reaching a threshold limit, creates and displays a group button that contains the like application files and removes the like taskbar buttons from the taskbar. Further, upon reaching a second threshold limit, the system ungroups the application taskbar buttons, displays them on the taskbar and removes the group button from the taskbar."
Big difference? Probably not, but enough for it to be 'new'...
Don't worry, I patented posting about abolishing the patent system. Anyone making covered posts will be sent a bill to cover licensing costs.
"Grouping in the taskbar has to be one of the most annoying "Features" ever seen in a taskbar."
It is? Funny, I've found it quite useful when having tons of windows open. Is my personal opinion insightful, too?
"Derp de derp."
They should also patent rebooting.
Apparently it is.
Which makes me wonder.. is this comment funny?
-- If no truths are spoken then no lies can hide --
When a case such as this is won, and the patent is revoked, is there any funding that is returned to the side that won to recover litigation costs?
---- Booth was a patriot ----
Even if you had thought of it years before, not everyone did. And they still had a right to patent it since you didn't, and you didn't implement it.
Perhaps you should take a look at what is supposed to be patentable before you warm up your fingers.
Two aspects of patent - it must be NOVEL, and it must be NON-OBVIOUS.
You figure this as both "NOVEL" and "NON-OBVIOUS"?
Neither do I, and that's why the complaining.
I have no problem with your religion until you decide it's reason to deprive others of the truth.
I think all this patenting is actually a bad move on m$'s behalf..
Think about it, if they keep patenting little stupid things like this as an attempt to cripple and slow down alternate desktops such as X from advancing in the market place then this in the long run is probably a bad move,
As it's already been proved many times that if you make something not possible for someone they will work out a compromise and at least 70% of the time come up with something better and more efficient.
Obviously the desktop war is far from over but the industry needs innovation (Even if it has to be forced into it)
Apparently this patent was wordsmithed by a thirteen year old girl: "displays a group button that contains the like application files and removes the like taskbar buttons from the taskbar"
By the perception of illusion, we experience reality
Unfortunatly I patented posting about how you patented posting about abolishing the patent system...I think...that's a lot of patenting posted...potents pasted? Wait, now I'm really mixed up...
Track your TV Shows with your iPhone - FREE
The problem everyone is hav ing here is that "obvious" doesn't mean "obivous". Sure, maybe it seems obvious to a user, but obvious in the context of patentability has a very specific definition:
From the Manual of Patent Examining Procedure, section 706.02(j):
"To establish a prima facie case of obviousness, three basic criteria must be met. First, there must be some suggestion or motivation, either in the references themselves or in the knowledge generally available to one of ordinary skill in the art, to modify the reference or to combine reference teachings. Second, there must be a reasonable expectation of success. Finally, the prior art reference (or references when combined) must teach or suggest all the claim limitations. The teaching or suggestion to make the claimed combination and the reasonable expectation of success must both be found in the prior art and not based on applicant's disclosure. In re Vaeck, 947 F.2d 488, 20 USPQ2d 1438 (Fed. Cir. 1991). See MPEP 2143 - 2143.03 for decisions pertinent to each of these criteria."
The basic notion is that there must be some prior art, or combination of prior art, that "teaches" EACH AND EVERY claim element in the later patent -- PLUS there has to be a "motivation" to combine them. Just because there is prior art, or because something seems "obvious" to a user, doesn't mean that it meets the LEGAL definition of "obvious" relevant to the USPTO.
Just thought I would mention that...
"That's not even wrong..." -- Wolfgang Pauli
Of course I noticed the thread -- especially as the reference featured MY NAME in the first place!
:-) ;-)
Of course I was surprised to see that Microsoft seems to patent something that is closely built after my thoughts mentioned on the kde-look mailing list in 1999 already.
One of the problems with considering my thread as prior art is that unfortunately it was implemented by Matthias Elter some months later. It only turned out during implementation that task grouping only becomes interesting if
- the user doesn't use virtual desktops already (because he already organizes his tasks himself already)
- the tasks are only grouped after a certain thresholded is reached.
It doesn't take to be a genius to get that threshold idea because it's just the logical next step once you implement it but it seems that Microsoft actually implemented my idea before we did and therefore realized this tiny step before us.
Anyways it's interesting to see how Microsoft seems to monitor the KDE mailinglists since 1997.
E.g. I had the idea to create kpersonalizer which featured a dialog with a slider which you could easily use to configure the amount of eyecandy versus performance in KDE.
It was funny to see a very similar dialog in XP Betas two months later which contained almost the same wording in some places
So much for cross-polluting ideas between KDE and MS developers
I don't wish to seem petty, but the examples you give are NOT software. They're mathematical algorithms which could be implemented in software if you wanted. Or you could build dedicated hardware to do it, or you could work it all out by hand, (in theory), or anything else you fancy.