Joe Wilcox, over at the Microsoft Monitor blog in the post Microsoft Monitor: What is Life Changing?, makes the following observation (bold mine):
Microsoft has a history of releasing products that sometimes are hard to categorize or to explain. Outlook combined e-mail, calendaring, contacts and forms, something totally new in 1996. And the approach made Outlook difficult to describe. How about InfoPath? People still don't really understand what it is. There's a presumption that somehow InfoPath is a forms product. Well, yes, but absolutely no.
Looks like we've got some work to do.
Hey, guess what's new with Wired 14.03: Wired Magazine Issue 14.03?
Well, you're not going to be able to tell online. What's new is that there's a lot less to Wired magazine now, physically. And I'm not talking about a lack of bloat from all of the Web 2.0 companies advertising.
No... it's smaller this way: (from the end of rants + raves): "The magazine you're holding is a smidge smaller than previous issues - we took an inch off the side, to be exact."
Wha!?! Sometimes an inch is a smidge, and sometimes it's not. Sigh. First they kick-out their patron saint and his monthly quotes, lose the whacky styling, and now they get smaller.
I've been reading Wired since the very first issue. I guess I don't deal with change well.
Thank goodness for Firefox. Once Firefox / Mozilla decided that the XMLHttpRequest object was a good idea (thank you, AlexHop) a new level of buzzy innovation got kicked off.
On my to-do list:
I recently purchased a Dell Axim 51v running Windows Mobile 5.0.
It hasn't exactly been a breathless love affair.
I am disappointed at a number of issues still present by default in the PocketPC OS. I had one of the very first Jornada's. Then a later Jornada. Then I stopped buying from HP after they ditched the Jornada and decided only iPaqs would be upgradeable to the next OS.
I think I'll need to try out Magic Button from http://www.trancreative.com/mb.aspx to deal with one thing that continues to burn my bisquits: most default WM apps don't provide you with a "Quit" option. I don't want to keep all those programs running, hogging up resources. I want them to close. So Dell ships the earnest but buggy task-switcher. It sometimes stops working and it's on my suspect list of causing some recent problems requiring a soft-reboot (man, I reboot this thing way too much).
So I'll try the little magic button as a way to help those lingering apps exit and move on, but I really wish I didn't need it in the first place.
A review of the O'Reilly hacks books from The Financial Express: It's time to hone your hacking skills, legally
As much as I'd like to, I'm not buying the O'Reilly hacks books.
I recently looked through two of the hack titles: Mapping Hacks and Google Maps Hacks (I'm interested in learning more about mapping technology so that I can write a GPS app for my Windows Mobile device).
To be in a neutral territory, most of the hack titles that involve code have decided to work mostly with Linux-based software, some of which might work for Windows (e.g., some perl scripts might just run).
Or sometimes they use Java.
And of course, this is completely within O'Reilly's right to decide on what technology to use as the foundation of their titles. I first used O'Reilly titles when I was an X11 Windows System widget-based GUI guy. Loved them books.
But now the cash in my pocket stays where it is more often then not when I'm flipping through the latest O'Reilly book. I can't use it and life is getting so incredibly complex that I no longer engage in the joy of porting code from one platform to work on another. I think that O'Reilly is missing out.
And as soon as another publisher brings out quality work that I can use in my world of Windows and IE, the cash is going to spring right out of my pocket and into their pocket.
Are you ready for a deep sneak peak at InfoPath 2007's new level of integration with Outlook? Here you go: InfoPath 12 - Tudor Toma : Using InfoPath e-mail forms
The current version of InfoPath allows you to send your form via email. What you get is an HTML version of the form and the XML as an attachment. You can then open that attachment up in InfoPath and go from there.
That's a fine experience, but it's sort of a disconnected. Good, but with lots of room to grow.
Thanks to a lot of good thinking, we've integrated InfoPath forms into Outlook to where it's a first class Outlook item. When you receive an InfoPath email form and open it, it opens directly in InfoPath. Any changes you make can be saved back to the original item.
And the biggest, greatest, get-ready-to-pick-up-your-socks-coz-I'm-about-to-knock-them-clear-off feature is InfoPath folders: you can create an InfoPath folder associated with a particular form, set-up a rule to route forms of that type into the folder, and then promote columns out of the XML forms into your Outlook folder view.
Have you tried InfoPath on SharePoint? You can promote properties (fields) out of your form design into column on SharePoint to get a quick view into the data (or to sort columns or such based on the data).
That same promotion information is now used by Outlook to promote values from each form into an Outlook column. Once promoted, too, you can unleash the power of Outlook to do further manipulation.
It's like having your very own SharePoint folder inside of Outlook to do with as you like... online, offline, whatever.
Plus we've made it easy to fill-out InfoPath forms while you're inside of Outlook by writing a smaller version of the InfoPath "fill-out-a-form" dashboard inside of Outlook.
One last thing to call out: analysis. You can select a bunch of InfoPath forms, either as regular items or items in an InfoPath folder, and export them to Excel. You can also take that selection and merge the forms together into a single InfoPath file.
Oh, and one last last thing to call out, too: Access uses InfoPath email forms as one of its data collection features. The items go out as an InfoPath email form and then are collected using Access' special add-in to roll all your responses together.
InfoPath technology is spreading through more and more of the core Office applications. Now is the best time to start coming up to speed on how to design, distribute, and use InfoPath forms so that you're ready to leverage Office 2007 to the fullest when it's released.
But remember, I'm biased.
Rule #4 here is the most challenging (9 tips for running more productive meetings 43 Folders) at Microsoft:
4. No electronic grazing. Period. - Laptops closed. Phones off. Blackberries left back in the cube. Youâ€™re either at the meeting or youâ€™re not at the meeting, and few things are more distracting or disruptive than the guy who has to check his damned email every five minutes.
I feel bad for some folks up in-front of an important audience and ready to do a big presentation or demo and all of the audience is staring at their screens.
This usually leads to the "huh-wha?" moment when something important enough is said to get a person's attention and now they are busy coming back up to speed on everything that's been said.
You can't do email and pay attention at the same time. I'd be damn happy for it to start being a requirement that the laptops are closed when the meeting begins, or at least folded downwards for easy access should you need to look up something relevant to what the room is discussing.
The link you can download the rocking video from: Download details: Expense Reports Made Easy with Microsoft Office Solutions
As a member of the InfoPath team, I certainly use InfoPath all the time to make little dogfoody examples of InfoPath forms (and, you know, quickly edit OPML and such).
Occasionally, I have the opportunity to behold InfoPath form solutions that just plain amaze me. Sometimes it's because the form designer put in that last little straw that caused the bulkheads to collapse and we need to fix a problem, othertimes it's because people have basically replaced the need to write a complex client or web application with an InfoPath form template.
Check out MSExpense to see one of the more complicated InfoPath form templates. If you're filling out your travel expenses and such, you now use InfoPath. And you can do it offline once you have opened the form at least once and have a cached version on your machine.
Eli Robillard asks Where did forms go in Word 12? and I want to paste in my comment to his post regarding additional InfoPath form technology integrated into Word 2007:
Hi - Eric Richards from the InfoPath dev team here. I'm not answering your question off hand - there's lots of UI that's been moved around. Be sure that you have your "Developer" tab turned on first for the options of the application where you're trying to do something whizzy. More complicated UI has been turned off by default.
And as for forms and InfoPath - note that there's a new feature called... oh, what's the official name, Document Information Panel? When you view the properties for a document, you're seeing an embedded, autogenerated InfoPath form.
This gets more interesting when you go and open the Office 2007 document from SharePoint. You can see the SharePoint properties in this InfoPath form, too.
Now the fun part: you can customize this form to add rules, calculations, validation, etc, etc (or just make it look snazzy).
For the new Office format, we also provide a feature where you can add a customized InfoPath form into the document (running against XML content in the docx file).
One cool thing for advanced Word devs out there: both Word and InfoPath can run against the same XML in the docx at the same time, meaning that you can easily drop SharePoint properties into your Word doc and see both InfoPath and Word handling changes in either place. So, you can have structured information with all sorts of easy to write declarative validation and calculations in the InfoPath form and just drop it into Word and have everything continue working.
This way, you can focus on your structured, validated data in the InfoPath portion of your document and the more free flowing unstructured info in your traditional Word canvas.
Note that PowerPoint and Excel also have the new InfoPath Document Information Properties but it is not nearly as integrated as Word.
I ran into this today while reading a new Engadget entry: Ask Engadget: What's the best gadget bag? - Engadget
Bad thing about giving into gadget lust? How to carry all those flipping gadgets around. No e-vest for me. Nor am I Batman with the utility belt from hell.
I ended up quite happy with an Eddie Bauer tote. It's very well designed. It's like a small courier bag. You can run your ear phones through a specifically designed duck logo and have two mesh pockets on the side ideal for slipping your phone or a bottle into. There's a big main pocket and a smaller pocket, ideal for big gadgets and little gadgets, along with a slip area in the big pocket.
I probably only utilize 50% of the bag.
I initially called it my Man Purse but have recently upgraded its name to my Man Pack.
I wasn't the quickest bunny to figure out all the yammering over RSS until I installed Radio and saw all these wonderful feeds coming onto my screen.
Now the buzz is over Attention and OPML. I'm back to being a bit of a dumb bunny trying to figure out why certain folks are so worked up about it. For a screencast about attention-engines, go to: Alex Barnett - attention engine screencast
From Alex's blog, I found the article The Attention Economy and the Net by Michael H. Goldhaber. Exactly the kind of read I was working for while sweating away on the elliptical. It's interesting and you can see some of this coming to be in the Blogosphere and how services are emerging to try to find the few rare gems in the blogs that are worth reading. Within a glut of information, what's relevant to you? And once people start paying attention to you, that's golden.
But I'm still a bit of a bunny scratching between the ears as I ramp up on the extremem passion over attention.xml and the OPML file. Usually, stuff like this seems so natural and organic (like HTML) that everyone says, "Of course!" and starts using it and benefitting from it. I'm not there yet.
But I'm paying attention.
Below is a comment I submitted for Bill Trippe's post:Gilbane Report Blog: Whither InfoPath?
Eric Richards from the InfoPath dev team here to give you my own personal perspective. I respect the points you make.
Now then, Microsoft Office is not retreating from InfoPath at all - if you read the Sinofsky keynote from
PDC06 PDC05 you get an idea of how integrated InfoPath technology is within the upcoming Office release. My team in particular has been responsible for the hard work of making the InfoPath editor hostable in Word, Excel, and PowerPoint, along with being a hostable ActiveX control. Plus we've made the designer hostable inside of Visual Studio, and have integrated VSTA into the design experience for those who want to write managed biz logic but don't have Visual Studio.
Also, consider the investment we've made in the new forms server that renders InfoPath forms within IE or Firefox (hot!). Read more on Tudor Toma's blog entry on the server features.
As for the quiet... I don't have any excuse. Just note that we're busting our collective butt to write these features and now, especially, stabilize them and ensure all the gears mesh together beautifully.
I personally have some bandwidth to start blogging again, including about InfoPath, and I imagine once the public beta comes out other team members will step up their desire to share all the cool features they have designed, implemented, and stabilized.
So, I can only try to spin this as the quiet before the storm of InfoPath goodness, and I personally look forward to sharing more as we ship the public Beta and the final release. If there are particular aspects of InfoPath you'd like to hear us talk about more, please post about it.
Updated: link text said PDC06 when I meant PDC05. That check writing algorithm to transform all 2005 references to 2006 must have kicked in...
Updated: trying a ping.
InfoPath Super-PM Ned Friend has a post up regarding the upcoming InfoPath integration with Visual Studio Tools for Applications (VSTA):Visual Studio Tools for Applications : Microsoft Office InfoPath 2007 Beta integration with VSTA
The integration here includes passing on whether you're designing a rich client form or a form for the rich and the reach (web) environment, meaning that we ensure Intellisense only shows you the OM that you should be using (some client OM doesn't make sense when you're writing managed business logic for the server).
And if you're really interested in writing business logic for the reach forms (those rendered in IE and Firefox), you'll be writing against the new managed OM (sorry, no script business logic on the server).
Craig Pringle has gone through the hard effort to create a screencast video of InfoPath's inking feature: Blog:: Craig Pringle - Ink in Infopath Screencast. Thanks, Craig!
I was fortunate to have this work on my InfoPath dev team as one of the many features we added to InfoPath 2003 SP1. As Craig showed, you can just start inking ontop of your InfoPath form and InfoPath will convert your ink into text.
Based on where you start inking we determine what control the ink should go into. Also, note you don't have to limit your inking just to the region of the control! :-)
If you pause your inking, we'll just kick in and convert it. If you'd like a quicker convert, you can customize this pause time under Tools->Options->Ink.
For InfoPath 2003 SP1, we do some basic from field data type detection regarding if this form's design has a field as a number or a date or such and pass that on to the ink conversion code as a hint for better recognition.
For the next version of Office, we've exposed to the form designer the standard input-scopes for use in recognition (e.g., IS_EMAIL_SMTPADDRESS) along with allowing you to drop into a custom recognition input scope, based on phrase list or regular expression. Better reco is better.
Also adding in InfoPath 2003 SP1 around ink that you can use everyday right now:
But as Craig shows, just plain inking ontop of the form is one of the more rewarding features we were able to ship.
Bonus tip: one of the gestures we support is scratch-out! So, if you want to clear content, just scratch out right on top of it!
Something I saw on Engadget a while back: SanDisk Products MP3 Players SanDisk Sansa e200 Series MP3 Players.
I am so looking forward to trying this out. I've been wanting a non-hard-disk MP3 player with FM tuning so that I can work out at the Pro-Club or such without worrying about the bouncing around damaging it.
I currently have a Creative Zen Micro. It has two big problems that prevent me from using it more:
(1) Awful touch-senstive controls. I'm constantly being "off-by-one" when selecting something and having to back up and try again, oops, overshot, back-up, try again.
(2) Creative Zen specific software required to sync to it. Dumb. I use lots of computers. I might download a podcast at work and want to listen to it on the way home. Well, I could lay down the Creative Zen software on ever laptop and computer I use, but I don't want to do that. I just want to plug it in and drop files onto it.
I used an ipod nano in the Apple store shortly after it came out. It just worked. I figured out the controls naturally and was able to bounce around and easily do whatever I wanted with it.
But all my music is WMA and it's staying that way. So no ipod for me. I can only hope that the Sansa e200 is similar enough that I can be happy with using it.
(Files to download noted at the end of this post.)
A while back, I was once again extolling to my team the virtues of blogs as a place to keep track of emerging technical and business trends. Oh, all the useful stuff that shows up on http://blogs.msdn.com/ ! Oh, the analysts giving their competitive insights into what Microsoft is and is not doing.
As a way to jump start people, I wanted to share my blog list. The easiest way to do that is to create an OPML file and send it out. I happen to have moved from NewsGator to Bloglines (thanks to OPML) and I decided I would export my current Bloglines subscriptions and send that file out so that people could import it into their newsreader of choice (even http://live.com/ !) and see all the great stuff I scan during the day.
But... I really didn't want to share the fact that I subscribe to Cute Overload. It provides the occasional "aw!" moment during the day that puts a smile on my face, but it's not something the old bearded manager geek should necessarily broadcast in their OPML attachment. So I wanted to edit my file before sending it out. I loaded the OPML XML up in notepad. Oh, no, it's all one big compressed stream of angelized XML. Damn, I thought. Now I have to go and find an XML pretty printer so that I can be sure I can read the whole thing and make sure that Cute Overload and Luann and Rose is Rose are all properly removed.
But wait. I need to edit XML. Hey... I happen to be on a team that makes an XML editor. How about if I try using my own product to whip up a quick form to edit my OPML?
So, here's what I did to quickly edit my OPML file with InfoPath. It was quick for me since I know the product reasonably well. If you have InfoPath installed and readily available, get used to it so that when you find yourself having to deal with XML just dying to be edited you can quickly whip up your own InfoPath form template and start jamming with it.
Create the InfoPath form: I started up InfoPath, told it I was designing a new form and that I was using my downloaded OPML file as an example of the XML. Look over at the data-source: that's the schema structure that InfoPath has inferred. Oh, how InfoPath eats XML for breakfast!
Create the layout: well, here's what you might be tempted to do: drag the opml root of the tree over and release and choose section with controls. Hey, that looks good! Well, not column lined up kind of good, but there are nicely named labels and text boxes for all of the controls. But, there's a problem if you just leave it with this: you don't get the recursive nature of the outline node.
In the data source task pane, expand the outline node. Notice that outline includes outline. We need to make sure that InfoPath generates the correct structure here and right now, it's only good for the first level of the schema (which, when you're designing something meant to be an outliner, doesn't get you too far). So, do the following:
Now, at this point, you are at a very basic, functional, OPML editor. It's not pretty. Things are not all lined up. But, you can now edit that OPML so that people don't know you like looking at little bunnies and ferrets and puppies.
Publish the form: in order to use the form template, you actually have to get it out of the designer and into a file that anyone can open. Choose File -> Publish and the publish wizard pops up. We're just going to publish this to c:\infopath\edit-opml.xsn, so choose the first option to publish to your computer, enter c:\infopath\edit-opml.xsn as the destination (of course, creating c:\infopath\ if you have to), and hit Next. Unless you're sharing this with people, just Next through the next screen and hit Finish. Now you have a checkbox to check before you press Close: open this form from its current location. Now press Close.
Alright. You've got a new blank OPML form. That's fine and all. Save this XML to something like blank.xml. We need to do one last thing before we can edit your OPML in InfoPath.
Make it an InfoPath form: Open blank.xml up in Notepad. Notice those processing-instructions up on top, the ones that start with <? and end with ?> ? We need the two that have mso in the name. They look something like:
<?mso-infoPathSolution solutionVersion="126.96.36.199" productVersion="11.0.6357" PIVersion="188.8.131.52" href="file:///C:\InfoPath\edit-opml.xsn" name="urn:schemas-microsoft-com:office:infopath:Edit-my-OPML-:" ?>
Yeah, I know. Lovely. Well that's the secret sauce for making an XML file (a) an InfoPath file and (b) identify which InfoPath form is best suited for opening the XML up. Paste this into your OPML file after the XML declaration and save your OPML file - be sure it has an .xml extension.
Wait for it: double click on that file you just saved. It opens up in InfoPath ready to edit! Now you're cookin' with gas! Edit, add, use InfoPath edit-UI to your heart's content. Goodbye Cute Overload. My coworkers will have to find you themselves. Save and share.
XSD: Ideally, you would have designed off of a real XSD for OPML. Looking at the OPML spec site, I see there's a reference to a DTD but I don't see any XSD. I think, like RSS, OPML has been a bit flexible in what it allows. So even if you find an XSD, you might end up having it not like whatever OPML you try to validate against it.
So thank goodness that InfoPath can infer an XSD. Just be sure you have the biggest, meanest XML instance to start designing against.
Design: if I was going to share this or use this solution over and over again, I would go back and spend 15 minutes in the designer making it look better. I like labels and controls to line up, so I would go under the auto-generated control and insert a two-column layout table, dragging the label into the first column and the control into the second, making sure the control was as wide as possible. See below for my 15 minute clean-up results.
Publish to share: if you want to share this with more people, publish it to a public area. A SharePoint site. Maybe a network share. Or a web server. Just realize that that the processing-instruction secret sauce is based on where you published it.
Additional views: if I was editing a bunch of OPML and then wanted to paste them into a blog-roll like web page part, I'd create a second view of non-editable output and use that to paste. But really the best answer here is just an XSLT you can apply to the final OPML.
Files you can download:
Updated: see if I can manage to get Technorati tags to actually work...
This is a really good read:
Philo shows how to start with InfoPath to design your schema for your form and then create a web service for consuming that exact schema. On the server end, you can do whatever you want to get it saved / act on it / etc etc.
Here's the important realization: do not design your schema in a vacuum. Start with designing your schema for the technology and the enivronment that it needs to work within.
XSD is... well, awful. It did not grow organically out of smart people solving a problem. It is the worse that committee design has to offer. As such, you can design some pretty broken constructs in XSD. Sure, sure, it's valid and legal.
But just try to get modern tools to accept it.
You need to work backwards according to what your tools and environment can effectively deal with. InfoPath is pretty powerful when it comes to schema, but it doesn't support everything. xsd.exe doesn't support everything. Look at the tools and find the relevant intersection and go from there.
And put in the occasional prayer that something better than XSD will one day ascend out of this noise...
Non-technical stuff going on with EricRi in the Northwest.
Lots More About Eric.
Disclaimer: The postings (and comments) here represent personal point of views and in no way represent the point of view or official opinions of my employer (Microsoft Corporation). The postings here are provided "AS IS" with no warranties, and confers no rights. And if you're reading this blog, you're not only incredibly discerning, you're also knee-weakening good looking.
More blogs about Eric Richards.