401
社区成员
发帖
与我相关
我的任务
分享powerbuilder9.0 新功能！
新功能有：
1、可以将datawindow report save sa xml data
2、提供jsp的快速开发
3、支持手持机设备软件的开发，包括wince,palm，但是 重点是wince
4、强大的Powerscript++，ejb,weblogic,webphere.....等等
5、提供了一种使用外部对象的机制，可以用C＋＋写一个类然后在pb中调用
6、移动服务器......
PB9.0推出后，可能出现：easever应用越来越广，基于xml开发的某些开发人员（such as vb,vb.net）可能被pb开发人员挤出去,因为pb9.0开发xml将会很简单，而且最重要的是可以将pb强大的datawindow 数据 -----xml，在电子商务、网络数据传输上将会有大的发展
j2ee技术继续前进
pb开发人员薪水大幅增加
个人观点！欢迎指正！
1、可以将datawindow report save sa xml data
2、提供jsp的快速开发
3、支持手持机设备软件的开发，包括wince,palm，但是 重点是wince
4、强大的Powerscript++，ejb,weblogic,webphere.....等等
5、提供了一种使用外部对象的机制，可以用C＋＋写一个类然后在pb中调用
6、移动服务器......
PB9.0推出后，可能出现：easever应用越来越广，基于xml开发的某些开发人员（such as vb,vb.net）可能被pb开发人员挤出去,因为pb9.0开发xml将会很简单，而且最重要的是可以将pb强大的datawindow 数据 -----xml，在电子商务、网络数据传输上将会有大的发展
j2ee技术继续前进
pb开发人员薪水大幅增加
个人观点！欢迎指正！
...全文
请发表友善的回复…
发表回复
RechardXc 2002-03-04
- 打赏
- 举报
感觉我们这些PB开发人员将来可以挺挺腰杆了,免的那些用delphi的人总是狂扁pb
llitcwl 2002-03-04
- 打赏
- 举报
也就是支持回调函数接口？那可方便多了，可以偿试用PB多做一些事了....
Hanson_bati_zhu 2002-03-04
- 打赏
- 举报
The PowerBuilder VM automatically passes an interface pointer to the PowerScript++ class so that its methods can call back into PowerBuilder. This lets the PowerScript++ methods invoke a PowerScript function or trigger an event. Callback functions can be implemented in PowerScript.
拭目以待
8－）
拭目以待
8－）
llww 2002-03-04
- 打赏
- 举报
哪里可以DOWN
llww 2002-03-04
- 打赏
- 举报
PB9现在是开发阶段 ， 还是已经投入市场了。
abcn 2002-03-04
- 打赏
- 举报
又有新的出来了，学呀，马不停蹄!!新版本如能在界面设计上改进一点就好了
am2000 2002-03-04
- 打赏
- 举报
With PowerBuilder 8.0 off and running, Sybase is developing the next version—PowerBuilder 9.0 (PB 9.0)—which will extend PowerBuilder's capabilities and add new functions to provide a more open development environment. PB9 will contain a solid code base, many new productivity-enhancing features, and further integration with Web and n-tier development. The release features more than 50 productivity improvements, including new workspaces and targets, a system tree, clip and output windows, Java-style exception handling, a source editor, and a redesigned source control.
It also provides tighter integration with Sybase Enterprise Application Server (EAServer), with the ability to call Enterprise JavaBeans (EJBs) within EAServer and to implement existing component interfaces into it. More-robust Web development capabilities, such as generic Web Targets and autogeneration of template code, are also available. At Sybase's annual user conference in August, Sybase vice president and general manager of the Enterprise Solutions Division, Dr. Raj Nathan, promised renewed commitment to PB. The road map for PB includes a 9.0 release in 2002 and a 9.x release in 2003.
Among PB 9.0's major new initiatives are:
Saving DataWindow report data as Extensible Markup Language (XML) data. Users will be able to select data values from a DataWindow and save as them XML according to a user-defined XML Export Template. A new Save-As Template view allows users to either graphically define a new XML export template from scratch, generate a default template from the DataWindow definition, or import an existing XML schema to help format the XML output.
An XML Export Template consists of element and attribute names that are fully customizable. They will be mapped to specific DataWindow columns, computed fields, and other data values. Expressions and formatting can be applied to the data values in order to produce XML data values that differ from the display format on the printed report.
Each XML Export Template will be saved by name, and users can create multiple XML Export Templates for each DataWindow. A new Save-As XML configuration property lets users choose which XML template to apply at runtime, thereby allowing a single DataWindow to generate several XML data files, each with a unique customized format. Similarly, new ImportFile Templates can be defined to import data from XML documents into a DataWindow. Again, the XML element and attribute names will be mapped to specific DataWindow columns and computed fields.
JavaServer Pages. JavaServer Page (JSP) development is one of the key new features scheduled for PB 9.0. This new feature will give users a rapid application development (RAD) environment for JSP development yet will allow full configuration flexibility for advanced users.
PB JSP will employ wizards to help users quickly develop a skeleton for a JSP Web application. Wizards will guide the creation of a JSP Web application target and the building of skeleton JSP pages.
Because JSP pages are an extension of a common HTML page, editing JSP pages is much like editing HTML Web pages in the existing PB Web Target page view. PB 8.0 Web Target allows for WYSIWYG editing to build an HTML page. It also has capabilities for adding ActiveX controls and scripts to a Web page. PB JSP will build on the existing Web Target implementation to allow creation and editing of JSP pages in the familiar environment of HTML pages.
PB 8.0 Web Target support has a powerful object model that handles the complexities of data transfer, HTML generation, and JavaScript generation for server-side scripts. The PB 9.0 JSP object model will include the capabilities of the PB 8.0 object model and some additional features for JSP development.
When it comes to deploying a JSP Web application, there are two JSP server target choices in PB 9.0: EAServer 4.0 and the Apache Foundation's Tomcat Server. JSP development in PB and support for Tomcat Server demonstrate Sybase's continuing commitment to open platform support. Other servers may also be supported.
PowerBuilder Applications targeted for handheld devices. PB desktop applications will be deployable to various handheld devices. In particular, support will be provided for devices using the WinCE operating system and the Palm Computing operating system, with an emphasis first on WinCE.
Changes to the desktop PB Integrated Development Environment (IDE) will allow deployment to one of a list of handheld target devices. The Project Painter is the logical place to make these changes; this is where a developer specifies the parameters required to build an application from the associated PB objects. When a handheld target device is selected, the application will check for unsupported functionality and issue appropriate warnings, allowing the developer to alter the offending items or ignore them if it's reasonable to do so.
The requested PB application will then be converted to run on the target handheld device. Both DataWindow retrieval and update will be supported for handheld databases. PowerScript++ PowerScript++ classes are C++ DLLs that will vastly extend the functionality of PB. They may be developed by Sybase, by third parties, or by users. Using a Register function, the PowerScript++ class declares its methods and events to the PB virtual machine. Once registered, the class can be used just like a normal PowerBuilder object. The PowerScript++ class may take the form of a nonvisual user object, a visual user object, or a window. Nonvisual PowerScript++ classes are instantiated with the Create statement. You instantiate visual controls by opening a window containing the control. PowerScript++ windows would be instantiated with the Open statement.
The PowerBuilder VM automatically passes an interface pointer to the PowerScript++ class so that its methods can call back into PowerBuilder. This lets the PowerScript++ methods invoke a PowerScript function or trigger an event. Callback functions can be implemented in PowerScript.
PowerScript++ provides an excellent way to create reusable components such as an XML parser.
Provide bridge technology and detailed samples that illustrate how to invoke EJBs in third-party application servers. Today, a Java component deployed in EAServer can act as a proxy to allow PB applications to access business logic developed in EJBs and deployed on a third-party J2EE application server.
Sybase has developed a fully automated utility to code-generate these proxy components for higher productivity. This solution is code-named EAServer Integrators (or "EASi").
In its initial release, EASi allows PB to act as a client to BEA WebLogic, IBM WebSphere, or any J2EE-certified application server via a proxy stateless session Bean generated and deployed in EAServer. In a future release, pending demand, it could be extended to generate a "reverse proxy" in which PB components would be wrapped by a proxy that could be called via SOAP from another application server.
It also provides tighter integration with Sybase Enterprise Application Server (EAServer), with the ability to call Enterprise JavaBeans (EJBs) within EAServer and to implement existing component interfaces into it. More-robust Web development capabilities, such as generic Web Targets and autogeneration of template code, are also available. At Sybase's annual user conference in August, Sybase vice president and general manager of the Enterprise Solutions Division, Dr. Raj Nathan, promised renewed commitment to PB. The road map for PB includes a 9.0 release in 2002 and a 9.x release in 2003.
Among PB 9.0's major new initiatives are:
Saving DataWindow report data as Extensible Markup Language (XML) data. Users will be able to select data values from a DataWindow and save as them XML according to a user-defined XML Export Template. A new Save-As Template view allows users to either graphically define a new XML export template from scratch, generate a default template from the DataWindow definition, or import an existing XML schema to help format the XML output.
An XML Export Template consists of element and attribute names that are fully customizable. They will be mapped to specific DataWindow columns, computed fields, and other data values. Expressions and formatting can be applied to the data values in order to produce XML data values that differ from the display format on the printed report.
Each XML Export Template will be saved by name, and users can create multiple XML Export Templates for each DataWindow. A new Save-As XML configuration property lets users choose which XML template to apply at runtime, thereby allowing a single DataWindow to generate several XML data files, each with a unique customized format. Similarly, new ImportFile Templates can be defined to import data from XML documents into a DataWindow. Again, the XML element and attribute names will be mapped to specific DataWindow columns and computed fields.
JavaServer Pages. JavaServer Page (JSP) development is one of the key new features scheduled for PB 9.0. This new feature will give users a rapid application development (RAD) environment for JSP development yet will allow full configuration flexibility for advanced users.
PB JSP will employ wizards to help users quickly develop a skeleton for a JSP Web application. Wizards will guide the creation of a JSP Web application target and the building of skeleton JSP pages.
Because JSP pages are an extension of a common HTML page, editing JSP pages is much like editing HTML Web pages in the existing PB Web Target page view. PB 8.0 Web Target allows for WYSIWYG editing to build an HTML page. It also has capabilities for adding ActiveX controls and scripts to a Web page. PB JSP will build on the existing Web Target implementation to allow creation and editing of JSP pages in the familiar environment of HTML pages.
PB 8.0 Web Target support has a powerful object model that handles the complexities of data transfer, HTML generation, and JavaScript generation for server-side scripts. The PB 9.0 JSP object model will include the capabilities of the PB 8.0 object model and some additional features for JSP development.
When it comes to deploying a JSP Web application, there are two JSP server target choices in PB 9.0: EAServer 4.0 and the Apache Foundation's Tomcat Server. JSP development in PB and support for Tomcat Server demonstrate Sybase's continuing commitment to open platform support. Other servers may also be supported.
PowerBuilder Applications targeted for handheld devices. PB desktop applications will be deployable to various handheld devices. In particular, support will be provided for devices using the WinCE operating system and the Palm Computing operating system, with an emphasis first on WinCE.
Changes to the desktop PB Integrated Development Environment (IDE) will allow deployment to one of a list of handheld target devices. The Project Painter is the logical place to make these changes; this is where a developer specifies the parameters required to build an application from the associated PB objects. When a handheld target device is selected, the application will check for unsupported functionality and issue appropriate warnings, allowing the developer to alter the offending items or ignore them if it's reasonable to do so.
The requested PB application will then be converted to run on the target handheld device. Both DataWindow retrieval and update will be supported for handheld databases. PowerScript++ PowerScript++ classes are C++ DLLs that will vastly extend the functionality of PB. They may be developed by Sybase, by third parties, or by users. Using a Register function, the PowerScript++ class declares its methods and events to the PB virtual machine. Once registered, the class can be used just like a normal PowerBuilder object. The PowerScript++ class may take the form of a nonvisual user object, a visual user object, or a window. Nonvisual PowerScript++ classes are instantiated with the Create statement. You instantiate visual controls by opening a window containing the control. PowerScript++ windows would be instantiated with the Open statement.
The PowerBuilder VM automatically passes an interface pointer to the PowerScript++ class so that its methods can call back into PowerBuilder. This lets the PowerScript++ methods invoke a PowerScript function or trigger an event. Callback functions can be implemented in PowerScript.
PowerScript++ provides an excellent way to create reusable components such as an XML parser.
Provide bridge technology and detailed samples that illustrate how to invoke EJBs in third-party application servers. Today, a Java component deployed in EAServer can act as a proxy to allow PB applications to access business logic developed in EJBs and deployed on a third-party J2EE application server.
Sybase has developed a fully automated utility to code-generate these proxy components for higher productivity. This solution is code-named EAServer Integrators (or "EASi").
In its initial release, EASi allows PB to act as a client to BEA WebLogic, IBM WebSphere, or any J2EE-certified application server via a proxy stateless session Bean generated and deployed in EAServer. In a future release, pending demand, it could be extended to generate a "reverse proxy" in which PB components would be wrapped by a proxy that could be called via SOAP from another application server.
kalven_chan 2002-03-04
- 打赏
- 举报
老是去学习那种不是很熟悉的语言，多累
iamxia 2002-03-04
- 打赏
- 举报
哇~~~~~~~~~~~~~~
一个月没上网，落伍了 ：（
一个月没上网，落伍了 ：（
