Screen Shot Format

Apple’s Cocoa Development mailing list archives contain an interesting snippet that explains how to change the default screenshot (command-shift-3 and -4) format from TIFF to JPEG, PICT or PNG. The original article can be seen here (read the dialog box for the username and password), but it’s basically a one-line terminal command:
defaults write NSGlobalDomain AppleScreenShotFormat imageFormat

Replace imageFormat with one of JPEG, TIFF, PNG, or PICT to change the format of the screenshot

Disable Specific Software Updates

found on Mac OS X Hints…

In the midst of playing around with the newly discovered Software Update log file (see the recent hint), I also found out how to remove those annoying notices that pop-up when you try to quit Software Update without installing all the updates. In my case, it’s the AirPort update on my desktop G4. It shows up every time, and when I quit the updater application, I get a warning dialog about “are you sure you want to do this even though you haven’t installed this update?”

Like a few others published this week, this tip is probably blatantly obvious to many people, but I’d never previously looked at the menubar in Software Update. If I had, I would have seen the Update -> Make Inactive option. If you simply highlight the package you’d like to ignore and then select this menu item, you’ll get a dialog box warning you that you won’t be able to update this package while its inactive. Click on Make Inactive and that’s the end of the warnings when you quit Software Update.

If you ever wish to update the inactive package, select Update -> Show Inactive Updates and then reactivate the package(s) you are wish to update.

Again, my apologies if this was obvious to everyone but me, but I had no idea you could ignore updates!


Replacing the Manila site with a Movable Type site…doing it all by hand.



By Bob Lewis

Posted February 07, 2003 12:00 Pacific Time

“Imagination is the only weapon in the war against reality.” — Jules de Gautier

Gartner has achieved fame and fortune through the publicity it generates from regular publication of outrageous “TCO (total cost of ownership)” calculations. It’s time for Gartner to share the fame if not the fortune.

SCHEV – An Example Information Source

SCHEV – An Example Information Source

The State Council of Higher Education for Virginia (SCHEV) is the Commonwealth’s coordinating body for higher education. SCHEV was established by the Governor and General Assembly in 1956. Then as now, our mission, which is outlined in the Code of Virginia, is “to promote the development of an educationally and economically sound, vigorous, progressive, and coordinated system of higher education” in Virginia.

Future Information Environment

From John Wilson –

This could be a chance to put the “I” in CIO in a meaningful way. To do so, we need to address real Information issues, not just technology and transaction systems issues. These might include, in increasing order of complexity and scope:

Addressing the real overlaps on information providing among DAPS, UIS, PSOS, HR, FRS, etc. (essentially an expansion of the Sander memo idea to where there is duplication and confusion as distinguished from ignorance).

Addressing the real information needs of the management of the institution and what to do about them. DAPS began a series of interviews with deans and other administrators but it kind of got side-tracked by events.

Addressing the lack of a university sense of what is required to have an effective information environment for management, process improvement (e.g., determining the key factors in student success by discipline), etc.

Continue reading “Future Information Environment”

XML — Where Do We Go From Here?

XML — Where Do We Go From Here?

Jon Bosak – What XML cannot do is to magically solve the problem of data interoperability. XML just provides a framework within which interested groups can work out agreements about the vocabularies and data structures to be used in a given domain. The widespread adoption of XML has created a wonderful infrastructure of standardized tools and products to support the creation and implementation of such agreements, but deep down, the job of semantic definition requires the same grinding committee work that standards groups have been engaged in for more than a century.

Given that as a caveat, analysts, marketeers, and engineers talk about XML after 5 years.

Transforming IT

Transforming IT

An article I found thought-provoking.

A start to a discussion about transforming how we provide Information to the community.

There are many parts of this article that I find uncomfortable (anything that spends more time measurning results than creating products).

There are a number of points that I find interesting and thought provoking. If we change a word here or there we get some starting points for a UDAP initiative.

Read…Comment…Think out loud…I am

If you don’t like the format try this printer-ready version of the article.

I particularly like the words “transforming while performing” – it describes the way I feel about what I do.
Continue reading “Transforming IT”


tell application "Terminal"
 do script with command "top -u -s10 10"
 set number of rows of window 1 to 18
 set number of columns of window 1 to 80
 set background color of window 1 to "black"
 set normal text color of window 1 to "yellow"
 set custom title of window 1 to "Top"
 set miniaturized of window 1 to true
end tell