[asparker]

Anyone have any information on how exactly one would go about making a dockling? I can't find any info on Apple's site. Is it just an application with an extension of .dock instead of .app or something?

Thanks,
- Tony

[Since EBCDIC]

You might want to drop a line to the creators of VolumeDockling (at versiontracker).

I don't know a direct pointer to a sample dockling, sorry.

[Xeri]

Has anyone found any documentation at all about Docklings? I'm interested in the idea but I haven't been able to find anything among the X docs on the disc or on Apple's developer page.

[bewebste]

Currently, the API for creating docklings is private, which means that it can change at any time and any software written using the API will break in the next release. I know for a fact that Apple is planning to extend the API in the future, which means that all the current docklings out there will break when MacOS X is updated.

A couple of developers have reverse engineered the API and created docklings, like the people at On-Core who made their audio CD and volume docklings. I did the same thing, but what I've done is to wrap up the API in a Cocoa wrapper. A tutorial on using this wrapper should be appearing shortly on Stepwise. This way, a whole bunch of people can write docklings, but without directly using the private API, so that when the API is updated, I can just update the wrapper and everyone can recompile their docklings with few or no code changes. That way, every can write and use docklings now, and they will still break, but they'll be much easier to update.

[bewebste]

Currently, the API for creating docklings is private, which means that it can change at any time and any software written using the API will break in the next release. I know for a fact that Apple is planning to extend the API in the future, which means that all the current docklings out there will break when MacOS X is updated.

A couple of developers have reverse engineered the API and created docklings, like the people at On-Core who made their audio CD and volume docklings. I did the same thing, but what I've done is to wrap up the API in a Cocoa wrapper. A tutorial on using this wrapper should be appearing shortly on Stepwise. This way, a whole bunch of people can write docklings, but without directly using the private API, so that when the API is updated, I can just update the wrapper and everyone can recompile their docklings with few or no code changes. That way, every can write and use docklings now, and they will still break, but they'll be much easier to update.