Difference between revisions of "Why Native?"

From MidrangeWiki
Jump to: navigation, search
Line 5: Line 5:
  
  
 
+
==IBM i Native Virtual Machine Vs. Other Virtual Machines And Scripting Environments==
 
 
==Green Screen Emulation / Conversion / Open Access Options==
 
  
 
Tools that leverage existing green-screen interfaces and offer emulation or a quick migration path to browser user interfaces with little or no programming required.
 
Tools that leverage existing green-screen interfaces and offer emulation or a quick migration path to browser user interfaces with little or no programming required.

Revision as of 23:14, 21 July 2014


IBM i Native Virtual Machine Vs. Other Virtual Machines And Scripting Environments

Tools that leverage existing green-screen interfaces and offer emulation or a quick migration path to browser user interfaces with little or no programming required.


Comparison Attributes IBM i Native Virtual Machine Other Virtual Machines (ie. Java, .Net) Scripting Environments (PHP, Python, Perl, Ruby)
aXes LANSA aXes transforms RPG and COBOL 5250 programs into Rich Internet Applications accessible via multiple Web Browsers on multiple devices (including mobiles) — without having to change a single line of code. aXes runs in a standard Web browser without installing any software or ActiveX controls on the client device. All web apps are served off the IBM i, no Windows servers required. Commercial
PSC/400 Pluta Brothers Design Converts your screens into two standard UI types: green screen and gray screen. The green screen acts as a replacement for the standard 5250 display, and requires no HTML skills on your part and no retraining for your programmers or your end users. A simple conversion and you're on the web. If you then choose to deploy a more "web-like" appearance, your HTML developers can customize the generated gray screen in whatever way they see fit. Commercial


This article is a stub. You can help by editing it.