1. Gzim Ramizi
  2. PowerServer
  3. Wednesday, 26 June 2024 06:49 AM UTC

Hi all

what really happens in the background and what is true? i have queried two current AI engines and get different answers. Does it depend on whether you are making a new application or deploying an existing one?

 

We are using PB/PS 2022 R3. 

 

Our input to the AI engine:

When I convert a power builder application to Power Server, the DataWindows still look exaxtly the same way as before. Are they really rendered with HTML, CSS, and JavaScript?

 

The output:

 

ChatGPT

When you convert a PowerBuilder application to PowerServer, the DataWindows do indeed maintain their original look and feel, which might give the impression that they haven't changed. However, they are actually being rendered using modern web technologies such as HTML, CSS, and JavaScript.

Here’s a brief explanation of how this works:

  1. DataWindow Conversion: During the conversion process, the DataWindows are transformed from their original PowerBuilder format to web-compatible formats. This means their definitions are converted into HTML for structure, CSS for styling, and JavaScript for functionality.
  2. Rendering: In the PowerServer environment, the converted DataWindows are rendered by the browser using these web technologies. This is why they appear the same as in the original PowerBuilder application – the conversion process ensures that the appearance and behavior are preserved.
  3. JavaScript Libraries: PowerServer uses specific JavaScript libraries that replicate the behavior of PowerBuilder DataWindows. These libraries handle the interactions, data binding, and other functionalities, ensuring a seamless user experience.
  4. Styling and Layout: The CSS ensures that the styling and layout of the DataWindows are consistent with what you had in PowerBuilder. This includes fonts, colors, alignments, and other visual aspects.
  5. Interactivity: JavaScript is used to handle the interactive elements of the DataWindows, such as data manipulation, event handling, and other dynamic behaviors.

The conversion process is designed to be as transparent as possible to the end user, so while the underlying technology changes, the user interface remains consistent. This approach minimizes the learning curve and ensures a smooth transition from a desktop application to a web application.

In summary, yes, the DataWindows are indeed rendered using HTML, CSS, and JavaScript after the conversion to PowerServer, even though they retain the same appearance and functionality as in the original PowerBuilder application.

Google Gemini

No, while Power Server offers some improvements over PowerBuilder for web applications, DataWindows in Power Server are not rendered with HTML, CSS, and JavaScript.

Thank you in advance for your comments.

 

Here's a breakdown of how DataWindows work in both environments:

  • PowerBuilder: DataWindows are native controls within the PowerBuilder application. They are rendered using the application's own graphics engine and don't rely on web technologies.
  • Power Server: While Power Server can create web applications, DataWindows here still maintain their native rendering approach. They are not converted into HTML, CSS, and JavaScript for display in a web browser.

However, Power Server offers some advantages for DataWindow presentation in web applications:

  • Data Window Web ActiveX control: Power Server can leverage the Data Window Web ActiveX control to present DataWindows within a web page. This control acts as a bridge between the server-side Power Server application and the client-side web browser.
  • Enhanced data access: Power Server can improve data access for DataWindows in web applications by providing connectivity to various data sources.

If you're specifically looking to achieve web-based rendering with HTML, CSS, and JavaScript for your DataWindows, you might need to explore alternative solutions beyond Power Server. Some options include:

  • Third-party reporting tools: Several third-party tools can generate HTML, CSS, and JavaScript output from your DataWindow designs.
  • Custom development: You could develop a custom solution that translates DataWindow definitions into web-compatible formats.

For a more in-depth comparison of PowerBuilder and Power Server for web development, consider searching for resources on "[PowerBuilder vs PowerServer web development]"


Responses (4)
  1. Likes
  2. Latest
  3. Oldest
Loading...

Find Questions by Tag

.EXE .NET 6.0 .NET Assembly .NET Core 3.1 .NET Core Framework .NET DataStore .NET Std Framework 32-bit 64-bit ADO.NET AEM AI Algorithm Amazon AWS Android Apache API APK App Store App Store (Apple) Appeon Workspace Appeon Xcelerator Plug-in Architecture Array ASE Asynchronous Methods Authentication AutoBuild AutoCompiler Automated Testing Automation AutoScript Azure Barcode Base64 Batch BigData BLOB Branch & Merge Browser Bug Build Button C# C# Class Importer C# Editor C# Model generator Calendar Camera Certificate Chrome Citrix Class Client Client/Server Cloud Cluster Collection COM Command Line Compiler Compression Computed Field Configuration Controls Cookies Cordova Crash Cross-Platform Crosstab CSharpAssembly CSharpObject CSS CSV Cursor Data Database Database Driver Database Painter Database Profile Database Provider DataObject DataSource DataStore DataStore (C#) DataStore (PS) DataType DataWindow DATE DATETIME DB2 Debug Debugger Debugging Deployment Design DLL DO-WHILE Dockable Docker Documentation DOUBLE Download DragDrop Edge Edit Style Editor Elevate Conference Email Embedded SQL Emulator Encoding Encryption Enhancement Request Entity Entity Framework ERP Error Event Event Handler Event Handling Excel Exception Export Expression External Functions F# Field File File Access Filter Firefox Firewall Font FOR-NEXT Foreground Format Function Garbage Collection GeoLocation Git Graph HANA Hash Header HTML/5 HTTP/S HTTPClient Icon IDE Identity IIS IMAPI Import InfoMaker Inheritance Installation Integer IntelliSense Interface Internet Internet Explorer iOS IPA iPad iPhone IWA J# Java JavaScript JBoss JDBC JOIN JSON JSONGenerator JSONParser Kestrel Label Lambda Large File LDAP Library License LINQ Linux OS Load Balancing Localization Localized PBVM Log In Log Out Logging LONG LONGLONG macOS MAPI Maps MDI Memory Memory Leak Menu Merge MessageBox Messagging Method Migration MIME TYPE Mobile Model ModelStore ModelStore (C#) MSOLEDBSQL Multi Threading MVC MySQL n-Tier Namespace NativePDF NVO OAuth ODATA ODBC Office Offline OLE OLEDB Online Open Source OpenAPI OpenSSL Oracle OrcaScript Other Outlook Output Package Parameter Patch PayPal PB Classic PB Native PB.NET PBC PBD PBDOM PBG PBJVM PBL PBNI PBORCA PBVM PBX PDF Performance Permission PFC Picture Pipeline Play Store (Google) Plugin Popup Port POST PostgreSQL PowerBuilder PowerBuilder (Appeon) PowerBuilder (SAP) PowerBuilder Compiler PowerBuilder Runtime PowerClient PowerScript (PS) PowerScript IDE PowerScript Migrator PowerServer PowerServer Mobile PowerServer Toolkit PowerServer Web PowerServerLabel Print Properties Proxy Publish PULL PUSH Query Regression Release Renew Resize Response REST Retrieve RibbonBar RibbonBar Builder Rich Text Roadmap RPC Runtime Packager SaaS Scaffolding Script SDI SDK Security Server Service Session Single Sign-on Size SMTP SMTPClient SnapDevelop SOAP Sort Source Code Speech Recognition SQL SQL Anywhere SQL Server SqlBuilder SqlExecutor SQLite SqlModelMapper Storage Stored Procedure Subscription SVN Swagger Syntax TabbedBar TabbedView Tablet TabPage Target TE Control Testing Text TFS Theme TIME Timer TLS/SSL Tomcat TortoiseGit TortoiseSVN Transaction Transparency Trial Trigger TRY-CATCH TX Control Type UI ULONG UltraLite Uninstall Unit Test Unit Testing UNIX OS Update Upgrade Upload URL User Center User Object UWP Validation VARCHAR Variable Versioning Visual Studio Visual Studio Code VM Voice Warning WCF Web API Web Extensions Web Service WebBrowser WebForms WebLogic WebSphere WildFly WinAPI Window Windows OS WinForms Wizard Workgroup Workspace WPF XCODE XHTML XML Zoom

Helpful?

If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.