I have seen the future…

…and it still kinda creeps me out. I’m referring specifically to the Adobe-Macromedia merger. While both companies have a history of making excellent products, Adobe seems to have lost its way the last few years, and I’m worried it will drag the Macromedia product line down with it. I’m especially dismayed about the future of competing products: Freehand versus Illustrator, Fireworks versus ImageReady, Dreamweaver versus GoLive, Flash versus LiveMotion, FlashPaper versus Acrobat. Adobe’s programs (with a few exceptions) have become massive bloatware… try installing CreativeSuite 2 sometime — it takes up over 2GB of hard drive space!

Will Adobe force its interface standards onto Macromedia products? Personally, I prefer Macromedia’s “docked” interface style to Adobe’s tab system… it’s easier to manage and more efficient for my workflow. Will Adobe force the PDF format into all of the programs? (The answer is yes… they’re even planning on integrating PDFs with Breeze.)

So what’s my point? I’m concerned — like MANY others — about the future of both Adobe and Macromedia product lines because of how it will affect the work I do. Which brings me to a Bruce Chizen (Adobe head honcho) interview I just read. While he doesn’t address some of my concerns, he does give a pretty thorough overview of Adobe’s plans for the near future. This will potentially affect anyone who uses Office-style software, online services, and mobile devices, so I thought I’d post a link for you to read. Enjoy! 🙂

http://knowledge.wharton.upenn.edu/index.cfm?fa=viewArticle&id=1399

– philip

The Fonthead

My brother recently sent me a link to a webpage with free font downloads. This tickled my on-again off-again love affair with typography, and triggered me to post a quickie blog about the subject. The more intricate details of typography (kerning, leading, metrics and the like) seem as obscure as ever to the everday computer user these days. Most people — quite understandably — only know what MS Word requires them to know. Then there are people like me who know a bit about the subject but still get too lazy to follow all the etiquette, such as using em and en dashes appropriately (see the previous sentence for an example) or using ligatures in printed documents.

What’s the difference between a font and a typeface? No, they aren’t the same thing (at least they didn’t used to be). What about the difference between Times Roman and Times New Roman? And why is using Times Roman (either iteration) NOT a good idea for webpages and other on-screen purposes? (Short answer: it’s a serif font designed for newspapers — specifically the London Times in the mid-1800s — and therefore has a smaller x-height than fonts designed for on-screen use, such as Verdana.)

Anyway, being a geek about this sort of thing, I figured I’d present you with links to some typography sites I’ve been browsing recently. They contain excellent primers on typography, its uses and some typograhical history. Enjoy!

Now if I could only remember how to do that pesky em dash…

I hate to say it…

But I found another Microsoft product helpful today.

It pains me to say it, but it’s true.

I have created an XML template for an online course delivery system I’m building at my workplace. The course data for each course needs to be placed into a copy of this XML template. The problem is that I don’t want to work directly in XML all day, and my coworkers can’t be expected to write course content directly in XML format. I needed to devise an easy-to-use method for inputting data to an XML document (filling in the blanks).

My initial research into the subject found some ‘export-to-XML’ methods that use Excel and/or Word, but they are prone to formatting errors and require extensive workarounds such as oodles of conditional formatting. Didn’t sound very fun. Not to mention the custom XML schema I’d have to write to enable the Excel/Word file to be properly transformed to my custom XML. Other methods involved databases and content management systems, which I wanted to avoid for simplicity’s sake.

Enter: InfoPath. A “how’d I get that?” program that came with our Office 2003 update a few months ago. I had never heard of it until I saw it while randomly browsing my computer’s Program Files shortcuts.

Turns out it’s a program for designing forms that are connected to a data source such as an Access database or… you guessed it… an XML document. And what I truly found surprising is that you don’t need an XML schema, just a sample XML document that follows the format you want your future XML docs to be in. A copycat, so-to-speak. InfoPath will automatically infer the schema from your sample XML! Note: you should probably go in and check the schema details, such as using a “date” data type rather than “integer”.

InfoPath was very easy to use. I created a new blank form, then selected my sample XML file as the data source; InfoPath made the XML tags available as drag-and-drop items, kind of like Flash components. I quickly arranged the items how I wanted them (including using “repeating regions”), and voila!, I had a fully functional form in one afternoon. The data entered into the form is exported to a fresh XML file — based on and validated against my custom XML — whenever I hit “save.”

Of course, that’s a very simplified explanation of how InfoPath works and what it does… I’m still a newbie with the program. However, I can say it greatly simplified the work I needed to do (no crazy workarounds using multiple programs), gave me a form I can share with my coworkers (although you need InfoPath to use the form), and produced valid XML that I can import into other programs as needed, all in one afternoon.

I should note there are other programs that perform similar functions, including Adobe Designer (companion to Acrobat Professional). I will have to investigate the alternatives — I hate being beholden to Microsoft — but so far InfoPath is leading the pack.

http://office.microsoft.com/en-us/FX010857921033.aspx [link no longer available]

Daily newness: An online XML-to-XSD Converter

OK, most of you probably don’t know the difference between an XML file and an XSD (“XML Schema”) file. For a brief intro check out W3Schools’ XML Schema tutorial. A brief quote: “The purpose of an XML Schema is to define the legal building blocks of an XML document, just like a DTD.”

This week I needed to create an XML Schema doc for work. The XSD file would be used to validate XML files I’ll be making for my online courses. Well, being a newbie to XSD files (though not XML), I was making decent but very slow progress when a thought occurred to me: it should be possible to reverse-engineer an XML file to create an XSD file. And, considering how prevalent XML is these days, someone probably posted an online converter for it! Google to the rescue!

I found a number of tools (mostly software downloads such as XMLSpy), but the easiest one I’ve tried so far is by — gulp — the Evil Empire itself: Microsoft.

http://apps.gotdotnet.com/xmltools/xsdinference/ [link no longer available]

All I can say is whether you love ’em or hate ’em, their tool works great and is completely free. On my first try it pointed out some invalid XML I had written. After correcting my mistake, BAM!, I had a complete XSD file. It wasn’t perfect and needed some tweaking (optional versus required tags, string v. integer, etc.), but it eliminated most of the heavy lifting for me and I’ll be finished a heck of a lot sooner than I would have been without it.

Umm… thanks, Microsoft! (For once…)

Today’s bit o’ knowledge: Firefox Web Developer Extension

today i learned about chris pederick’s ultra-handy Web Developer Extension for Firefox. yeah yeah yeah, i know it’s been around for a while, but i never TRIED it until today. i wish i had tried it sooner!

among its many features is the ability to toggle outlines on and off (looking at other sites’ block-level CSS is fun in a voyeuristic way), as well as the ability to disable a site’s CSS, images, javascript, cookies and more! it makes it really easy to examine the nuts-and-bolts of a web page’s structure/design without doing a save-as and opening in an editor like dreamweaver. me likey mucho.

http://chrispederick.com/work/webdeveloper/