Slashdot Mirror

← Back to Stories (view on slashdot.org)

'Type Manager' The File Manager of Tomorrow?

Posted by CmdrTaco on from the no-not-for-fonts-silly dept.

IceFox writes "In the past few years many of us have been introduced to a new type of application, the Type Manager. Most of us are familiar with iTunes, but there are many other Type Managers out there that are gaining market share and a rabid fan base of users such as digiKam and amaroK. Type Managers seem to have that magic combinations of features that makes users love them. I have been taken a closer look at the Type Manager, what makes them so usefull, what they really provide for the user and came to some surprising results. After creating a list of all the traits of a Type Manager I was able to define exactly what a file manager should be and discovered that there are in fact many partial Type Managers out there now that implemented only half of what makes up a full Type Manager."

5 of 321 comments (clear)

  1. Type Manager? What? by Agermain · · Score: 5, Funny

    I hope I'm not the only one that had to wonder what iTunes and amaroK had to do with Adobe Type Manager and Suitcase.

  2. 'Type Manager'? Worst. Buzzword. Ever. by hoggoth · · Score: 5, Funny

    Could he come up with a more generic and confusion-prone buzzword than 'Type Manager'?!

    --
    - For the complete works of Shakespeare: cat /dev/random (may take some time)
  3. Re:Type Manager? What? by BushCheney08 · · Score: 5, Funny

    The best (and only) way to deal with a mime is with a gun.

    --
    Be a real patriot: Question authority. Think for yourself. Formulate your own conclusions.
  4. Creating type managers by Hal_Porter · · Score: 5, Funny

    What's needed is a class library which speeds the creation of Type Managers. It should have a Document base class which applications could extend to contain document info, and a View base class which would abstract the user interface. Both would have base methods for all the common stuff, and you'd extend them with the specifics of what you're trying to do. There'd be Views derived classes based on common widgets, like dialogs and lists.

    Additionally, there'd be a way for software components to register as viewers of file types in some global database, so that they could integrate with the default shell and display previews. They should also be able to open the type manager or print, perhaps integrating into shell's context menus.

    Yup, welcome to Windows 95 with a bunch of MFC applications, COM components and the registry.

    --
    echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
  5. Re:The missing question by nutrock69 · · Score: 5, Funny

    You don't even need to use a real gun.