Lion points: easy connection to Enterprise WEP

I won't be upgrading my 10.6 machines to Lion (10.7) until sometime in the spring or summer of 2012 - at the earliest. When it comes to Apple's OS updates, I've never regretted joining the 3rd wave of adoption.

Still, Lion does some things well - like killing Intuit's Quicken and opening up the market for better alternatives. Mission Control  and Full Screen are a big part of why the MacBook Air 11" is the world's best personal computer. Some of the best features, though, don't get much publicity.

Take, for example, Enterprise WEP. I don't know the full details of how this works, but I think it's some kludge that runs a VPN like connection through insecure WEP authentication. It's a bear to configure with XP, and I'm not sure Windows 7 is much better.

I didn't think my MacBook would connect to it. Sure enough, my manual configuration efforts all failed. Then, as a lark, I tried the "automatic configuration".

Poof. It connected. Works great.

You're not all bad Lion, even if you are a memory hog.

Tables for Blogger: newly buggy Google Spreadsheet embedding

One of my frustrations with MarsEdit is the lack of table support. (Another is the weak management of images. Windows Live Writer has the reference design for both.)

Blogger's newish editor is no better. No table support. Tables are a bit of a lost art [2]; recently I had to summon the ghost of Netscape Composer (SeaMonkey) to add tables to a blogger post. [Update: I think AppleWorks used to 'save as HTML'. Pages doesn't. However, I discovered, Apple's bundled TextEdit.app for does tables (fixed widths only, 10.6 and 10.7) and exports as pretty clean HTML.]

This morning, apropos of nothing, it occurred to me there might be an alternative. Google Spreadsheet does tables (including, now, both vertical and horizontal cell merge) ... I found a reference (warning - the reference is obsolete)

Publishing Google Spreadsheet to Blogger - Google Docs Help

Go to the top of right of the spreadsheet view. Press the 'Share' button. Then, click "publish as a webpage". Then, click "publish this document". At this point, it is published. If you want to embed it, click "more publishing options at the top of the mock pop-up. Then, choose 'html for embedding'. Finally, generate the embedding code."

The reference, of course, is obsolete and so is Google's online documentation. I call this the Facebooking of tech -- there is no more documentation.

Here is how it works with the new editor.

1. Click on the Google Spreadsheet "Collaborate" menu item.
2. Choose "Publish as web page"
3. Click "automatically republish" and enable publishing (top half of dialog as of today).
4. Then, from bottom half of same dialog, where it says "get a link" click on the "web page" drop down and choose "HTML to embed in a page" from the intriguing list of options [4]

It publishes as an iFrame [3]. It's only partly implemented -- the obvious Named Range drop down was empty even though I created a Named Range. I tried the undocumented range specification as below ...

But although that worked when I viewed the shared web page I still got the entire spreadsheet when I tried their generated embed code. So there's a bug in there somewhere.

------

Yech. Since this functionality is clearly not finished in the new editor, I hope they'll get this one together sometime soon. I suspect it worked better in the old spreadsheet editor.

BTW, this is what the generated HTML sort of renders as. The markup is CSS infested and hence unreadable. In the old days FrontPage would have generated easy to follow table markup.

.	cell A1	B1 + C1

.	cell A2 and A3	B2	C2
.			B3	C3
.	A4

 

 

-----

[1] It sucks that they use div tags instead of p tags to mark paragraphs.
[2] The web made a bad decision when we started using CSS rather than table embedding for dynamic layout.
[3] Incidentally, how I embed iframes for Google feed lists into an old web page.
[4] Interesting list of web publishing options!

 

My G+ Profile - open to connect

My blogs are pseudonymous, but it's not hard to find my true name if you click around a bit. I just prefer that my corporate colleagues and customers don't suffer the full range of my opinions and speculations.

Which means, since G+ is open, I'm good with sharing and corresponding there. I typically share with my "extended circle" (circles and one removed) -- just a bit short of public. I use LinkedIn for purely corporate and teaching connections, Facebook is where I tell kid stories, so G+ is the intellectual slot. It's a good match to the blogs.

If you're interested, here's my profile [1] and my "John Gordon" circle.

[1] Note the URL has the number of this beast: 113810027503326386174. Just call me 113.

(cross posted to notes and tech.)

Google Reader may yet live: signs of buzz/G+ integration

Today Google added G+ search to their newly opened Google Plus services.

First thing I did was search on "Google Reader" for signs of life in one of my favorite Google products. I'd recently put it on my death list due to long dangling half-finished work that encrusts Reader.

I found several optimistic signs, including this post:  Tracy L. Crawford - Google+ - Google Reader Shares have a G+ link!.

In my case it's that the "options" drop down in posts shared by people I follow says "View this shared item in Google Buzz". If I try that it actually shows in G+.

Seems like some Buzz/Reader integration is underway. What you see may depend on whether you have Buzz enabled or not.

Keynote.app for OS X (iWork)

I've made a stepwise transition to Apple's iWork suite for OS X. Apple's App Store made it easy; module prices are low and I could evaluate each iWork app separately. The license allows me to install on any number of 10.6+ machines on my account. Keynote.app, for example, cost $6/machine.

I started with Numbers.app nine months ago. My needs are not great, but so far I've been pleased. Of all the apps it comes closes to its Office counterpart. Since Excel has always been Microsoft's great software achievement this is strong praise. The main competitor to Numbers.app, however, is not Microsoft. It's Google's Spreadsheet. With offline support for Google Spreadsheet Mac users have two good alternatives to Office. I'm not sure which I'll go with.

This week I switched from Nisus Writer Pro to Pages. That's a surprisingly big jump. I'd forgotten that Pages is more of an desktop publishing app than a word processor. I'm not sure how well it will work for the family. I'll post more on Pages over time.

This post though, is about Keynote.app. I'll update it in bullet form as I use it to present a lecture this week. Below are my initial impressions.

• There's a lot of UI continuity and functional continuity with PowerPoint. My initial impression is that the base functionality is a simplified subset of PowerPoint.
• On my machines performance is much better than Office 2008 PPT (the latter was unusable). I suspect PPT's code base is a mess on any platform.
• Importing a relatively simple PPT took a fair bit of cleanup. Slide component alignment varied. Diagram overlays scattered.
• Exporting to PPT worked much better than import (mercifully).
• Applying themes to single slides or presentations is much better than PPT (big plus).
• Bug: I was unable to italicize text on an imported PPT. Seems Keynote assigned the text an exotic font that lacked italics or bold. It's a bug because the UI implied I could italicize, there's no error when you try, and the substitution is odd. The fix was to 'View Masters', consolidate masters, and change the Master Slide font.
• Themes made a mess of an imported PPT. I'm disappointed in the Themes -- they're often tacky. Almost Microsoft tacky.
• Consolidating Master is well done. View Masters, if you delete one you're asked to choose another to apply. Really helped clean up an ugly PPT file.
• The default fonts in text boxes for my imported PPT had an odd font. I had to use the Format>Advanced>Define Text for All Masters to fix it.
• Bug: Unpredictably, when creating a new row, I get a very odd bullet point. It looks like a Satanic glyph.
• Bug: Keynote/Lion can run into issues with window positioning and external displays. There are also weird behaviors with save/versioning. These look like a mixture of Lion and Keynote bugs.
• The default font for presenter notes is ridiculously small. There's no UI way to change it but you can hack the theme. If you make the font large, however, you can't read it in the fixed and narrow speakers notes display -- and long notes are mess when printing handouts. I hope this is fixed in the next release; it needs real work.

Update 10/20: Exporting as PPT -> "An unknown error occurred". Right. Not the only keynote bug, but certainly a bad one. Apple doesn't do very many industrial quality apps, and this isn't one of them (yet).

Resolving ghost printers in Win7 - delete redundant print queue

My corporate Win 7.64 box had a printing problem. Everything looked fine, but jobs sent to some printers didn't appear.

I was also seeing "ghost" printers -- they displayed in Windows print dialogs, but they didn't show in Control Panel "Devices and Printers".

For example, from the print dialog I saw "biz-c1" and "biz-c1 (copy 1)", but from the control panel I saw only "biz-c1 (copy 1)".

I think this glitch came from running an XP or 32 bit Win 7 printer installer on a 64 bit machine.

The printers that had this problem had an extra context menu entry "delete print queue". After a I deleted the "older" (non-copy 1) queues this context menu item disappeared! (Google was no help, this was my closest hit.).

The transient "delete print queue" menu item worked to fix the print dialogs. They again show a single queue. Even better, my printing was restored.

I assume this is a bug in Windows 7 that Microsoft knows about. There has to be a reason that the "delete print queue" option appeared on printers that had a redundant print queue. It's odd that it's not better documented however.

Facebook Pages: Only Administrator status updates go to fans

There are many books and web pages that try to explain how Facebook works.

Alas, even the most topical material gets most things wrong -- confusing messages with stream updates for example. It doesn't help that the rules change constantly [2]. Even Facebooks own, very limited, documentation is often dated. For example ...

Facebook Pages: How to manage a Facebook Page - Facebook Help Center:

... Your Page [1] can now post status messages - short text-only messages like those found on user profiles. Soon, these statuses will appear in fans’ News Feeds...

I don't know when this was last revised, but Page updates have been appearing in my News Feeds for months.

Ultimately, the only documentation on Facebook is Facebook. It's mind-boggling that this works for them. Suggests most of humanity has given up on understanding how the modern world works; which means that modern services need not be understandable.

If you want to know how something works, you have to experiment.

So I did this experiment on one of the Pages I administer. These Pages are "Liked" in my Profile.

I posted from two non-admin accounts (Emily and mine) and 1 admin account. I found.

1. When a Person posts an update on a publicly accessible Page it is public and viewable to anyone on the net, regardless of one's FB privacy settings. This is obvious in retrospect, but I suspect most people don't know this.
2. When a Page posts an update it goes to all subscribers.
3. When someone you "Friend" posts an update on a Page you subscribe to you will receive a Wall (stream) update notice.

What I couldn't test is what happens when someone who is not a "Friend" of mine posts an update to Page I "Like". I suspect, in this case, I will not receive any Wall update.

So for the Pages I administer, if I want a status update to be received by all "Fans", I need to post it "as the Page" rather than using my personal account.

john

[1] In Facebook lingo a "Page" is something belong to an organization or celebrity or business. Individuals have "Walls". "Pages" have "Fans", regular people have "Friends".
[2] For example -- until today Facebook sharing has been symmetrical. If I "Like" someone they are notified of my shares and I'm notified of their shares. We have mutual access. Ok, I'm simplifying, the notification rules are constantly changing.