This conference is more in my line - both developer centric AND on Saturday/Sunday.
Yup - we don't miss any "real" work and this looks to be very developer centric with little marketeer / mousketeer fluff.

www.voicesthatmatter.com/iphone2009

Yes - I'll miss church that morning, but I'll be with fellow nerds and geeks!!!
(and since Saturday Shabbat is supposed to be a JOYOUS day - well - what is more joyous than an iPhone developer conference!  and.... I don't consider 'learning' to be melachah...)

The ultimate cell phone - the Pommegranate (click here).
Start with the projector and watch all the other features.  The projector technology seems like the micro-projector that MicroVision has come out with (their "pico projector").  (I want the coffee maker!)

Ths site also has a wonderful link for Nova Scotia, a wonderful place to go in the summer.

I have been approved to unveil my screen captures (using Adobe Captivate) for some of the new features in the PB.NET (a.k.a. PB12 WPF Workshop) system tree (now called "solution explorer").

The first two show some basic capability that I prefer over the PB-Classic approach...

Showing dragging source files around:  pb12_soln_source_drag_drop.zip
Showing creating folders and dragging files into the target for resources and documentation: pb12_solncopyresources.zip

Now that I'm doing more Apple iPhone development (in my non-existant spare time), the use of "multi touch" (the two finger pinch motion, and up to 5 fingers for any gesture) is wonderfully handy.  Hence the lack of any mention about "multi-touch" in the Microsoft docs for WM 6.5 was puzzling.  A comment in an Ars Technica blog shed some light on this:

As flexible as the hardware specs are in some ways, they're lacking in others. Chief among the deficits is the lack of support for capacitative touchscreens. All touch-enabled 6.5 devices will have resistive touchscreens. The upshot of this is that they will all also lack support for multitouch.

Source:
http://arstechnica.com/microsoft/news/2009/02/ballmer-windows-mobile-65-phones-are-just-windows-phones.ars

FINALLY
Was able to hide the XAML files in the system tree (Microsoft basically said 'exercise left for the student' and provided NO documentation).  These files provide the layout information for the window (or UO) and seeing this extra node in the system tree would be both confusing for the poor user AND was pointed out every week by the QA folks.

Of course, the visibility is selectable.  It will eventually end up as a Tools -> Options item.

Yes - I'm the poor soul implementing the system tree and the project system.  The project system keeps all the relationships between the workspaces, targets, pbls, and ultimately the objects.  I'll post a screen snap if I can get Sue to OK it...

I also want to post a screen snap of a DataWindow from PB3 migrated into PB12-WPF.  Yes - this is a PowerBuilder-3 SRD file that we migrated into PowerBuilder12-WPF - with no sweat.  Of course, that would show the new DataWindow painter too...