People have been asking again about the PocketBuilder roadmap and its state...

(a) PocketBuilder 2.0.4 - EBF #5 is wending its way through all the paperwork to be released onto the download site.

(b) PocketBuilder 2.1 -
a major update (but not requiring a migration) will soon be looking for some beta testers.  I was hoping to start the beta program right after Easter, but PB-11 and UL-10 kept sucking time away from PocketBuilder-centric activities.

• Official Windows Mobile 6 support
• LOADS of SCC updates (beyond what PB-11 has)
• more IDE usability enhancements that did not make it into PB-11 (on top of essentially all the updates that were put into PB-11 - in fact - most of the IDE enhancements were put into PocketBuilder first...)
• SA-10 support and MobiLink-10 and (hopefully) UL-10 support
• Full support for the "standalone ARM emulators" (and dropping the X86 emulators)
• making the "timing" object work on the PocketPC (one of those little things that irritated me)
• the "notification broker" example and the enhanced "network available" example.

(c) PocketBuilder 3.0 - (I can't say the planned date)
This leverage the .NET 2.0 "Compact Framework" (CF) enhancements that FINALLY contain SOME managed to native interoperability (IOW - using .NET from PK).
This enables us to deliver the overall theme of PK3 - "Enterprise Messaging" (and more).
The "enterprise messaging" theme is the next step in the "occasionally connected, always available" mantra.
Your application can send/receive MQ messages with all the guaranteed delivery that the infrastructure provides.
We are also considering supporting ALL the DataWindow styles from PowerBuilder.  With the advent of VGA devices and more memory, we can give this another think.
We are also considering the tabbed output window in PocketBuilder.  I'm still on the fence about this because in our world this is really only handy for keeping searches around...

Of course, we are planning some other goodies since the .NET 2.0 CF has a semblance of interoperability on the PocketPC platform, but I don't really want to go into details until we have figured it all out (but since many of you know that I put in the ability to show .NET assemblies in the PB-11 system tree, well, you can see where my mind is headed (and yes, IntelliSense works for those .NET assemblies)).