Slashdot Mirror


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."

15 of 714 comments (clear)

  1. BeOS had that in 1999 by Anonymous Coward · · Score: 5, Informative

    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.

    1. Re:BeOS had that in 1999 by OblongPlatypus · · Score: 4, Informative

      I fail to see how this new "twist" is non-obvious, though. It seems an extremely obvious combination of the Windows taskbar and the Be deskbar.

      By the way, here is a USENET post from 1998 discussing the deskbar.

      --
      -- If no truths are spoken then no lies can hide --
    2. Re:BeOS had that in 1999 by fyngyrz · · Score: 4, Informative
      Imagemaster (not an OS, but a program) for the Amiga had toolbars for processsing images. The toolbars had pop-up lists of windows containing images. These pop up (some of them "popped sideways", in fact) lists were dynamically generated, dynamically grouped, and dynamically positioned with the other tools. Images (we just called them "buffers") could be items without an assigned role, paintbrushes, composing sources, composing targets, filter sources, etc. And there could be any number of buffers loaded. So grouping by assigned role was a big issue.

      The entire toolbar was dynamically generated, and could contain various assortments of tools, images, palettes and so forth - and there were a number of other dynamically instantiated things there too, such as proportional controls, buttons, text entry widgets and so forth. Various classes of things always grouped together. The toolbar itself could auto-hide and pop up when you moused down to it, or it could pop in and out based upon a right-click. And in fact, we had implemented both auto-hide of the toolbar, and auto-hide of contextually inapropriate and not recently used tools in May of 1990, in an earlier product called "reg-paint", now that I think about it.

      The fact that the toolbars in Imagemaster were totally dynamic and context-sensitive with the specific aim of being reductionist was actually a selling point for the program, well beyond the convenience of having the UI configure itself for what you were doing at the moment. This was because the Amiga had a limited amount of what was called "chip" memory (1 or 2 mb), which was basically the only memory that could contain drawable graphics, playable sounds, and some other system stuff. So the fact that the program's huge number of controls, windows and so on were dynamically generated and accessed by a panel that only contained what you needed, as you needed it, was a pretty big deal. That made the panel itself a very stingy consumer of chip memory, and that was the primary inspiration for a lot of what it did.

      Imagemaster was shipping in February of 1991. Tons of supporting documentation, magazine articles, manuals, users, you name it. Way too much to get lost in the sands of time. Very popular application, too. Imagemaster brought out the very first implementation of morphing on a desktop PC. Imagemaster shipped until Commodore's demise and for a little while thereafter, and that toolbar existed in every version.

      So Billy can bite me. Either Pete Patterson and myself came up with the idea first, or someone before us did (which would be fine, I could care less), but it sure as heck wasn't Microsoft. Or Be. :)

      Sideways remark: We used to say that if Commodore owned the Kentucky Fried Chicken franchise, they'd market it as "lukewarm, dead bird." The Amiga was amazing for its time. I still miss the machine at times. But I sure don't miss Commodore.

      --
      I've fallen off your lawn, and I can't get up.
  2. Not exactly the same by Anonymous Coward · · Score: 5, Informative

    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'...

  3. Prior Art by the+eric+conspiracy · · Score: 4, Informative

    While there is probably prior art for this, you have to realize that the issue date in not what determines if the prior art is relevant. It is the invention date or original filing date, which in this case was back in April 2000.

  4. Re:OK, so MS has had this since winXP... by ewhac · · Score: 4, Informative

    BeOS. Since 1998, and probably much earlier.

    Schwab

  5. Re:USPTO and time elapsed between filing and grant by Edmund+Blackadder · · Score: 4, Informative

    "What is the average time to get a patent approved,"

    It mostly depends on the field of art. Because there has been a huge boom in computer patents, there is a backlog in that department ... they often take 2 years to examine your invention on the merits.

    Once the patent is examined on the merits, the examiner often makes rejections, to which the applicant answers with arguments/ammendments, and that may repreat several times, until the examiner agrees on a version of the application that is patentable. That part may take several years as well.

    Three years is not really a long time to get a patent. I have seen some patents that have been languishing for 5 years. And sometimes the delay is not due to the PTO, rather it is the applicant's fault.

  6. Re:Another one for the EFF to bust. by EvanED · · Score: 4, Informative

    XP's release date has nothing to do with it. You need to find a system than had it in use no later than April 1999, one year before the filing date, to be sure of prior art.

    The regulations are that prior art disqualifies a patent if and only if it was in use or on sale or had a description published before the latter of the invention date (which might be hard to prove) or one year before the filing for the patent. (35 USC 102.) Because we are not sure of the invention date, we need to go off of the one year previous rule.

  7. Re:Funding by CaseyB · · Score: 5, Informative

    You don't "file a case" to defeat a patent. You release a product that uses the patented work, and wait for them to come to you.

  8. Re:Wow.. by Anonymous Coward · · Score: 4, Informative

    They didn't patent double clicking. Go read the patent.... they patented application buttons on PDA's (and similar devices) that performs different functions depending on how long the buttons are pressed, and how many times it's clicked within a specific amount of time. Whether or not they should've been granted that patent debatable, but simply saying that they've been granted a patent on double clicking is just wrong, and just plain silly.

  9. Re:Wow.. by dasmegabyte · · Score: 4, Informative

    Stephen Levy often plays fast and loose with the facts in order to make a more entertaining book (hence all the "hey cool" but impossible anecdotes in "Hackers").

    The GUI was invented aways back in the 1960s. At first, it was just a cursor, but it was definitely driven by a puck with a button on it. There's you're mouse, years before PARC. PARC, which was a research center, by the way, not a product development center, created a graphical interface for performing actions featuring windows and icons. This was brought to the attention of Steve Jobs, who thought it was neat and traded several million dollars worth of Apple stock to Xerox in exchange for a "field trip" with his developers to PARC. Apple didn't license the technology per se -- there was nothing to license at that point, there was no product yet -- but they also didn't use Xerox's idea. They took the interface for performing actions and used the basic premise to create an interface for managing objects. They turned icons as verbs into icons as nouns, inventing in the process such things as the first Desktop, the first file management system (Finder) and the first graphical forms, controls and alerts (Xerox's interface was basically a CLI in a window with buttons).

    Microsoft's "patent for double clicking" pertains only to hardware buttons on palm sized devices, and only to the specific use of timed accesses. Sounds like double clicking, but it isn't -- the patent is on using one hardware button on a handheld to perform three distinct actions using three distinct input methods, not on any of the three methods. Want to avoid the patent? Make sure YOUR handheld device only uses two of the three methods. Of course, this doesn't make for quite so sensational an article as "OMG M$ Patentz dbl click," which is probably why you don't know about it. Or, like Mr. Levy, do you prefer spreading colorful and entertaining fictions so long as the outline is correct?

    --
    Hey freaks: now you're ju
  10. Re:Another one for the EFF to bust. by rusty0101 · · Score: 4, Informative

    To my certain knowledge, BeOS had 'task grouping' in version 4 which I beleive predates April 1999. Since I did not use BeOS before version 4, I do not know when it was introduced as a BeOS feature.

    Then again, I could be wrong.

    -Rusty

    --
    You never know...
  11. Re:Another one for the EFF to bust. by DCMonkey · · Score: 4, Informative
    According to this, they added it around May 2001.

    Sorry.

    --
    DCMonkey
  12. Re:This isn't obvious by Macadamizer · · Score: 5, Informative

    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
  13. Re:KDE... by tackat · · Score: 5, Informative

    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 ;-)