Slashdot Mirror


Dockapps Arrive at the OS X Dock

An anonymous reader writes "Many of us have fallen in love with the convenience of dockapps through fvwm2, Windowmaker and Afterstep. Now, it looks like dockapps are finally coming to OS X at last. It's not Dashboard, but it is very cool."

10 of 27 comments (clear)

  1. So what? by Redshift · · Score: 4, Interesting

    Activity Monitor has been working in my dock for years, showing me my bandwidth utilisation. What's new about this?

    Looks like a shameless plug from the site author for his GPL library.

    1. Re:So what? by amonredotorg · · Score: 5, Informative

      Agreed. In fact, Dockapps (usually called Docklings) are being deprecated in newer versions of Mac OS X. There were quite a few Docklings in 10.0 and 10.1 (including SlashDock), but there's very, very few Docklings left for 10.2 and later.

      This article at CocoaDev has a tutorial on making Docklings. Really easy.

      Dockapps aren't exactly the same as Docklings though, it seems... they have animated icons. Doing that is very easy as well, you just call NSApplication's -setApplicationIconImage: method every second or so. I don't need a framework for that.

  2. Re:System-Friendly? by Chucker23N · · Score: 4, Informative

    "...and Dashboard's widgets only update when you pull them into view, which is sort of lame and not at all keeping with the 'dash' idea."

    Not true.

    Widgets /can/ enter sleep mode when the Dashboard hides (onHide{sleep;}) and then later refresh once Dashboard comes back, but they don't need to. The normal case is that a widget continuusly gets updated, whether the Dashboard is visible or not.

    Furthermore, there's a somewhat hidden feature to show a particular Dashboard widget while the rest of the Dashboard is invisible, i.e. make the widget sticky.

  3. Re:System-Friendly? by trendyhendy · · Score: 5, Informative

    Instructions for having a widget always visible are at Mac OS X Hints

  4. GNDN by Anonymous Coward · · Score: 4, Informative

    Dockapps/docklings haven't "arrived" -- they've been here all along. This framework just makes certain kinds slightly easier. Namely network monitors/graphs -- you know, like the Activity Monitor that comes with the OS -- the one that does exactly the same thing as the one existing app that uses this framework.

    Oh, and by the way, it's GPL, so you can forget about using it in your real projects. Why not LGPL? Why not BSD? Because that might be useful!

    Anybody else get the feeling that the "anonymous reader" happens to be the guy that wrote the framework? It's totally "post your homework" season, isn't it?

  5. Re:veiled licencing bitching by Chucker23N · · Score: 2, Insightful

    Indeed. GPL'd libraries are useless to the realistic-thinking world.

  6. I Don't Use The Dock by Goo.cc · · Score: 2, Interesting

    Personally, I find the Dock to be a waste of screen real estate. I keep it at its smallest size, empty and hidden; I prefer to usee Quicksilver to launch applications.

  7. For future reference by Lally+Singh · · Score: 4, Funny

    If you're coming in from fvwm2 and get on a mac, for the love of God, don't try to make the mac more like fvwm2.

    --
    Care about electronic freedom? Consider donating to the EFF!
  8. Why? by Bastian · · Score: 2, Insightful

    I would suggest that, while there are certain times when a dockapp is a great idea in OS X (the little red dot that shows how much new mail you have in Mail.app, for instance), and certain times when it's not perfect, but it is the only thing that will really do in some cases (Activity Monitor), for the most part dockapps have no place in OS X.

    In the various X11 windowmanagers that have them, they work well because they afford you a great deal of control over where the dockapp can be placed onscreen, and because they provide that degree of freedom with everything else, too.

    OS X, on the other hand, gives you a menubar that is already firmly attatched to the top of the screen which already contains a clock, battery monitor, and various other useful indicators and controls. The menubar alone simultaneously makes 3/8 of the good places for random dockapps (corners and sides) off-limits, and severely reduces their usefulness by providing most of the most popular dockapp functionality in a much more compact form.
    It also gives you an incredibly cramped and inflexible dock. All the user gets to control is how large its icons are, whether it is on the left, right, or bottom edge of the screen, and partial control of icons within the dock. The dock then decides where the icon's physical location on the screen is, makes adjustments to the ordering of apps by throwing new apps you run in the bottom of the first compartment (i.e., the middle), and resizes the dock as needed. And there is only one dock - no dock and clip like in WM, no whatevertheheckyouwant like in fvwm2. OS X just doesn't really leave much room for the dockapp author and its user to implement and place the dockapp's interface in such a way that it serves to be both useful and something more than ugly clutter.

    While I realize there are major differences between dockapps and the "desktop widgets" model of random useful crap, I gotta say that in general it's a much better idea to buy a copy of Konfabulator or Tiger and make use of that system. Enjoy the way it allows you to put more information up there, and get used to the way it only shows that information when you want it to. (I haven't used either much, but it could be that they allow you to design widgets that "pop up" on the screen briefly when they need to tell you something right away. . . I have used other OS X apps that will do that.) In the end, the desktop widgets model just meshes much better with Aqua.

  9. Not compatible with Tiger! by cypherz · · Score: 3, Informative

    It seems like it isn't compatible with Tiger. Installed but no-workee.

    --
    This sig kills fascists.