Длинно, посему по аглицки:

The following is in no particular order. Expectation is that this information can become quickly outdated, so take everything with a grain of salt (ie. not too seriously).
Coming Releases: At TechWave 2003, details were given about upcoming releases. PowerBuilder 10 (code name: Diamond) was announced with nervous predictions of first half of 2004 as the target time frame. Very specific details were given about the plans for PowerBuilder 11, so yawn whenever you hear that PowerBuilder 9 is the last release of PowerBuilder, and Sybase is giving up on it. Sybase announced that they are targeting a 12-18 month major release cycle, so you can make your own extrapolations about dates. (This is actually the time frame used before PowerBuilder 7, and the time frame relative to PowerBuilder 8 that PowerBuilder 9 came out in.) Feature details are listed below, in no particular order.
PowerBuilder and .NET: Some support for Microsoft’s .NET initiative already exists, like being able to deploy PowerBuilder components as web services on EAServer (PowerBuilder 7) http://www.sybase.com/products/applicationservers/easerver/webservices, and being able to consume web services and generate and use XML in datawindows and PowerScript (PowerBuilder 9).
Sybase has released a .NET strategy http://www.sybase.com/detail?id=1020722
Phase 1 is essentially what we got in PowerBuilder 9.
Phase 2 talks about “DataWindow.NET and DataStore.NET” as components for .NET languages.
Phase 3 is deploying non-visual objects to .NET servers.
Phase 4 talks vaguely about being able to pick environments and platforms, including Windows DNA and .NET framework
The press release suggests no time frame for any of the future phases.
Subsequent to this at TechWave 2003, engineers were demonstrating using both a datawindow and a datastore in Visual Studio .NET. These components will be available for all .NET languages. The concepts and nomenclature were very similar to what PowerBuilder developers are used to, but expect minor changes in syntax you have to write in order to accommodate the .NET paradigm. The time frame discussed was PowerBuilder 10, although they are not expecting the component to be only packaged with PowerBuilder.
PowerBuilder 10 will also be able to deploy web services directly to EAServer (without the intervention of server-side utilities). It will also contain a UDDI browser, to facilitate integration of web services.
They also described how in PowerBuilder 11, PowerBuilder applications would be able to import and use .NET classes within a PowerScript environment. This would make available all .NET classes that are built into Microsoft’s framework, as well as third party components built for .NET. They also described a more generic build engine, that would be able to, among other things, deploy to MSIL (ie. a .NET component or executable).
PowerBuilder and WinCE/PocketPC: The Pocket PowerBuilder product page <http://www.sybase.com/products/internetappdevttools/pocketpowerbuilder> lists Pocket PowerBuilder is generally available, and in fact is on sale at the Sybase eShop web site <http://eshop.sybase.com/eshop> for under half price for the month of August/2003. This will give you a separate IDE that can import much of your PowerBuilder application from standard PowerBuilder. A stored webcast <http://www.sybase.com/detail/1,6904,1024638,00.html> has a lot of information about Pocket PowerBuilder, as well as the Pocket PowerBuilder product page <http://www.sybase.com/products/internetappdevttools/pocketpowerbuilder>. As far as what is coming (or at least planned) in Pocket PowerBuilder:
Rhubarb (v1.0.1, August 2003)
Updated MobiLink wizard
SIP notification events
New EditMask code
XP-style IDE
Pumpkin (v1.2, 2003Q4)
PPC 2003 support
More native controls (ink, rich text, calendar, voice, today, mail)
Customizable application icons
Post-Pumpkin (both planned in Turnip, 2004H1, and wish lists)
COM support
More PowerBuilder native objects
More database drivers
PBNI
Native XScale compiling
Access to the native PPC object store
POOM (Pocket Outlook Object Model)
Smart phones
Native bar code reader control
Application icon on Start menu
PowerBuilder and Unicode: PowerBuilder had a separate Unicode product line, but that was discontinued at version 6.5. PowerBuilder 8.0.2 supplied Unicode database drivers for ASE, Oracle and ASA (see the PB802readme.txt, available both with the 8.0.2 patch and separately from the downloads section of the Sybase web site <http://www.sybase.com/downloads>), which converted to and from DBCS, which is what is used on the front end.
For those having Unicode needs that extend beyond the database (e.g. Unicode files), Sybase has announced full Unicode support in PowerBuilder 10. PBLs will require a format change to support Unicode. JSPs will support ANSI, UTF8 and UTF16. Expect all imports, exports, file reads and file writes to support both ANSI and Unicode. Of course, it will support both Unicode and non-Unicode DBMSes.
PowerBuilder and application servers: PowerBuilder 9 introduced the capability to access EJB and web services components on other non-EAServer application servers. Since TechWave 2002, it has been suggested that PBNI will be the foundation on which it will be possible to deploy PowerBuilder components to application servers that do not explicitly support the PowerBuilder virtual machine. One third party, Sunlly <http://www.sunlly.com>, is already working on a product to do that.
PowerBuilder 10 is expected to be able to deploy to several J2EE servers, based on this technology. In particular, PowerBuilder 10 should be able to deploy NVOs to Weblogic 6, Weblogic 7, Websphere 4 and Sun J2EE 1.3.1. An Server Plugin SDK will be published to be able to allow others to configure other types of application servers as deployment targets. These components will be able to participate in transaction management, be able to use database connections from the server’s connection cache and be able to leverage the server’s logging service. These components will not be constrained to the standard J2EE data types when communicating with a PowerBuilder client, as a marshaling layer will allow any data types (e.g. datastores, blobs) to be transferred between the client and the PowerBuilder components on these application servers.
PowerBuilder and the web: Beyond what has been discussed above for .NET and third party application servers, the big buzz is about Appeon <http://www.appeon.net> and their partnering with Sybase. They promise a tool that will migrate PowerBuilder Windows applications to thin-client applications that will preserve much of the functionality that Windows client developers have been loathed to lose. Appeon caused a big stir on the exhibitors floor at TechWave 2002, and this year.
At TechWave <http://techwave.sybase.com/TechWave/search.stm>, Sybase described the “next generation web datawindow,” that will use XHTML, client-side XML, client-side XSLT and a standalone CSS stylesheet with absolute positioning. This will allow new levels of functionality with potential for smaller downloads by separating data and presentation. This also off-loads processing from the server to the client, which should improve scalability. Nested and composite datawindows will be supported. This technology will be aimed only at newer browsers that support this functionality, namely starting at: Internet Explorer 6, Netscape 6 and Mozilla 1.
In addition, a TechWave 2003 keynote demonstrated very easy datawindow deployment to their Enterprise Portal product, with “click across” functionality that allowed data linkages and interactive master-detail designs.
PowerBuilder and PowerDesigner <http://www.sybase.com/products/enterprisemodeling/powerdesigner>: As of PowerDesigner 9.5.2, all classes (not just non-visual) can be reverse engineered into PowerDesigner. As a result, you can get a UML diagram of all your classes, and take advantage of templates and VBScript to generate, manipulate or report on attributes and scripts.
In PowerBuilder 10, you will be able to have PowerDesigner integrated entirely into the PowerBuilder IDE. With such, not only will you have a more powerful database design tool at your fingertips and a more visual XML design tool (that will be available in PowerDesigner 10, which is currently in beta), but you will be able to even more easily create your classes in PowerDesigner, taking advantage of templates and VBScript to initialize your object to much more than just an empty object (e.g. your custom comment header at the top of every script created, objects created with your custom attributes already set).
PowerBuilder and PowerScript: At TechWave 2003, Sybase presented their vision of what they call the “Next Generation PowerScript,” which they hope will make it a more general purpose language. Included in the list of features they wanted to add to the language were:
Packages
Interfaces
Parameterized constructors
User-defined enumerations
Bit-wise methods
New native data types, like
Hash tables
Lists
Regular expressions
Easier extensibility, both with C++ and PowerScript itself
Supporting classes from .NET and perhaps Java
In addition, they discussed a compiler that would produce an abstract syntax tree, which could then be processed by various modules. These modules could produce various binaries, like PCode, MSIL and Java byte-code. They could also process the tree and produce documentation like a javadoc style report, or a cross-reference.
The time frame for “Next Generation PowerScript” was to start at PowerBuilder 11, and would likely continue on beyond that.